Jump to content

Driver Power State Failure

benjaminllim
 Share
Posted

It's not just me that's having this issue then. I had this alot and then I changed PSU and haven't had it scince. So either it's a coincidence or that the PSU was on its way out. 

Have you tried turning it off and on again?

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
18 minutes ago, fixitnow said:

It's not just me that's having this issue then. I had this alot and then I changed PSU and haven't had it scince. So either it's a coincidence or that the PSU was on its way out. 

Is this on your PC or you have the same laptop as me?

Pretty sure it's the PC.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
1 hour ago, benjaminllim said:

Is this on your PC or you have the same laptop as me?

Pretty sure it's the PC.

Yeah it's pc. Reinstalling windows didn't make a difference. Maybe it's the drive connection to the board? I did ajust that too

Have you tried turning it off and on again?

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
5 minutes ago, fixitnow said:

Yeah it's pc. Reinstalling windows didn't make a difference. Maybe it's the drive connection to the board? I did ajust that too

I didn't get this issue until Fall Creators Update smh...

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
16 minutes ago, benjaminllim said:

I didn't get this issue until Fall Creators Update smh...

Hmm. Nor did I but after reinstalling windows (with the update) I had it once and then it went away. Probably just another windows bug. Interestingly I only got the bsod when I hit 100% usage. 

Have you tried turning it off and on again?

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
1 minute ago, fixitnow said:

Hmm. Nor did I but after reinstalling windows (with the update) I had it once and then it went away. Probably just another windows bug. Interestingly I only got the bsod when I hit 100% usage. 

Waiting for someone to analyse the dump files

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
1 minute ago, benjaminllim said:

Waiting for someone to analyse the dump files

