Windows 10: Multi Errors of Hardware Error DRIVER_POWER_STATE_FAILURE caused by ntoskrnl.exe

Discus and support Multi Errors of Hardware Error DRIVER_POWER_STATE_FAILURE caused by ntoskrnl.exe in Windows 10 BSOD Crashes and Debugging to solve the problem; I frequently put my computer into sleep state as I hop between classes and rest time. Today, I noticed the computer started from cold start multiple... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by OrdinaryW10User, Jul 28, 2020.

  1. Multi Errors of Hardware Error DRIVER_POWER_STATE_FAILURE caused by ntoskrnl.exe


    I frequently put my computer into sleep state as I hop between classes and rest time. Today, I noticed the computer started from cold start multiple times when I go ahead and want to wake my computer the power light is not flashing, indicating either it was in hibernate mode, or shut down. BTW, this is a laptop.


    Before this, two people on the MS Community had advised me to get the wireless adapter driver up to date, done it, but still the issue presents.


    Viewing from the minidump using nirsoft's bluescreenview, it states that those were caused by DRIVER_POWER_STATE_FAILURE by ntoskrnl.exe.


    If you want memory dump or the minidump, here's it, labeled by the date.

    :)
     
    OrdinaryW10User, Jul 28, 2020
    #1

  2. Stop Error Caused by ntoskrnl.exe

    Hi Luke,

    For us to isolate your concern regarding the error that caused by ntoskrnl.exe, we would like to know the following:

    • Were there any updates made on your computer prior to this concern?
    • To make sure we have not missed on anything, what troubleshooting steps have you done so far?
    • Send us a screenshot of the exact error message.

    We look forward to your response.
     
    Michael Gall, Jul 28, 2020
    #2
  3. BSOD caused by ntoskrnl.exe driver_power_state_failure windows 10

    Over the last couple of weeks, my Asus laptop has intermittently crashed with the blue error screen several times even after trying multiple fixes. I tried searching if anyone else has had the problem but none of the discussion are recent enough to apply
    to me.

    Any help would be greatly appreciated. Thanks in advance!

    Asus Flip 14 UX461UN

    CPU: Intel i5- 8250U

    GPU: Nvidia Geforce MX150

    Hard Drive:

    RAM: 16GB

    Architecture: 64bit

    OS: Windows 10 Home 1909

    Here are recent dump files ive viewed with whocrashed.

    On Mon 2020-05-18 6:31:21 PM your computer crashed or a problem was reported

    crash dump file: C:\WINDOWS\Minidump\051820-10828-01.dmp

    This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)

    Bugcheck code: 0x9F (0x3, 0xFFFFDD0CFC2A6060, 0xFFFFF20D36C6F7B0, 0xFFFFDD0D075D97A0)

    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. 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 Mon 2020-05-18 6:31:21 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+0x24467)

    Bugcheck code: 0x9F (0x3, 0xFFFFDD0CFC2A6060, 0xFFFFF20D36C6F7B0, 0xFFFFDD0D075D97A0)

    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.

    On Mon 2020-05-18 1:10:19 PM your computer crashed or a problem was reported

    crash dump file: C:\WINDOWS\Minidump\051820-11859-01.dmp

    This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)

    Bugcheck code: 0x9F (0x3, 0xFFFF8E021F57B060, 0xFFFFED845E26F7B0, 0xFFFF8E022882DB00)

    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. 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 Thu 2020-05-14 11:42:39 PM your computer crashed or a problem was reported

    crash dump file: C:\WINDOWS\Minidump\051420-11250-01.dmp

    This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)

    Bugcheck code: 0x9F (0x3, 0xFFFFB683C0BD0060, 0xFFFF8E0013C3F7B0, 0xFFFFB683C9A49B10)

    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. 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 Thu 2020-05-07 8:44:59 PM your computer crashed or a problem was reported

    crash dump file: C:\WINDOWS\Minidump\050720-10500-01.dmp

    This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)

    Bugcheck code: 0x9F (0x3, 0xFFFFA98ECC05F060, 0xFFFF850A8D43F7B0, 0xFFFFA98ECC0D1010)

    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. 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 2020-05-06 11:47:16 PM your computer crashed or a problem was reported

    crash dump file: C:\WINDOWS\Minidump\050620-11812-01.dmp

    This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)

    Bugcheck code: 0x9F (0x3, 0xFFFFAC0A1411E060, 0xFFFFFC0E4467F7B0, 0xFFFFAC0A1AB49A80)

    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. 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.



    Conclusion


    6 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce
    a full memory dump may help you.
     
    justinalmonte, Jul 28, 2020
    #3
  4. Multi Errors of Hardware Error DRIVER_POWER_STATE_FAILURE caused by ntoskrnl.exe

    Multi Errors of Hardware Error (DRIVER_POWER_STATE_FAILURE caused by ntoskrnl.exe). Please help.

    I frequently put my computer into sleep state as I hop between classes and rest time. Today, I noticed the computer started from cold start multiple times when I go ahead and want to wake my computer (the power light is not flashing, indicating either it
    was in hibernate mode, or shut down. BTW, this is a laptop. )

    Viewing from the minidump using nirsoft's bluescreenview, it states that those were caused by DRIVER_POWER_STATE_FAILURE by ntoskrnl.exe.

    If you want memory dump or the minidump, here's it.


    Below are the reports details pulled from Reliability Monitor.


    Multi Errors of Hardware Error DRIVER_POWER_STATE_FAILURE caused by ntoskrnl.exe 15a06f2a-a8fe-46f0-95e8-ebc02ca9b4aa?upload=true.png


    Code:
    Source
    
    Windows
    
    Summary
    
    Hardware error
    
    Date
    
    ‎18/‎7/‎2020 8:43 AM
    
    Status
    
    Not reported
    
    Description
    
    A problem with your hardware caused Windows to stop working correctly.
    
    Problem signature
    
    Problem Event Name:    LiveKernelEvent
    
    Code:    15e
    
    Parameter 1:    30
    
    Parameter 2:    ffffbd8c634051a0
    
    Parameter 3:    ffffbd8c60c07060
    
    Parameter 4:    0
    
    OS version:    10_0_18363
    
    Service Pack:    0_0
    
    Product:    768_1
    
    OS Version:    10.0.18363.2.0.0.768.100
    
    Locale ID:    17417
    
    Source
    
    Windows
    
    Summary
    
    Hardware error
    
    Date
    
    ‎18/‎7/‎2020 11:50 AM
    
    Status
    
    Not reported
    
    Description
    
    A problem with your hardware caused Windows to stop working correctly.
    
    Problem signature
    
    Problem Event Name:    LiveKernelEvent
    
    Code:    193
    
    Parameter 1:    810
    
    Parameter 2:    0
    
    Parameter 3:    0
    
    Parameter 4:    0
    
    OS version:    10_0_18363
    
    Service Pack:    0_0
    
    Product:    768_1
    
    OS Version:    10.0.18363.2.0.0.768.100
    
    Locale ID:    17417
    
    Source
    
    Windows
    
    Summary
    
    Hardware error
    
    Date
    
    ‎18/‎7/‎2020 11:50 AM
    
    Status
    
    Not reported
    
    Description
    
    A problem with your hardware caused Windows to stop working correctly.
    
    Problem signature
    
    Problem Event Name:    LiveKernelEvent
    
    Code:    193
    
    Parameter 1:    810
    
    Parameter 2:    0
    
    Parameter 3:    0
    
    Parameter 4:    0
    
    OS version:    10_0_18363
    
    Service Pack:    0_0
    
    Product:    768_1
    
    OS Version:    10.0.18363.2.0.0.768.100
    
    Locale ID:    17417
    
    Source
    
    Windows
    
    Summary
    
    Hardware error
    
    Date
    
    ‎18/‎7/‎2020 11:50 AM
    
    Status
    
    Not reported
    
    Description
    
    A problem with your hardware caused Windows to stop working correctly.
    
    Problem signature
    
    Problem Event Name:    LiveKernelEvent
    
    Code:    193
    
    Parameter 1:    810
    
    Parameter 2:    0
    
    Parameter 3:    0
    
    Parameter 4:    0
    
    OS version:    10_0_18363
    
    Service Pack:    0_0
    
    Product:    768_1
    
    OS Version:    10.0.18363.2.0.0.768.100
    
    Locale ID:    17417
    
    The program dwm.exe version 10.0.18362.387 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
    
     Process ID: 444
    
     Start Time: 01d65c9c1e699838
    
     Termination Time: 60000
    
     Application Path: C:\Windows\System32\dwm.exe
    
     Report Id: 7e24b8ef-ae68-4fcb-8374-3144cdd2c79b
    
     Faulting package full name: 
    
     Faulting package-relative application ID: 
    
     Hang type: Unknown
    
    The previous system shutdown at 11:33:09 AM on ‎18/‎7/‎2020 was unexpected.
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffbd8c60c07060, 0xffffae031d23f870, 0xffffbd8c692e2010). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 1ce0a77d-c8c8-41a2-9d87-efb47d0dbc51.
    
    Source
    
    Windows
    
    Summary
    
    Shut down unexpectedly
    
    Date
    
    ‎18/‎7/‎2020 12:59 PM
    
    Status
    
    Not reported
    
    Problem signature
    
    Problem Event Name:    BlueScreen
    
    Code:    9f
    
    Parameter 1:    3
    
    Parameter 2:    ffffbd8c60c07060
    
    Parameter 3:    ffffae031d23f870
    
    Parameter 4:    ffffbd8c692e2010
    
    OS version:    10_0_18363
    
    Service Pack:    0_0
    
    Product:    768_1
    
    OS Version:    10.0.18363.2.0.0.768.100
    
    Locale ID:    17417
    
    Source
    
    Windows
    
    Summary
    
    Hardware error
    
    Date
    
    ‎18/‎7/‎2020 5:31 PM
    
    Status
    
    Not reported
    
    Description
    
    A problem with your hardware caused Windows to stop working correctly.
    
    Problem signature
    
    Problem Event Name:    LiveKernelEvent
    
    Code:    193
    
    Parameter 1:    810
    
    Parameter 2:    0
    
    Parameter 3:    0
    
    Parameter 4:    0
    
    OS version:    10_0_18363
    
    Service Pack:    0_0
    
    Product:    768_1
    
    OS Version:    10.0.18363.2.0.0.768.100
    
    Locale ID:    17417
    
    The program dwm.exe version 10.0.18362.387 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
    
     Process ID: 458
    
     Start Time: 01d65cc03fef15cf
    
     Termination Time: 60000
    
     Application Path: C:\Windows\System32\dwm.exe
    
     Report Id: 53bc5580-1630-4d88-9e17-d8bdb16a0446
    
     Faulting package full name: 
    
     Faulting package-relative application ID: 
    
     Hang type: Unknown
    
    The previous system shutdown at 5:35:22 PM on ‎18/‎7/‎2020 was unexpected.
    
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff9e0a409ce060, 0xfffff8025e268870, 0xffff9e0a4815c010). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: b8d88f25-9280-4193-810b-1c444f732110.
    
    Source
    
    Windows
    
    Summary
    
    Shut down unexpectedly
    
    Date
    
    ‎18/‎7/‎2020 6:57 PM
    
    Status
    
    Not reported
    
    Problem signature
    
    Problem Event Name:    BlueScreen
    
    Code:    9f
    
    Parameter 1:    3
    
    Parameter 2:    ffff9e0a409ce060
    
    Parameter 3:    fffff8025e268870
    
    Parameter 4:    ffff9e0a4815c010
    
    OS version:    10_0_18363
    
    Service Pack:    0_0
    
    Product:    768_1
    
    OS Version:    10.0.18363.2.0.0.768.100
    
    Locale ID:    17417
     
    OrdinaryW10User, Jul 28, 2020
    #4
