ntoskrnl.exe BSOD Error: DRIVER_POWER_STATE_FAILURE and Error: CUSTOM_ERROR

[Ariel_Engle]

when I shut down my laptop it restarts after 30mins without me doing anything and who crashed gave me this
On Wed 7/12/2017 6:52:17 PM 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 (0x4, 0x12C, 0xFFFFC1887A7EC040, 0xFFFFF80350855890)
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.

today it gave me a BSOD and who crashed gave this.
On Wed 7/12/2017 6:52:17 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\071217-43921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x171226)
Bugcheck code: 0x1000009F (0x4, 0x12C, 0xFFFFC1887A7EC040, 0xFFFFF80350855890)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I really need to fix this cause it is my work computer and I can not afford to buy another computer right now. plus it has not been a whole year since I bought it from best buy

 

[johnbl]

basically, the bugcheck said that windows told some hardware to change a power state (sleep or wake up) and windows set a timer for 0x12c second = 300 seconds (5 minutes) for the device to respond. the device did not respond in the 5 minutes so windows called a bugcheck to stop the system.

generally, the reason for something like this is because the device never actually got the signal. The most common fix will be to update the BIOS and the motherboard drivers from the motherboard vendors website. often, you can also work around the problem by going into windows control panel and setting the device not to sleep or set the entire machine to run in high performance mode.
Best option is just to update the BIOS and drivers as a fix to the problem.
Note this was a very common problem during windows 7 because sleep or low power states were turned off by default, windows 8.x and window 10 have them turned on by default.

 

[aa211033aa]

basically, the bugcheck said that windows told some hardware to change a power state (sleep or wake up) and windows set a timer for 0x12c second = 300 seconds (5 minutes) for the device to respond. the device did not respond in the 5 minutes so windows called a bugcheck to stop the system.

generally, the reason for something like this is because the device never actually got the signal. The most common fix will be to update the BIOS and the motherboard drivers from the motherboard vendors website. often, you can also work around the problem by going into windows control panel and setting the device not to sleep or set the entire machine to run in high performance mode.
Best option is just to update the BIOS and drivers as a fix to the problem.
Note this was a very common problem during windows 7 because sleep or low power states were turned off by default, windows 8.x and window 10 have them turned on by default.