I just bought a new Hard Drive and DVD Drive a Seagate 750 raptor 10000rpm and a lite-on DVD Drive my system is as follows:
MB: ASUS M5A99X EVO
Processor: AMD FX 8300 @ 4.4Ghz
RAM: Kingston Hyper X 32GB @1866Mhz
GC: Readon HD 7770 @ 2GB
HD Setup: 750GB SG Raptor Primary @ 10000rpm / SG 1TB @ 7200rpm / WD 320GB @ 5200RPM / WD 160 GB @ 5200 RPM
So ever since I installed the new HD and installed windows 8 I have been having BSOD issues on wake up from sleep with the error message Drive Power State Failure I downloaded WhoCrashed and the report it passed me was as follows:
On Sun 1/25/2015 5:12:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012515-28078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE0019B227610, 0xFFFFF803570548E0, 0xFFFFE0019ED2E460)
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 that cannot be identified at this time.
On Sun 1/25/2015 5:12:20 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, 0xFFFFE0019B227610, 0xFFFFF803570548E0, 0xFFFFE0019ED2E460)
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 that cannot be identified at this time.
On Sun 1/25/2015 3:57:21 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012415-39812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE00158E29060, 0xFFFFF803652548E0, 0xFFFFE00158A1ADC0)
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 that cannot be identified at this time.
On Fri 1/23/2015 4:20:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012315-182859-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
MB: ASUS M5A99X EVO
Processor: AMD FX 8300 @ 4.4Ghz
RAM: Kingston Hyper X 32GB @1866Mhz
GC: Readon HD 7770 @ 2GB
HD Setup: 750GB SG Raptor Primary @ 10000rpm / SG 1TB @ 7200rpm / WD 320GB @ 5200RPM / WD 160 GB @ 5200 RPM
So ever since I installed the new HD and installed windows 8 I have been having BSOD issues on wake up from sleep with the error message Drive Power State Failure I downloaded WhoCrashed and the report it passed me was as follows:
On Sun 1/25/2015 5:12:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012515-28078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE0019B227610, 0xFFFFF803570548E0, 0xFFFFE0019ED2E460)
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 that cannot be identified at this time.
On Sun 1/25/2015 5:12:20 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, 0xFFFFE0019B227610, 0xFFFFF803570548E0, 0xFFFFE0019ED2E460)
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 that cannot be identified at this time.
On Sun 1/25/2015 3:57:21 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012415-39812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE00158E29060, 0xFFFFF803652548E0, 0xFFFFE00158A1ADC0)
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 that cannot be identified at this time.
On Fri 1/23/2015 4:20:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012315-182859-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR