Are there frequent BSODs in Windows 11 Professional?
Are there frequent BSODs in Windows 11 Professional?
WinDbg gave me this analysis, I'll dig into deeper when I get a chance, just going to bed...
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
BugCheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffffbc81e1fade70
Arg3: ffffce80beffe8b0
Arg4: fffff80293683977
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1312
Key : Analysis.Elapsed.mSec
Value: 7903
Key : Analysis.IO.Other.Mb
Value: 8
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 24
Key : Analysis.Init.CPU.mSec
Value: 515
Key : Analysis.Init.Elapsed.mSec
Value: 55082
Key : Analysis.Memory.CommitPeak.Mb
Value: 93
Key : Analysis.Version.DbgEng
Value: 10.0.27793.1000
Key : Analysis.Version.Description
Value: 10.2410.02.02 amd64fre
Key : Analysis.Version.Ext
Value: 1.2410.2.2
Key : Bugcheck.Code.LegacyAPI
Value: 0x1000007f
Key : Bugcheck.Code.TargetModel
Value: 0x1000007f
Key : Dump.Attributes.AsUlong
Value: 0x10808
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: 0x7f_8_nt!SwapContext
Key : Failure.Hash
Value: {0a536fca-e86e-11a0-a4d4-16697b5ca16e}
Key : Hypervisor.Enlightenments.ValueHex
Value: 0x7497cf94
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key : Hypervisor.Flags.ApicEnlightened
Value: 1
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 1
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0
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: 38408431
Key : Hypervisor.Flags.ValueHex
Value: 0x24a10ef
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: 0x3f7
BUGCHECK_CODE: 7f
BUGCHECK_P1: 8
BUGCHECK_P2: ffffbc81e1fade70
BUGCHECK_P3: ffffce80beffe8b0
BUGCHECK_P4: fffff80293683977
FILE_IN_CAB: 041725-16015-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x10808
Kernel Generated Triage Dump
FAULTING_THREAD: ffffe68aa3e07240
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: soffice.bin
STACK_TEXT:
ffffce80`beffe8b0 fffff802`93683776 : 00000000`00000000 ffffce80`beffeac0 ffffbc81`e1800180 00000000`00000000 : nt!SwapContext+0x197
ffffce80`beffe8f0 fffff802`9321e9a8 : 00000000`00000047 ffffbc81`e1800198 00000000`00000000 ffffe68a`5d6b1280 : nt!KiSwapContext+0x76
ffffce80`beffea30 fffff802`93289bc3 : 00000000`00000000 00000000`00000000 ffffce80`beffebe0 00001f80`000000d2 : nt!KiSwapThread+0x928
ffffce80`beffeac0 fffff802`9322f96e : ffffbc81`e1800180 ffffe68a`a3e07240 ffffe68a`000000d2 00000261`f74af2b6 : nt!KiCommitThreadWait+0x483
ffffce80`beffeb50 fffff802`938345e5 : ffffe68a`bc47d0b0 00000000`00000001 00000000`00000006 00000000`00000000 : nt!KeWaitForMultipleObjects+0x56e
ffffce80`beffec50 fffff802`9397fcba : 00000000`00000000 fffff802`9323f426 00000000`00000001 ffffbc81`e20d1180 : nt!ObWaitForMultipleObjects+0x345
ffffce80`befff160 fffff802`9368ef58 : 00000000`00000000 00000000`00000006 ffffe68a`a3e07240 000000e3`0098f6a8 : nt!NtWaitForMultipleObjects+0x11a
ffffce80`befff3f0 00007ff8`6f25cb14 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000e3`0098f688 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`6f25cb14
SYMBOL_NAME: nt!SwapContext+197
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.26100.3775
STACK_COMMAND: .process /r /p 0xffffe68aa839e080; .thread 0xffffe68aa3e07240 ; kb
BUCKET_ID_FUNC_OFFSET: 197
FAILURE_BUCKET_ID: 0x7f_8_nt!SwapContext
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {0a536fca-e86e-11a0-a4d4-16697b5ca16e}
Followup: MachineOwner
I also checked it using windbg and got the same result.
I shared the minidump to see if anyone might have noticed something I missed.
It seems the crash was likely due to Libre Office, as "soffice.bin" is part of the software I found online.
I had it running in the background at that time.
normally for a double fault you would be looking for heating problems to the cpu or power problems to the cpu.
you should disable
AMDRyzenMasterDriver.sys Mon Sep 2 23:16:28 2024
and retest.
also, bugcheck was a panic bugcheck and I could not read the bios info from the minidump.
this happens with a overheated cpu, failing power supply, or bad overclocks. I would also look for cpu fan that stopped.
note the system uptime was over 3 days.
double fault indicates that the system hit a fault, then transfered to a fault handler but the fault handler also hit a fault so the system just gives up and calls a bugcheck. (often not a complete bugcheck since it is a panic bugcheck before the cpu fails)
Just responding after some time, but I remember having a BSOD long ago, so I think this is fixed.