X870E NOVA Boot issue/BIOS loop
Printed From: ASRock.com
Category: Technical Support
Forum Name: AMD Motherboards
Forum Description: Question about ASRock AMD motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=113326
Printed Date: 01 Nov 2025 at 6:07am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: X870E NOVA Boot issue/BIOS loop
Posted By: greg0828
Subject: X870E NOVA Boot issue/BIOS loop
Date Posted: 15 Sep 2025 at 3:58am
|
I keep getting stuck in a BIOS boot loop with ASRock X870E NOVA. It's weird as when I hold power button down on my system , wait a second, then turn it back on, my computer boots to Windows. I started off with the factory 5.02 bios, then 5.35, then 5.40 and been having boot loop issues with at least the last 2, unsure about 5.02 as first boot I updated. It occurs essentially 100% of the time when I tell Windows to restart. It typically doesnt when I tell it to shutdown. I did clear CMOS but using the jumper (not button) once. In the course of creating my own system, I had all drives using DRM / legacy with Windows 10, to GPT / UEFI / secure boot with Windows 11. I had my DDR5 ram at 4800 and switched to both XPO and XMS settings to get it to 6000. I cloned hard drives so switched between an old M2 drive to a new one. I made a lot of changes and boot issues were consistent across all. CORSAIR Vengeance DDR5 RAM 96GB (2x48GB) 6000MHz CL36-44-44-96 1.4V AMD Expo Intel XMP 3.0 Desktop Computer MemoryCMK96GX5M2E6000Z36 AMD Ryzen 9 7950X CPU Socket AM5, memory type DDR5 5200 (can do 6000) up to 128 GB. Radeon RX 9070 16GB GPU M2 hard drives, Samsung 9100 Pro and 970 EVO Disk drives, Westren Digital Sata drives. ------------- Gregory Simmons |
Replies:
Posted By: Xaltar
Date Posted: 15 Sep 2025 at 3:24pm
|
Given the issue is repeatable but specific to restarting, I would suspect an OS issue that has survived migration between drives. Have you tried a fresh drive with a fresh OS install? UEFI flags are stored on your drive by the OS so if you keep pushing cloned data onto your new drives you could simply be pushing the issue from one drive to the next. I hope this makes sense. ------------- 
|
Posted By: greg0828
Date Posted: 15 Sep 2025 at 3:40pm
|
When I started Windows I saw an ASRock message about a BIOS update, but looks like I was confused. I am on BIOS version 3.25. Should I update to 3.30 or 3.40? The error I get is 4d on the motherboard which is related to ram not initializing. I started with Windows 10 on an old M2 drive and have changed to Windows 11 on a new M2 drive. So I have changed both drives and Windows although I cloned Windows 10 over and then upgraded vs a clean install. I dont think this would cause a 4d error. ------------- Gregory Simmons |
Posted By: greg0828
Date Posted: 15 Sep 2025 at 3:56pm
|
After boot, when Windows fully loaded, the mother board was displaying code 53. Then a little later it started cycling through temps I believe. Maybe 53 wsa a temp....53 is also about ram not initializing I think ------------- Gregory Simmons |
Posted By: greg0828
Date Posted: 16 Sep 2025 at 4:27am
|
So I tried going to BIOS 3.40 and bios was staying on dark screens for long times and it was difficult getting into BIOS menu. System wouldnt boot. Then I tried 3.30, same issue. I didnt have 3.25 to revert to but I had 3.10 and going to that got me back to the same place I was at, which is boot loop when I restart windows vs power down. I am using 2 sticks of 48 gb DDR5 6000 ram and I dont see this on a lot of CPU compatibility tables for the 7000 series. 9000 I see it. I tried removing 1 stick and same issue. Havent tried other ram. The error during bios loop is 4d. ------------- Gregory Simmons |
Posted By: greg0828
Date Posted: 18 Sep 2025 at 8:36am
|
Ok, so I tried a new set of ram and no luck. Tried disconnecting my extra hard drives, clearing CMOS again, etc. Finally bought an ASUS motherboard and swapped everything. No issues. I am not sure what on the board would cause this. Since I tried 4 different BIOS versions, I doubt it was a bad install or version for my system. ------------- Gregory Simmons |
Posted By: Xaltar
Date Posted: 18 Sep 2025 at 3:21pm
|
The gremlins just get you sometimes. It's always a pain. Glad you got the system up properly at last. There is nothing worse than an issue you can't figure out. Sometimes you just have to pull the ripcord and go another direction. Hopefully it's smooth sailing from here on out. -------------
|
Posted By: lleomat1
Date Posted: 11 Oct 2025 at 4:14pm
| I am having a weird issue with this motherboard, it won't even go to bios, it shuts down after code f3 c3, I managed to get in the bios twice but it shuts down shortly after, I tried to use only 1 memory , I replaced the psu, I uninstalled all drives including sata ssds and nvme ssds, I reaseated the processor, I have tried everything and still I can't make it stay in the bios for more than 1 minute, I am kinda desperate because RMA is something kinda impossible where I live, Hope you can help me, I am using a 9900x and 64 gb of ram |
Posted By: Xaltar
Date Posted: 11 Oct 2025 at 5:44pm
|
What cooling are you using? Please list your full system specs. -------------
|
Posted By: lleomat1
Date Posted: 11 Oct 2025 at 6:15pm
| I am using a 9900x, 64 gbs of ram 4x 16, The cooling system is a gigabyte aorus waterforce II 360, there are 9 system fans apart from the 3 watercooler fans + pump, there are 5 nvme ssds and 4 sata ssds, case is corsair frame 4000d, power supply is an msi Meg ai1300p, right now I have disconnected all system fans and ssd drives, unplugged everything aside from the front panel, the current bios is 3.30, I have tried the first version, 3.40 and 3.50, good lord, I do not know what else I can do |
Posted By: Xaltar
Date Posted: 11 Oct 2025 at 6:59pm
|
Make sure your AIO (Waterforce) is properly connected. https://manuals.plus/gigabyte/360-ice-aorus-waterforce-x-ii-360mm-liquid-cpu-cooler-manual" rel="nofollow - Here is the installation guide I found on Gigabyte's website. If the CPU block isn't getting power the CPU could be overheating. The BIOS and POST process really heat up the CPU, far more than you will experience at the desktop. -------------
|