Following the OC 9800X3D update, system issues persist without stable OS access.
Following the OC 9800X3D update, system issues persist without stable OS access.
I recently assembled my initial Ryzen setup using the 9800X3D on an MSI B850M Mag Mortar with 2x32GB Kingston Fury RAM at 6400MT/s. The kit fits the slot level. I activated the expo profile in BIOS and discovered a stable overclock of +150MHz with a -30mA voltage curve. I also adjusted the fabric clock to 2133MHz from the default 2000, aiming for a 2:3:3 fabric:controller:memory ratio. This configuration has kept the system stable across various stress tests and benchmarks, so everything appears normal once I launch the OS. However, booting remains inconsistent—four out of five attempts succeed, but in one case the BIOS splash appears and disappears normally, followed by a brief black screen after a successful POST. During this period, all diagnostic LEDs for the motherboard (CPU, RAM, GPU, boot device) remain inactive. I’m using the latest BIOS version for my motherboard, though I suspect this might indicate an unstable overclock. I’m considering lowering the frequency slightly or switching to the expo profile 2 (6000MT/s) with a reset of the clock to 2000MHz. I’m curious if others have encountered similar issues, especially since the symptoms—stable post-boot but failed OS entry in 20% of cases—seem unusual. Any insights would be greatly appreciated.
Ensure you're confident the overclocking or undervolting isn't responsible. Proceed by eliminating those factors and observe if the issue persists. If boot problems remain even at default settings, it suggests another source. Consider potential issues like a faulty Windows installation or SSD malfunction. However, if the boot issue disappears, it points toward overclocking or undervolting problems. Have you attempted running the system at default settings and performed boot tests?
I believe it always started up properly even with the OC in Ryzen Master until I adjusted the fabric clock to 2133MHz, though this might just be a coincidence. When I return to my computer, I plan to test it again but I was mainly curious to see if others faced similar issues.
The adjustment to FCLK might be the problem; revert it to 2GHz and verify
Avoid using 6400mhz on AMD systems. Stick to 6000mhz and lower timings. You can adjust this setting. Tip: Ensure RAM stability before experimenting with negative offset, as you may need per-core adjustments for consistency.
I'm back at my computer now. I reset the Fclk to 2000 but the problem kept happening again right away. -> The system restarts, the splash disappears, then nothing works. This isn't a permanent failure. I kept lowering the OC and switched to Basic PBO settings (not PBO advanced) so I didn't hit any clock speed limits, no undervolt, just the higher power limit. The issue still exists...
Already attempted that. After adjusting the OC, I initially used Ryzen Master for all configurations (Memory and CPU). However, when configuring EXPO in Ryzen Master, the system rejected starting due to CPU and RAM error indicators. I had to reinstall the BIOS to resolve the issue, then reconfigure EXPO in BIOS and finally focused on CPU-only OC settings within Ryzen Master.
It turned out the problem wasn't connected to the original configuration. If anyone encounters the same situation, this thread likely offers the right explanation and fix: Thanks to ChatGPT (I'm impressed) I turned on boot logging, which suggested an issue with the graphics drivers. It wasn't the drivers themselves, but rather the integrated graphics and the dedicated GPU sometimes failing to determine which driver stack should take control, leading to no one being held responsible and Windows not booting further. Disabling the internal graphics in the BIOS (Advanced/Integrated Graphics Configuration/Integrated Graphics) resolved it—by default it's set to auto.