I wish you a speedy recovery. Once you're well, attach the dumps and we'll take a look for you. Without the dumps, usama's post is probably nail on the head. Sleep and hibernate to me are fairly buggy, I never use them. For example, on my old Asus P8P67 Pro Rev 3.0 board, if the computer went to sleep, upon wake up it would not bring up display. Only a replacement Rev 3.1 board fixed this, and even after I still don't use sleep / hibernate.
Sleep and hibernate issues are a little more difficult than other issues to solve because there are many variables in causing a system to hang, crash, etc during its wake up.
Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).
In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation"IRP Logging and Force Pending I/O Requests. and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking
Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
I will run the sfc when I get back to my computer later today. As for the driver verifyer it does seem too iffy especially since its the only machine I have for work. My netbook isn't geared for anything.
Ah, it's a work computer.. understandable as to why you wouldn't want to run Driver Verifier. I'll go ahead and take a look a the dumps regardless and see what I can personally see.
First off, both dumps from 4/17 were 116 TDR bugchecks, but the next dump we get to is 5/31 and from that point on it's all 9F DRIVER_POWER_STATE_FAILURE. First thing I have to ask, did you ever solve the 116 TDRs? If not, it's likely that is leading us towards what we see now. I notice in the 116 TDR bugchecks, your nVidia drivers are dated from 2010, and they're still dated from 2010 in the newest attached dump.
It's possible that the current nVidia drivers you're using were causing the 116 TDRs and now they're causing an inconsistent power state. This would make the most sense as you're having issues waking up from sleep mode, so it seems only likely.