BSOD: Driver Power State Failure

neoxblu

Distinguished
Jul 15, 2009
62
0
18,640
Hi Everyone,

My fairly new ASUS GL551-JM laptop randomly gets Driver_Power_State_Failure bsod, I recently updated some drivers but it didnt help, I'm thinking of updating the BIOS next, could you guys please help me out? I've attached the windows deblogger file below system information.

Thank you,

Neoxblu

------------------
System Information
------------------
Time of this report: 5/6/2015, 21:38:40
Machine name: NEOX
Operating System: Windows 8.1 64-bit (6.3, Build 9600) (9600.winblue_r9.150322-1500)
Language: English (Regional Setting: English)
System Manufacturer: ASUSTeK COMPUTER INC.
System Model: G551JM
BIOS: G551JM.202
Processor: Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz (8 CPUs), ~2.5GHz
Memory: 16384MB RAM
Available OS Memory: 16268MB RAM
Page File: 4443MB used, 28207MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 120 DPI (125 percent)
DWM DPI Scaling: UnKnown
DxDiag Version: 6.03.9600.17415 64bit Unicode

------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Display Tab 2: No problems found.
Sound Tab 1: No problems found.
Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)

---------------
Display Devices
---------------
Card name: Intel(R) HD Graphics 4600
Manufacturer: Intel Corporation
Chip type: Intel(R) HD Graphics Family
DAC type: Internal
Device Type: Full Device
Device Key: Enum\PCI\VEN_8086&DEV_0416&SUBSYS_185D1043&REV_06
Display Memory: 4040 MB
Dedicated Memory: 1992 MB
Shared Memory: 2048 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: unknown
Monitor Id: AUO36ED
Native Mode: 1920 x 1080(p) (60.052Hz)
Output Type: Internal
Driver Name: igdumdim64.dll,igd10iumd64.dll,igd10iumd64.dll,igdumdim32,igd10iumd32,igd10iumd32
Driver File Version: 10.18.0010.3574 (English)
Driver Version: 10.18.10.3574
DDI Version: 11
Feature Levels: 11.0,10.1,10.0,9.3,9.2,9.1
Driver Model: WDDM 1.3
Graphics Preemption: DMA
Compute Preemption: Thread
Miracast: Supported
Hybrid Graphics GPU: Integrated
Power P-states: Not Supported
Driver Attributes: Final Retail
Driver Date/Size: 5/9/2014 01:16:30, 26190816 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71E3E-50D2-11CF-6760-50381FC2C435}
Vendor ID: 0x10DE
Device ID: 0x1392
SubSys ID: 0x185D1043
Revision ID: 0x00A2
Driver Strong Name: oem7.inf:5f63e534dd929195:iHSWM_w81:10.18.10.3574:pci\ven_8086&dev_0416&subsys_185d1043
Rank Of Driver: 00DA0001
D3D9 Overlay: Not Supported
DXVA-HD: Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled

Card name: NVIDIA GeForce GTX 860M
Manufacturer: NVIDIA
Chip type: GeForce GTX 860M
DAC type: Integrated RAMDAC
Device Type: Render-Only Device
Device Key: Enum\PCI\VEN_10DE&DEV_1392&SUBSYS_185D1043&REV_A2
Display Memory: 4040 MB
Dedicated Memory: 1992 MB
Shared Memory: 2048 MB
Current Mode: n/a
Driver Name: nvd3dumx,nvwgf2umx,nvwgf2umx,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 9.18.0013.5012 (English)
Driver Version: 9.18.13.5012
DDI Version: 11
Feature Levels: 11.0,10.1,10.0,9.3,9.2,9.1
Driver Model: WDDM 1.3
Graphics Preemption: DMA
Compute Preemption: DMA
Miracast: Not Supported by Graphics driver
Hybrid Graphics GPU: Discrete
Power P-states: Not Supported
Driver Attributes: Final Retail
Driver Date/Size: 4/8/2015 17:58:18, 15818528 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: n/a
Vendor ID: 0x10DE
Device ID: 0x1392
SubSys ID: 0x185D1043
Revision ID: 0x00A2
Driver Strong Name: oem55.inf:0f066de3321db02a:Section212:9.18.13.5012:pci\ven_10de&dev_1392&subsys_185d1043
Rank Of Driver: 00DA0001
Video Accel: n/a
DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeVC1_VLD DXVA2_ModeH264_VLD_NoFGT
Deinterlace Caps: n/a
D3D9 Overlay: n/a
DXVA-HD: n/a
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled

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

Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Machine Name:
Kernel base = 0xfffff802`e9288000 PsLoadedModuleList = 0xfffff802`e9561850
Debug session time: Wed May 6 21:05:07.658 2015 (UTC - 7:00)
System Uptime: 0 days 6:29:36.370
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols

Loading unloaded module list
...................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffe000bb4a8060, ffffd0018d131960, ffffe000bb4a5010}

Probably caused by : pci.sys

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe000bb4a8060, Physical Device Object of the stack
Arg3: ffffd0018d131960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe000bb4a5010, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 53d0f1d4

MODULE_NAME: pci

FAULTING_MODULE: fffff80028b74000 pci

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre

DPC_STACK_BASE: FFFFD0018D138FB0

STACK_TEXT:
ffffd001`8d131928 fffff802`e9490782 : 00000000`0000009f 00000000`00000003 ffffe000`bb4a8060 ffffd001`8d131960 : nt!KeBugCheckEx
ffffd001`8d131930 fffff802`e94906a2 : ffffe000`bb4a6a38 00000000`00000001 ffffe000`bb4a6a70 fffff802`e932c391 : nt!PopIrpWatchdogBugcheck+0xde
ffffd001`8d131990 fffff802`e932e2d8 : 00000000`00000000 ffffd001`8d131ae0 00000000`00000001 00000000`00000002 : nt!PopIrpWatchdog+0x32
ffffd001`8d1319e0 fffff802`e93dc7ea : ffffd001`8d107180 ffffd001`8d107180 ffffd001`8d1133c0 ffffe000`be215080 : nt!KiRetireDpcList+0x4f8
ffffd001`8d131c60 00000000`00000000 : ffffd001`8d132000 ffffd001`8d12c000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

IMAGE_VERSION: 6.3.9600.17238

FAILURE_BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys

BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x9f_3_acpi_image_pci.sys

FAILURE_ID_HASH: {20ddeb92-07eb-ebdc-bd08-44da71ffbd68}

Followup: MachineOwner
---------
 
I would start with a BIOS update or reset the BIOS to defaults. You want to make sure your PCI bus is not overclocked (there are execptions where you have to overclock the PCI bus)
the BIOS update/reset will make the BIOS re scan and reassign hardware settings and builds a database that is sent to windows to allow winodows to know what settings are in use.

A power state failure is generally caused when a device driver is told to go into a low power state and then told to power back up and it does not respond. This is a very common problem for device drivers written before windows 8. Windows 7 had these power states turned off by default, windows 8 turns them on by default and exposes a lot of broken hardware and bad drivers. (most vendors will have updated drivers on their motherboard vendor site) You might just go and run the various setups to get updated and just hit the correct driver. (often it will be a wireless driver that has this problem)

it can also be a bug in the BIOS so install any BIOS updates.

if you change your memory dump type to kernel, then when you bugcheck you can put the memory dump on a server and post a link and I can tell you the name of the device that is failing.

you might also be able to run cmd.exe as an admin then run
powercfg.exe /energy
and look at the report, it might indicate the name of the device that fails to respond.