K
KevanGibbings
I have a Dell Inspiron 5379 Laptop that keep blue screening (randomly!)
It always happens when left to go to sleep or hibernate, but not every time. Did not happen for 2 days then again this morning.
I get the following message in the event log
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff8583566c6870, 0xffff80077303f750, 0xffff858369fb7860). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: eb34b479-c4b6-4649-873d-2960e316e97f.
Just before the blue screen there is an error in the Event log
Miniport Dell Giga Ethernet, {a2b388e7-513a-49f2-a28d-ee30b57ab892}, had event Fatal error: The miniport has failed to start by returning an error code from MiniportRestart
But not always
This started after installing Windows 10 feature update "20H2"
All Windows updates have been installed and all Dell drivers are the latest
I have run
sfc /scannow
and
dism /online /cleanup-image /restorehealth
I have tried removing the NIC and reinstalling
I removed the feature update and all was ok for a few days but installed again 3 days ago and got the blue screen again this morning.
I think it must be a driver problem, but identifying which one.
I have analysed memory.dmp file, but that is where I run out of ideas.
Microsoft (R) Windows Debugger Version 10.0.19041.685 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*C:\Windows\symbol_cache*Symbol information
Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`2a000000 PsLoadedModuleList = 0xfffff803`2ac2a490
Debug session time: Tue Mar 23 17:25:55.238 2021 (UTC + 0:00)
System Uptime: 1 days 5:12:10.382
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
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: ffff8583566c6870, Physical Device Object of the stack
Arg3: ffff80077303f750, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff858369fb7860, The blocked IRP
Debugging Details:
------------------
Implicit thread is now ffff8583`39ab6040
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 2
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-LTB5D1K
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 11
Key : Analysis.Memory.CommitPeak.Mb
Value: 77
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 9f
BUGCHECK_P1: 3
BUGCHECK_P2: ffff8583566c6870
BUGCHECK_P3: ffff80077303f750
BUGCHECK_P4: ffff858369fb7860
DRVPOWERSTATE_SUBCODE: 3
FAULTING_THREAD: ffff858339ab6040
ADDITIONAL_DEBUG_TEXT: DXG Power IRP timeout.
IRP_ADDRESS: ffff858369fb7860
DEVICE_OBJECT: ffff85835a8bf030
DRIVER_OBJECT: ffff858347850310
IMAGE_NAME: IndirectKmd.sys
MODULE_NAME: IndirectKmd
FAULTING_MODULE: fffff8034e880000 IndirectKmd
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
STACK_TEXT:
ffff8007`730173a0 fffff803`2a265850 : 00000028`00000008 00000000`ffffffff 00000050`00000000 ffff8583`3baf0558 : nt!KiSwapContext+0x76
ffff8007`730174e0 fffff803`2a264d7f : ffff8583`39e36000 ffff8583`39ab6040 ffff8007`730176a0 00000000`00000000 : nt!KiSwapThread+0x500
ffff8007`73017590 fffff803`2a264623 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff8583`39ab6180 : nt!KiCommitThreadWait+0x14f
ffff8007`73017630 fffff803`41b6339e : ffff8007`73017780 ffff8007`00000000 ffff8583`5a8bf100 ffff8583`52813100 : nt!KeWaitForSingleObject+0x233
ffff8007`73017720 fffff803`41b62486 : 00000000`00000003 00000000`00000010 ffff8583`5a8c0050 ffff8583`5a8c0050 : dxgkrnl!DpiRequestIoPowerState+0xbe
ffff8007`730177c0 fffff803`41b63024 : 00000000`00000000 ffff8583`69fb7860 00000000`00000004 00000000`00000004 : dxgkrnl!DpiFdoSetAdapterPowerState+0x336
ffff8007`73017880 fffff803`41b62631 : 00000000`00000001 00000000`00000000 ffff8007`7307ff00 ffff8583`69fb7f18 : dxgkrnl!DpiFdoHandleDevicePower+0x134
ffff8007`73017920 fffff803`41b63b81 : ffff8583`69fb7860 ffff8583`5a8bf180 ffff8583`5a8bf030 ffff8007`73017a40 : dxgkrnl!DpiFdoDispatchPower+0x21
ffff8007`73017950 fffff803`2a39cb29 : ffff8583`69fb7908 ffff8583`00000000 ffff8583`39ab6040 ffff8583`39ab6000 : dxgkrnl!DpiDispatchPower+0xe1
ffff8007`73017a70 fffff803`2a317e85 : 00000000`00000000 fffff803`2a39c950 00000000`00000000 00000000`0000009e : nt!PopIrpWorker+0x1d9
ffff8007`73017b10 fffff803`2a3fd2a8 : ffffc001`e8080180 ffff8583`39ab6040 fffff803`2a317e30 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff8007`73017b60 00000000`00000000 : ffff8007`73018000 ffff8007`73011000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
STACK_COMMAND: .thread 0xffff858339ab6040 ; kb
SYMBOL_NAME: IndirectKmd!VIDPN_TARGET_INFO::~VIDPN_TARGET_INFO <PERF> (IndirectKmd+0x0)+0
BUCKET_ID_FUNC_OFFSET: 0
FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_DXG_POWER_IRP_TIMEOUT_IndirectKmd!VIDPN_TARGET_INFO::_VIDPN_TARGET_INFO__PERF__(IndirectKmd+0x0)
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {e7010bde-1525-fe49-08c6-f896c6d75436}
Followup: MachineOwner
---------
Any help, would be appreciated.
Thanks in advance.
Kevan
Continue reading...
It always happens when left to go to sleep or hibernate, but not every time. Did not happen for 2 days then again this morning.
I get the following message in the event log
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff8583566c6870, 0xffff80077303f750, 0xffff858369fb7860). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: eb34b479-c4b6-4649-873d-2960e316e97f.
Just before the blue screen there is an error in the Event log
Miniport Dell Giga Ethernet, {a2b388e7-513a-49f2-a28d-ee30b57ab892}, had event Fatal error: The miniport has failed to start by returning an error code from MiniportRestart
But not always
This started after installing Windows 10 feature update "20H2"
All Windows updates have been installed and all Dell drivers are the latest
I have run
sfc /scannow
and
dism /online /cleanup-image /restorehealth
I have tried removing the NIC and reinstalling
I removed the feature update and all was ok for a few days but installed again 3 days ago and got the blue screen again this morning.
I think it must be a driver problem, but identifying which one.
I have analysed memory.dmp file, but that is where I run out of ideas.
Microsoft (R) Windows Debugger Version 10.0.19041.685 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*C:\Windows\symbol_cache*Symbol information
Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`2a000000 PsLoadedModuleList = 0xfffff803`2ac2a490
Debug session time: Tue Mar 23 17:25:55.238 2021 (UTC + 0:00)
System Uptime: 1 days 5:12:10.382
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
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: ffff8583566c6870, Physical Device Object of the stack
Arg3: ffff80077303f750, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff858369fb7860, The blocked IRP
Debugging Details:
------------------
Implicit thread is now ffff8583`39ab6040
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 2
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-LTB5D1K
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 11
Key : Analysis.Memory.CommitPeak.Mb
Value: 77
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 9f
BUGCHECK_P1: 3
BUGCHECK_P2: ffff8583566c6870
BUGCHECK_P3: ffff80077303f750
BUGCHECK_P4: ffff858369fb7860
DRVPOWERSTATE_SUBCODE: 3
FAULTING_THREAD: ffff858339ab6040
ADDITIONAL_DEBUG_TEXT: DXG Power IRP timeout.
IRP_ADDRESS: ffff858369fb7860
DEVICE_OBJECT: ffff85835a8bf030
DRIVER_OBJECT: ffff858347850310
IMAGE_NAME: IndirectKmd.sys
MODULE_NAME: IndirectKmd
FAULTING_MODULE: fffff8034e880000 IndirectKmd
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
STACK_TEXT:
ffff8007`730173a0 fffff803`2a265850 : 00000028`00000008 00000000`ffffffff 00000050`00000000 ffff8583`3baf0558 : nt!KiSwapContext+0x76
ffff8007`730174e0 fffff803`2a264d7f : ffff8583`39e36000 ffff8583`39ab6040 ffff8007`730176a0 00000000`00000000 : nt!KiSwapThread+0x500
ffff8007`73017590 fffff803`2a264623 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff8583`39ab6180 : nt!KiCommitThreadWait+0x14f
ffff8007`73017630 fffff803`41b6339e : ffff8007`73017780 ffff8007`00000000 ffff8583`5a8bf100 ffff8583`52813100 : nt!KeWaitForSingleObject+0x233
ffff8007`73017720 fffff803`41b62486 : 00000000`00000003 00000000`00000010 ffff8583`5a8c0050 ffff8583`5a8c0050 : dxgkrnl!DpiRequestIoPowerState+0xbe
ffff8007`730177c0 fffff803`41b63024 : 00000000`00000000 ffff8583`69fb7860 00000000`00000004 00000000`00000004 : dxgkrnl!DpiFdoSetAdapterPowerState+0x336
ffff8007`73017880 fffff803`41b62631 : 00000000`00000001 00000000`00000000 ffff8007`7307ff00 ffff8583`69fb7f18 : dxgkrnl!DpiFdoHandleDevicePower+0x134
ffff8007`73017920 fffff803`41b63b81 : ffff8583`69fb7860 ffff8583`5a8bf180 ffff8583`5a8bf030 ffff8007`73017a40 : dxgkrnl!DpiFdoDispatchPower+0x21
ffff8007`73017950 fffff803`2a39cb29 : ffff8583`69fb7908 ffff8583`00000000 ffff8583`39ab6040 ffff8583`39ab6000 : dxgkrnl!DpiDispatchPower+0xe1
ffff8007`73017a70 fffff803`2a317e85 : 00000000`00000000 fffff803`2a39c950 00000000`00000000 00000000`0000009e : nt!PopIrpWorker+0x1d9
ffff8007`73017b10 fffff803`2a3fd2a8 : ffffc001`e8080180 ffff8583`39ab6040 fffff803`2a317e30 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff8007`73017b60 00000000`00000000 : ffff8007`73018000 ffff8007`73011000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
STACK_COMMAND: .thread 0xffff858339ab6040 ; kb
SYMBOL_NAME: IndirectKmd!VIDPN_TARGET_INFO::~VIDPN_TARGET_INFO <PERF> (IndirectKmd+0x0)+0
BUCKET_ID_FUNC_OFFSET: 0
FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_DXG_POWER_IRP_TIMEOUT_IndirectKmd!VIDPN_TARGET_INFO::_VIDPN_TARGET_INFO__PERF__(IndirectKmd+0x0)
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {e7010bde-1525-fe49-08c6-f896c6d75436}
Followup: MachineOwner
---------
Any help, would be appreciated.
Thanks in advance.
Kevan
Continue reading...