Memory corruption + race condition bug hides when running Driver Verifier

NTDEV
1

Hello all,

I’ve got a stubborn bug that manifests itself with
various different bugchecks: IRQL_NOT_LESS_OR_EQUAL,
DRIVER_CORRUPTED_EXPOOL, BAD_POOL_HEADER, BAD_POOL_CALLER, et cetera.
My first reaction was to run Driver Verifier with Special Pool and Pool
Tracking, but I am not able to reproduce this bug at all with Driver
Verifier running, regardless of the verification level, leaving me
completely baffled on how to fix it. I am able to consistently
replicate the bug when the verifier isn’t running.

Any ideas on how to tackle this?

  • dpj
2

Hi David

Kindly share the !analyze -v output.

Thanks

  • Anuj
3

Hi Anuj,

Thank you for offering help, but I was hoping to get some general tips and strategies on dealing with these types of problems where tools normally recommended cannot be used.