If you get a program called blue screen view it can tell you a more specific code. I cannt be of much help otherwise. Sorry. :(

Have you tried turning it off and on again?

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
2 hours ago, benjaminllim said:

Waiting for someone to analyse the dump files

You have an Nvidia dGPU in your laptop? Only two of the dump files are useable, the others have a size of 0 bytes.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

In both cases for the dump files I was able to open, the memory stack shows "nvlddmkm" as the driver that caused an issue. That is a Nvidia GPU driver. It seems to possibly be related to a power setting. 

 

Update to the latest driver from Nvidia's website, and my personal advice would be to not to run Windows 10 insider builds, I believe build 16299 is an insider build IIRC.

 

Spoiler 

Windows 8 Kernel Version 16299 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff801`51814000 PsLoadedModuleList = 0xfffff801`51b75fd0
Debug session time: Thu Nov  9 10:45:03.819 2017 (UTC - 5:00)
System Uptime: 0 days 17:23:49.566
*******************************************************************************
*                                                                             *
*                        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: ffffb0061edfc060, Physical Device Object of the stack
Arg3: ffff8282b8637c40, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: ffffb006250a7550, 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:  0

MODULE_NAME: pci

FAULTING_MODULE: fffff806d2550000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
ffff8282`b8637c08 fffff801`51a45c17 : 00000000`0000009f 00000000`00000003 ffffb006`1edfc060 ffff8282`b8637c40 : nt!KeBugCheckEx
ffff8282`b8637c10 fffff801`51a45b22 : ffffb006`26a644a0 ffffd380`f585d180 00000000`000000a0 00000000`00000080 : nt!PopIrpWatchdogBugcheck+0xeb
ffff8282`b8637c70 fffff801`5187e0a3 : ffffb006`26a644d8 ffffd380`f585d180 ffff8282`b8637e68 ffffb006`1a0a1040 : nt!PopIrpWatchdog+0x22
ffff8282`b8637cc0 fffff801`5187f13d : 00000000`0000000e 00000000`00000000 00000000`00253178 ffffd380`f585d180 : nt!KiProcessExpiredTimerList+0x153
ffff8282`b8637db0 fffff801`5197caf5 : 00000000`00000000 ffffd380`f585d180 ffff8282`bd55e880 ffffb006`19b21300 : nt!KiRetireDpcList+0x43d
ffff8282`b8637fb0 fffff801`5197c900 : 00000000`00000000 fffff801`520e9356 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
ffff8282`bd55e7c0 fffff801`5197b345 : 00000000`00000000 fffff801`51979541 00000000`00000000 fffff801`520e9356 : nt!KiDispatchInterruptContinue
ffff8282`bd55e7f0 fffff801`51979541 : 00000000`00000000 fffff801`520e9356 00000000`00000000 fffff801`5197c8cf : nt!KiDpcInterruptBypass+0x25
ffff8282`bd55e800 fffff806`d7c0bdf9 : 00000002`00000087 ffffb006`25965000 00000000`00100cd0 00000000`0000101c : nt!KiInterruptDispatchNoLockNoEtw+0xb1
ffff8282`bd55e990 00000002`00000087 : ffffb006`25965000 00000000`00100cd0 00000000`0000101c ffffb006`25965000 : nvlddmkm+0x1dbdf9
ffff8282`bd55e998 ffffb006`25965000 : 00000000`00100cd0 00000000`0000101c ffffb006`25965000 fffff806`d7c0ca3f : 0x2`00000087
ffff8282`bd55e9a0 00000000`00100cd0 : 00000000`0000101c ffffb006`25965000 fffff806`d7c0ca3f ffffb006`25965000 : 0xffffb006`25965000
ffff8282`bd55e9a8 00000000`0000101c : ffffb006`25965000 fffff806`d7c0ca3f ffffb006`25965000 fffff806`d7c0c10e : 0x100cd0
ffff8282`bd55e9b0 ffffb006`25965000 : fffff806`d7c0ca3f ffffb006`25965000 fffff806`d7c0c10e 00000000`00000000 : 0x101c
ffff8282`bd55e9b8 fffff806`d7c0ca3f : ffffb006`25965000 fffff806`d7c0c10e 00000000`00000000 00000000`00000000 : 0xffffb006`25965000
ffff8282`bd55e9c0 ffffb006`25965000 : fffff806`d7c0c10e 00000000`00000000 00000000`00000000 ffffb006`25965000 : nvlddmkm+0x1dca3f
ffff8282`bd55e9c8 fffff806`d7c0c10e : 00000000`00000000 00000000`00000000 ffffb006`25965000 fffff806`d7c0bab8 : 0xffffb006`25965000
ffff8282`bd55e9d0 00000000`00000000 : 00000000`00000000 ffffb006`25965000 fffff806`d7c0bab8 ffffb006`25965000 : nvlddmkm+0x1dc10e


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_nvlddmkm_IMAGE_pci.sys

BUCKET_ID:  X64_0x9F_3_nvlddmkm_IMAGE_pci.sys

Followup: MachineOwner

 

 

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
7 hours ago, ionbasa said:

In both cases for the dump files I was able to open, the memory stack shows "nvlddmkm" as the driver that caused an issue. That is a Nvidia GPU driver. It seems to possibly be related to a power setting. 

 

Update to the latest driver from Nvidia's website, and my personal advice would be to not to run Windows 10 insider builds, I believe build 16299 is an insider build IIRC.

 

  Reveal hidden contents 


Windows 8 Kernel Version 16299 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff801`51814000 PsLoadedModuleList = 0xfffff801`51b75fd0
Debug session time: Thu Nov  9 10:45:03.819 2017 (UTC - 5:00)
System Uptime: 0 days 17:23:49.566
*******************************************************************************
*                                                                             *
*                        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: ffffb0061edfc060, Physical Device Object of the stack
Arg3: ffff8282b8637c40, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: ffffb006250a7550, 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:  0

MODULE_NAME: pci

FAULTING_MODULE: fffff806d2550000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
ffff8282`b8637c08 fffff801`51a45c17 : 00000000`0000009f 00000000`00000003 ffffb006`1edfc060 ffff8282`b8637c40 : nt!KeBugCheckEx
ffff8282`b8637c10 fffff801`51a45b22 : ffffb006`26a644a0 ffffd380`f585d180 00000000`000000a0 00000000`00000080 : nt!PopIrpWatchdogBugcheck+0xeb
ffff8282`b8637c70 fffff801`5187e0a3 : ffffb006`26a644d8 ffffd380`f585d180 ffff8282`b8637e68 ffffb006`1a0a1040 : nt!PopIrpWatchdog+0x22
ffff8282`b8637cc0 fffff801`5187f13d : 00000000`0000000e 00000000`00000000 00000000`00253178 ffffd380`f585d180 : nt!KiProcessExpiredTimerList+0x153
ffff8282`b8637db0 fffff801`5197caf5 : 00000000`00000000 ffffd380`f585d180 ffff8282`bd55e880 ffffb006`19b21300 : nt!KiRetireDpcList+0x43d
ffff8282`b8637fb0 fffff801`5197c900 : 00000000`00000000 fffff801`520e9356 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
ffff8282`bd55e7c0 fffff801`5197b345 : 00000000`00000000 fffff801`51979541 00000000`00000000 fffff801`520e9356 : nt!KiDispatchInterruptContinue
ffff8282`bd55e7f0 fffff801`51979541 : 00000000`00000000 fffff801`520e9356 00000000`00000000 fffff801`5197c8cf : nt!KiDpcInterruptBypass+0x25
ffff8282`bd55e800 fffff806`d7c0bdf9 : 00000002`00000087 ffffb006`25965000 00000000`00100cd0 00000000`0000101c : nt!KiInterruptDispatchNoLockNoEtw+0xb1
ffff8282`bd55e990 00000002`00000087 : ffffb006`25965000 00000000`00100cd0 00000000`0000101c ffffb006`25965000 : nvlddmkm+0x1dbdf9
ffff8282`bd55e998 ffffb006`25965000 : 00000000`00100cd0 00000000`0000101c ffffb006`25965000 fffff806`d7c0ca3f : 0x2`00000087
ffff8282`bd55e9a0 00000000`00100cd0 : 00000000`0000101c ffffb006`25965000 fffff806`d7c0ca3f ffffb006`25965000 : 0xffffb006`25965000
ffff8282`bd55e9a8 00000000`0000101c : ffffb006`25965000 fffff806`d7c0ca3f ffffb006`25965000 fffff806`d7c0c10e : 0x100cd0
ffff8282`bd55e9b0 ffffb006`25965000 : fffff806`d7c0ca3f ffffb006`25965000 fffff806`d7c0c10e 00000000`00000000 : 0x101c
ffff8282`bd55e9b8 fffff806`d7c0ca3f : ffffb006`25965000 fffff806`d7c0c10e 00000000`00000000 00000000`00000000 : 0xffffb006`25965000
ffff8282`bd55e9c0 ffffb006`25965000 : fffff806`d7c0c10e 00000000`00000000 00000000`00000000 ffffb006`25965000 : nvlddmkm+0x1dca3f
ffff8282`bd55e9c8 fffff806`d7c0c10e : 00000000`00000000 00000000`00000000 ffffb006`25965000 fffff806`d7c0bab8 : 0xffffb006`25965000
ffff8282`bd55e9d0 00000000`00000000 : 00000000`00000000 ffffb006`25965000 fffff806`d7c0bab8 ffffb006`25965000 : nvlddmkm+0x1dc10e


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_nvlddmkm_IMAGE_pci.sys

BUCKET_ID:  X64_0x9F_3_nvlddmkm_IMAGE_pci.sys

Followup: MachineOwner

 

 

Shouldn't I download the latest driver for my laptop from ASUS site?

 

And I just checked NVIDIA's site and I already have the latest driver installed.

Link to comment
Share on other sites
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Troubleshooting

×