BSOD on hibernating in Windows 7

Hello,
I run Windows 7 Home Premium x64 and I'm having BSODs when I put the machine in hibernation or in sleep mode with hybrid sleep activated (the latter means hibernation takes place along with sleep). Mind you I haven't had any other problems with my setup and I can use the sleep function without problems when hybrid sleep is deactivated.

In Event Viewer I get the following error messages:
Event 6008 "The Previous shutdown was unexpected"
Event 41 "The system has rebooted without cleanly shutting down first"
Event 1005 "Unable to produce a minidump file from the full dump file"
Event 1001 "the computer has rebooted from a bugcheck. The bugcheck was: 0x000000a0"

In the attached zip file you'll find an analysis report of the memory dump file after BSOD when trying to put the machine in hybrid sleep mode named memdump.txt and an analysis report of the memory dump file after BSOD when trying to hibernate named memdump2.txt. These were generated by Microsoft's Debugging Tools for Windows (x64).

Also, after disabling auto-restart and enabling minidumps by following instructions from Set MiniDump, my computer now generates minidumps that I also enclose in the zip file. I used the WhoCrashed program which generated the following analysis

On Wed 12/05/2010 23:09:41 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA0 (0x9, 0xFFFFFFFFC0000185, 0x1, 0x0)
Error: INTERNAL_POWER_ERROR
Dump file: C:\Windows\Minidump\051210-25256-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

Any help would be greatly appreciated.

my computer
CPU: Intel Core 2 Duo E6420
M/B: GIGABYTE GA-P35C-DS3R rev. 1.0 (Intel P35 + ICH9R)
RAM: 4GB (4x1G) DDRII 800MHz
PSU: Seasonic S12-430 (430W)
HDD: Intel X25-M SATA SSD on 34nm (silver case) - FW version 02HD - msahci driver
GPU: NVIDIA GeForce 6600/256MB
TV: AVerMedia AVerTV Duo Hybrid PCI-E (A177)

While I'm not a Power Supply expert, I wonder if 430 watts is enough to run your equipment.
The problems that you're experiencing are somewhat sporadic - so that would seem to indicate the PSU.
Otherwise, you'd be suffering from some sort of issue with the creation of your hibernation file.

In most cases this would be related to either:
- your video drivers
- your storage drivers
- you hard drive or the file system(s) being used on it

I would suggest trying Driver Verifier according to these directions:

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.

So, 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).

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" and click "Next"
- 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.

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 (an estimate on my part).

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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

If it identifies a 3rd party driver - then we can presume that that's the problem.
If it identifies anything else - then we have to presume that it's a hardware issue - and we can move on from there.

Summary of the BSOD:

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May  9 21:35:25.263 2010 (GMT-4)
System Uptime: 0 days 8:41:35.230
BugCheck A0, {9, ffffffffc0000185, 1, 0}
Probably caused by : ntkrnlmp.exe ( nt!PopEndMirroring+145 )
BUGCHECK_STR:  0xA0
PROCESS_NAME:  System