I’ve been troubleshooting a recurring CS2 crash since early August that I no longer believe to be a CS2 issue but believe to actually be a steam issue. I’ve collected multiple crash dumps over several months. I'm an idiot when it comes to this stuff so forgive me if my conclusions are completely off base.

All minidumps point to the same failure pattern:
HEAP_CORRUPTION_ACTIONABLE_BlockNotBusy_DOUBLE_FREE
Exception: c0000374
Module: steamnetworkingsockets.dll
Failure Bucket: HEAP_CORRUPTION_ACTIONABLE_BlockNotBusy_DOUBLE_FREE_c0000374_steamnetworkingsockets.dll!unknown_function
Failure Hash: {d773163a-bc32-d894-224f-11a3678ecbd1}

The behavior is consistent with allocator-layout-sensitive heap corruption (e.g., double free or invalid free).

Notable:
Switching Steam branches (Stable ↔ Beta) temporarily hides the crash
After switching, crashes stop or become rare
After days/weeks of runtime, crashes gradually return and become frequent again
Pattern repeats across multiple Steam client versions
CS2 itself does not appear to be the faulting module
The failure is always inside steamnetworkingsockets.dll, not game code

System/environment notes:
Windows 11 26100 (25H2)
No overclocking
RAM tested memtest86+ and windows built in memory testing
GPU driver reinstalled (DDU)
Steam Client reinstalled cache
CS2 verified, reinstalled
No overlays (NVIDIA/Discord/Steam)
Crash appears during matchmaking or early in a match
Another player I queue with has the same crash signature

This signature appears to originate from Steam’s networking runtime, not the CS2 game client.
Heap corruption from double-free is not something environmental issues typically explain, and the reproducibility across Steam builds suggests a runtime issue.

Can provide:
Multiple recent minidumps (~200–400 MB each)
Full WinDbg analysis headers
Reproduction logs if needed

Thanks!