UNSOLVED
D
darkman007e
1 Rookie
•
5 Posts
0
8211
July 17th, 2022 21:00
XPS 9570 DRIVER_POWER_STATE_FAILURE BSoD
Since late June 27, I've been having random BSoD with the error DRIVER_POWER_STATE_FAILURE.
I used WinDLG to try to find the root cause.
Here is what I have from my latest BSoD.
Spoiler
Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be 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 = 0xfffff801`12400000 PsLoadedModuleList = 0xfffff801`1302a2b0
Debug session time: Mon Jul 18 00:07:53.949 2022 (UTC - 4:00)
System Uptime: 1 days 1:09:05.612
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
...............................................
For analysis of this file, run !analyze -vnt!KeBugCheckEx:
fffff801`127f7dd0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe687`51e5f720=000000000000009f
4: 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: ffffd602ceb20060, Physical Device Object of the stack
Arg3: ffffe68751e5f750, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffd602fb833a40, The blocked IRP
Debugging Details:
------------------
Implicit thread is now ffffd602`cc48e040
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvdm.inf_amd64_d622d16ed9c37077\nvlddmkm.sys, Win32 error 0n2
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4874
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 5755
Key : Analysis.Init.CPU.mSec
Value: 3218
Key : Analysis.Init.Elapsed.mSec
Value: 4326
Key : Analysis.Memory.CommitPeak.Mb
Value: 104
Key : Bugcheck.Code.DumpHeader
Value: 0x9f
Key : Bugcheck.Code.KiBugCheckData
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: MEMORY.DMP
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
BUGCHECK_CODE: 9f
BUGCHECK_P1: 3
BUGCHECK_P2: ffffd602ceb20060
BUGCHECK_P3: ffffe68751e5f750
BUGCHECK_P4: ffffd602fb833a40
DRVPOWERSTATE_SUBCODE: 3
FAULTING_THREAD: ffffd602cc48e040
ADDITIONAL_DEBUG_TEXT: DXG Power IRP timeout.
IRP_ADDRESS: ffffd602fb833a40
DEVICE_OBJECT: ffffd602ceb20060
DRIVER_OBJECT: ffffd602ceaa9270
IMAGE_NAME: pci.sys
MODULE_NAME: pci
FAULTING_MODULE: fffff801170b0000 pci
BLACKBOXACPI: 1 (!blackboxacpi)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
STACK_TEXT:
ffffe687`51e1f3c0 fffff801`126550b0 : ffffc580`fce80180 fffff801`ffffffff 00000000`00000001 fffff801`170301ca : nt!KiSwapContext+0x76
ffffe687`51e1f500 fffff801`126545df : 00000000`00000001 fffff801`00000000 ffffe687`51e1f6c0 ffffd602`00000000 : nt!KiSwapThread+0x500
ffffe687`51e1f5b0 fffff801`12653e83 : 00000000`00000000 fffff801`00000000 00000000`00000000 ffffd602`cc48e180 : nt!KiCommitThreadWait+0x14f
ffffe687`51e1f650 fffff801`244019c6 : ffffe687`51e1f778 ffffd602`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x233
ffffe687`51e1f740 fffff801`24400ee1 : ffffe687`51e1f800 ffffd602`ef877700 ffffd602`ceaedde0 ffffd602`fb833c30 : dxgkrnl!DpiFdoHandleDevicePower+0x226
ffffe687`51e1f7e0 fffff801`24402431 : ffffd602`fb833a40 ffffd602`e748c180 ffffd602`e748c030 ffffe687`51e1f900 : dxgkrnl!DpiFdoDispatchPower+0x21
ffffe687`51e1f810 fffff801`2b48eb8c : ffffd602`fb2d9000 ffffd602`ea5bf000 ffffd602`fb2d9000 ffffd602`fb833c30 : dxgkrnl!DpiDispatchPower+0xe1
ffffe687`51e1f930 fffff801`2b48dc90 : ffffd602`e748c030 ffffd602`ea5bf000 ffffd602`e748c030 ffffd602`00000000 : nvlddmkm!nvDumpConfig+0x4c86fc
ffffe687`51e1fa40 fffff801`1279d629 : ffffd602`cc48e040 ffffe687`51e1faf0 ffffd602`fb833a40 ffffd602`00000000 : nvlddmkm!nvDumpConfig+0x4c7800
ffffe687`51e1fa70 fffff801`126eea75 : 00000000`00000000 fffff801`1279d450 00000000`00000000 00000000`00000138 : nt!PopIrpWorker+0x1d9
ffffe687`51e1fb10 fffff801`127ff428 : ffffc580`fd101180 ffffd602`cc48e040 fffff801`126eea20 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffe687`51e1fb60 00000000`00000000 : ffffe687`51e20000 ffffe687`51e19000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
IMAGE_VERSION: 10.0.19041.1741
STACK_COMMAND: .process /r /p 0xffffd602cc4c5080; .thread 0xffffd602cc48e040 ; kb
FAILURE_BUCKET_ID: 0x9F_3_DXG_POWER_IRP_TIMEOUT_IMAGE_pci.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {52f87b6b-6f6d-7c24-f421-639ee8689be5}
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Bitmap Dump File: Kernel address space is available, User address space may not be 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 = 0xfffff801`12400000 PsLoadedModuleList = 0xfffff801`1302a2b0 Debug session time: Mon Jul 18 00:07:53.949 2022 (UTC - 4:00) System Uptime: 1 days 1:09:05.612 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ................................................................ ........... Loading User Symbols Loading unloaded module list ............................................... For analysis of this file, run !analyze -vnt!KeBugCheckEx: fffff801`127f7dd0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe687`51e5f720=000000000000009f 4: 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: ffffd602ceb20060, Physical Device Object of the stack Arg3: ffffe68751e5f750, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffffd602fb833a40, The blocked IRP Debugging Details: ------------------ Implicit thread is now ffffd602`cc48e040 Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvdm.inf_amd64_d622d16ed9c37077\nvlddmkm.sys, Win32 error 0n2 KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 4874 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 5755 Key : Analysis.Init.CPU.mSec Value: 3218 Key : Analysis.Init.Elapsed.mSec Value: 4326 Key : Analysis.Memory.CommitPeak.Mb Value: 104 Key : Bugcheck.Code.DumpHeader Value: 0x9f Key : Bugcheck.Code.KiBugCheckData 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: MEMORY.DMP TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b BUGCHECK_CODE: 9f BUGCHECK_P1: 3 BUGCHECK_P2: ffffd602ceb20060 BUGCHECK_P3: ffffe68751e5f750 BUGCHECK_P4: ffffd602fb833a40 DRVPOWERSTATE_SUBCODE: 3 FAULTING_THREAD: ffffd602cc48e040 ADDITIONAL_DEBUG_TEXT: DXG Power IRP timeout. IRP_ADDRESS: ffffd602fb833a40 DEVICE_OBJECT: ffffd602ceb20060 DRIVER_OBJECT: ffffd602ceaa9270 IMAGE_NAME: pci.sys MODULE_NAME: pci FAULTING_MODULE: fffff801170b0000 pci BLACKBOXACPI: 1 (!blackboxacpi) BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: System STACK_TEXT: ffffe687`51e1f3c0 fffff801`126550b0 : ffffc580`fce80180 fffff801`ffffffff 00000000`00000001 fffff801`170301ca : nt!KiSwapContext+0x76 ffffe687`51e1f500 fffff801`126545df : 00000000`00000001 fffff801`00000000 ffffe687`51e1f6c0 ffffd602`00000000 : nt!KiSwapThread+0x500 ffffe687`51e1f5b0 fffff801`12653e83 : 00000000`00000000 fffff801`00000000 00000000`00000000 ffffd602`cc48e180 : nt!KiCommitThreadWait+0x14f ffffe687`51e1f650 fffff801`244019c6 : ffffe687`51e1f778 ffffd602`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x233 ffffe687`51e1f740 fffff801`24400ee1 : ffffe687`51e1f800 ffffd602`ef877700 ffffd602`ceaedde0 ffffd602`fb833c30 : dxgkrnl!DpiFdoHandleDevicePower+0x226 ffffe687`51e1f7e0 fffff801`24402431 : ffffd602`fb833a40 ffffd602`e748c180 ffffd602`e748c030 ffffe687`51e1f900 : dxgkrnl!DpiFdoDispatchPower+0x21 ffffe687`51e1f810 fffff801`2b48eb8c : ffffd602`fb2d9000 ffffd602`ea5bf000 ffffd602`fb2d9000 ffffd602`fb833c30 : dxgkrnl!DpiDispatchPower+0xe1 ffffe687`51e1f930 fffff801`2b48dc90 : ffffd602`e748c030 ffffd602`ea5bf000 ffffd602`e748c030 ffffd602`00000000 : nvlddmkm!nvDumpConfig+0x4c86fc ffffe687`51e1fa40 fffff801`1279d629 : ffffd602`cc48e040 ffffe687`51e1faf0 ffffd602`fb833a40 ffffd602`00000000 : nvlddmkm!nvDumpConfig+0x4c7800 ffffe687`51e1fa70 fffff801`126eea75 : 00000000`00000000 fffff801`1279d450 00000000`00000000 00000000`00000138 : nt!PopIrpWorker+0x1d9 ffffe687`51e1fb10 fffff801`127ff428 : ffffc580`fd101180 ffffd602`cc48e040 fffff801`126eea20 00000000`00000000 : nt!PspSystemThreadStartup+0x55 ffffe687`51e1fb60 00000000`00000000 : ffffe687`51e20000 ffffe687`51e19000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28 IMAGE_VERSION: 10.0.19041.1741 STACK_COMMAND: .process /r /p 0xffffd602cc4c5080; .thread 0xffffd602cc48e040 ; kb FAILURE_BUCKET_ID: 0x9F_3_DXG_POWER_IRP_TIMEOUT_IMAGE_pci.sys OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {52f87b6b-6f6d-7c24-f421-639ee8689be5} Followup: MachineOwner ---------
This line indicates the issues is caused by the Nvidia GPU.
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvdm.inf_amd64_d622d16ed9c37077\nvlddmkm.sys
I've performed all of this already :
-Disabled all sleep features in Windows
-Install latest Nvidia drivers
-Install Nvidia studio drivers (BSoD still happens but a bit less frequently)
-Install the Bios update (1.25.0)
-Install latest DisplayLink drivers (I use mostly an old USB 3.0 dock)
-Uninstall both Intel and Nvidia drivers
-Reinstall the latest Dell Intel and Nvidia drivers (this has initally help where I had 5 days with no BSoD as opposed to a BSoD every 1-2 days).
My only option left at this point is to reinstall Windows 10. The other weird thing is that sometime it happens when I'm using my PC but most BSoD happens when the PC hasn't been used for a while.
I have just disabled the Nvidia GPU in the device manager. We'll see in a few days what happens.
4176
1
Posted July 23rd, 2022 00:00
I have disabled the Nvidia GPU from the Device Manager and I had no BSoD since then.
4173
0
Posted July 23rd, 2022 02:00
I did something similar, I uninstalled the Nvidia GPU graphics driver and I have no BSoD after that as well. With this I am unable to use visual effects in google meet, asks to enable hardware acceleration, while I can use visual effects in zoom.
Waiting for Nvidia GPU driver update...
4142
1
Posted July 26th, 2022 15:00
Same here, repeated BSODs with DRIVER_POWER_STATE_FAILURE following an update of the BIOS and NVidia drivers. My stack dump is very different from the one posted.
Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available. Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff805`27e00000 PsLoadedModuleList = 0xfffff805`28a2a230 Debug session time: Wed Jul 27 00:03:55.859 2022 (UTC + 3:00) System Uptime: 0 days 3:46:35.735 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ................................................................ Loading User Symbols Loading unloaded module list ............................ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, ffff8007b4c0f360, ffffa1811989f750, ffff8007b4c53a20} Probably caused by : pci.sys Followup: MachineOwner --------- 8: 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: ffff8007b4c0f360, Physical Device Object of the stack Arg3: ffffa1811989f750, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffff8007b4c53a20, The blocked IRP Debugging Details: ------------------ KEY_VALUES_STRING: 1 STACKHASH_ANALYSIS: 1 TIMELINE_ANALYSIS: 1 DUMP_CLASS: 1 DUMP_QUALIFIER: 401 BUILD_VERSION_STRING: 19041.1.amd64fre.vb_release.191206-1406 SYSTEM_MANUFACTURER: Dell Inc. SYSTEM_PRODUCT_NAME: XPS 15 9570 SYSTEM_SKU: 087C BIOS_VENDOR: Dell Inc. BIOS_VERSION: 1.25.0 BIOS_DATE: 04/19/2022 BASEBOARD_MANUFACTURER: Dell Inc. BASEBOARD_PRODUCT: 0YYW9X BASEBOARD_VERSION: A06 DUMP_TYPE: 1 BUGCHECK_P1: 3 BUGCHECK_P2: ffff8007b4c0f360 BUGCHECK_P3: ffffa1811989f750 BUGCHECK_P4: ffff8007b4c53a20 DRVPOWERSTATE_SUBCODE: 3 IMAGE_NAME: pci.sys DEBUG_FLR_IMAGE_TIMESTAMP: 47055b1e MODULE_NAME: pci FAULTING_MODULE: fffff80529ba0000 pci CPU_COUNT: c CPU_MHZ: 8a0 CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 9e CPU_STEPPING: a CPU_MICROCODE: 6,9e,a,0 (F,M,S,R) SIG: F0'00000000 (cache) F0'00000000 (init) BLACKBOXACPI: 1 (!blackboxacpi) BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXPNP: 1 (!blackboxpnp) DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 ANALYSIS_SESSION_HOST: DELLXPS ANALYSIS_SESSION_TIME: 07-27-2022 01:02:45.0246 ANALYSIS_VERSION: 10.0.17763.132 amd64fre STACK_TEXT: ffffa181`1989f718 fffff805`28360547 : 00000000`0000009f 00000000`00000003 ffff8007`b4c0f360 ffffa181`1989f750 : nt!KeBugCheckEx ffffa181`1989f720 fffff805`28360461 : ffff8007`b4c1b2c0 00000000`00000000 ffff8007`d77b7220 00000000`00000000 : nt!PopIrpWatchdogBugcheck+0xdf ffffa181`1989f790 fffff805`28022782 : ffff8007`b4c1b2f8 ffffd081`ddf6f180 ffffd081`ddf6f180 00000000`00000002 : nt!PopIrpWatchdog+0x31 ffffa181`1989f7e0 fffff805`280c9bfd : 00000000`00000000 fffff805`2805e535 00000000`00140001 00000000`0007ea04 : nt!KiProcessExpiredTimerList+0x172 ffffa181`1989f8d0 fffff805`281fc0fe : ffffffff`00000000 ffffd081`ddf6f180 ffffd081`ddf7a340 ffff8007`b24e9040 : nt!KiRetireDpcList+0x5dd ffffa181`1989fb60 00000000`00000000 : ffffa181`198a0000 ffffa181`19899000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e THREAD_SHA1_HASH_MOD_FUNC: 418dcf5cc7a95525fe8ac8ffec7980c508fac304 THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 4c65ff5f309ccfd98ef088c1b3f1874e6801d38a THREAD_SHA1_HASH_MOD: ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693 FOLLOWUP_NAME: MachineOwner IMAGE_VERSION: 10.0.19041.1741 STACK_COMMAND: .thread ; .cxr ; kb FAILURE_BUCKET_ID: 0x9F_3_AML!_SB.PCI0.PEG0.PG00._ON_ACPI_IMAGE_pci.sys BUCKET_ID: 0x9F_3_AML!_SB.PCI0.PEG0.PG00._ON_ACPI_IMAGE_pci.sys PRIMARY_PROBLEM_CLASS: 0x9F_3_AML!_SB.PCI0.PEG0.PG00._ON_ACPI_IMAGE_pci.sys TARGET_TIME: 2022-07-26T21:03:55.000Z OSBUILD: 19041 OSSERVICEPACK: 0 SERVICEPACK_NUMBER: 0 OS_REVISION: 0 SUITE_MASK: 272 PRODUCT_TYPE: 1 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS OS_LOCALE: USER_LCID: 0 OSBUILD_TIMESTAMP: 2031-08-23 06:49:24 BUILDDATESTAMP_STR: 191206-1406 BUILDLAB_STR: vb_release BUILDOSVER_STR: 10.0.19041.1.amd64fre.vb_release.191206-1406 ANALYSIS_SESSION_ELAPSED_TIME: 6ba ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x9f_3_aml!_sb.pci0.peg0.pg00._on_acpi_image_pci.sys FAILURE_ID_HASH: {fe45222d-6294-f08d-fc4c-a4480753a8dc} Followup: MachineOwner ---------4047
0
Posted 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 (autocad, sketchup). 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.
Has anyone tried rolling back to 1.24 bios and see how it goes?
Any ideas would be kindly appreciated.
Thanks!
3914
3
Posted September 5th, 2022 15:00
In my particular case, the problem occured without anything connected.
I realised the problem had to do with a Dell service related to Dell apps I had installed in my pc. I found out that disabling all Dell services at startup with msconfig solved the issue. Insted of trying one by one, I just uninstalled all Dell apps and now the problem is gone.
These were the services running in my pc before I uninstalled everything.
PS. Thanks @damianop for everything!
3916
0
Posted September 5th, 2022 15:00
For me, it seems, that I get this issue when I leave my XPS idle with a portable SSD (Crucial X8) connected. When the portable SSD is not connected, then the problem does not occur. I will test out this theory tonight.
3525
0
Posted September 24th, 2022 20:00
Having the same issue on a 9560. Google TDR (Timeout Detection and Recovery), set it to 5 seconds (or disable it, altogether) and see if it helps. No guarantees...
3399
1
Posted September 29th, 2022 00:00
I've got a Dell XPS 15 9570 and have been having problems on and off for months with the DRIVER_POWER_STATE_FAILURE. Luckily my machine is still under warranty so I've had Dell service trying to fix this. A few weeks ago they replaced the motherboard, SSD, battery and a few other bits and pieces. It appeared to have fix the problem until Tuesday when I had a Nvidia driver update. Then my machine crashed 4 times in about 3 hours with BSOD and the DRIVER_POWER_STATE_FAILURE warning. I'm using a Lightroom a lot and had previously suspected it to be related to the GPU. This confirmed it. This video shows a solution for how to do a full clean re-install of the NVIDIA drivers using a utility called Display Driver Uninstaller (DDU) - https://youtu.be/_6NPVZ7sdZU . I did this on Tuesday and it appears to have fixed the issue so far (2 days with no lockups, crashes or BSOD).
925
0
Posted October 23rd, 2022 13:00
This worked for me too (disabling all Dell startup services). Thanks @etchetche !
bgmagar
2 Posts
4239
1
Posted July 18th, 2022 06:00
Any update on this?
I am getting the same issue after updating to BIOS 1.25.0
Getting BSoD almost everyday on xps 9570