Solved! Installed new CPU and the pc won't boot

[Xoliouse]

So I decided to upgrade my CPU from the Ryzen 5 2600 to the Ryzen 7 5800x3d. My motherboard came with BIOS P1.90 and I updated it to p5.60 via Instant Flash. I downloaded the update from ASRock, as they manufactured the mobo. It shows it's been updated successfully and I have no issues continuing to run my R5 2600. I finally swapped it with the 5800x3d and my pc gets stuck in a boot loop. I turn it on and the CPU and DRAM lights come on and nothing happens for about 20 seconds. It then shuts off completely then comes back on about 3 seconds later to repeat the process. The monitor doesn't show anything during this. Alternately, with the 2600 installed the same two lights come on but then move on to the VGA and BOOT lights until they shut off after a few seconds and the pc then continues to boot. I've been researching and trying different options for the better part of 6 hours all to no avail. I have also tried the "Steps to Update the Supported BIOS For Renoir/Cezanne/Vermeer" pdf from ASRock as well but for some reason i was told "30 - file could not be opened" when trying to update that way. (I tried this because of some other info I came across while researching. This link will send you to a thread in ASRock forums) I am at a loss as I even returned the first 5800x3d I ordered because of the same problem thinking it was possibly a faulty CPU, but the chances of getting two faulty 5800x3d's are virtually zero.

Motherboard: X570m Pro 4
Windows 10 Home
2x16GB Corsair Vengeance RGB Pro 3200Mhz
EVGA GeForce RTX 3060

Not sure what else to list. If you need some info, just let me know.

 

[Abwx]

No venturing giving advices with such a curious issue since i dont have an AM4 set up, personaly when i had boot problems on older hardware than this one it was often related to RAM issues, you could check by removing one RAM module and test each slot, one never knows.

 

[gdansk]

When I installed the 5800X3D in a B350 board I had to clear the CMOS. Otherwise it simply wouldn't boot with the beta BIOS (there was a debug light however).

 

[DAPUNISHER]

Clearing CMOS is good advice. Should be running optimized defaults until everything is running smoothly.

 

[Oneto]

Another vote for clearing CMOS. That's a nice upgrade BTW.

 

[Xoliouse]

I did try clearing the CMOS before coming here. Should have mentioned that

 

[igor_kavinski]

you could check by removing one RAM module and test each slot, one never knows.

Second that.

Is this your RAM kit? https://www.corsair.com/us/en/p/mem...-kit-a-black-cmw32gx4m2e3200c16#tab-techspecs

Don't see it listed on the QVL: https://www.asrock.com/mb/AMD/X570M Pro4/#MemoryVM

I bet it's the culprit.

 

[Xoliouse]

Second that.

Is this your RAM kit? https://www.corsair.com/us/en/p/mem...-kit-a-black-cmw32gx4m2e3200c16#tab-techspecs

Don't see it listed on the QVL: https://www.asrock.com/mb/AMD/X570M Pro4/#MemoryVM

I bet it's the culprit.

Yes that's correct. So I actually wondered that myself but I guess I ignored it since I haven't had any issues with the ram prior to this. This cpu is the first upgrade I've done in years and to my best knowledge they run the same speed

 

[SteinFG]

Here, googled your issue and came up on this reddit thread.

https://www.reddit.com/r/ASRock/comments/uhccno

Seems like you made so that only 3000 series processors (Matisse) work on it now. Borrow R5 3600, or any other Matisse, and try to run your board nevermind this isn't the right conclusion

 

[Tech Junky]

p5.60

First off I would back off to a lower revision and avoid anything w/ "patch" regarding AGESA.

V3.50 looks like a good option to try. Just DL the file and put it on a USB and from the UEFI you should be able to select the file or use the IF option. I've never had luck w/ the blind approach though. I've noticed tough that AGESA is a PITA. It took me a few tries to find something that worked consistently w/ x670e/7900x. Latest options aren't always the best options. My issue wasn't not being able to boot though it was warm reboots would hang until reset. Well, there was an issue with the first boot post build that turned out to be RAM not being fully seated.

 

[Xoliouse]

First off I would back off to a lower revision and avoid anything w/ "patch" regarding AGESA.

V3.50 looks like a good option to try. Just DL the file and put it on a USB and from the UEFI you should be able to select the file or use the IF option. I've never had luck w/ the blind approach though. I've noticed tough that AGESA is a PITA. It took me a few tries to find something that worked consistently w/ x670e/7900x. Latest options aren't always the best options. My issue wasn't not being able to boot though it was warm reboots would hang until reset. Well, there was an issue with the first boot post build that turned out to be RAM not being fully seated.

I just tried this and it didn't work unfortunately. Also tried v5.50

 

[In2Photos]

It appears this is a pretty common thing. It looks like you were on the right track with the special steps. According to a post in this thread : https://forum.asrock.com/forum_posts.asp?TID=27309&title=amd-ryzen-5700x-upgrade-not-booting upgrading the BIOS is not possible from a 2000 series processor. It requires a 3000 series. So you need to figure out why the special instructions aren't working. Maybe try re-downloading the files and unzipping them again? Or maybe these steps only work from an older BIOS and not v5.xx as the motherboard may think it is already updated? Did you remove all other drives from the system?

 

