ASRock.com Homepage
Forum Home Forum Home > Technical Support > AMD Motherboards
  New Posts New Posts RSS Feed - X870E NOVA Boot issue/BIOS loop
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

X870E NOVA Boot issue/BIOS loop

 Post Reply Post Reply
Author
Message
greg0828 View Drop Down
Newbie
Newbie
Avatar

Joined: Yesterday
Location: Irvine
Status: Offline
Points: 60
Post Options Post Options   Thanks (0) Thanks(0)   Quote greg0828 Quote  Post ReplyReply Direct Link To This Post Topic: X870E NOVA Boot issue/BIOS loop
    Posted: 15 hours 55 minutes ago 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
Back to Top
Xaltar View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 16 May 2015
Location: Europe
Status: Offline
Points: 29548
Post Options Post Options   Thanks (0) Thanks(0)   Quote Xaltar Quote  Post ReplyReply Direct Link To This Post Posted: 4 hours 29 minutes ago 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.
Back to Top
greg0828 View Drop Down
Newbie
Newbie
Avatar

Joined: Yesterday
Location: Irvine
Status: Offline
Points: 60
Post Options Post Options   Thanks (0) Thanks(0)   Quote greg0828 Quote  Post ReplyReply Direct Link To This Post Posted: 4 hours 13 minutes ago 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
Back to Top
greg0828 View Drop Down
Newbie
Newbie
Avatar

Joined: Yesterday
Location: Irvine
Status: Offline
Points: 60
Post Options Post Options   Thanks (0) Thanks(0)   Quote greg0828 Quote  Post ReplyReply Direct Link To This Post Posted: 3 hours 57 minutes ago 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
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.04
Copyright ©2001-2021 Web Wiz Ltd.

This page was generated in 0.156 seconds.