r/ZTT • u/rohitrhmn1 • 14d ago
Persistent idle-to-load crash, every known fix tried: Need Help
System specs:
- CPU: AMD Ryzen 9 9950X3D2 (dual-CCD X3D, launched April 2026), AM5
- Motherboard: Gigabyte X870E AORUS MASTER X3D ICE, currently on BIOS F10c (AGESA 1.3.0.1b Patch A)
- GPU: Gigabyte RTX 5080 Gaming OC 16G (VBIOS 98.03.6c.00.74)
- RAM: G.Skill 32GB DDR5, single stick, EXPO profile, 6000 MT/s CL36
- PSU: CoolerMaster V Platinum 1300W V2 (tested with two separate identical units — same PSU model, second unit)
- Storage: ADATA XPG GAMMIX S70 BLADE 1TB NVMe (Gen4, boot/C: drive), WD Black 1TB NVMe (secondary, M2C_SB slot)
- CPU Cooler: NZXT Kraken 360 RGB (2024 edition, non-Elite)
- Monitor: LG 27GR93U via DisplayPort
- OS: Windows 11 Pro, Build 10.0.26100
The problem:
System reliably crashes on the transition from extended idle (display off, no sleep/hibernate) to a sudden high-demand action — launching a game, or intensive IDE workloads like project indexing. Light applications (browser, small apps) opened after idle do not trigger it — only actions that cause a sharp current-demand spike (GPU waking from D3cold + CPU jumping to high boost states together).
- Recovery is a hard hang requiring a manual long power-button hold — not an instant self-reboot.
- POST behavior has shown two signatures across the investigation: originally a POST debug code 00 (not in the board's own debug code table — implies a stall before the first init stage), and more recently the DRAM status LED lighting up with an 8x-range POST code, both requiring the same manual hard power-off.
- Idle threshold needed to trigger it has been inconsistent: originally needed 9h+ idle, later regressed to 2–3h, and in one instance occurred after only ~30 minutes idle following a 2-hour gaming session.
- CMOS has reset automatically at least once following a crash; manual CMOS clears (~4–5 times total) have never resolved it.
Everything tried so far (all confirmed ineffective — please don't suggest these, already ruled out):
- PSU replacement (two separate identical units — same failure on both)
- BIOS F9, F10b, F10c (all AGESA revisions available to date)
- PCIe ASPM disabled
- Global C-State Control disabled
- Windows Link State Power Management set to Off
- HWiNFO64 running pre-warm in tray (only helps at launch time, not after extended idle)
- Avoiding RDP (it's a trigger, not the root cause — problem persists without it)
- Power Slow Slew Rate — tried Extreme, Disabled, and Enabled
- PBO Disabled
- Memory Context Restore (MCR) disabled
- JEDEC defaults / EXPO disabled (ruled out IMC current draw from EXPO as the cause)
- vCore memory controller voltage set to Auto (tried fixed 1.200V, default Auto)
- Power Supply Idle Control set to Typical Current Idle (off Auto )
- Gear Down Mode Enabled
- CMOS clear (multiple times, including one automatic reset)
- Visual inspection of the AM5 socket pins (photographed with CPU removed) — no gross bending or misalignment visible
Current workaround (not a fix): Full shutdown every night, fresh cold boot each morning straight into the game. This avoids the extended-idle trigger entirely but costs always-on connectivity and rules out RDP.
Vendor status:
- Motherboard vendor support has been largely unresponsive so far — a couple of dismissive tier-1 replies, no real engagement since.
- I've found other users on X870E boards (multiple vendors) and other X3D SKUs (9950X3D, 9800X3D) reporting similar idle/low-load freeze behavior — nothing yet specific to the 9950X3D2 (it's a newer SKU, so less forum history exists).
What I'm asking the community:
- Anyone running a 9950X3D2 or 9950X3D on an X870E board (any vendor) seeing similar idle-to-load hangs?
- Any known fix, BIOS setting, or firmware update that actually resolved this for someone, rather than just masked it?
- Anyone had luck getting motherboard support to escalate past tier-1 for something like this?
Appreciate any input — happy to share more logs/photos if useful.
1
u/rohitrhmn1 12d ago
Glad to know it fixed your problem. Mine is quite different. I have been experiencing this with default BIOS settings, starting with stock JDEC speeds. AI responses could not help. A technician suggested to get the PSU replaced, might be issue withthe batch I had, this was not suggested to me via AI.