How to interpret Windows minidump files?
How to interpret Windows minidump files?
Hi,
I have a new Dell laptop and pretty much every time it goes to sleep it crashes with error code 0x9f
I have done all WIndows updates, driver updates and BIOS update, this seems to be a fairly common problem with Dell laptops
I have 5 minidump files I can upload somewhere if needed
I have analysed the dump file with Windbg and it gives the following output but I don't really know what to make from it
Thanks
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000005, The device failed to complete a directed power transition within the required
amount of time.
Arg2: ffff830fb8d60dd0, Physical Device Object of the stack
Arg3: ffff830fb8fb4010, The POP_FX_DEVICE object
Arg4: 0000000000000000, nt!TRIAGE_9F_DIRECTED_TRANSITION on Win11 SV2 and higher.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 828
Key : Analysis.Elapsed.mSec
Value: 5673
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 78
Key : Analysis.Init.Elapsed.mSec
Value: 11433
Key : Analysis.Memory.CommitPeak.Mb
Value: 102
Key : Analysis.Version.DbgEng
Value: 10.0.27725.1000
Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre
Key : Analysis.Version.Ext
Value: 1.2408.27.1
Key : Bugcheck.Code.LegacyAPI
Value: 0x9f
Key : Bugcheck.Code.TargetModel
Value: 0x9f
Key : Dump.Attributes.AsUlong
Value: 1808
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: 0x9F_5_nt!PopFxDirectedWorkOrderWatchdog
Key : Failure.Hash
Value: {da85288c-1a50-174b-7827-291ce60ff821}
Key : Hypervisor.Enlightenments.ValueHex
Value: 1417df84
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key : Hypervisor.Flags.ApicEnlightened
Value: 0
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 1
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1
Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1
Key : Hypervisor.Flags.Epf
Value: 0
Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1
Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1
Key : Hypervisor.Flags.MaxBankNumber
Value: 0
Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0
Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0
Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1
Key : Hypervisor.Flags.Phase0InitDone
Value: 1
Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key : Hypervisor.Flags.RootScheduler
Value: 0
Key : Hypervisor.Flags.SynicAvailable
Value: 1
Key : Hypervisor.Flags.UseQpcBias
Value: 0
Key : Hypervisor.Flags.Value
Value: 21631230
Key : Hypervisor.Flags.ValueHex
Value: 14a10fe
Key : Hypervisor.Flags.VpAssistPage
Value: 1
Key : Hypervisor.Flags.VsmAvailable
Value: 1
Key : Hypervisor.RootFlags.AccessStats
Value: 1
Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1
Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1
Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key : Hypervisor.RootFlags.IsHyperV
Value: 1
Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1
Key : Hypervisor.RootFlags.MceEnlightened
Value: 1
Key : Hypervisor.RootFlags.Nested
Value: 0
Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1
Key : Hypervisor.RootFlags.Value
Value: 1015
Key : Hypervisor.RootFlags.ValueHex
Value: 3f7
BUGCHECK_CODE: 9f
BUGCHECK_P1: 5
BUGCHECK_P2: ffff830fb8d60dd0
BUGCHECK_P3: ffff830fb8fb4010
BUGCHECK_P4: 0
FILE_IN_CAB: 112724-12484-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump
FAULTING_THREAD: fffff8077414d700
DRVPOWERSTATE_SUBCODE: 5
DEVICE_OBJECT:
ffff830fb8ec4280
BLACKBOXBSD: 1 (
!blackboxbsd
)
BLACKBOXNTFS: 1 (
!blackboxntfs
)
BLACKBOXPNP: 1 (
!blackboxpnp
)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff807`797e8758 fffff807`73987657 : 00000000`0000009f 00000000`00000005 ffff830f`b8d60dd0 ffff830f`b8fb4010 : nt!KeBugCheckEx
fffff807`797e8760 fffff807`73611b4b : ffff830f`00000004 ffff830f`00000001 fffff807`00000000 ffff830f`00000002 : nt!PopFxDirectedWorkOrderWatchdog+0x27
fffff807`797e87a0 fffff807`73612ed9 : fffff79f`0001fea8 00000000`00989680 fffff807`6fee1180 fffff807`6fee7b68 : nt!KiProcessExpiredTimerList+0x1eb
fffff807`797e88d0 fffff807`73819fae : 00000000`0000176c fffff807`6fee1180 fffff807`7414d700 ffff830f`bca0e080 : nt!KiRetireDpcList+0xaf9
fffff807`797e8b80 00000000`00000000 : fffff807`797e9000 fffff807`797e2000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e
SYMBOL_NAME: nt!PopFxDirectedWorkOrderWatchdog+27
MODULE_NAME:
nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.22621.4455
STACK_COMMAND: .process /r /p 0xfffff80774149f40; .thread 0xfffff8077414d700 ; kb
BUCKET_ID_FUNC_OFFSET: 27
FAILURE_BUCKET_ID: 0x9F_5_nt!PopFxDirectedWorkOrderWatchdog
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {da85288c-1a50-174b-7827-291ce60ff821}
Followup: MachineOwner
I own a new Dell laptop with the specified model and SKU.
All Windows updates, driver updates, and BIOS updates have been applied, which appears to be a typical issue for Dell devices.
Have you attempted reinstalling the operating system via a bootable USB, then installing it in offline mode, followed by installing all required drivers using the latest version through an elevated command? (Right click installer > Run as Administrator?)
I have five minidump files available for upload to a platform such as DropBox or similar services.
Uninstall Norton Security, it came with the laptop and it's a mess. One of the dumps (112724-12718-01.dmp) fails due to a Norton driver (nllVmm.sys). The rest are power transition issues, probably caused by Norton too. In my opinion, it's just junk. Winders Defender and Windows Firewall are all you need.
It's my wife's laptop and it's not here at the moment, though I'm 99% sure I took out any Norton or McAfee software that came pre-installed. I'll double-check tomorrow.
I'll try using the Norton removal tool as well and let you know.
Thanks
Certainly use the Norton Removal Tool. Simply uninstalling from Apps & Features isn’t sufficient. There are still multiple Norton drivers installed, so it won’t be fully removed. This is what’s causing the issue.
You don’t need third-party security software; Windows Firewall and Defender are more than adequate.
Norton and McAffe are both problematic, and combining them was disastrous. I’d remove both, but make sure to use the right tools instead of a standard uninstall.