Windows 11 24h2 keeps having bsod with slightly different errors ever since update from windows 10.

[LordRhysJones]

Hello, My PC has been frequently having BSODs since i upgraded from windows 10 to 11, I am currently running version 24H2 with the latest patch. Despite reinstalling windows multiple times including changing driver versions, The crashes still occur. I have attached my most recent bsod analyzed error which i got from WinDGB.

 

 

8: kd> !analyze -v

Loading Kernel Symbols

...............................................................

................................................................

................................................................

....................

Loading User Symbols

 

Loading unloaded module list

..........

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

 

KERNEL_SECURITY_CHECK_FAILURE (139)

A kernel component has corrupted a critical data structure. The corruption

could potentially allow a malicious user to gain control of this machine.

Arguments:

Arg1: 000000000000001d, An RTL_BALANCED_NODE RBTree entry has been corrupted.

Arg2: ffff9a8d86767560, Address of the trap frame for the exception that caused the BugCheck

Arg3: ffff9a8d867674b8, Address of the exception record for the exception that caused the BugCheck

Arg4: 0000000000000000, Reserved

 

Debugging Details:

------------------

 

 

KEY_VALUES_STRING: 1

 

Key : Analysis.CPU.mSec

Value: 1000

 

Key : Analysis.Elapsed.mSec

Value: 2389

 

Key : Analysis.IO.Other.Mb

Value: 1

 

Key : Analysis.IO.Read.Mb

Value: 1

 

Key : Analysis.IO.Write.Mb

Value: 2

 

Key : Analysis.Init.CPU.mSec

Value: 406

 

Key : Analysis.Init.Elapsed.mSec

Value: 9951

 

Key : Analysis.Memory.CommitPeak.Mb

Value: 104

 

Key : Analysis.Version.DbgEng

Value: 10.0.27829.1001

 

Key : Analysis.Version.Description

Value: 10.2503.24.01 amd64fre

 

Key : Analysis.Version.Ext

Value: 1.2503.24.1

 

Key : Bugcheck.Code.LegacyAPI

Value: 0x139

 

Key : Bugcheck.Code.TargetModel

Value: 0x139

 

Key : Dump.Attributes.AsUlong

Value: 0x21008

 

Key : Dump.Attributes.DiagDataWrittenToHeader

Value: 1

 

Key : Dump.Attributes.ErrorCode

Value: 0x0

 

Key : Dump.Attributes.KernelGeneratedTriageDump

Value: 1

 

Key : Dump.Attributes.LastLine

Value: Dump completed successfully.

 

Key : Dump.Attributes.ProgressPercentage

Value: 0

 

Key : FailFast.Name

Value: INVALID_BALANCED_TREE

 

Key : FailFast.Type

Value: 29

 

Key : Failure.Bucket

Value: 0x139_1d_INVALID_BALANCED_TREE_dxgmms2!CVirtualAddressAllocator::FreeVadVirtualAddressRangeInternal

 

Key : Failure.Exception.Code

Value: 0xc0000409

 

Key : Failure.Exception.Record

Value: 0xffff9a8d867674b8

 

Key : Failure.Hash

Value: {51096f11-6157-a1ca-b2e7-679e2416cf57}

 

 

BUGCHECK_CODE: 139

 

BUGCHECK_P1: 1d

 

BUGCHECK_P2: ffff9a8d86767560

 

BUGCHECK_P3: ffff9a8d867674b8

 

BUGCHECK_P4: 0

 

FILE_IN_CAB: 061825-9171-01.dmp

 

DUMP_FILE_ATTRIBUTES: 0x21008

Kernel Generated Triage Dump

 

FAULTING_THREAD: ffffe38896a5f180

 

TRAP_FRAME: ffff9a8d86767560 -- (.trap 0xffff9a8d86767560)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=0000000000000000 rcx=000000000000001d

rdx=ffff9b84b09cf990 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8019f41d2a4 rsp=ffff9a8d867676f8 rbp=0000000000000003

r8=ffff9b84b09e4a90 r9=0000000000000000 r10=ffff9b84b09cd890

r11=0000000000000008 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl nz na pe cy

nt!RtlpTreeDoubleRotateNodes+0x34:

