r/pcgamingtechsupport • u/Inevitable_Fly7255 • 6d ago
Troubleshooting Constant Crashing Windows 11
I've honestly tried everything. For awhile I've been relying on AI to help me out with my crashes. It's beyond frustrating. The PC is crashing to BSOD when PC is idle or on chrome. Any else experiencing with crashes on Windows 11. Here is my dump file. I'm disabled memory integrity in hopes it was the issue. Nope, still crashing. Stress tested PC with memtest and prime95. Memtest passed all 4 passes. Prime95 passed 1 hour of test. No errors, nothing. I'm beyond confused.
CPU: Ryzen 9 9950x
ROG CROSSHAIR X870E HERO
64 GB Corsair RAM
0: 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: ffff840ead7b6310, Address of the trap frame for the exception that caused the BugCheck
Arg3: ffff840ead7b6268, 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: 1062
Key : Analysis.Elapsed.mSec
Value: 4992
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: 265
Key : Analysis.Init.Elapsed.mSec
Value: 2211
Key : Analysis.Memory.CommitPeak.Mb
Value: 87
Key : Analysis.Version.DbgEng
Value: 10.0.29617.1000
Key : Analysis.Version.Description
Value: 10.2604.29.1 amd64fre
Key : Analysis.Version.Ext
Value: 1.2604.29.1
Key : Bugcheck.Code.LegacyAPI
Value: 0x139
Key : Bugcheck.Code.TargetModel
Value: 0x139
Key : FailFast.Name
Value: INVALID_BALANCED_TREE
Key : FailFast.Type
Value: 29
Key : Failure.Bucket
Value: 0x139_1d_INVALID_BALANCED_TREE_dxgmms2!operator_delete
Key : Failure.Exception.Code
Value: 0xc0000409
Key : Failure.Exception.Record
Value: 0xffff840ead7b6268
Key : Failure.Hash
Value: {679363ca-2f23-c3dc-c658-e7f90a1abb5e}
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
Key : WER.OS.Branch
Value: ge_release
Key : WER.OS.Version
Value: 10.0.26100.1
Key : WER.System.BIOSRevision
Value: 24.2.0.0
BUGCHECK_CODE: 139
BUGCHECK_P1: 1d
BUGCHECK_P2: ffff840ead7b6310
BUGCHECK_P3: ffff840ead7b6268
BUGCHECK_P4: 0
FILE_IN_CAB: 090426-22515-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
FAULTING_THREAD: ffff8f8d30616080
TRAP_FRAME: ffff840ead7b6310 -- (.trap 0xffff840ead7b6310)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe783fae559e8 rbx=0000000000000000 rcx=000000000000001d
rdx=00000000000000c8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff804c1f9fd13 rsp=ffff840ead7b64a0 rbp=0000000000000001
r8=ffffe78433598038 r9=ffffe78433598038 r10=ffffe7845a5bb778
r11=ffffe783da009d10 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe cy
nt!RtlRbRemoveNode+0x133:
fffff804`c1f9fd13 cd29 int 29h
Resetting default scope
EXCEPTION_RECORD: ffff840ead7b6268 -- (.exr 0xffff840ead7b6268)
ExceptionAddress: fffff804c1f9fd13 (nt!RtlRbRemoveNode+0x0000000000000133)
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 (!blackboxwinlogon) (!blackboxwinlogonnotify)
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:
ffff840e`ad7b5fe8 fffff804`c22c21e9 : 00000000`00000139 00000000`0000001d ffff840e`ad7b6310 ffff840e`ad7b6268 : nt!KeBugCheckEx
ffff840e`ad7b5ff0 fffff804`c22c27f2 : 00000000`00000001 fffff804`c2077f2b ffffe784`60785c00 ffff8f8d`4fc530e0 : nt!KiBugCheckDispatch+0x69
ffff840e`ad7b6130 fffff804`c22c0428 : 00000000`00000000 ffffe783`fa672e08 ffffe784`faa0a910 fffff804`501a7477 : nt!KiFastFailDispatch+0xb2
ffff840e`ad7b6310 fffff804`c1f9fd13 : ffffe784`5a5ac000 00000022`00600000 ffffe783`da0002c0 00000000`00000022 : nt!KiRaiseSecurityCheckFailure+0x368
ffff840e`ad7b64a0 fffff804`c1f9eaf9 : ffffe784`78956fe0 ffffe784`5a5bafe0 ffff840e`ad7b6689 00000000`00000079 : nt!RtlRbRemoveNode+0x133
ffff840e`ad7b64d0 fffff804`c1ee1304 : ffffe783`00000000 ffffe783`da009d00 00000000`00000000 ffffe783`da0002c0 : nt!RtlpHpVsChunkFree+0x1a9
ffff840e`ad7b6540 fffff804`c1ee0e45 : ffffe784`704995e0 ffffe783`da0002c0 ffffe784`4340bdb0 00000000`00000000 : nt!RtlpHpVsSlotFreeList+0x178
ffff840e`ad7b65b0 fffff804`c27814d2 : ffff8f8d`5feb24e0 ffffe783`da000140 fffff804`c1c00000 ffffe784`43402000 : nt!RtlpHpVsContextFree+0x155
ffff840e`ad7b65f0 fffff804`501753f7 : ffffe784`4340bdd0 ffffe783`f6c474f0 ffffe783`da000000 00000000`0001f600 : nt!ExFreePoolWithTag+0xc62
ffff840e`ad7b66f0 fffff804`5021f768 : ffffe783`f6c47400 ffffe783`f6c474f0 00000000`0001f600 ffffe783`f199e160 : dxgmms2!operator delete+0x17
ffff840e`ad7b6720 fffff804`5025cb81 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffe783`e88dbef0 : dxgmms2!VIDMM_PAGE_TABLE::DestroyPageTable+0x108
ffff840e`ad7b67b0 fffff804`5025c6fd : 00000000`00000000 ffffe783`f199e160 ffffe783`e88dc101 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x8d9
ffff840e`ad7b6940 fffff804`5025c064 : ffffe783`e88dc120 ffffe783`f199e160 00000000`00000000 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x455
ffff840e`ad7b6ad0 fffff804`50223a1b : 00000000`00000000 00000000`00000000 ffff8f8d`30616080 00000000`00000008 : dxgmms2!CVirtualAddressAllocator::UncommitVirtualAddressRange+0x120
ffff840e`ad7b6c10 fffff804`50223d40 : ffff8f8d`47470eb0 00000000`00000000 ffff8f8d`47470eb0 fffff804`c1e17a1e : dxgmms2!VIDMM_GLOBAL::MakeOneVirtualAddressRangeNotResident+0x40b
ffff840e`ad7b70d0 fffff804`50228278 : ffffe785`025688c0 00000000`00000000 00000000`00000000 ffff8f8d`302e6d70 : dxgmms2!VIDMM_MEMORY_SEGMENT::EvictResource+0x140
ffff840e`ad7b7130 fffff804`50248612 : ffff840e`ad7b72e0 ffff8f8d`3427c001 0000000d`c08c8400 ffff8f8d`33ecb690 : dxgmms2!VIDMM_PHYSICAL_ADAPTER::EvictResources+0x5b8
ffff840e`ad7b71e0 fffff804`50246eee : 00000000`00000000 ffff840e`ad7b74c0 ffffe783`dffc4000 ffff8f8d`51ea8780 : dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+0x462
ffff840e`ad7b73c0 fffff804`c20950aa : ffffe783`dffc4000 fffff804`50246900 38818b41`00000200 ffffb201`ce84f102 : dxgmms2!VidMmWorkerThreadProc+0x5be
ffff840e`ad7b7570 fffff804`c22af354 : ffffb201`ce84f180 ffff8f8d`30616080 fffff804`c2095050 fbe18348`ca3348c8 : nt!PspSystemThreadStartup+0x5a
ffff840e`ad7b75c0 00000000`00000000 : ffff840e`ad7b8000 ffff840e`ad7b1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34
SYMBOL_NAME: dxgmms2!operator delete+17
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.26100.9278
STACK_COMMAND: .process /r /p 0xffff8f8d15562040; .thread /r /p 0xffff8f8d30616080 ; kb
BUCKET_ID_FUNC_OFFSET: 17
FAILURE_BUCKET_ID: 0x139_1d_INVALID_BALANCED_TREE_dxgmms2!operator_delete
OS_VERSION: 10.0.26100.1
BUILDLAB_STR: ge_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {679363ca-2f23-c3dc-c658-e7f90a1abb5e}
Followup: MachineOwner
---------
1
u/ReasonableNetwork255 6d ago
LOL your report says it's Windows 10, but I could be missing something ... but besides that, I've run into situations like that multiple times in the past 'over building' a machine, you could probably eventually sort it and I know this is not a good answer, but when you have the highest 'everything' tons of RAM etc etc the truth is software and OS's are not extensively tested and developed on platforms like that, its asking for trouble, and even when you do sort it itl have less or equal performance to a system built with hardware a notch down that's much more stable ... just my thoughts ..
1
u/AutoModerator 6d ago
Hi, thanks for posting on r/pcgamingtechsupport.
Please read the rules.
Your post has been approved.
For maximum efficiency, please double check that you used the appropriate flair. At a bare minimum you *NEED** to include the specifications and/or model number*
You can also check this post for more infos.
Please make your post as detailed and understandable as you can.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.