• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Windows 10 errors

Joined
May 17, 2021
Messages
3,852 (2.64/day)
Processor Ryzen 5 5700x
Motherboard B550 Elite
Cooling Thermalright Perless Assassin 120 SE
Memory 32GB Fury Beast DDR4 3200Mhz
Video Card(s) Gigabyte 3060 ti gaming oc pro
Storage Samsung 970 Evo 1TB, WD SN850x 1TB, plus some random HDDs
Display(s) LG 27gp850 1440p 165Hz 27''
Case Lian Li Lancool II performance
Power Supply MSI 750w
Mouse G502
My main PC started to act strange this last few days, it all works fine except at first boot it power cycles twice (not always) and i get this error:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000139 (0x0000000000000003, 0xfffffa08f0c1a350, 0xfffffa08f0c1a2a8, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\010922-6468-01.dmp. Report Id: 8173ed7d-3e00-488d-b1d9-ff70ec7975b7.

and the minidump:

*******************************************************************************
* *
* 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: ffff818484a7d0e0, Address of the trap frame for the exception that caused the BugCheck
Arg3: ffff818484a7d038, 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: 1796

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 1793

Key : Analysis.Init.CPU.mSec
Value: 483

Key : Analysis.Init.Elapsed.mSec
Value: 30667

Key : Analysis.Memory.CommitPeak.Mb
Value: 81

Key : FailFast.Name
Value: INVALID_BALANCED_TREE

Key : FailFast.Type
Value: 29


FILE_IN_CAB: 010922-6421-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 139

BUGCHECK_P1: 1d

BUGCHECK_P2: ffff818484a7d0e0

BUGCHECK_P3: ffff818484a7d038

BUGCHECK_P4: 0

TRAP_FRAME: ffff818484a7d0e0 -- (.trap 0xffff818484a7d0e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff94096773d5c8 rbx=0000000000000000 rcx=000000000000001d
rdx=ffff9409677355c8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8066723d7df rsp=ffff818484a7d278 rbp=0000000000000059
r8=ffff9409665c85c8 r9=0000000000000000 r10=ffff94096773d5c8
r11=ffff940967c135c8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!RtlRbRemoveNode+0x1b246f:
fffff806`6723d7df cd29 int 29h
Resetting default scope

EXCEPTION_RECORD: ffff818484a7d038 -- (.exr 0xffff818484a7d038)
ExceptionAddress: fffff8066723d7df (nt!RtlRbRemoveNode+0x00000000001b246f)
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:
ffff8184`84a7cdb8 fffff806`67209069 : 00000000`00000139 00000000`0000001d ffff8184`84a7d0e0 ffff8184`84a7d038 : nt!KeBugCheckEx
ffff8184`84a7cdc0 fffff806`67209490 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff8184`84a7cf00 fffff806`67207823 : ffff8184`84a7d248 ffff8184`84a7d270 ffff9409`67713c60 fffff806`6708ae2c : nt!KiFastFailDispatch+0xd0
ffff8184`84a7d0e0 fffff806`6723d7df : 00000059`00a20000 00010000`00590000 fffff806`6708b203 00000000`00000059 : nt!KiRaiseSecurityCheckFailure+0x323
ffff8184`84a7d278 fffff806`6708b203 : 00000000`00000059 ffff9409`67735030 00000000`00000000 ffff9409`677355c0 : nt!RtlRbRemoveNode+0x1b246f
ffff8184`84a7d290 fffff806`6708ab78 : ffff9409`42200280 ffff9409`67735000 ffff9409`42200280 ffff8184`84a7d398 : nt!RtlpHpVsChunkCoalesce+0x183
ffff8184`84a7d2f0 fffff806`67089504 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff806`00000000 : nt!RtlpHpVsContextFree+0x188
ffff8184`84a7d390 fffff806`677b1149 : 00000000`00000580 ffffdb8d`d38c4938 00000000`00000001 01000000`00100000 : nt!ExFreeHeapPool+0x4d4
ffff8184`84a7d470 fffff806`6c8c702a : ffff8184`84a7d548 ffffdb8d`d3909300 00000000`00004992 ffffdb8d`b6f36180 : nt!ExFreePool+0x9
ffff8184`84a7d4a0 fffff806`6c7a5e42 : ffffdb8d`00000000 ffff9409`67619200 ffff9409`000006a1 00000000`00000000 : Ntfs!NtfsDeleteFcb+0x47a
ffff8184`84a7d520 fffff806`6c8c73fa : ffffdb8d`b91029e8 ffffdb8d`b6f36180 ffff9409`6773c5a0 ffff9409`6773c9f8 : Ntfs!NtfsTeardownFromLcb+0x272
ffff8184`84a7d5c0 fffff806`6c7939f0 : ffffdb8d`b91029e8 ffff8184`84a7d6c2 00000000`00000000 ffff9409`6773c5a0 : Ntfs!NtfsTeardownStructures+0xea
ffff8184`84a7d640 fffff806`6c875a27 : ffff8184`84a7d700 ffff9409`00000000 00000000`00000000 ffff9409`6773c500 : Ntfs!NtfsDecrementCloseCounts+0xb0
ffff8184`84a7d680 fffff806`6c874ba3 : ffffdb8d`b91029e8 ffff9409`676cf7c0 ffff9409`6773c5a0 ffffdb8d`b6f36180 : Ntfs!NtfsCommonClose+0x467
ffff8184`84a7d760 fffff806`6708f7d5 : ffffdb8d`cbe5d001 ffffdb8d`cbe5d010 ffff8184`84a7e000 ffff8184`00000002 : Ntfs!NtfsFsdClose+0x2d3
ffff8184`84a7d8a0 fffff806`666d6c5f : ffffdb8d`b60ff280 ffffdb8d`b6f2d140 ffffdb8d`d37e61ee fffff806`67089392 : nt!IofCallDriver+0x55
ffff8184`84a7d8e0 fffff806`666d4673 : ffff8184`84a7d970 00000012`a05f2000 ffffdb8d`b6f2d1a8 ffffdb8d`b2eefd80 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x28f
ffff8184`84a7d950 fffff806`6708f7d5 : ffffdb8d`d3a5c370 fffff806`67091fd8 ffffdb8d`b6ece1b0 00000000`00000000 : FLTMGR!FltpDispatch+0xa3
ffff8184`84a7d9b0 fffff806`6747907a : ffffdb8d`d3a5c370 fffff806`67498ab0 ffffdb8d`b0870a80 ffffdb8d`b0870a80 : nt!IofCallDriver+0x55
ffff8184`84a7d9f0 fffff806`674733e0 : fffff806`67498ab0 00000000`00000001 ffffdb8d`b06fa7a0 00000000`00000001 : nt!IopDeleteFile+0x13a
ffff8184`84a7da70 fffff806`67498cb4 : 00000000`00000000 ffffdb8d`d3a5c340 fffff806`67498ab0 ffffdb8d`b07aea60 : nt!ObpRemoveObjectRoutine+0x80
ffff8184`84a7dad0 fffff806`670b85f5 : ffffdb8d`d52b7040 fffff806`67498ab0 ffffdb8d`b07aea60 ffffdb8d`00000000 : nt!ObpProcessRemoveObjectQueue+0x204
ffff8184`84a7db70 fffff806`67155935 : ffffdb8d`d52b7040 00000000`00000080 ffffdb8d`b06dc100 ff060d13`00000001 : nt!ExpWorkerThread+0x105
ffff8184`84a7dc10 fffff806`671fe728 : ffffb601`cadc5180 ffffdb8d`d52b7040 fffff806`671558e0 ff00080f`ff000910 : nt!PspSystemThreadStartup+0x55
ffff8184`84a7dc60 00000000`00000000 : ffff8184`84a7e000 ffff8184`84a78000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nt!ExFreePool+9

IMAGE_NAME: Pool_Corruption

IMAGE_VERSION: 10.0.19041.1415

MODULE_NAME: Pool_Corruption

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 9

FAILURE_BUCKET_ID: 0x139_1d_INVALID_BALANCED_TREE_nt!ExFreePool

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ab43366d-59cb-5971-8e17-b53398bf3f90}

Followup: Pool_corruption
---------


It seems before these i had 2 0x000000a0 errors. Any idea what is going on here?
 
The crash dump you posted, may be a symptom of unstable RAM.
 
The crash dump you posted, may be a symptom of unstable RAM.

ok thanks, they have been running for a couple months but i will try to set them to 2133 or something with no xmp
 
Overclocks can lose stability over time, definitely a good place to start - trying at stock

Maybe update the BIOS while you're at it, lots of recent updates for AM4 boards (even 300 series)
 
Yeh, the BIOS so the latest microcode is used.
 
Overclocks can lose stability over time, definitely a good place to start - trying at stock
It may be acting flaky, just because of temps, including merely a warm room! This is more likely to happen with extreme overvolting with CPU core(s). Dunno about RAM.
I had a Radeon RX 5600 XT, where the VRAM got flaky, just because it got warm in my room, it seemed! It would cause random Cache Hierarchy Error WHEAs!
Sometimes, it was so bad that I couldn't even load a game completely before Windows 10 blacked out and rebooted itself with that WHEA reason.

The VRAM sux on that Radeon RX 5600 XT, glad I'm using that GeForce GTX 1660 Super now!

Even when I loved the Radeon RX 5600 XT! Regarding the BIOS flash, (RX 5600 XT) an objective failure has occurred! (bricked!) And the MSI B450 Tomahawk that I was using, with the debug LEDs, always pointed at the card. :( But I knew the card got doomed, even without the debug LED.

ok thanks, they have been running for a couple months but i will try to set them to 2133 or something with no xmp
The "3333 Mhz" line, made it suspect. I wonder if 3200 or 3000 would do the trick. It seems that anything else is better than 2133.

Can't say if it will make a major difference for you, as your Ryzen 5, is a Matisse, (3rd gen) but my Ryzen 5 5600X, really stinks at 2666, it was at 76 ms, IIRC! Yikes!
Looks like the sweet spot for me is 3200 or 3000 at minimum for my Vermeer! I got it down to 63 ms, IIRC! (benching with AIDA64) That was solely with XMP!
 
Last edited:
The "3333 Mhz" line, made it suspect. I wonder if 3200 or 3000 would do the trick. It seems that anything else is better than 2133.

Sorry i forgot to change the system specs. Those are my old sticks i already sold, those were solid, ran for over a year. I have this new sticks, 32GB for some time now.
 
Sorry i forgot to change the system specs. Those are my old sticks i already sold, those were solid, ran for over a year. I have this new sticks, 32GB for some time now.
32 GB in what configuration? 2 or 4 sticks? What rank?
 
Back
Top