fffff801`9f41d2a4 cd29 int 29h

Resetting default scope

 

EXCEPTION_RECORD: ffff9a8d867674b8 -- (.exr 0xffff9a8d867674b8)

ExceptionAddress: fffff8019f41d2a4 (nt!RtlpTreeDoubleRotateNodes+0x0000000000000034)

ExceptionCode: c0000409 (Security check failure or stack buffer overrun)

ExceptionFlags: 00000001

NumberParameters: 1

Parameter[0]: 000000000000001d

Subcode: 0x1d FAST_FAIL_INVALID_BALANCED_TREE

 

BLACKBOXBSD: 1 (!blackboxbsd)

 

 

BLACKBOXNTFS: 1 (!blackboxntfs)

 

 

BLACKBOXPNP: 1 (!blackboxpnp)

 

 

BLACKBOXWINLOGON: 1

 

CUSTOMER_CRASH_COUNT: 1

 

PROCESS_NAME: System

 

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

 

EXCEPTION_CODE_STR: c0000409

 

EXCEPTION_PARAMETER1: 000000000000001d

 

EXCEPTION_STR: 0xc0000409

 

STACK_TEXT:

ffff9a8d`86767238 fffff801`9f8b95e9 : 00000000`00000139 00000000`0000001d ffff9a8d`86767560 ffff9a8d`867674b8 : nt!KeBugCheckEx

ffff9a8d`86767240 fffff801`9f8b9bf2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69

ffff9a8d`86767380 fffff801`9f8b7828 : ffff408e`f0bf429d ffffe388`a3906080 00000000`00000000 ffffe388`a3906080 : nt!KiFastFailDispatch+0xb2

ffff9a8d`86767560 fffff801`9f41d2a4 : fffff801`9f41cf4d 00000000`00000013 ffff9b84`b09cf9a0 ffff9b84`b3e58413 : nt!KiRaiseSecurityCheckFailure+0x368

ffff9a8d`867676f8 fffff801`9f41cf4d : 00000000`00000013 ffff9b84`b09cf9a0 ffff9b84`b3e58413 00000000`00000000 : nt!RtlpTreeDoubleRotateNodes+0x34

ffff9a8d`86767700 fffff801`4f58374b : ffff9b84`b09d8010 ffff9b84`b37aa4b0 ffff9b84`b09d8010 ffff9a8d`867677f9 : nt!RtlAvlRemoveNode+0x30d

ffff9a8d`86767760 fffff801`4f582b47 : ffff9b84`a715a8c0 ffff9a8d`86767901 ffff9a8d`86767901 ffff9b84`b09d8010 : dxgmms2!CVirtualAddressAllocator::FreeVadVirtualAddressRangeInternal+0xab

ffff9a8d`867677c0 fffff801`4f5aab98 : ffff9b84`a715a8c0 00000000`00000000 ffff9a8d`86767951 ffff8901`89599180 : dxgmms2!CVirtualAddressAllocator::RemoveVaRangeFromVad+0x14f

ffff9a8d`86767810 fffff801`4f59cc73 : ffffe388`a22a1710 ffff9a8d`86767951 ffffe388`994d9000 ffff9b84`9056c860 : dxgmms2!CVirtualAddressAllocator::FreeAllocMappedVaRangeList+0x134

ffff9a8d`867678b0 fffff801`4f59aedf : ffff9b84`94980ab0 ffff9b84`9056c830 ffff9b84`9056c830 00000000`00000000 : dxgmms2!VIDMM_GLOBAL::ProcessSystemCommand+0x6c3

ffff9a8d`867679b0 fffff801`4f5a878f : ffff9b84`9056c830 ffff9a8d`86767ac9 fffff801`4f510bc0 ffffe388`994e2c20 : dxgmms2!VidMmSubmitPacket+0x15f

ffff9a8d`86767a10 fffff801`9f6a3e1a : ffffe388`96a5f101 fffff801`4f5a8000 ffff8901`89599100 066fe47f`bd9bbf02 : dxgmms2!VidMmWorkerThreadProc+0x69f

ffff9a8d`86767b30 fffff801`9f8a6754 : ffff8901`89599180 ffffe388`96a5f180 fffff801`9f6a3dc0 00000004`00000000 : nt!PspSystemThreadStartup+0x5a

ffff9a8d`86767b80 00000000`00000000 : ffff9a8d`86768000 ffff9a8d`86761000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

 

 

SYMBOL_NAME: dxgmms2!CVirtualAddressAllocator::FreeVadVirtualAddressRangeInternal+ab

 

MODULE_NAME: dxgmms2

 

IMAGE_NAME: dxgmms2.sys

 

IMAGE_VERSION: 10.0.26100.4202

 

STACK_COMMAND: .process /r /p 0xffffe3887c6d6040; .thread 0xffffe38896a5f180 ; kb

 

BUCKET_ID_FUNC_OFFSET: ab

 

FAILURE_BUCKET_ID: 0x139_1d_INVALID_BALANCED_TREE_dxgmms2!CVirtualAddressAllocator::FreeVadVirtualAddressRangeInternal

 

OSPLATFORM_TYPE: x64

 

OSNAME: Windows 10

 

FAILURE_ID_HASH: {51096f11-6157-a1ca-b2e7-679e2416cf57}

 

Followup: MachineOwner

 

-----------------------------------------

 

 

PS. I am currently running the following specs:

CPU= I7-14700KF

GPU= AMD 7900XTX

MOTHERBOARD: Gigabyte B760 AX/Gaming (I'm not exactly sure)

RAM= 32gb ddr5 5600mhz

 

I have also attached a onedrive link with both dump files from when i last reinstalled windows and now. 

https://1drv.ms/f/c/e633e9534f282710/EmyLpsv-LK9OskAqZ41Ui-sBqdw-HgAbVvk90FbX0PzdFQ?e=2zw4UD

[Bjoolz]

The two crashes are pointing to completely different things which usually means a memory issue.  Memory doesn't have to mean RAM, but it's usually the main suspect. Windows puts low priority data from RAM into the page file and loads it back in when needed so storage can look like memory (And memory can look like storage). The memory controller is in the CPU and if this fails it will just look like memory.

 

When it's storage about half of the dumps will usually blame storage or storage drivers, which I don't see here, so it's likely not storage.

 

If anything is overclocked or undervolted, remove it.

 

To test the RAM, use the machine normally with one stick at a time. If just one of the sticks cause crashes, faulty stick. If it crashes with either stick it's probably the CPU. Memory testers miss faulty RAM fairly often with DDR4 and newer so I don't trust them.

 

You do also have a 14th gen CPU and Intel made a mistake with the voltage of 13th and 14th gen CPUs where the CPUs will fry themselves over time. Almost 50% of 13900K and 14900K CPUs have failed. When they fail from this voltage issue, it looks like memory. I don't know if the CPU ran for any time without the BIOS update, but there was also yet another BIOS update less than a month because the issue wasn't completely fixed and some CPUs were still frying.  

 

Intel did extend the warranty by two years (So you have 5 years total), getting it replaced on the warranty is no problem. Updating the BIOS fixes the bug, but it won't fix an already fried CPU.

[LordRhysJones]

Okay, I last updated my bios about a month ago. Was there a new bios update since then?

 

I never had any issues when i was on windows 10, and ever since i upgraded from windows 10 to 11, which was about december 2024 time, the same day i got to windows 11, it blue screened and ever since then, it has been happening very frequently.

[Bjoolz]

5 hours ago, LordRhysJones said:

Okay, I last updated my bios about a month ago. Was there a new bios update since then?

Yes, but note again that if it's the issue the new BIOS fixes, it's already too late for that CPU. You should update regardless though. 

[LordRhysJones]

 

38 minutes ago, Bjoolz said:

Yes, but note again that if it's the issue the new BIOS fixes, it's already too late for that CPU. You should update regardless though. 

Okay thanks, It is most likely the CPU i suppose as for example one crash i have experienced was literally just closing the microsoft store which i'm aussuming interacts with the CPU then which probably causes a crash.

[Bjoolz]

9 hours ago, LordRhysJones said:

 

Okay thanks, It is most likely the CPU i suppose as for example one crash i have experienced was literally just closing the microsoft store which i'm aussuming interacts with the CPU then which probably causes a crash.

That doesn't track. Test the RAM first. 

[LordRhysJones]

9 hours ago, Bjoolz said:

That doesn't track. Test the RAM first. 

I have tested both ram sticks by removing one at a time and testing it, both sticks of my ram worked fine when.

[Bjoolz]

3 hours ago, LordRhysJones said:

I have tested both ram sticks by removing one at a time and testing it, both sticks of my ram worked fine when.

Unless it crashed very often before, you have to test each stick for longer than that. Each stick working fine on its own could suggest an issue with the speed, though the 5600 that you are using shouldn't cause issues. Maybe if the timings are really tight. It could also mean an issue with the memory controller or that the CPU just doesn't like that kit. The kit working with one stick at a time complicates things, it would be much simpler if it didn't.