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

[essenbe]

I don't have a DVD either, but I do have a portable one, just in case I need one. Driver Verifier puts stress on the drivers in an attempt to make the bad driver make the computer BSOD, and the dump file catch the driver. The problem comes when some people can't boot because of driver verifier. If you can get into the recovery environment you can disable it. The repair DVD helps you do that. That is why you created the restore point. The decision is up to you. The worst case scenario is you will have to do a clean install. Enable only the NON-Microsoft drivers when you set it up. This is a video showing how to do it on Windows 10. It is the exact same in Windows 7. I hope this helps.

 

[Zibeltor]

Interesting; I like the portable DVD drive idea. I'll stop by the store later today and pick up one of those and some blank DVD's, thanks for the tip! (I'd really like to avoid having to do a clean install). Then I'll get started with the test later tonight.

 

[essenbe]

No problem. It is just a possibility. In all honesty, we go to great lengths to try to make sure that does not happen. I have never had it happen to me, because of those precautions, but it could still happen.

 

[Zibeltor]

Alright; apologies for the delay, I got a bit held up last night but was able to do everything this morning. It took probably less than five seconds for it to BSOD with the verifier program running. Then I just restarted it in safe mode to go ahead and disable the verifier so that I could get this crash dump (which should be attached, I believe) and deliver it to you. (This portable DVD writer is a really nifty gismo, by the way! It's way better than having one installed in a computer, IMO. Again, thanks for all the help and super useful info! I always learn a lot when I come here. )

 

[essenbe]

OK, when you reinstalled the Nvidia drivers, I take it you installed GeForce Experience. I had told you only the Display Driver and PhysX. Here are the results of the dump. You won't like it, I'm sure.

Use !analyze -v to get detailed debugging information.

 
BugCheck C4, {f6, 58, fffffa800f5fe3b0, fffff88010b90430}

 
*** WARNING: Unable to verify timestamp for rzpmgrk.sys
*** ERROR: Module load completed but symbols could not be loaded for rzpmgrk.sys
Probably 
[COLOR=red]caused by : rzpmgrk.sys[/COLOR] ( rzpmgrk+1430 )
Followup: MachineOwner
 
Those are your Razor drivers. Thay are known to cause some people bad problems. I would suggest you uninstall all Razor Drivers at least to test. Also noted in the dump was
 
[CODE]BUGCHECK_STR:  0xc4_f6
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
[COLOR=red]PROCESS_NAME:  OAWrapper.exe[/COLOR]

That is part of the GeForce Experience
[/CODE]

 

[Zibeltor]

Alrighty, well, when I tried to uninstall the Razer software, I got this error message: "Error opening installation log file. Verify that the specified log file location exists and is writable." Like a lot of basic drivers/utilities on my computer, it inexplicably installed itself in C:\Users\[Me]\AppData\Local\Temp\[Crazy Alphanumeric String]. That seemed to also start happening when I tried to separate the libraries from the Windows folder. Anyway, advice on that?

And sorry about the Nvidia stuff--their software suite kind of confuses me. I thought Geforce Experience was like a necessary installer for the other stuff. Should I uninstall that as well?

 

[essenbe]

Yes, uninstall GeForce Experience. It causes a lot of people problems.

Try going to device manager, find your Razor products, Right click them and click properties, go to the drivers tab, click the uninstall driver. You will get some 'are you sure' messages and 'this may not work right messages', but continue and uninstall it. You should have to reboot afterwards. On reboot, I suspect Windows will install some generic drivers. You may have to reboot again, but I'm not sure on that part.

 

[Zibeltor]

Yeehaw! I was able to do three successful, consecutive shutdowns after uninstalling the things you recommended. And my mouse still works! (Apparently yeah, they did install some generic driver, but the Razer "Synapse" software is still there, kind of interesting.) Thank you so much for the help Essenbe! I'm not sure if that just resolved the ultimate problem, or just enough things for it to stop acting so screwy. Either way, I'm very grateful. EDIT: Oh, and I just noticed this on my fourth shut down--that "Waiting for background programs to close" screen that always appeared has stopped appearing if I have all the open programs closed. Seems rather telling.

 

[essenbe]

I'm glad it helped. I hope it continues to work right. Just let me know how it goes.

 

[Zibeltor]

I'm sad to report that the problem returned; albeit in a minor way. Last night, I had to do a second shut down before it would "stick" (e.g. the computer stayed shut down). This kinda mirrors the history of the problem where it tended to lapse for a while (it would shutdown fine), then occur more and more often, until eventually it's just impossible to shut down (the last two steps usually just taking a couple days). There seems to be a significant difference though in how fast the problem is escalating. Usually, by now, it would have reoccurred sooner and the problem would be more significant (requiring more than two shutdowns to fully, actually shutdown). Sorry; I know that's probably not very helpful. :/

 

[essenbe]

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. http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html, 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 http://www.sevenforums.com/bsod-hel...-me-if-i-let-run-post3107518.html#post3107518.

   Warning

Be sure to create a System Restore point before proceeding further http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

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]

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]

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

 

[Zibeltor]

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]

Right.

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
[COLOR=red]Probably caused by : rzpmgrk.sys[/COLOR] ( rzpmgrk+1430 )
Followup: MachineOwner

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

 

[Zibeltor]

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]

Yes, see if anything else pops up.

 

[Zibeltor]

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]

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]

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.