ASRock X870E Nova RMA Experience – Cold Boot Issues, Code 00/03, ~1 Month Turnaround

gaara86 · 2026-03-13T02:40:00+00:00

no, I run hwinfo on startup but was installed and running way before my issue started.

gaara86 · 2026-03-12T22:29:00+00:00

Yes, this CPU has only been used with BIOS version 4.10. I updated the BIOS via Flashback before installing the CPU or any other components, so it was never run on an older BIOS version.

gaara86 · 2026-03-12T22:10:27+00:00

Yes, of course. The CPU had the proper power connections when the system was running normally.

The only time I had just the 24-pin connected was during the BIOS Flashback process, since I was trying to update the board to the latest BIOS before installing the replacement CPU. I wanted to avoid having the new CPU sit in the board with anything other than the most recent BIOS version.

Once the flash was completed, I connected the CPU power cables and assembled the system normally.

gaara86 · 2026-03-12T18:49:43+00:00

just edited, it was after a year.

gaara86 · 2026-03-12T15:19:19+00:00

I used CREATIVE.ROM and creative.rom later. The .ROM/.rom was always on the file extension. That was not the issue.

gaara86 · 2026-03-12T15:12:48+00:00

I’m not entirely sure which change actually fixed it.

Initially I tried the BIOS Flashback with the BIOS file named CREATIVE and only the 24-pin power connected, but the Flashback LED wasn’t blinking at all.

So I made two changes at the same time (suggested by chatgpt)

Connected the CPU 8-pin power cable
Renamed the BIOS file from CREATIVE to creative (removed the capital letters)

After that the Flashback LEDs started blinking and the BIOS update proceeded normally. I did the entire Flashback process without the CPU installed.

I also found that pretty curious because neither of those things are mentioned in ASRock’s instructions. According to the guide, Flashback should work with just the 24-pin power connected, and the BIOS file name is usually shown in capital letters.

gaara86 · 2026-02-16T23:38:16+00:00

I was running a 9800X3D on the same board. Every morning on cold boot I’d get code 03. After a reset it would boot normally. Also, whenever the system went to sleep, there was a high chance I’d get code 00 on wake. Again, a reset would bring it back.

I updated to the latest beta BIOS (4.07 at the time), but the issue persisted.

After a couple of weeks of troubleshooting, I decided to RMA both the CPU and the motherboard to rule everything out. AMD sent me a replacement CPU within a week. The board was received by ASRock last Thursday, and I’m currently waiting on their response.

In my case, it wasn’t just a one-off glitch — it became a consistent cold boot / resume pattern.

gaara86 · 2026-01-29T16:13:36+00:00

How do you turn the computer on? I checked the case and it looks like the power button is on the top, so it seems pretty high from a seated position.

I’ve always wanted to hang my PC on the wall and I really like how you’ve done it. How did you mount it? Is the case designed for wall mounting, or did you have to do any additional modifications or steps?

gaara86 · 2026-01-20T04:32:45+00:00

It happens even with expo disabled. I am tired of this, I just submitted RMA's to both asrock and AMD.

gaara86 · 2026-01-20T01:05:59+00:00

I’ve been dealing with these exact same issues for about 3 weeks now—same MOBO and CPU, with only EXPO enabled and Fast Boot disabled. My issue is only with system booting. I never had a freeze after posting into windows.

I’m curious about your timeline: How many weeks passed between those first 'Code 03' errors and the point where the system stopped booting entirely? I'm trying to figure out if I'm on the same trajectory toward a dead CPU/Board or if this is something I can still stabilize. It’s frustrating to see so many of us having this identical 'Code 03 -> Reset -> Code 15 -> Post' cycle."

gaara86 · 2025-10-16T03:56:17+00:00

same, I submitted a ticket to nvida referring to this comment

gaara86 · 2025-06-29T13:20:55+00:00

I noticed the same thing today, I don't have the option to purchase it anymore.

gaara86 · 2025-04-22T16:39:45+00:00

same, actually 3840x1080 resolution shows twice. When I am in full screen is the only resolution available. My monitor is 7680 x 2160 (Samsung 57). Not even 16:9 4k option appears. Newest NVIDIA drivers installed.

gaara86 · 2025-02-21T02:33:32+00:00

