Question Sporadic BSODs in Windows 11 Professional ?

[darknightgarden]

MiniDumps:
https://drive.google.com/file/d/1DKD3Bf-Nm7YdwE6GK2Vl5P-iFIT_eq_l/view?usp=drive_link

Specs:

Microsoft Windows 11 Professional (x64) Build 26100.3775 (24H2)

CPU: AMD Ryzen 9 7950X3D 4.2 GHz 16-Core Processor
CPU Cooler: Deepcool LT720 85.85 CFM Liquid CPU Cooler
Motherboard: MSI MAG B650 TOMAHAWK WIFI ATX AM5 Motherboard
Memory: Corsair Vengeance RGB 32 GB (2 x 16 GB) DDR5-6000 CL30 Memory
Storage: Crucial T500 W/Heatsink 2 TB M.2-2280 PCIe 4.0 X4 NVME Solid State Drive
Storage: Western Digital WD_Black SN850X 4 TB M.2-2280 PCIe 4.0 X4 NVME Solid State Drive
Storage: Western Digital WD_Black SN850X 4 TB M.2-2280 PCIe 4.0 X4 NVME Solid State Drive
Video Card: Gigabyte GAMING OC GeForce RTX 4070 Ti SUPER 16 GB Video Card
Case: Montech SKY TWO GX ATX Mid Tower Case
Power Supply: MSI MAG A850GL PCIE5 850 W 80+ Gold Certified Fully Modular ATX Power Supply
Case Fan: Phanteks PH-F120SK 50 CFM 120 mm Fan

BIOS Version: 1.M3 - AMD AGESA ComboAm5PI 1.2.0.3a Patch A

What I've Done:

• Run tests with windows memory diagnostics, memtest86 and memtest86+ which all passed
• Turned off memory context restore
• Removed Meta Quest Link because event viewer events for it coincided at a similar time to the BSOD, I'm not sure if this was the cause and I'll have to wait and see since the BSODs are sporadic (Nope, another BSOD happened)

The BSODs seem to happen when I'm not using the computer but some of the time i have had software running in the background like qbitorrent or firefox when not using the computer.

In event viewer there is always

Event 12 Wininit,
LSASS.exe was started as a protected process with level: 4.

Before the crash

I also just had a crash today while using the computer so it may not be idle thats causing it, the minidump for this crash is here: https://drive.google.com/file/d/1SKFbRmpFS6jj7U73wJtZB15nLIHNHvcJ/view?usp=drive_link

What I have observed is that the BSODs are more common when qBittorrent is running.

 

[Fix_that_Glitch]

What power setting are you using in Windows?

 

[darknightgarden]

What power setting are you using in Windows?

High performance

 

[johnbl]

files not shared for public access

 

[darknightgarden]

files not shared for public access

Should be fixed now, didn't realise I needed to change the permissions besides sharing the links

 

[johnbl]

Should be fixed now, didn't realise I needed to change the permissions besides sharing the li

you have two programs that are messing each other up.
ffxiv_dx11.exe
fiio_usbaudio.sys Mon Feb 5 05:07:52 2024
fiio_usbaudioks.sys Mon Feb 5 05:08:44 2024

CorsairVBusDriver.sys Tue Jun 30 09:53:14 2020
CorsairVHidDriver.sys Tue Jun 30 09:53:18 2020

I would uninstall the audio driver, update the corsair icue software. update any firmware for the audio device and then reinstall the audio device

i think this is a known bug. I will see if I can find the official fix instructions.

edit update the icue software and see if you still get a bugcheck.
(looks like heap corruption due to both software packages using the same resource)

note: after the update, go into windows device manager and find the menu item to show hidden devices, check it and delete any usb device software that is greyed out.

you will also want to delete your pagefile.sys and reboot to dump corruptions that have been saved to virtual memory (pagefile.sys)
or you can google how to force windows to delete the pagefile on system restart and make the registry changes and reboot.

note: be sure to update any firmware for your audio device and your corsair device.

 

[darknightgarden]

ffxiv_dx11.exe

I don't play final fantasy and have never installed it.

I uninstalled icue ages ago due to it conflicting with openrgb and i cant find those other drivers mentioned in DevManView

 

[johnbl]

I just attempted to look at the dumps again but it looks like it returned a error and i looked at a different dump.
all of your dumps return 0x80004005 error when I attempt to extract them. (Unspecified Error)

note: could not unzip the file with explorer or the microsoft store winzip app. tried on a old zip file from another user and it still works. I would guess something is wrong with your zip file or you are using a different version to compress the file.

 

[kerberos_20]

one dump shows hypervisor crashed due to amdppm.sys driver , version shows 10.0.26100.3624 which is insider build number?
edit: ok its on release preview now (KB5053656), uninstall this update


another dump shows kaspersky antivirus (klif.sys)

another once again shows kaspersky (avp.exe)

one dump points to upnp device caused dpc watchdog violation

one crash from GCC ( GNU C Compiler?)

anyway id start with uninstalling kaspersky

 

[kerberos_20]

last dump points to storport.sys called illegal instruction, which would be storage driver incompatibility

 

[johnbl]

last dump points to storport.sys called illegal instruction, which would be storage driver incompatibility

did you do anything special to uncompress this file? both my machines returned a error.
I renamed the file name to test and retested with failure.

 

[kerberos_20]

did you do anything special to uncompress this file? both my machines returned a error.
I renamed the file name to test and retested with failure.

google has built in zip extractor, i just let it uncompress it and dl just dump
or maybe not direct google unzip, but it shows me linked app to https://zipextractor.app/

 

[johnbl]

ok, I just used windows, then that failed I tried a 3rd party unzip that also failed. Then tried a different machine. Must be some change that messed it up.

 

