Computer refuses to shut down and then BSOD's on me if I let it run.

essenbe · 16 Jul 2015

OK, lets try this again. Make sure you have a backup of all of your personal files. Make a system repair disk. Make sure your computer is set to create small memory dumps, even though I think it is. Dump Files - Configure Windows to Create on BSOD, next create a restore point , link is below. Then enable Driver verifier, Make sure to sort the drivers by Provider and select all drivers NOT provided by Microsoft. Do not enable it on Microsoft drivers. The You Tube Video is at Computer refuses to shut down and then BSOD's on me if I let it run..

Warning

Be sure to create a System Restore point before proceeding further System Restore Point - Create

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

Information

What is Driver Verifier:
It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.

What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.

Warning

Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. 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, do a System Restore to a point you made earlier.

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

Zibeltor · 16 Jul 2015

Alrighty, thanks! I'll go ahead and run the driver verifier protocol after I get off work and edit this post to include the results. Thank you for your continued assistance!

essenbe · 16 Jul 2015

That will be fine. But, if you would, please make a new post with the results.

Zibeltor · 16 Jul 2015

Haha, right. I realized pretty quickly that you probably wouldn't get notified of an edited post. Anyway, the logs from (a very quick) BSOD are attached. Looks like one of those pesky Razer drivers is still around somehow... I'll try uninstalling it and running the verifier program again. EDIT: Huh... when I went into device manager and check the driver details, the only drivers listed are C:\Windows\system32\DRIVERS\mouclass.sys and C:\Windows\system32\DRIVERS\mouhid.sys but neither of those looked like the Razer .exe I saw mentioned on the BSOD...hmmm.

essenbe · 16 Jul 2015

Right.

Code:

Use !analyze -v to get detailed debugging information.
BugCheck C4, {f6, 54, fffffa800f20e380, fffff8800b801430}
*** 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

That is the Razer Overlay Support Driver. I would try to get rid of everything that says Razor.

Zibeltor · 16 Jul 2015

Alright; well, I did as you instructed and uninstalled everything Razer related. Then I ran the verifier program and lo and behold, no instant BSOD. I let it run for about five minutes, but I actually have to use my computer tonight, so I think I'll start the 24-hour test run later tonight. Is that what you'd recommend as the next step? A 24-hour verifier test?

essenbe · 16 Jul 2015

Yes, see if anything else pops up.

Zibeltor · 18 Jul 2015

Alrighty! Well, it's been running the last thirteen hours or so pretty stably with the verifier protocol on. Of course, I'll let it run overnight just to make sure. Just thought I'd drop in and give an update.

Zibeltor · 18 Jul 2015

Alright, I'll continue to let it run for another hour or so while I mow the lawn just to make sure, but I'm pretty confident there wont be any BSOD's (and it might already have been over twenty-four hours). I'm kinda skeptical that the Razer drivers were the cause of the problem since I bought the mouse pretty recently (like within the last couple weeks). Perhaps it was the Razer drivers combined with the Nvidia software... anyway! I'm just wondering if you have some next steps you'd recommend. As always, your help is greatly appreciated Essenbe!

essenbe · 18 Jul 2015

When you run verifier, use the computer for anything you want to. There are no restrictions. It is better if you do run it. I would run it hard. Play games, do whatever you usually do. This is the only time you want it to crash. That's the idea of verifier. Make it crash so we can hopefully catch whatever driver is causing problems. The only driver it found was the Razor driver, so far.