I have had two blue screens with the error message Driver Power State Failure. The failure appears to occur in ntoskrnl.exe+7cc40. The first time happened when the computer was in sleep mode (or at least idle, I'm not sure because I was not at the computer at the time) and the second was when I was using it. Here is some information that might help:
111111-26660-01.dmp 11/11/2011 6:31:54 PM DRIVER_POWER_STATE_FAILURE 0x0000009f 00000000`00000003 fffffa80`0b895cd0 fffff800`00ba2748 fffffa80`0b37cc60 ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\111111-26660-01.dmp 4 15 7601 838,688
I recently did a fresh install of Windows, and this did not occur before that reinstallation. One thing that may be of importance is that my system has issues where it will freeze from time to time, which is why I did the reinstallation. I made a separate article for that a while back, you can see it here http://www.tomshardware.com/forum/298379-30-computer-fr...
Eeek, total system lockups are never good; I had a mobo that did that for a while [790i series, which was FAMOUS for hard-locking]. Usually points to the mobo, if it gets to the point where Windows is unable to BSOD...[seriously, you have to TRY to be able to pull that off... ]
Might want to RMA the mobo if possible, if for no other reason to rule that out.
Another concern about the mobo is that when I installed my Hyper 212+ cooler, the nuts seemed to tear up the paint a bit on the PCB. Would this cause problems and/or void my motherboard warranty? I used this cooler on other mobos and not had this problem...
I would think it's the mobo, except I've run Memtest multiple times with no problems.
In the case of my old 790i, the hard-locks were due to a northbridge that needed a significant boost in voltage [1.3V from 1.1V], overvolting the RAM significantly, setting RAM timings to the more conservative 2T, and syncing the RAM/FSB to 1:1. Never ONCE did I have a failure in memtest during any of this; its was a low-level mobo thing.
The main issue with hard-locks is they tend to be very low level, and near impossible to replicate on demand for testing.
With this setup, however, there's no FSB or northbridge, as it's all in the CPU. And it's certainly very difficult to test; every time I think it's fixed, it turns out it isn't. The motherboard is the only other thing I can think of.