Thema:

Multi Errors of Hardware Error DRIVER_POWER_STATE_FAILURE caused by ntoskrnl.exe

Loading...
  1. Multi Errors of Hardware Error DRIVER_POWER_STATE_FAILURE caused by ntoskrnl.exe - Similar Threads - Multi Errors Hardware

  2. Hardware Error caused by LiveKernelEvent

    in Windows 10 Gaming
    Hardware Error caused by LiveKernelEvent: Problem Event Name:LiveKernelEventCode:141Parameter 1:ffff890fa40b6050Parameter 2:fffff8068a6116a0Parameter 3:0Parameter 4:0OS version:10_0_22631Service Pack:00Product:768_1OS Version:10.0.22631.2.0.0.768.101Locale ID:1033what could this mean?...
  3. Hardware Error caused by LiveKernelEvent

    in Windows 10 Software and Apps
    Hardware Error caused by LiveKernelEvent: Problem Event Name:LiveKernelEventCode:141Parameter 1:ffff890fa40b6050Parameter 2:fffff8068a6116a0Parameter 3:0Parameter 4:0OS version:10_0_22631Service Pack:00Product:768_1OS Version:10.0.22631.2.0.0.768.101Locale ID:1033what could this mean?...
  4. Hardware Error Causing Crash

    in Windows 10 Gaming
    Hardware Error Causing Crash: Hello All, I have been having this problem for a long time now and sometimes it will get better and sometimes it will happen 4-8 times a day... but looking at the Reliability Report it always seems to have a downward trend.Problem signatureProblem Event Name:...
  5. Hardware Error Causing Crash

    in Windows 10 Software and Apps
    Hardware Error Causing Crash: Hello All, I have been having this problem for a long time now and sometimes it will get better and sometimes it will happen 4-8 times a day... but looking at the Reliability Report it always seems to have a downward trend.Problem signatureProblem Event Name:...
  6. Hardware Error Causing Crash

    in Windows 10 BSOD Crashes and Debugging
    Hardware Error Causing Crash: Hello All, I have been having this problem for a long time now and sometimes it will get better and sometimes it will happen 4-8 times a day... but looking at the Reliability Report it always seems to have a downward trend.Problem signatureProblem Event Name:...
  7. DRIVER_POWER_STATE_FAILURE Error

    in Windows 10 BSOD Crashes and Debugging
    DRIVER_POWER_STATE_FAILURE Error: There is a DRIVER_POWER_STATE_FAILURE BSOD occurring on my device. When I analyzed I found out the error mentioned as "Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvam.inf_amd64_8cded5d1cdb5d080\nvlddmkm.sys, Win32 error 0n2". I asked the same...
  8. Multi Errors of Hardware Error DRIVER_POWER_STATE_FAILURE caused by ntoskrnl.exe. Please help.

    in Windows 10 BSOD Crashes and Debugging
    Multi Errors of Hardware Error DRIVER_POWER_STATE_FAILURE caused by ntoskrnl.exe. Please help.: I frequently put my computer into sleep state as I hop between classes and rest time. Today, I noticed the computer started from cold start multiple times when I go ahead and want to wake my computer the power light is not flashing, indicating either it was in hibernate mode,...
  9. Having this Bug error: INTERNAL_POWER_ERROR and DRIVER_POWER_STATE_FAILURE; Caused by...

    in Windows 10 Drivers and Hardware
    Having this Bug error: INTERNAL_POWER_ERROR and DRIVER_POWER_STATE_FAILURE; Caused by...: ================================================== Dump File : 060220-50218-01.dmp Crash Time : 02-06-2020 11:42:05 Bug Check String : INTERNAL_POWER_ERROR Bug Check Code : 0x000000a0 Parameter 1 : 00000000`00000618 Parameter 2 :...
  10. BSOD ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe: My computer has crashed a few times often when i play games. I bought more ram because i thought that it was the issue but it didn't help. It did work a few days but then the crashes came back. After that i fixed the BSOD´s by lowering the graphics and the resolution on the...