Question windows power state failure

Aug 27, 2020
4
0
10
0
I been having power state fails and do not know what driver is causing it.

Here is the crash dump/minidump

Thanks

Crash dump directories:C:\WindowsC:\Windows\MinidumpOn Wed 8/26/2020 9:13:39 AM your computer crashed or a problem was reportedcrash dump file: C:\Windows\Minidump\082620-8343-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x3DDF40)Bugcheck code: 0x9F (0x3, 0xFFFFE00EF698E830, 0xFFFFF8033406C750, 0xFFFFE00F118A7760)Error: DRIVER_POWER_STATE_FAILUREfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.This is 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 Wed 8/26/2020 9:13:39 AM your computer crashed or a problem was reportedcrash dump file: C:\Windows\MEMORY.DMPThis was probably caused by the following module: ntkrnlmp.exe (nt!MmTrimAllSystemPagableMemory+0x2A767)Bugcheck code: 0x9F (0x3, 0xFFFFE00EF698E830, 0xFFFFF8033406C750, 0xFFFFE00F118A7760)Error: DRIVER_POWER_STATE_FAILUREBug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.This is 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 Wed 8/26/2020 12:22:57 AM your computer crashed or a problem was reportedcrash dump file: C:\Windows\Minidump\082620-15015-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x3DDF40)Bugcheck code: 0x9F (0x3, 0xFFFFA287C8EBDB50, 0xFFFFF8011F06C750, 0xFFFFA287D1D709A0)Error: DRIVER_POWER_STATE_FAILUREfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.This is 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 Tue 8/25/2020 11:45:37 PM your computer crashed or a problem was reportedcrash dump file: C:\Windows\Minidump\082520-13843-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x3DDF40)Bugcheck code: 0x9F (0x3, 0xFFFF920BA45A4CE0, 0xFFFFF8011826C750, 0xFFFF920BC6AE79A0)Error: DRIVER_POWER_STATE_FAILUREfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.This is 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 Tue 8/25/2020 5:13:51 PM your computer crashed or a problem was reportedcrash dump file: C:\Windows\Minidump\082520-9234-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x3DDF40)Bugcheck code: 0x9F (0x3, 0xFFFFC98FF0A53C80, 0xFFFFF8042966C750, 0xFFFFC98FEFF0F630)Error: DRIVER_POWER_STATE_FAILUREfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.This is 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.
 

hang-the-9

Titan
Moderator
What happened before the issues started, Windows update, driver update, installed/uninstalled, something? Need some details about the issue past just the messages which don't really help much since ntoskrnl.exe is a pretty generic process.
 
Aug 27, 2020
4
0
10
0
What happened before the issues started, Windows update, driver update, installed/uninstalled, something? Need some details about the issue past just the messages which don't really help much since ntoskrnl.exe is a pretty generic process.
My pc had a driver problem before so I reset my pc,all drives cleared and windows reinstalled,then i just put all my software back and this happend.
 

hang-the-9

Titan
Moderator
My pc had a driver problem before so I reset my pc,all drives cleared and windows reinstalled,then i just put all my software back and this happend.
If this is after a clean Windows setup, did you install the drivers again for the motherboard and other hardware? Did you check if the issue happened again after you installed something? Test RAM one stick at a time or different RAM?
 
Aug 27, 2020
4
0
10
0
so its been a few days, wiped all drives, fresh install of windows 10 pro, after getting everything set up again I am still having the same problem
crash dump , its different this time, at least the number and letter code thing
On Sun 9/6/2020 10:10:13 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!MmTrimAllSystemPagableMemory+0x28937)
Bugcheck code: 0x9F (0x3, 0xFFFF9389ED231A80, 0xFFFFF8027F66C750, 0xFFFF9389F6DB1850)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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.
 

ASK THE COMMUNITY

TRENDING THREADS