Unsolved
25 Posts
2
6160
BSOD Driver Power State Failure ntoskrnl.exe
XPS 15 9570
Hi,
I am experiencing random Driver_Power_State_Failure BSODs 0x9f.
Problem started under Windows 10 a few weeks ago, all the drivers were updated. It has persisted after the update to Windows 11.
I uninstalled the latest Nvidia drivers (30.0.15.1272, A11), in Safe mode, DDU uninstaller, and installed the previous release (30.0.15.1169, A10), since I suspected the problems was the GPU. Today I had the same problem after a GPU stress test by HeavyLoad.
I uploaded all the minidups to the following link. If I check them by BlueScreenView I see ntoskrnl.exe is involved:
Any suggestion is warmly appreciated.
Best. Dam
damianop
25 Posts
0
August 6th, 2022 04:00
Edit: If I check the Nvidia drivers I see that the system has automatically reinstalled the last version (30.0.15.1272, A11). Maybe SupportAssist did it. So I try to go back to the previous Nvidia Driver release (30.0.15.1169, A10) which worked without problems until the update.
damianop
25 Posts
0
August 8th, 2022 03:00
Hi everyone,
nothing has changed, even with the previous version of the Nvidia drivers. I experienced a new BSOD driver Power State Failure ntoskrnl.exe at the startup of Windows, a few minutes ago.
I have just uploaded the last minidump file and it can be dowloaded at the following link.
Any suggestion is warmly appreciated.
Best. Dam
etchetche
5 Posts
0
August 8th, 2022 20:00
Hi, I'm having the same BSOD for the last couple of months when I updated to Win 11.
I have already tried installing lots of nvidia and intel video drivers, changing power plan settings, running support assist and windows update, and I even tried a fresh windows 10 install.. but I'm still facing the same problems. The BSOD kicks in whenever I use an app that uses hardware acceleration. Diabling this is kind of a workaround for now, but I NEED hardware acceleration.
I'm thinking it coud be a physical problem with the nvidia card or something to do with its fan or heatsink (checked temps and everything seems to be ok) or maybe something related with the latest 1.25.0 bios, which I updated sometime near my win 11 update.
I'll try rolling back to 1.24 bios and see how it goes.
Any ideas?
damianop
25 Posts
0
August 9th, 2022 01:00
Good morning,
I suspect it is something related to the power management, since I had a similar problem a few years ago and I fortunately solved it, for a while.
Have a look at the following thread please:
Dell XPS 9570 ntoskrnl.exe error in Windows 10
Do you have any external doc connected by the USB-C/Thunderbolt port? The ntoskrnl.exe BSOD which I had in 2020 (the link above) was caused by the power management of the Ethernet card (Dell DA200 doc). I had to disable the sleep mode to solve the issue.
Now I am facing a similar situation, it started under Windows 10 and it persists under Windows 11.
Probably the last updates by support assist are the origin of everything. I don't exclude the problem could be the new bios 1.25, but who knows.
What I ask to the 'experts', is there any way to understand the hardware which is responsible of the BSOD by the minidumps?
I don't expect the customer care helps since my experience with them has been more than terrible, in the last years. I have never had a problem solved by them. Sometimes google is the best customer care.
Any other user is experiencing the same issue?
Best.
Dam
etchetche
5 Posts
1
August 9th, 2022 07:00
For what I've been reading it is in fact a power management problem conflicting with a driver. In my case I'm sure it has to be the nvidia card because problems start when I enable hardware acceleration. Without doing that, there are no BSODs.
The thing is I tried everything regarding disabling sleep mode and hibernate, bumping up power plan and card settings to maximum performance, SFC /SCANNOW, DSIM, and I even tried underclocking the card by 100mhz. I followed your link and tried to restore legacy power plans and can't seem to do it. 'CsEnable' is no longer to be found in registry.
I tried reverting bios version to 1.24.0 and also tried the newly published 1.26.0 bios and I'm still experiencing the same issues.
Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\080922-10265-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff802`53a00000 PsLoadedModuleList = 0xfffff802`5462a330 Debug session time: Tue Aug 9 10:43:08.381 2022 (UTC - 3:00) System Uptime: 0 days 0:46:47.308 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ............................................ Loading User Symbols Loading unloaded module list .................. For analysis of this file, run !analyze -vnt!KeBugCheckEx: fffff802`53df88b0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff802`58883720=000000000000009f 0: 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: ffff8b03d862c360, Physical Device Object of the stack Arg3: fffff80258883750, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffff8b03d857a010, The blocked IRP Debugging Details: ------------------ *** WARNING: Unable to verify checksum for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 6234 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 25468 Key : Analysis.Init.CPU.mSec Value: 452 Key : Analysis.Init.Elapsed.mSec Value: 4083 Key : Analysis.Memory.CommitPeak.Mb Value: 104 Key : Bugcheck.Code.DumpHeader Value: 0x9f Key : Bugcheck.Code.Register Value: 0x9f Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1 FILE_IN_CAB: 080922-10265-01.dmp BUGCHECK_CODE: 9f BUGCHECK_P1: 3 BUGCHECK_P2: ffff8b03d862c360 BUGCHECK_P3: fffff80258883750 BUGCHECK_P4: ffff8b03d857a010 DRVPOWERSTATE_SUBCODE: 3 IMAGE_NAME: pci.sys MODULE_NAME: pci FAULTING_MODULE: fffff80256470000 pci BLACKBOXACPI: 1 (!blackboxacpi) BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: fffff802`58883718 fffff802`53f60047 : 00000000`0000009f 00000000`00000003 ffff8b03`d862c360 fffff802`58883750 : nt!KeBugCheckEx fffff802`58883720 fffff802`53f5ff61 : ffff8b03`d8655710 00000000`00000000 ffff8b03`f8df75e0 00000000`00000000 : nt!PopIrpWatchdogBugcheck+0xdf fffff802`58883790 fffff802`53c9da12 : ffff8b03`d8655748 fffff802`4f333180 fffff802`4f333180 ffff8b03`00000002 : nt!PopIrpWatchdog+0x31 fffff802`588837e0 fffff802`53c6766d : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`0001a26a : nt!KiProcessExpiredTimerList+0x172 fffff802`588838d0 fffff802`53dfc41e : 00000000`00000000 fffff802`4f333180 fffff802`54727a00 ffff8b03`fd452080 : nt!KiRetireDpcList+0x5dd fffff802`58883b60 00000000`00000000 : fffff802`58884000 fffff802`5887d000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e IMAGE_VERSION: 10.0.19041.1865 STACK_COMMAND: .cxr; .ecxr ; kb FAILURE_BUCKET_ID: 0x9F_3_AML!_SB.PCI0.PEG0.PG00._ON_ACPI_IMAGE_pci.sys OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {fe45222d-6294-f08d-fc4c-a4480753a8dc} Followup: MachineOwner ---------
BIOS 1.26.0 (09/08/2022)
Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\080922-10312-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff807`53c00000 PsLoadedModuleList = 0xfffff807`5482a330
Debug session time: Tue Aug 9 09:14:08.383 2022 (UTC - 3:00)
System Uptime: 0 days 0:24:19.184
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`53ff88b0 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff108`a0c87b70=000000000000009f
6: 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: ffffc28e0af30360, Physical Device Object of the stack
Arg3: fffff108a0c87ba0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffc28e0e021a20, The blocked IRP
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 6312
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 58361
Key : Analysis.Init.CPU.mSec
Value: 796
Key : Analysis.Init.Elapsed.mSec
Value: 121510
Key : Analysis.Memory.CommitPeak.Mb
Value: 93
Key : Bugcheck.Code.DumpHeader
Value: 0x9f
Key : Bugcheck.Code.Register
Value: 0x9f
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: 080922-10312-01.dmp
BUGCHECK_CODE: 9f
BUGCHECK_P1: 3
BUGCHECK_P2: ffffc28e0af30360
BUGCHECK_P3: fffff108a0c87ba0
BUGCHECK_P4: ffffc28e0e021a20
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: pci.sys
MODULE_NAME: pci
FAULTING_MODULE: fffff80755870000 pci
BLACKBOXACPI: 1 (!blackboxacpi)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: SearchFilterHost.exe
DPC_STACK_BASE: FFFFF108A0C87FB0
STACK_TEXT:
fffff108`a0c87b68 fffff807`54160047 : 00000000`0000009f 00000000`00000003 ffffc28e`0af30360 fffff108`a0c87ba0 : nt!KeBugCheckEx
fffff108`a0c87b70 fffff807`5415ff61 : ffffc28e`0af7a2c0 00000000`00000000 00000000`00000000 00000000`0000d987 : nt!PopIrpWatchdogBugcheck+0xdf
fffff108`a0c87be0 fffff807`53e9da12 : ffffc28e`0af7a2f8 ffffd601`14200180 fffff108`a0c87e68 fffff108`a0c87c98 : nt!PopIrpWatchdog+0x31
fffff108`a0c87c30 fffff807`53e6766d : ffffd601`14200180 1542fa39`00000000 00000000`00000008 00000000`0000d987 : nt!KiProcessExpiredTimerList+0x172
fffff108`a0c87d20 fffff807`53fff8f5 : c0c8a3d0`65e1e982 ffffd601`14200180 ffffc28e`08b07380 00000000`00000001 : nt!KiRetireDpcList+0x5dd
fffff108`a0c87fb0 fffff807`53fff6e0 : ffffc28e`2ffd0080 fffff807`53f2a9ea 00000000`00000000 00000000`00000281 : nt!KxRetireDpcList+0x5
fffff108`a6f779c0 fffff807`53ffef95 : 00000000`00000001 fffff807`53ffa941 00000262`28062348 00000262`00000001 : nt!KiDispatchInterruptContinue
fffff108`a6f779f0 fffff807`53ffa941 : 00000262`28062348 00000262`00000001 fffff108`a6f77a18 00000000`00000000 : nt!KiDpcInterruptBypass+0x25
fffff108`a6f77a00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xb1
IMAGE_VERSION: 10.0.19041.1865
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x9F_3_AML!_SB.PCI0.PEG0.PG00._ON_ACPI_IMAGE_pci.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {fe45222d-6294-f08d-fc4c-a4480753a8dc}
Followup: MachineOwner
---------
What troubles me most is that a fresh windows install didn't solve the problem so it has to be something outside OS config... having tried other bios versions I have no idea where else to look.
I read somewhere to try disabling Intel Power Management Driver but being a driver I don't thing it will change much.
etchetche
5 Posts
0
September 12th, 2022 13:00
Solution to my BSOD:
https://www.dell.com/community/XPS/XPS-9570-DRIVER-POWER-STATE-FAILURE-BSoD/m-p/8263259/highlight/true#M101650
It had to do with a rogue Dell app conflicting with my nvidia card.