BSOD at Randomtimes, WDF1000.sys 0x1e when idle or under load.

One of yesterday's BSOD ....

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys

Probably caused by : sptd.sys ( sptd+46ae8 )

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall the program at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Also, USB related issues are there in all the three crash dumps. Remove the webcam, at least as a test. Observe if it is BSODing there in absence of the webcam or not.

Code:

fffff880`0378caa0 fffff880`048d7b0f USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff880`0378cb80 fffff880`048d566f USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`0378cbe0 fffff880`048c6f89 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`0378cc20 fffff880`010d6ae8 USBPORT!USBPORT_Xdpc_Worker+0x1d9

Let us know the situation after doing these two.

Well, then all the possible options those can be taken form the crash dumps are already taken. If you have communicated about those in your original post, it would have been a better idea.

Test for any failing driver in that case. 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

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Well done, as both the DV enabled crashes pointed the same thing out; and afterburner is really problem causer.

And, Your plan for the next is the right action. You know how to troubleshoot a computer.

Reading dumps is not really hard .... you can learn it easily if you want. The real thing is to decide the appropriate course of action among a lot of possible alternatives, which you can do for sure.

If you are interested about reading dumps, we have some nice resources in our forum .... Have a look at Debugging A BSOD - My way ....

Disable Driver Verifier.

Considering it as solved in that case.

If it starts to create problems again, unmark it and continue discussion :)