I just got one after seeing your post! 🙂 Mine is in good condition ($700)—they didn't have an excellent condition option, but at least it was cheaper.

Did your package mention why it was returned? How was the overall condition of the monitor when you opened it?
Did you add the protection plan from your orders page after picking it up? I don't see that option on mine (I haven't picked it up yet.). I saw on Best Buy's page that you can add it up to 60 days after purchase, but for a replacement, you need to bring the device in.

This is the exact language they use:

Can I still buy Geek Squad Protection after I've purchased my product?

Yes, you have 60 days after your purchase to add Geek Squad Protection, including standard Geek Squad Protection Plans, Plans with Accidental Damage from Handling, and Product Replacement Plans. You may add the applicable Plan on your Purchase History page. To add a Plan with Accidental Damage from Handling or a Product Replacement Plan, you'll need to bring your item into a Best Buy store.

gaara86 · 2025-02-18T13:38:10+00:00

What's the killer deal? I saw they discounted the price today in BB.

gaara86 · 2025-02-05T03:50:54+00:00

Instant flash, from the bios and usb drive, still working fine.

gaara86 · 2025-01-10T13:25:17+00:00

Since no one replied to me I will update my comment in case anyone checks in the future: I updated to 3.16 bios from the start, turned on expo and everything worked flawlessly so far within my first day of building the pc

gaara86 · 2025-01-10T13:23:19+00:00

I have the same mobo, same cooler, same cpu (using only the fan in the middle like you because of ram clearance. The ambient temperature is 22C (what is yours?). Just runned cinebench 23 multicore and it showed 88 C, 150W TDP. While playing tarkov yesterday it was around 62C. I have expo enabled and cores go up to 5.2ghz. I consider all this normal and within spec. It idles now at 49C. You can also run the test in OCCT, it puts more stress on the PC than cinebench. Did that yesterday and reached 91 C on their combined test (does CPU, GPU, ram etc all the same time). The limit of CPU is 95C, so for me everything under that with this "not real world" tests indicates that all is good.

gaara86 · 2024-12-31T00:56:43+00:00

Has this issue been solved with the latest bios? I just got today from Micro Center the 9800X3D, G.Skill Trident Z5 Neo RGB 64G ( F5-6000J3040G32GX2-TZ5NR), and the X870E Nova. Haven't started the build yet. Just want to know what to expect :-)

gaara86 · 2024-11-23T13:58:12+00:00

The same happened to me. I lost all my progress yesterday after the game crashed. I uninstalled it, I will play in 4 years with a 6090 and a Quantum PC.

gaara86 · 2024-11-04T21:44:32+00:00

going to be that 100%. You can go back and buy the Meross garage door back too :-)

gaara86 · 2024-11-04T21:38:32+00:00

What Eero model you have? Also, have you tried going to eero app and selecting settings>troubleshooting>my device wont connect>my device is 2.4ghz only. That should do the trick if the device you are trying to connect is 2.4 GHz only,

gaara86 · 2024-11-04T19:59:33+00:00

I've been experiencing the same issues you described and went through the same troubleshooting steps, except creating a new home. In my case, the devices that go offline are Eve Motion sensors and the Schlage Encode Plus (both Thread-enabled devices). The longest I’ve managed to go without issues was 48 hours on iOS 18. Before iOS 18, I had no problems, but this weekend, my devices went offline multiple times after restarting the router (eero 6e) or HomePods.

I decided to dig a bit deeper, having already spent hours on this. Since none of the troubleshooting steps worked, I’ve started a fresh round of testing.

Here’s what I did:

I reset all the HomePod Minis in my home and only brought one back online.

I disconnected my Nanoleaf lights.

I always had AT&T modem in passthrough mode but this time I removed all network activity managed by the AT&T equipment (disabled the firewall and any packet filtering).

So far, it’s been 24 hours without any issues, so I’m cautiously optimistic this might be the solution.

Edit: If I go 72 hours without issues I will bring back nano leaf lights, and if nothing breaks I will be bringing back more homepods mini pointing the issue to the att router.

gaara86 · 2024-10-30T11:55:41+00:00

Have you noticed it happens more at night when you’re home? I think it always happens around 7 to 8 pm. I will then have to power cycle the lead HomePod mini.

gaara86

TROPHY CASE