X870E Nova Wifi code 00

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Oops, I should have researched for one second before I responded.

Yes ok, I understand I can use the flash-back function to in flash-forward. It will take me some time to get a FAT32 thumbdrive as I'm in the middle of nowhere in Costa Rica, so all of this is particularly slow and challenging.

Thanks again.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
melchizedek Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 15 Jul 2025 Status: Offline Points: 120	Post Options Post Reply Quote melchizedek Report Post Thanks(1) Quote Reply Posted: 16 Jul 2025 at 2:44am
	Oops, I should have researched for one second before I responded. Yes ok, I understand I can use the flash-back function to in flash-forward. It will take me some time to get a FAT32 thumbdrive as I'm in the middle of nowhere in Costa Rica, so all of this is particularly slow and challenging. Thanks again.

melchizedek Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 15 Jul 2025 Status: Offline Points: 120	Post Options Post Reply Quote melchizedek Report Post Thanks(0) Quote Reply Posted: 21 Jul 2025 at 11:53am
	The board still doesn't POST after following Xaltar's instructions for clearing CMOS. My question is, given the CMOS clearing didn't help the board POST, is there truly a possibility that flashing could help it POST? Obviously if the board would POST, I would flash it to prevent the issue with the 9000 series X3D CPUs. I ask because I'm waiting to just buy a new PSU to cross that off the list and feeling its best to move on to this phase now, rather than wait for to get my hands on a USB stick. Thanks.

Th3Cap3 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 9 hours 57 minutes ago Location: AL, USA Status: Offline Points: 30	Post Options Post Reply Quote Th3Cap3 Report Post Thanks(0) Quote Reply Posted: 9 hours 55 minutes ago at 12:30am
	I'm running into the same issue, just flashed to the latest BIOS version, I've checked everything but the board is still showing code 00. I've noticed that sometimes it'll fire up if I let it sit unpowered for a little bit and it stays on and runs for days/weeks as long as I don't shut it down. This leads me to think it's not a hardware issue per se. I'm running an AMD 9950x3d and I've noticed that my wifes computer whos running a 7800 has never had this issue.

Xaltar Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 16 May 2015 Location: Europe Status: Offline Points: 27548	Post Options Post Reply Quote Xaltar Report Post Thanks(0) Quote Reply Posted: 8 hours 59 minutes ago at 1:26am
	I hate to say it but it may be worth trying an RMA on the CPU, for both of you. As far as I know AMD have been very helpful regarding RMAs of the 9000X3D series given the compatibility issues with ASRock's boards. I am not certain but from what I have figured out it seems AMD provided specs to ASRock that were unsafe and while other brands took a less aggressive tack in their default BIOS configuration, ASRock opted for performance, pushing the CPUs to the upper edge of the spec AMD provided. As it turned out, not all Ryzen 9kX3D CPUs could handle it. Again, purely speculation on my part but it does fit the narrative and explain why AMD didn't point the finger at ASRock on this issue. Whatever the reason, a small number, compared to the number used in ASRock boards, of AMD 9k X3D CPUs experienced partial and in some cases complete failure. The upside is that, AFAIK as of this moment, AMD have not failed to honor RMA claims on CPUs that fell victim to this issue. The issue has been fully resolved in the latest BIOS of all supporting boards. From what I know, a few voltage settings were set to much more conservative values, more in line with other manufacturers. This was not a mistake or isolated issue, all ASRock boards that support 9k X3D CPUs had the same values set which is why I believe AMD's provided spec was off. If it was only a particular board model then I would lean to ASRock making a mistake but for every single model to be susceptible, that had to be an issue with the provided specs of the CPU range and their tolerances. None of that matters to either of you right now however, I would RMA those CPUs and make sure your boards are on the latest BIOS version when you get your replacements. If the CPU was damaged then that should completely resolve your issues.