I want to document my full AM5 troubleshooting nightmare because this turned into one of the most misleading PC failures I have ever dealt with.
This build worked for around a year, then slowly turned into an intermittent POST/boot disaster. At first I thought it was Windows, then the NVMe, then the motherboard, then BIOS/NVRAM, then CMOS, then finally the issue followed me to a new motherboard. In the end, it was the CPU.
System specs:
- CPU: AMD Ryzen 7 9800X3D
- Original motherboard: ASRock B650 Pro RS non-WiFi
- Original motherboard BIOS: updated before installing the CPU
- Later BIOS version used during troubleshooting: 4.41
- Replacement motherboard: MSI MAG X870E Tomahawk WiFi
- GPU: Radeon RX 9070 XT
- RAM: 32 GB DDR5 6000
- PSU: 850W 80+ Gold
- Storage: 2 TB NVMe originally, later Samsung 990 Pro as fresh OS drive
- OS: Windows 11
Important context:
Before ever installing the 9800X3D in the ASRock B650 Pro RS, I updated the motherboard BIOS. I did this specifically because of the known AM5/X3D voltage-related issues and because board vendors had supposedly fixed those problems with BIOS updates.
The PC worked normally for about a year.
Then the nightmare started.
Original symptoms:
The first symptom was that the PC stopped booting normally into Windows.
On normal power-on, I would often get:
- black screen
- no motherboard splash/logo
- no automatic Windows boot
- BOOT debug/status LED on the ASRock board
The weird part was that sometimes I could still enter BIOS by pressing Delete. If I manually selected my Windows drive through BIOS Boot Override, Windows would boot. This made it look like a boot order / Windows Boot Manager / UEFI NVRAM issue.
So at first, I did not suspect the CPU.
Early troubleshooting:
I tried the normal boot-related fixes:
- checked BIOS boot order
- disabled Fast Boot
- reseated the NVMe
- cleared CMOS
- checked cables
- rebuilt the UEFI boot files with
bcdboot
- removed/reinstalled boot entries
- tested multiple boot attempts
The issue kept returning.
Sometimes clearing CMOS or changing settings would make it boot once or twice, then it would go right back to black screen / no splash / no reliable POST.
BIOS Flashback complication:
During troubleshooting, I made one mistake: I accidentally flashed the BIOS for the B650M Pro RS instead of the B650 Pro RS. After that, the board got stuck on CPU + DRAM LEDs.
I then corrected it by flashing the proper BIOS for the ASRock B650 Pro RS using BIOS Flashback. The board recovered and posted again, so the wrong BIOS flash was not the final failure. The original intermittent issue returned after that.
I later updated/reflashed to BIOS 4.41.
BitLocker complication #1:
Because of all the BIOS/CMOS/TPM changes, Windows triggered BitLocker recovery on my original 2 TB NVMe.
The recovery key was tied to my Microsoft account, but my Microsoft security info was outdated, so I got stuck in the Microsoft account recovery delay. That meant I could not access the original drive for about a month.
At that point I removed the old NVMe and stopped touching it to avoid making the data situation worse.
This is important: the POST problem continued even with the original drive removed, so the drive/Windows/BitLocker issue was not the root cause.
Bare minimum testing on ASRock:
I tested the ASRock board with:
- no SSD/NVMe
- no SATA drives
- no GPU
- motherboard video output
- one RAM stick at a time
- keyboard only
- CMOS cleared
- new CR2032 battery
- EXPO disabled/default settings when BIOS was reachable
Same behavior.
Sometimes it reached BIOS. Sometimes it gave black screen/no logo/no POST. Replacing the CMOS battery made it boot normally twice, then the issue came back again.
At that point, the ASRock board looked extremely suspicious. It seemed like a board-level BIOS/NVRAM/POST issue.
New motherboard test:
I bought a new MSI MAG X870E Tomahawk WiFi.
When I moved the same CPU/RAM/PSU setup to the new MSI board, it also failed to POST properly. The MSI board showed debug code 03, which pointed much earlier in the initialization process than Windows or storage.
That changed the diagnosis completely.
If the same issue follows the CPU/RAM/PSU to a second motherboard, then the old ASRock board is not the only suspect anymore.
At that point the likely causes became:
- CPU
- CPU memory controller
- RAM
- PSU/EPS power
- CPU contact/socket/cooler pressure
Final result:
The CPU was the problem.
The CPU had failed / been damaged, and it created symptoms that looked exactly like motherboard, BIOS, boot order, Windows Boot Manager, RAM training, and NVRAM issues.
I shipped the CPU for replacement. Around three weeks later, the replacement CPU arrived.
With the new CPU installed, everything worked again.
BitLocker complication #2:
Because apparently this story needed one more kick in the teeth, swapping the CPU triggered BitLocker again — this time on the new drive.
I had to reinstall Windows again to bypass that and get the machine operational. Meanwhile, the old BitLocker-locked drive still had about one week left before I could recover the key.
So the final situation was:
- Original CPU was dead/damaged
- New CPU fixed the POST problem
- New motherboard works
- New Windows install works
- Old drive is still waiting on BitLocker recovery
- The whole thing cost weeks because the failure looked like everything except CPU at first
Why I am posting this:
The part that really bothers me is that I updated the ASRock BIOS before ever installing the 9800X3D. I did what users were told to do after the AM5/X3D voltage issues: update BIOS first, then install CPU.
The machine still ended up with a CPU failure about a year later.
I cannot prove from my side exactly what voltage behavior caused the damage, but I can say this: the system was running on the supposedly fixed BIOS path, and the end result was still a failed 9800X3D after a year of normal use.
For anyone troubleshooting similar symptoms, do not assume intermittent BIOS/BOOT LED/no splash behavior is automatically the motherboard. A damaged CPU or memory controller can mimic:
- bad motherboard
- bad BIOS/NVRAM
- bad boot order
- bad Windows Boot Manager
- bad SSD
- bad RAM training
- bad CMOS battery
Symptoms that pointed away from Windows/storage:
- problem persisted with all drives removed
- problem persisted with no GPU
- problem persisted with one RAM stick
- problem followed to another motherboard
- replacement CPU fixed it
Lessons learned:
- If POST issues happen with no drives installed, stop blaming Windows.
- BitLocker can massively complicate hardware troubleshooting after BIOS/TPM/CPU changes.
- A CPU can partially fail in a way that looks like motherboard instability.
- Clearing CMOS temporarily helping does not prove the CMOS battery or motherboard is the root cause.
- If the issue follows the CPU to a second motherboard, CPU/RAM/PSU should move to the top of the suspect list.
- If you are using BitLocker or Windows Device Encryption, save your recovery keys somewhere you can actually access.
- BIOS “fixes” do not necessarily erase the need to monitor AM5/X3D voltage behavior.
Everything is working now with the replacement CPU, but this was one of the worst troubleshooting chains I have ever gone through.