Windows 10: Help analyzing BSOD dump files - DRIVER_POWER_STATE_FAILURE

Hello,

I have been receiving blue screens of death related to DRIVER_POWER_STATE_FAILURE. I have not been able to identify which driver is causing this and I was wondering if someone would analyze my dump files to gain more information regarding this BSOD error. The full dump and minidump has been included.


So far I have ran the follow commands but the issue still occurs.


DISM /Online /Cleanup-Image /CheckHealth

DISM /Online /Cleanup-Image /ScanHealth

DISM /Online /Cleanup-Image /RestoreHealth

sfc /scannow

:)

 

BSOD driver_power_state_failure on shutdown and no dump file

Hello,

My computer can`t shutdown properly or sleep. After shutdown screen goes black and 5min i get BSOD driver_power_state_failure but there is no dump file and no error in events. I did windows 10 clean install and i got same bsod during installation.

Steps i took:

Checked dump settings. OK

Checked ram. OK

Checked drive. OK

Tried updating drivers. No effect

Tried dissabling fast boot. No effect

Tried dissabling non essensial drivers. No effect

Uninstaling AVG. No effect

Reseting bios to default settings. No effect

I am out of ideas.

My setup:

Asus n56vz

i7 3610QM, 8gb ram, gt650, samsung 840 evo 250GB, 1TB hdd instead of cd-rom.

Would be awesome if anyone could help me.

Othervise I am left with hope that updates will fix it

 

Please Help analyze MiniDump Files (included)/BSODs/ ntoskrnl.exe/

Hi,

In most cases, this problem is caused by corrupted system files. For us to provide the best resolution possible, we'll be needing additional information:

• Have you made any recent changes on your computer prior to the issue?
• Was there an error code displayed when experiencing the blue screen error?

Meanwhile, we suggest following the troubleshooting steps provided on this
article to help fix the blue screen error. We also recommend posting on
TechNet forum to analyze the dump files.

If you need further assistance, don't hesitate to reach out.

 

Need help analyzing dump file.

If your computer crashes, how can you find out what happened, fix the issue and it prevent it from happening again? You may find the small memory dump file useful in this situation. The small memory dump file contains
the smallest amount of useful information that could help you identify why your computer crashed. The memory dump file contains the following information:

• The Stop message, its parameters and other data
• A list of loaded drivers
• The processor context (PRCB) for the processor that stopped
• The process information and kernel context (EPROCESS) for the process that stopped
• The process information and kernel context (ETHREAD) for the thread that stopped
• The Kernel-mode call stack for the thread that stopped

To create a memory dump file, Windows requires a paging file on the boot volume that is at least 2 megabytes (MB) in size. On computers that are running Microsoft Windows 2000, or a later version of Windows, a new memory
dump file is created each time that a computer crash may occur. A history of these files is stored in a folder. If a second problem occurs and if Windows creates a second small memory dump file, Windows preserves the previous file. Windows gives each file
a distinct, date-encoded file name. For example, Mini022900-01.dmp is the first memory dump file that was generated on February 29, 2000. Windows keeps a list of all the small memory dump files in the %SystemRoot%\Minidump folder.

The small memory dump file can be useful when hard disk space is limited. However, because of the limited information that is included, errors that were not directly caused by the thread that was running at the time of
the problem may not be discovered by an analysis of this file.