Answered driver power state failure (windows 10)

Joe Pineapples

Distinguished Member
Got an old Dell tower with windows 10 (latest 1809 build, fresh install) and getting this error
driver power state failure
and then it reboots. Strangely enough it seems to behave itself after the restart, but get the same problem again next time from a cold boot. Have disabled power saving options linked with the gfx card/pci-e slot (after a bit of research), but to no avail. Graphics card is a GT 630 and Nvidia driver wouldn't install, after going through a manual selection on their site. It did successfully update to a 'working' version from device manager > 'update driver', and appears to be an Nvidia one anyway. Just wondering what else to try and if anyone else has had that pattern of it working after a restart.

Got this from OSR Online....

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 17763 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff806`27ea1000 PsLoadedModuleList = 0xfffff806`282bcad0
Debug session time: Tue Feb 5 05:36:00.614 2019 (UTC - 5:00)
System Uptime: 0 days 0:09:41.454
*******************************************************************************
* *
* 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: ffffc983cd5f4060, Physical Device Object of the stack
Arg3: fffff8062a25e9d0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: ffffc983d0cdc010, The blocked IRP

Debugging Details:
------------------

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

DRVPOWERSTATE_SUBCODE: 3

DRIVER_OBJECT: ffffc983cd55d940

IMAGE_NAME: atapi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: atapi

FAULTING_MODULE: fffff8017e390000 atapi

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:
fffff806`2a25e998 fffff806`28172e06 : 00000000`0000009f 00000000`00000003 ffffc983`cd5f4060 fffff806`2a25e9d0 : nt!KeBugCheckEx
fffff806`2a25e9a0 fffff806`28172d12 : ffffc983`d2607f00 ffffc983`cd5cf520 00000000`000000bc fffff806`27cea180 : nt!PopIrpWatchdogBugcheck+0xea
fffff806`2a25ea10 fffff806`27f58659 : fffff806`28400400 00000000`000000ff fffff806`2a25ec18 00000000`00000008 : nt!PopIrpWatchdog+0x22
fffff806`2a25ea60 fffff806`27f595a7 : 00000000`00000004 00000000`00989680 fffff806`28400400 00000000`00000019 : nt!KiProcessExpiredTimerList+0x159
fffff806`2a25eb50 fffff806`28057e5a : 00000000`00000000 fffff806`27cea180 00000000`00000000 fffff806`28400400 : nt!KiRetireDpcList+0x4a7
fffff806`2a25ed60 00000000`00000000 : fffff806`2a25f000 fffff806`2a259000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_IMAGE_atapi.sys

BUCKET_ID: X64_0x9F_3_IMAGE_atapi.sys
 

EndlessWaves

Distinguished Member
Can you explain how your research led you to the graphics card?

From the log you've posted the first candidate would be an SATA/IDE/M.2 device as that's what the ATAPI driver mentioned usually handles. Hard drives, SSDs, DVD drives etc.

So I'd check your backups are valid as first priority, and then perhaps disconnect any secondary drives to see if it stops.
 

Joe Pineapples

Distinguished Member
Hi, the gfx card thing was before I ran the minidump through OSR Online. Had a bit of trouble getting a driver installed so had followed that thought originally. Have looked for any updated atapi drivers but to no avail. Motherboard is an old oem one and no newer Windows ones were found. I will try disconnecting the 2 dvd drives and see if that sorts it (thanks).

Its quite an old tower that originally came with Vista, so 10+ years old.
 

Joe Pineapples

Distinguished Member
Looks like I've found the culprit. One of the two DVD drives is a hybrid dvd & card reader. Had it disconnected all afternoon and no crashing/reboots. Previously it would reboot within 2mins max, guaranteed. Thanks for steering me in the right direction matey :thumbsup:
 

The latest video from AVForums

Are the TCL MiniLED TVs better than OLED? TCL Interview with Marek Maciejewski | AVForums Podcast
Subscribe to our YouTube channel
Support AVForums with Patreon

Top Bottom