Unsolved
11 Posts
1
1273
July 25th, 2022 08:00
XPS 9570, BSOD, computer has rebooted from a bug check
XPS 15 9570
I've been getting frequent BSODs lately. No discernable pattern or trigger.
I got the following from the Minidump file. Any ideas what to do?
Microsoft (R) Windows Debugger Version 10.0.22621.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\072522-15484-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are 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
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`41000000 PsLoadedModuleList = 0xfffff802`41c2a190
Debug session time: Mon Jul 25 09:10:08.089 2022 (UTC - 4:00)
System Uptime: 2 days 23:39:42.573
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
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: ffffa5062be1c060, Physical Device Object of the stack
Arg3: ffffba8e87a5f750, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffa506353e5010, The blocked IRP
Debugging Details:
------------------
Implicit thread is now ffffa506`298c6040
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4358
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 9806
Key : Analysis.Init.CPU.mSec
Value: 2359
Key : Analysis.Init.Elapsed.mSec
Value: 18765
Key : Analysis.Memory.CommitPeak.Mb
Value: 106
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: 072522-15484-01.dmp
BUGCHECK_CODE: 9f
BUGCHECK_P1: 3
BUGCHECK_P2: ffffa5062be1c060
BUGCHECK_P3: ffffba8e87a5f750
BUGCHECK_P4: ffffa506353e5010
DRVPOWERSTATE_SUBCODE: 3
FAULTING_THREAD: ffffa506298c6040
ADDITIONAL_DEBUG_TEXT: DXG Power IRP timeout.
IRP_ADDRESS: ffffa506353e5010
DEVICE_OBJECT: ffffa5062be1c060
DRIVER_OBJECT: ffffa5062b5f0dc0
IMAGE_NAME: pci.sys
MODULE_NAME: pci
FAULTING_MODULE: fffff80245970000 pci
BLACKBOXACPI: 1 (!blackboxacpi)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffba8e`87a1f3d0 fffff802`4120c970 : fffff802`3e654180 fffff802`ffffffff 00000000`00000001 fffff802`458f01ba : nt!KiSwapContext+0x76
ffffba8e`87a1f510 fffff802`4120be9f : 00000000`00000000 fffff802`0000000a ffffba8e`87a1f6d0 ffffa506`00000000 : nt!KiSwapThread+0x500
ffffba8e`87a1f5c0 fffff802`4120b743 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffa506`298c6180 : nt!KiCommitThreadWait+0x14f
ffffba8e`87a1f660 fffff802`548d3f26 : ffffba8e`87a1f788 ffffa506`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x233
ffffba8e`87a1f750 fffff802`548d3441 : ffffa506`48f44d00 ffffa506`32af77c0 ffffa506`2bd58d00 ffffa506`353e5200 : dxgkrnl!DpiFdoHandleDevicePower+0x226
ffffba8e`87a1f7f0 fffff802`548d4991 : ffffa506`353e5010 ffffa506`34309180 ffffa506`34309030 e94bd39e`4794807b : dxgkrnl!DpiFdoDispatchPower+0x21
ffffba8e`87a1f820 fffff802`579dbab6 : 00000000`00000001 ffffba8e`87a1f9d9 00000000`00000001 ffffa506`366ac000 : dxgkrnl!DpiDispatchPower+0xe1
ffffba8e`87a1f940 00000000`00000001 : ffffba8e`87a1f9d9 00000000`00000001 ffffa506`366ac000 ffffa506`00000004 : nvlddmkm+0x9bab6
ffffba8e`87a1f948 ffffba8e`87a1f9d9 : 00000000`00000001 ffffa506`366ac000 ffffa506`00000004 00000000`00000001 : 0x1
ffffba8e`87a1f950 00000000`00000001 : ffffa506`366ac000 ffffa506`00000004 00000000`00000001 00000000`00000001 : 0xffffba8e`87a1f9d9
ffffba8e`87a1f958 ffffa506`366ac000 : ffffa506`00000004 00000000`00000001 00000000`00000001 00000000`0000ffff : 0x1
ffffba8e`87a1f960 ffffa506`00000004 : 00000000`00000001 00000000`00000001 00000000`0000ffff ffffa506`366ac000 : 0xffffa506`366ac000
ffffba8e`87a1f968 00000000`00000001 : 00000000`00000001 00000000`0000ffff ffffa506`366ac000 00000000`00000000 : 0xffffa506`00000004
ffffba8e`87a1f970 00000000`00000001 : 00000000`0000ffff ffffa506`366ac000 00000000`00000000 00000000`00000000 : 0x1
ffffba8e`87a1f978 00000000`0000ffff : ffffa506`366ac000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
ffffba8e`87a1f980 ffffa506`366ac000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff
ffffba8e`87a1f988 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffa506`366ac000
IMAGE_VERSION: 10.0.19041.1165
STACK_COMMAND: .process /r /p 0xffffa506298c50c0; .thread 0xffffa506298c6040 ; 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
---------
0 events found
No Events found!
Tech_Query
1 Message
1
July 28th, 2022 07:00
HI,
I am also facing this issue on several Precision 5560/5540/5510/5520 Models as well as Lattitude 7480/7280/7490/5420
Is this an issue with Dell or Microsoft impact Dell devices only ?
******************************************************************************
* *
* 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: ffffbc88813c7060, Physical Device Object of the stack
Arg3: fffff406acc3f150, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffbc888d758ba0, The blocked IRP
Debugging Details:
------------------
Implicit thread is now ffffbc88`7c51a040
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 5890
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 8411
Key : Analysis.Init.CPU.mSec
Value: 21327
Key : Analysis.Init.Elapsed.mSec
Value: 865054
Key : Analysis.Memory.CommitPeak.Mb
Value: 114
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: 072822-10609-01.dmp
BUGCHECK_CODE: 9f
BUGCHECK_P1: 3
BUGCHECK_P2: ffffbc88813c7060
BUGCHECK_P3: fffff406acc3f150
BUGCHECK_P4: ffffbc888d758ba0
DRVPOWERSTATE_SUBCODE: 3
FAULTING_THREAD: ffffbc887c51a040
ADDITIONAL_DEBUG_TEXT: DXG Power IRP timeout.
IRP_ADDRESS: ffffbc888d758ba0
DEVICE_OBJECT: ffffbc88813c7060
DRIVER_OBJECT: ffffbc888138dc70
IMAGE_NAME: pci.sys
MODULE_NAME: pci
FAULTING_MODULE: fffff8065d2a0000 pci
BLACKBOXACPI: 1 (!blackboxacpi)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff406`acc16dc0 fffff806`5ac37890 : fffff806`5550d180 fffff806`00000000 00000000`00000001 fffff806`00000000 : nt!KiSwapContext+0x76
fffff406`acc16f00 fffff806`5ac36dbf : 00000000`00000000 fffff806`0000000a fffff406`acc170c0 ffffbc88`00000000 : nt!KiSwapThread+0x500
fffff406`acc16fb0 fffff806`5ac36663 : 00000000`00000000 fffff806`00000000 00000000`00000000 ffffbc88`7c51a180 : nt!KiCommitThreadWait+0x14f
fffff406`acc17050 fffff806`70d129c6 : fffff406`acc17178 ffffbc88`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x233
fffff406`acc17140 fffff806`70d11ee1 : ffffbc88`7fcf8400 00000000`00989680 ffffbc88`813baaa0 ffffbc88`8d758d90 : dxgkrnl!DpiFdoHandleDevicePower+0x226
fffff406`acc171e0 fffff806`70d13431 : ffffbc88`8d758ba0 ffffbc88`86c38180 ffffbc88`86c38030 00000000`0000004c : dxgkrnl!DpiFdoDispatchPower+0x21
fffff406`acc17210 fffff806`76c06c32 : ffffbc88`8ebe5000 00000000`00000001 ffffbc88`8ebe5000 ffffbc88`86eae000 : dxgkrnl!DpiDispatchPower+0xe1
fffff406`acc17330 ffffbc88`8ebe5000 : 00000000`00000001 ffffbc88`8ebe5000 ffffbc88`86eae000 ffffbc88`00000004 : nvlddmkm+0xea6c32
fffff406`acc17338 00000000`00000001 : ffffbc88`8ebe5000 ffffbc88`86eae000 ffffbc88`00000004 fffff406`00000000 : 0xffffbc88`8ebe5000
fffff406`acc17340 ffffbc88`8ebe5000 : ffffbc88`86eae000 ffffbc88`00000004 fffff406`00000000 ffffbc88`00000001 : 0x1
fffff406`acc17348 ffffbc88`86eae000 : ffffbc88`00000004 fffff406`00000000 ffffbc88`00000001 fffff406`000000ff : 0xffffbc88`8ebe5000
fffff406`acc17350 ffffbc88`00000004 : fffff406`00000000 ffffbc88`00000001 fffff406`000000ff ffffbc88`86eae000 : 0xffffbc88`86eae000
fffff406`acc17358 fffff406`00000000 : ffffbc88`00000001 fffff406`000000ff ffffbc88`86eae000 fffff406`acc17360 : 0xffffbc88`00000004
fffff406`acc17360 ffffbc88`00000001 : fffff406`000000ff ffffbc88`86eae000 fffff406`acc17360 00000000`00000008 : 0xfffff406`00000000
fffff406`acc17368 fffff406`000000ff : ffffbc88`86eae000 fffff406`acc17360 00000000`00000008 fffff406`acc173a0 : 0xffffbc88`00000001
fffff406`acc17370 ffffbc88`86eae000 : fffff406`acc17360 00000000`00000008 fffff406`acc173a0 00000000`00000022 : 0xfffff406`000000ff
fffff406`acc17378 fffff406`acc17360 : 00000000`00000008 fffff406`acc173a0 00000000`00000022 ffffbc88`7c51a180 : 0xffffbc88`86eae000
fffff406`acc17380 00000000`00000008 : fffff406`acc173a0 00000000`00000022 ffffbc88`7c51a180 00690072`0044005c : 0xfffff406`acc17360
fffff406`acc17388 fffff406`acc173a0 : 00000000`00000022 ffffbc88`7c51a180 00690072`0044005c 005c0072`00650076 : 0x8
fffff406`acc17390 00000000`00000022 : ffffbc88`7c51a180 00690072`0044005c 005c0072`00650076 ffffbaf2`b36c8c7a : 0xfffff406`acc173a0
fffff406`acc17398 ffffbc88`7c51a180 : 00690072`0044005c 005c0072`00650076 ffffbaf2`b36c8c7a 006d006b`006d0064 : 0x22
fffff406`acc173a0 00690072`0044005c : 005c0072`00650076 ffffbaf2`b36c8c7a 006d006b`006d0064 ffffa901`641ce000 : 0xffffbc88`7c51a180
fffff406`acc173a8 005c0072`00650076 : ffffbaf2`b36c8c7a 006d006b`006d0064 ffffa901`641ce000 00000000`00000001 : 0x00690072`0044005c
fffff406`acc173b0 ffffbaf2`b36c8c7a : 006d006b`006d0064 ffffa901`641ce000 00000000`00000001 4e503f74`6e164758 : 0x005c0072`00650076
fffff406`acc173b8 006d006b`006d0064 : ffffa901`641ce000 00000000`00000001 4e503f74`6e164758 72d2a6d4`fa57bc9e : 0xffffbaf2`b36c8c7a
fffff406`acc173c0 ffffa901`641ce000 : 00000000`00000001 4e503f74`6e164758 72d2a6d4`fa57bc9e 00000000`00000000 : 0x006d006b`006d0064
fffff406`acc173c8 00000000`00000001 : 4e503f74`6e164758 72d2a6d4`fa57bc9e 00000000`00000000 ffffbc88`9203c000 : 0xffffa901`641ce000
fffff406`acc173d0 4e503f74`6e164758 : 72d2a6d4`fa57bc9e 00000000`00000000 ffffbc88`9203c000 00000000`00000001 : 0x1
fffff406`acc173d8 72d2a6d4`fa57bc9e : 00000000`00000000 ffffbc88`9203c000 00000000`00000001 ffffa901`641ce000 : 0x4e503f74`6e164758
fffff406`acc173e0 00000000`00000000 : ffffbc88`9203c000 00000000`00000001 ffffa901`641ce000 00000000`00000000 : 0x72d2a6d4`fa57bc9e
IMAGE_VERSION: 10.0.19041.1826
STACK_COMMAND: .process /r /p 0xffffbc887c502080; .thread 0xffffbc887c51a040 ; 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
Thanks
Nost152
2 Posts
0
August 7th, 2022 08:00
I have the same problem too!!!
JCeditor
2 Posts
0
August 26th, 2022 00:00
I have had the same problem since an update since July of 2022. This is very suspicious and definitely related to a software issue. Minidumps have identified causes from Ntoskrnl.exe. no errors determined with memtest, sfc scan found no integrity violations. Full reinstall did nothing, bios updated no change, different driver combos attempted with no change, even with laptop on cooling stand to keep thermals down, no change.
DELL-Chris M
Community Manager
•
56.9K Posts
0
October 20th, 2022 11:00
Verify that the Laptop pre-Windows ePSA diagnostics passes
Run the Intel DSA (Driver & Support Assistant) to see if it finds better drivers
How to Run Windows Startup Repair on a Dell computer