BSOD BCC 0x000000d1

Adroxis · 06 Jan 2016

Hello all,
I just got this BSOD yesterday, haven't had one in exactly 3 months and 1 day's time. The Bug Check String is " DRIVER_IRQL_NOT_LESS_OR_EQUAL" and BlueScreenView is telling me that it's some sort of kernal error with Windows 7. I haven't made any recent hardware changes other than my old ASUS USB DAC ended up dying and I went back to using my old headphone jack in the back of my computer. Also, I did a clean install of Windows 7 manually several months back when I was getting much more frequent BSOD's, following Brink's guide.

I posted the attachment for the SF Diagnostic Tool that I found here on the forums, because I wasn't able to track down the zip file that was being created for dm log collector so I used the Diagnostic Tool instead and followed Capt.Jack Sparrow's instructions.

Please let me know if you need any further information, I'd be happy to oblige. Thank you for your time.

Golden · 07 Jan 2016

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {669ca3cd, 2, 1, fffffa8008e69dc0}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

Followup: MachineOwner
---------

The .dmp file is inconclusive at this stage, but it has plenty of references to USBPORT.

Did the BSOD happen before, or after, you removed the ASUS USB DAC?

Adroxis · 09 Jan 2016

The BSOD happened after I removed the DAC, maybe 2-3 weeks if I had to guess.

Golden · 09 Jan 2016

Please do the following:

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

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
System Restore Point - Create

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
Safe Mode

essenbe · 12 Jan 2016

Adroxis, have you been able to run Driver Verifier? If you have Please upload the BSOD Posting Instructions https://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html. Upload the files here, this will tell you how. https://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Adroxis · 20 Jan 2016

Sorry, I got distracted this week and wasn't able to work on the driver verifier. I'll begin testing with it tonight and let you know in a day or 2 what I come up with, the SF Diagnostic Tool still works for uploading logs of the crash, right? I was having problems the last time figuring out where the dmp files were going with DM Log collector.

Adroxis · 20 Jan 2016

Okay, I ran the Driver Verifier and immediately after rebooting my computer, 2 different BSOD's occurred, 1 for each of the 2 attempts that I tried to reboot my computer. So, I booted my system into safe mode and disabled driver verifier because it won't work in safe mode from what I've read in the forums.

Here is the zip file recording what happened.

Golden · 21 Jan 2016

Please attach the. Zip file

Adroxis · 21 Jan 2016

All right, both zip files should be there now.

Golden · 21 Jan 2016

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck D3, {fffff8800108b2b9, 2, 0, fffff80002ca6b52}

*** WARNING: Unable to verify timestamp for WRkrn.sys
*** ERROR: Module load completed but symbols could not be loaded for WRkrn.sys
Probably caused by : WRkrn.sys ( WRkrn+4043 )

Followup: MachineOwner
---------

Uninstall WebRoot security and replace it with MSE for testing. Reboot and run Driver Verifier again please.