M
mo75ia
Guest
Hi
I got a new pc , which hangs randomly , and also gave BSOD after the latest windows update.
Windows version Windows 10 20H2 , OS Build 19042.789
Analyzing the last minidump using whocrashed:
crash dump file: C:\Windows\Minidump\020621-7250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0x9F (0x3, 0xFFFFD309DADCB060, 0xFFFFF8023E86C850, 0xFFFFD309DDEBC520)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
and with windbg
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: ffffd309dadcb060, Physical Device Object of the stack
Arg3: fffff8023e86c850, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffd309ddebc520, The blocked IRP
Debugging Details:
------------------
Implicit thread is now ffffd309`e4f96080
*** WARNING: Unable to verify timestamp for amdkmdag.sys
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 3
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on KIP-HOME
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 10
Key : Analysis.Memory.CommitPeak.Mb
Value: 83
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 9f
BUGCHECK_P1: 3
BUGCHECK_P2: ffffd309dadcb060
BUGCHECK_P3: fffff8023e86c850
BUGCHECK_P4: ffffd309ddebc520
DRVPOWERSTATE_SUBCODE: 3
FAULTING_THREAD: ffffd309e4f96080
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff8401`77101e60 fffff802`3b265850 : ffffbb00`68eca180 ffffd309`00000000 fffff802`3d31de40 00000000`00000000 : nt!KiSwapContext+0x76
ffff8401`77101fa0 fffff802`3b264d7f : fffff802`00000005 ffffbb00`00000001 ffff8401`77102190 00000000`00000000 : nt!KiSwapThread+0x500
ffff8401`77102050 fffff802`3b243d5e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x14f
ffff8401`771020f0 fffff802`510b1d65 : 00000000`00000000 fffff802`499bc591 ffffd309`df07d058 fffff802`3b2e7ee0 : nt!KeWaitForMultipleObjects+0x2be
ffff8401`77102200 00000000`00000000 : fffff802`499bc591 ffffd309`df07d058 fffff802`3b2e7ee0 ffffaafd`9c400000 : amdkmdag+0x12f1d65
STACK_COMMAND: .thread 0xffffd309e4f96080 ; kb
SYMBOL_NAME: amdkmdag+12f1d65
MODULE_NAME: amdkmdag
IMAGE_NAME: amdkmdag.sys
BUCKET_ID_FUNC_OFFSET: 12f1d65
FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_amdkmdag!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {aff31260-8acd-d807-e4e2-d1a5ea69c51a}
Followup: MachineOwner
---------
0: kd> lmvm amdkmdag
Browse full module list
start end module name
fffff802`4fdc0000 fffff802`5496f000 amdkmdag T (no symbols)
Loaded symbol image file: amdkmdag.sys
Image path: \SystemRoot\System32\DriverStore\FileRepository\u0361901.inf_amd64_204a65b18f2a904a\B361909\amdkmdag.sys
Image name: amdkmdag.sys
Browse all global symbols functions data
Timestamp: Fri Dec 4 18:24:23 2020 (5FCA62B7)
CheckSum: 04B70C3A
ImageSize: 04BAF000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
Any help figuring out what is the problem will be appriciated.
Continue reading...
I got a new pc , which hangs randomly , and also gave BSOD after the latest windows update.
Windows version Windows 10 20H2 , OS Build 19042.789
Analyzing the last minidump using whocrashed:
crash dump file: C:\Windows\Minidump\020621-7250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0x9F (0x3, 0xFFFFD309DADCB060, 0xFFFFF8023E86C850, 0xFFFFD309DDEBC520)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
and with windbg
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: ffffd309dadcb060, Physical Device Object of the stack
Arg3: fffff8023e86c850, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffd309ddebc520, The blocked IRP
Debugging Details:
------------------
Implicit thread is now ffffd309`e4f96080
*** WARNING: Unable to verify timestamp for amdkmdag.sys
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 3
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on KIP-HOME
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 10
Key : Analysis.Memory.CommitPeak.Mb
Value: 83
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 9f
BUGCHECK_P1: 3
BUGCHECK_P2: ffffd309dadcb060
BUGCHECK_P3: fffff8023e86c850
BUGCHECK_P4: ffffd309ddebc520
DRVPOWERSTATE_SUBCODE: 3
FAULTING_THREAD: ffffd309e4f96080
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff8401`77101e60 fffff802`3b265850 : ffffbb00`68eca180 ffffd309`00000000 fffff802`3d31de40 00000000`00000000 : nt!KiSwapContext+0x76
ffff8401`77101fa0 fffff802`3b264d7f : fffff802`00000005 ffffbb00`00000001 ffff8401`77102190 00000000`00000000 : nt!KiSwapThread+0x500
ffff8401`77102050 fffff802`3b243d5e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x14f
ffff8401`771020f0 fffff802`510b1d65 : 00000000`00000000 fffff802`499bc591 ffffd309`df07d058 fffff802`3b2e7ee0 : nt!KeWaitForMultipleObjects+0x2be
ffff8401`77102200 00000000`00000000 : fffff802`499bc591 ffffd309`df07d058 fffff802`3b2e7ee0 ffffaafd`9c400000 : amdkmdag+0x12f1d65
STACK_COMMAND: .thread 0xffffd309e4f96080 ; kb
SYMBOL_NAME: amdkmdag+12f1d65
MODULE_NAME: amdkmdag
IMAGE_NAME: amdkmdag.sys
BUCKET_ID_FUNC_OFFSET: 12f1d65
FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_amdkmdag!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {aff31260-8acd-d807-e4e2-d1a5ea69c51a}
Followup: MachineOwner
---------
0: kd> lmvm amdkmdag
Browse full module list
start end module name
fffff802`4fdc0000 fffff802`5496f000 amdkmdag T (no symbols)
Loaded symbol image file: amdkmdag.sys
Image path: \SystemRoot\System32\DriverStore\FileRepository\u0361901.inf_amd64_204a65b18f2a904a\B361909\amdkmdag.sys
Image name: amdkmdag.sys
Browse all global symbols functions data
Timestamp: Fri Dec 4 18:24:23 2020 (5FCA62B7)
CheckSum: 04B70C3A
ImageSize: 04BAF000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
Any help figuring out what is the problem will be appriciated.
Continue reading...