[Xoliouse]

It appears this is a pretty common thing. It looks like you were on the right track with the special steps. According to a post in this thread : https://forum.asrock.com/forum_posts.asp?TID=27309&title=amd-ryzen-5700x-upgrade-not-booting upgrading the BIOS is not possible from a 2000 series processor. It requires a 3000 series. So you need to figure out why the special instructions aren't working. Maybe try re-downloading the files and unzipping them again? Or maybe these steps only work from an older BIOS and not v5.xx as the motherboard may think it is already updated? Did you remove all other drives from the system?

I will go ahead and try it right now. ill roll back then try that method. will post again in a short bit with results

 

[Xoliouse]

Did not work. It's telling me "30 - Error: Unable to open specified file." I forgot that even tho i unplugged all my sata storage i still have my m.2 plugged in so maybe i need "Fs1" instead of "Fs0". I'm going to roll back to v3.0 as that's where asrock supplies the workaround link. will post results again

 

[In2Photos]

Did not work. It's telling me "30 - Error: Unable to open specified file." I forgot that even tho i unplugged all my sata storage i still have my m.2 plugged in so maybe i need "Fs1" instead of "Fs0". I'm going to roll back to v3.0 as that's where asrock supplies the workaround link. will post results again

They don't mention how drives would be allocated, but FS1 would be the logical choice. I'd just remove the M.2 to be certain.

 

[Xoliouse]

This is what I got after updating to 3.0 then doing the workaround. Fs3: is the only drive(?) that gives me anything other than "30 - Error: Unable to open specified file."

I'm at such a loss and I just honestly don't believe that it's the ram sticks doing it. I tried a single stick in all 4 slots with no changes.

 

[igor_kavinski]

Can you do an ls on that prompt and post the output?

 

[Xoliouse]

Can you do an ls on that prompt and post the output?

I don't know what that means, elaborate please

 

[In2Photos]

This is what I got after updating to 3.0 then doing the workaround. Fs3: is the only drive(?) that gives me anything other than "30 - Error: Unable to open specified file."
View attachment 93738
I'm at such a loss and I just honestly don't believe that it's the ram sticks doing it. I tried a single stick in all 4 slots with no changes.

I don't believe it is the RAM either. I just think there is some BIOS version incompatibility you need to work out. My guess is that trying to update to V5.xx with a non 3000 series chip didn't work and something is keeping you from going any further. At this point I would reinstall the 2600 and try to revert the BIOS back to v1.9 using the flash updater in BIOS. That should get you back to square 1. Then try the workaround to the latest version with all of your drives disconnected, including the M.2. You also might try a different USB drive?

 

[Xoliouse]

I don't believe it is the RAM either. I just think there is some BIOS version incompatibility you need to work out. My guess is that trying to update to V5.xx with a non 3000 series chip didn't work and something is keeping you from going any further. At this point I would reinstall the 2600 and try to revert the BIOS back to v1.9 using the flash updater in BIOS. That should get you back to square 1. Then try the workaround to the latest version with all of your drives disconnected, including the M.2. You also might try a different USB drive?

I've been using the same pc to come back and comment on this using my 2600. This flash drive hasn't given me any problems before, as it's the same I've been using to flash the BIOS with. I would try another but I don't currently have another. I'll try reverting back to 1.9 and try the workaround.

 

[igor_kavinski]

Type dir and enter or type ls and then enter.

Does it show the contents of the folder?

Never tried to list the contents of a drive in an EFI shell before so just guessing that either dir or ls should work.

May also help to format the USB with FAT or FAT32 file system and then try?

 

[igor_kavinski]

You could also try to update to BIOS version 3.70 using the alternate update method. That's the minimum BIOS version that supports 5800X3D.

 

[In2Photos]

You could also try to update to BIOS version 3.70 using the alternate update method. That's the minimum BIOS version that supports 5800X3D.

I think the problem is that any BIOS past 2.8 requires a Matisse CPU. So he has to get back to a version prior to that before he can perform the alternate update.

 

[igor_kavinski]

So he has to get back to a version prior to that before he can perform the alternate update.

That does make sense!

 

[Xoliouse]

Type dir and enter or type ls and then enter.

Does it show the contents of the folder?

Never tried to list the contents of a drive in an EFI shell before so just guessing that either dir or ls should work.

May also help to format the USB with FAT or FAT32 file system and then try?

It does indeed show the contents. Thank you for this little tidbit. I was able to confirm the drive.

I think the problem is that any BIOS past 2.8 requires a Matisse CPU. So he has to get back to a version prior to that before he can perform the alternate update.

I believe this was the issue. I updated back to 1.90 and then updated via the UEFI workaround to 3.0. It actually scared me a bit because after the bios update my screen went blue and the mouse made the screen all glitchy looking, like the screen wasn't refreshing. I ended up cutting power and installed the 5800x3d. Took a few moments but it did end up booting and I was able to sign in. It seemed to be working fine, although I didn't have the time to look stuff over and test the system. I won't be back to test it until the start of next week unfortunately but I am very glad we were able to get it figured out. I appreciate everyone's help on this and I hope anyone else in the future finds this helpful.