BSOD imaged PCs, random times, wdf01000.sys crash.

MichaelBassett · 27 May 2014

BSOD on imaged PC that happens at random times. BSOD says wdf01000.sys is the fault, DRIVER_IRQ_LESS_OR_EQUAL at the top of the screen. 0x000000D1

EDIT: Image from HP8200 to HP800 using SBER restore to anywhere, did my own driver installs. 5 PCs affected, all the model and hardware, brand new.

Thedoctor44 · 27 May 2014

BSOD imaged PCs, random times, wdf01000.sys crash.

Your Intel Management Engine Interface driver is causing issues.

Code:

Unable to load image TeeDriverx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for TeeDriverx64.sys
*** ERROR: Module load completed but symbols could not be loaded for TeeDriverx64.sys
 TeeDriverx64+0x151c8

Code:

0: kd> lmvm teedriverx64
start             end                 module name
fffff880`050d6000 fffff880`050f3000   TeeDriverx64 T (no symbols)           
    Loaded symbol image file: TeeDriverx64.sys
    Image path: TeeDriverx64.sys
    Image name: TeeDriverx64.sys
    Timestamp:        Mon Jun 10 22:37:50 2013 (51B6472E)
    CheckSum:         0001C525
    ImageSize:        0001D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it here.

I would also enable Driver Verifier is this doesn't help.

Enable driver verifier but only enable the options: Standard settings and IRP logging step 3.
Don't enable Force Pending I/O Requests

Enable Driver Verifier to monitor the drivers.
Driver Verifier -Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

We use Driver Verifier as it puts a stress on the drivers, and so it makes the unstable drivers crash. This should flag the driver responsible in the dump file.
It

Driver Verifier will make the system laggy, this is normal so don't worry.

Before enabling DV, make sure that you have earlier System restore points made in your computer.

If there are no points, make a System Restore Point Manually

Post back the results.