[kerberos_20]

ok, I just used windows, then that failed I tried a 3rd party unzip that also failed. Then tried a different machine. Must be some change that messed it up.

hmm windows zip extractor indeed throws 0x80004005 unspecified error
total commander unzips it fine and winrar also unzips it

 

[kerberos_20]

ok, I just used windows, then that failed I tried a 3rd party unzip that also failed. Then tried a different machine. Must be some change that messed it up.

okay had to do quick look, its compressed with LZMA compression, windows 10/11 doesnt supports it, it is basicly 7-zip and extension should be .7z

 

[johnbl]

ok, used the google extractor and got the first dump.

first problem: looks like you have two copies of the amd ryzen master driver running:

AMDRyzenMasterDriver.sys Mon Sep 2 23:16:28 2024
AMDRyzenMasterDriver.sys Wed Oct 30 01:52:15 2024

also this overclock driver running:
NTIOLib_X64.sys Tue Sep 10 19:37:34 2024

looks like a access violation reading from a register in the cpu
(nt!ReadAMDMsr)
I would remove both copies of the ryzen master driver and retest.
(or maybe just the older one)
not able to read the bios info from this dump
-----------
will look at the other dumps to see if there is something useful.
looks like a stack corruption, most involve the anti virus but the antivirus is always running so it is pretty common for it to be on the stack for bugchecks.
WinRing0x64.sys Sat Jul 26 06:29:37 2008

overall, I would expect the problem is caused by the two copies of ryzenmaster driver colliding.
shows up in the debugger as:
AMDRyzenMasterDriver
AMDRyzenMasterDriver_fffff805d5350000

windows adds the offset when drivers collide for loading.
I would fix this problem first and retest.

the ryzen master driver tweaks various voltages and setting of the cpu. This is the first memory dump I have ever seen with two copies running from different locations.

also, I could not read the bios info from any of your dumps. This normally means the bios is really out of date. (maybe the dump was corrupted? just not sure now)
-----------
you can download and run microsoft autoruns64 and find the 3 overclock drivers and disable or remove them and reboot and see if the problem is resolved.
https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns

i would also delete the pagefile.sys (turn off virtual memory and turn it back on)
just so that saved memory corruptions are not loaded back into memory from the pagefile.sys.
you could also google how to make windows delete the pagefile.sys on system reboot. Then make the registry changes and reboot.

 

[darknightgarden]

I just attempted to look at the dumps again but it looks like it returned a error and i looked at a different dump.
all of your dumps return 0x80004005 error when I attempt to extract them. (Unspecified Error)

note: could not unzip the file with explorer or the microsoft store winzip app. tried on a old zip file from another user and it still works. I would guess something is wrong with your zip file or you are using a different version to compress the file.

I'm using 7zip if that helps

 

[darknightgarden]

ok, used the google extractor and got the first dump.

first problem: looks like you have two copies of the amd ryzen master driver running:

AMDRyzenMasterDriver.sys Mon Sep 2 23:16:28 2024
AMDRyzenMasterDriver.sys Wed Oct 30 01:52:15 2024

also this overclock driver running:
NTIOLib_X64.sys Tue Sep 10 19:37:34 2024

looks like a access violation reading from a register in the cpu
(nt!ReadAMDMsr)
I would remove both copies of the ryzen master driver and retest.
(or maybe just the older one)
not able to read the bios info from this dump
-----------
will look at the other dumps to see if there is something useful.
looks like a stack corruption, most involve the anti virus but the antivirus is always running so it is pretty common for it to be on the stack for bugchecks.
WinRing0x64.sys Sat Jul 26 06:29:37 2008

overall, I would expect the problem is caused by the two copies of ryzenmaster driver colliding.
shows up in the debugger as:
AMDRyzenMasterDriver
AMDRyzenMasterDriver_fffff805d5350000

windows adds the offset when drivers collide for loading.
I would fix this problem first and retest.

the ryzen master driver tweaks various voltages and setting of the cpu. This is the first memory dump I have ever seen with two copies running from different locations.

also, I could not read the bios info from any of your dumps. This normally means the bios is really out of date. (maybe the dump was corrupted? just not sure now)
-----------
you can download and run microsoft autoruns64 and find the 3 overclock drivers and disable or remove them and reboot and see if the problem is resolved.
https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns

i would also delete the pagefile.sys (turn off virtual memory and turn it back on)
just so that saved memory corruptions are not loaded back into memory from the pagefile.sys.
you could also google how to make windows delete the pagefile.sys on system reboot. Then make the registry changes and reboot.

I have removed all of the AMD ryzen master drivers and clean installed my AMD drivers with the AMD cleanup utility

Now there's only one ryzen master driver there from the fresh install

I'll have to wait and see if the problem is solved

 

[darknightgarden]

Just a heads up for anyone viewing this thread

MSI Center does reinstall the ryzen master sdk on its own so I've uninstalled that and disabled it in bios

 

[darknightgarden]

No i just had another BSOD, will upload minidump later when i get the time

 

[darknightgarden]

No i just had another BSOD, will upload minidump later when i get the time

https://drive.google.com/file/d/1lzB4-Y3AAIK7VOM4X7QX2tsybfgXlXY3/view?usp=sharing

Here is the minidump

It was compressed into a zip with 7zip

 

[Zerquetch]

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

 

[darknightgarden]

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 had a look at it with windbg and it gave me the same output

I uploaded the minidump to see if anyone would see something i might have missed

I suspect that crash was caused by Libre Office since "soffice.bin" is part of the software from what i could find online

i did have it running in the background

 

[johnbl]

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)

 

[darknightgarden]

Just replying back after a while but I yahaven'had a BSOD in ages so I think this is solved