Windows 10: driver_power_state_failure nt!TRIAGE_9F_POWER Win 10

I keep having frequent BSODs all with the 'driver power state failure' description. It has been happening for a good while now. It has destroyed my HDD because of the frequent crashes and I recently replaced it with an SSD and the problem is still occurring. I've tried all the suggestions I could get from the internet. However, I recently decided to check for a dump file for the BSOD and found it. I will attach a link to it and any help in the analysis and suggestions would be good. Running Win 10, Acer Aspire ES1-132


Dump file here https://1drv.ms/u/s!ArH3OT10gZc4oAa5zuH4SUg2H0a8?e=JwIKAn

:)

 

BSOD on Win 10 DRIVER_POWER_STATE_FAILURE pci.sys

https://onedrive.live.com/redir?resid=EE95EBFD150AB147!208&authkey=!ALQv2tTr0VW3vmc&ithint=file,zip

I encounter a very frequent BSOD on WIndows 10

it is a DRIVER_POWER_STATE_FAILURE. It happens during running CAD programs, but not with games.

I am glad for any suggestions on how to fix it.

Thx

Instant Online Crash Analysis, brought to you by OSR Open Systems Resources, Inc.

Show DivPrimary Analysis

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Homepage - OSR)

Online Crash Dump Analysis Service

See OSR Online - The Home Page for Windows Driver Developers for more information

Windows 8 Kernel Version 10586 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 10586.122.amd64fre.th2_release_inmarket.160222-1549

Machine Name:

Kernel base = 0xfffff800`cb886000 PsLoadedModuleList = 0xfffff800`cbb64cf0

Debug session time: Sat Mar 5 15:17:06.395 2016 (UTC - 5:00)

System Uptime: 2 days 3:28:24.128

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)

A driver has failed to complete a power IRP within a specific time (usually 10 minutes).

Arguments:

Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time

Arg2: ffffe001fb3eb060, Physical Device Object of the stack

Arg3: ffffd001414f5990, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack

Arg4: ffffe001fb3e2010, The blocked IRP

Debugging Details:

------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5632d60a

MODULE_NAME: pci

FAULTING_MODULE: fffff801c5820000 pci

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:

ffffd001`414f5958 fffff800`cba66eca : 00000000`0000009f 00000000`00000003 ffffe001`fb3eb060 ffffd001`414f5990 :

nt!KeBugCheckEx

ffffd001`414f5960 fffff800`cba66dea : ffffe001`fb3e4a08 ffffe001`f9624a88 00000000`00000000 fffff800`cb94fd96 :

nt!PopIrpWatchdogBugcheck+0xde

ffffd001`414f59c0 fffff800`cb8f3fe6 : ffffe001`fb3e4a40 ffffd001`414f5b10 00000000`00000001 00000000`006bdc77 :

nt!PopIrpWatchdog+0x32

ffffd001`414f5a10 fffff800`cb9cb20a : ffffffff`00000000 ffffd001`414e0180 ffffd001`414eccc0 ffffe002`0325e240 :

nt!KiRetireDpcList+0x5f6

ffffd001`414f5c60 00000000`00000000 : ffffd001`414f6000 ffffd001`414f0000 00000000`00000000 00000000`00000000 :

nt!KiIdleLoop+0x5a

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_ACPI_IMAGE_pci.sys

BUCKET_ID: X64_0x9F_3_ACPI_IMAGE_pci.sys

 

BSOD Win 10 : DRIVER_POWER_STATE_FAILURE on win boot

Since 10/1/2016 last bg Win 10 update I am getting BSOD only on new start. Restart works ok.

Here is mini dump ,

https://drive.google.com/file/d/0B7QGIb4zX5LWOEMwLUJTZkJtaDg/view?usp=sharing

WhoCrashed does not help much

On Mon 10/3/2016 1:15:02 PM GMT your computer crashed

crash dump file: C:\WINDOWS\memory.dmp

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

Bugcheck code: 0x9F (0x3, 0xFFFFCF04763AE060, 0xFFFFF8023AAFBAA0, 0xFFFFCF04766AFB40)

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.

and this is crash analysis.

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Homepage - OSR)

Online Crash Dump Analysis Service

See OSR Online - The Home Page for Windows Driver Developers for more information

Windows 8 Kernel Version 14393 MP (24 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 14393.206.amd64fre.rs1_release.160915-0644

Machine Name:

Kernel base = 0xfffff803`2ca7f000 PsLoadedModuleList = 0xfffff803`2cd83080

Debug session time: Mon Oct 3 06:09:42.668 2016 (UTC - 4:00)

System Uptime: 0 days 1:03:27.521

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)

A driver has failed to complete a power IRP within a specific time (usually 10 minutes).

Arguments:

Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time

Arg2: ffffc7042f451400, Physical Device Object of the stack

Arg3: fffff8032e87faa0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack

Arg4: ffffc7042f7d84d0, The blocked IRP

Debugging Details:

------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: storahci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 57dacb44

MODULE_NAME: storahci

FAULTING_MODULE: fffff80adec30000 storahci

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:

fffff803`2e87fa68 fffff803`2cc7916f : 00000000`0000009f 00000000`00000003 ffffc704`2f451400 fffff803`2e87faa0 : nt!KeBugCheckEx

fffff803`2e87fa70 fffff803`2cc79082 : ffffc704`2f7d2620 00000000`00023775 00000000`00000001 fffff803`2cdc0180 : nt!PopIrpWatchdogBugcheck+0xeb

fffff803`2e87fad0 fffff803`2cab1fa0 : ffffc704`2f7d2658 00000000`0023ac62 00000000`00140001 00000000`00000000 : nt!PopIrpWatchdog+0x22

fffff803`2e87fb20 fffff803`2cbcc33a : 00000000`00000000 fffff803`2cdc0180 fffff803`2ce3b940 ffffc704`31754080 : nt!KiRetireDpcList+0x440

fffff803`2e87fda0 00000000`00000000 : fffff803`2e880000 fffff803`2e87a000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_disk_IMAGE_storahci.sys

BUCKET_ID: X64_0x9F_3_disk_IMAGE_storahci.sys

Followup: MachineOwner

Any help is appreciated!

 

Windows 10, compatibility mode, NT 4.0

The problem is that win 10 does not have compatibility settings for win NT 4.0 (open glide)

I cannot set installs for win NT4.0 because it is not listed. Is there a workaround, please???

Herb