Random, Infrequent BSOD

[NMania]

I have been having seemingly random blue screens for the past several months. Once one happens, I generally do not see another for at least a few days. It does not seem to be linked to stress on the system as I have had them occur both while the system is practically idle (browsing in chrome), as well as during resource intensive games.

I've monitored my temperatures during normal use as well as during stress testing with Prime95/FurMark and they are well within normal ranges so I don't believe that to be a cause. I've tried everything I can think of - from updating drivers to reseating the hardware - and at this point I don't know what else to do. I have attached the zip file as listed in the posting instructions.

Thanks in advance for any help given!

 

[Golden]

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

Use !analyze -v to get detailed debugging information.

BugCheck [B][COLOR="Red"]124[/COLOR][/B], {0, fffffa8012227028, be000000, 100110a}

Probably caused by : GenuineIntel

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

0x124's are typically related to a hardware issue and can only be isolated by stress testing the major components.

If overclocking, reset all overclocks back to their default settings and then follow these:

RAM - run for a minimum of 8 consecutive passes
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

CPU - run the HIGH test
http://www.sevenforums.com/tutorials/220743-cpu-stress-test-using-intelburntest.html

Video - run the FURMARK test for 20mins
http://www.sevenforums.com/tutorials/330579-graphics-card-problems-diagnose.html
http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

Storage - run the SHORT test using the DOS version
http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

 

[NMania]

Thanks you for the quick reply.

I just finished running the last of the tests that you suggested, and none of them revealed any problems. Memtest ran through all 8 passes with 0 errors, SeaTools passed both of my hard drives, IntelBurnTest indicated that my CPU is stable, and FurMark did not seem to encounter any problems while being run for close to 30 minutes.

I have attached the GPU-Z Sensor log as well as pictures of the results of the various tests in case there is something I missed which might allow you to shed some light on the cause of the blue screens.

 

[Golden]

Please do the following:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

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:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html

 

[NMania]

I followed the instructions and got a BSOD after restarting. I tried a few more times before disabling driver verifier in safe mode, and got a blue screen every time. I have attached the only dmp file that was generated.

 

[Golden]

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

Use !analyze -v to get detailed debugging information.

BugCheck D5, {fffff98005df6ff1, 1, fffff8800664a675, 0}

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

Could not read faulting driver name
Probably caused by : [B][COLOR="Red"]vdrive.sys[/COLOR][/B] ( vdrive+7675 )

Followup: MachineOwner
fffff880`06643000 fffff880`06651000   vdrive   T (no symbols)           
    Loaded symbol image file: vdrive.sys
    Image path: \SystemRoot\system32\DRIVERS\vdrive.sys
    Image name: vdrive.sys
    Timestamp:        Fri Aug 29 18:27:40 2014 (54004084)
    CheckSum:         00019B3C
    ImageSize:        0000E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
---------

See if there is an updated driver for DVDFab, and install it. If not, uninstall this software and re-run driver verifier.

 

[NMania]

I did not see an update for it, so I went ahead and uninstalled. I ran driver-verifier again and got a little farther (past the log in screen) before getting another blue screen. The blue screen listed rzpmgrk.sys as the cause, but hopefully that's not the root issue as it is linked to my mouse/keyboard and should be up to date. The most recent dmp file is attached.

 

[Golden]

I'll take a look at this tonight when I get home from work.

 

[Golden]

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

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 34, fffffa801242e340, fffff8800ced9430}

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

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

6: kd> lmvm rzpmgrk
start             end                 module name
fffff880`0ced8000 fffff880`0cedf280   rzpmgrk  T (no symbols)           
    Loaded symbol image file: rzpmgrk.sys
    Image path: \??\C:\Windows\system32\drivers\rzpmgrk.sys
    Image name: rzpmgrk.sys
    Timestamp:        Fri [B][COLOR="Red"]Apr 18[/COLOR][/B] 05:06:12 [B][COLOR="red"]2014[/COLOR][/B] (53502D2C)
    CheckSum:         0001707D
    ImageSize:        00007280
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Driver Reference Table - rzpmgrk.sys

Please check if there are updated drivers available.

 

[NMania]

I could not find a way to update that driver individually. Razer manages all of their drivers through a single piece of software (synapse). I removed the software and all of the drivers, and downloaded the most recent available version from their website. I ran driver verifier again and got the same blue screen.

I'm not sure where to go from here. I do have other keyboards I could use, but all my mice from the last several years are from the same company.

I really appreciate all the help you've given me so far.

 

[Golden]

Mmmm.....let me research this a bit more please.

 

[Golden]

Sorry, I've had no luck. My only suggestion is to uninstall it - use an alternative mouse/keyboard and see if the problem persists.

 

[NMania]

I know it's been a while, but I finally managed to get my hands on a non-razer mouse. I swapped out the mouse/keyboard, uninstalled everything related to razer, and went ahead and ran the verifier again. It crashed within a few minutes with hidclass.sys listed as the cause. I've attached the dmp file that was created.

 

[Golden]

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

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23b, fffff880073b0710, fffff9801fc10dc0, 0}

Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )

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

Can you confirm that Windows is fully updated - be sure to check Optional Updates too.

Besides the mouse and keyboard, what other USB devices are attached to the system at the time of the crash?

 

[NMania]

Yes, Windows is fully up to date. I make it a habit to keep it updated.

The only other devices that are consistently plugged in are an external hard drive, a wireless headset (I had the blue screens well before I added both of these), and a wireless receiver for an Xbox 360 controller with drivers straight from Microsoft.

 

[Golden]

Please unplug the XBox controller, then run Driver Verifier again:

Please do the following:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

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:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html

 

[NMania]

I ran it with the receiver removed and got a blue screen right after logging in again. For good measure I also ran verifier a second time, with the other 2 devices unplugged, and got the same blue screen.

 

[Golden]

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

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23b, fffff8800882d710, fffff9801942edc0, 0}

Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )

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

OK. Its most certainly a USB port driver problem. Can you check for updated drivers for any USB3.0 ports?

Also : are/have there been any Bluetooth devices installed to the system?

 

[NMania]

The most recent USB drivers on the manufacturers website are from early last year (before my last clean install of windows), but I went ahead and updated them to be safe and it's still crashing.

There aren't currently any Bluetooth devices on my system. I did try to add a USB dongle in the past, but I am fairly positive that I've re-installed since then.