System Specs:
OS Windows 7 Ultimate x64
CPU Core i5-3570K (stock speeds)
Motherboard Gigabyte Z77X-UD3H
Memory 8Gb (2x4 Gb) Corsair Vengeance 1600mhz
Graphics Card MSI Radeon HD 7870 HAWK (Ghz Edition)
Sound Card N/A
Monitor(s) Displays ASUS VW266H 25.5"
Screen Resolution 1920x1200
Keyboard Microsoft Sidewinder x4
Mouse Logitech G600
PSU OCZ Modxtream Pro 700w
Case Silverstone KL04
Cooling Corsair H80
Hard Drives Crucial m4 256Gb Western Digital Caviar Blue 7200rpm 500Gb
Internet Speed 50D/20U Cable
Brief history: I put together a brand new rig almost a month ago, which has had some odd bluescreens and lockup behavior. Sleep and Hibernate are totally disabled, but the monitor is set to turn off after 10 minutes of idle. Occasionally, the computer will go into this idle state and will completely refuse to exit it. The video card stops sending signal to the monitor, it refuses to "wake up". The LEDs on my keyboard/mouse will work right up until I unplug them and plug them back in, then nothing, and eventually after trying to get it to wake up long enough it bluescreens with a DRIVER POWER STATE FAILURE bluescreen. But the odd thing is that you can still access shared files on the PC over the network, and open/transfer them all fine, so *something* is still working right up until the total failure.
When this first started happening, the video card would also sometimes have odd fan spinning behavior while it was idle, making a half spin at 100% then stopping constantly until you kicked it out of idle when it would immediately work normally again, and the first time it froze it kicked the fans up to 100% on the video card and kept them there as soon as I tried to move the mouse to wake it up. Eventually the video card failed completely to the point where any system I put the card in would not POST.
I RMAed the card and saw on newegg that it had an almost 25% 1-egg review rating for DOA/failing cards. When I finally got my new card on Monday the box was a little dinged up but everything looked OK and I didnt have any issues since, until just today when it froze again while idle. I couldn't get the bluescreen to trigger and eventually just had to hold the power button until it hard booted.
Here's the WhoCrashed analysis of the first three freezes, not that it's much help. It didnt record a BSOD event today for some reason.
I've got nothing on this one outside of tearing the whole system apart and RMAing everything, it'd be great if you guys could help me out. I've done repeated stability testing on the GPU, CPU, and RAM and *everything comes back fine*. No errors with MemTest after 2000% coverage, Furmark and OCCT can run for an hour and a half with no errors or artifacts, and LinX passed a full 20 passes with flying colors. The system works great right up until the second it doesnt 🙁
OS Windows 7 Ultimate x64
CPU Core i5-3570K (stock speeds)
Motherboard Gigabyte Z77X-UD3H
Memory 8Gb (2x4 Gb) Corsair Vengeance 1600mhz
Graphics Card MSI Radeon HD 7870 HAWK (Ghz Edition)
Sound Card N/A
Monitor(s) Displays ASUS VW266H 25.5"
Screen Resolution 1920x1200
Keyboard Microsoft Sidewinder x4
Mouse Logitech G600
PSU OCZ Modxtream Pro 700w
Case Silverstone KL04
Cooling Corsair H80
Hard Drives Crucial m4 256Gb Western Digital Caviar Blue 7200rpm 500Gb
Internet Speed 50D/20U Cable
Brief history: I put together a brand new rig almost a month ago, which has had some odd bluescreens and lockup behavior. Sleep and Hibernate are totally disabled, but the monitor is set to turn off after 10 minutes of idle. Occasionally, the computer will go into this idle state and will completely refuse to exit it. The video card stops sending signal to the monitor, it refuses to "wake up". The LEDs on my keyboard/mouse will work right up until I unplug them and plug them back in, then nothing, and eventually after trying to get it to wake up long enough it bluescreens with a DRIVER POWER STATE FAILURE bluescreen. But the odd thing is that you can still access shared files on the PC over the network, and open/transfer them all fine, so *something* is still working right up until the total failure.
When this first started happening, the video card would also sometimes have odd fan spinning behavior while it was idle, making a half spin at 100% then stopping constantly until you kicked it out of idle when it would immediately work normally again, and the first time it froze it kicked the fans up to 100% on the video card and kept them there as soon as I tried to move the mouse to wake it up. Eventually the video card failed completely to the point where any system I put the card in would not POST.
I RMAed the card and saw on newegg that it had an almost 25% 1-egg review rating for DOA/failing cards. When I finally got my new card on Monday the box was a little dinged up but everything looked OK and I didnt have any issues since, until just today when it froze again while idle. I couldn't get the bluescreen to trigger and eventually just had to hold the power button until it hard booted.
Here's the WhoCrashed analysis of the first three freezes, not that it's much help. It didnt record a BSOD event today for some reason.
I've got nothing on this one outside of tearing the whole system apart and RMAing everything, it'd be great if you guys could help me out. I've done repeated stability testing on the GPU, CPU, and RAM and *everything comes back fine*. No errors with MemTest after 2000% coverage, Furmark and OCCT can run for an hour and a half with no errors or artifacts, and LinX passed a full 20 passes with flying colors. The system works great right up until the second it doesnt 🙁
Code:
On Mon 9/17/2012 10:18:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091712-4773-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800AB01AB0, 0xFFFFF800045183D8, 0xFFFFFA800B3D42C0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 9/17/2012 10:18:03 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800AB01AB0, 0xFFFFF800045183D8, 0xFFFFFA800B3D42C0)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 9/14/2012 10:26:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091412-5600-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800AF87AB0, 0xFFFFF800045143D8, 0xFFFFFA800CBCB010)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
Last edited: