Asrock X399 Fatal1ty not booting with code 7A/7b

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

   Hi

I've installed a "new" Asrock X399 Fatal1ty into my server with a TR1920x and 16GB 2133mhz RAM. Everything worked without a problem for about a week or so but after I've done a reboot of the server, it wont start anymore.

Post code is showing 7A most of the time, sometimes it's showing 7b or 76 dont know if that's a "b" or a "6"

The manual says "Chipset initialization error. Clear CMOS or reset". It didn't work. I also tried to remove the battery. Boot with one stick of ram but same problem. Removed also every PCIe device and changed the PSU, still hangs with the same 2 post codes.

Should I try to re-flash the BIOS? BTW the latest BIOS is installed

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
agent-orange Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 25 May 2021 Status: Offline Points: 35	Post Options Post Reply Quote agent-orange Report Post Thanks(0) Quote Reply Topic: Asrock X399 Fatal1ty not booting with code 7A/7b Posted: 25 May 2021 at 3:19am
	Hi I've installed a "new" Asrock X399 Fatal1ty into my server with a TR1920x and 16GB 2133mhz RAM. Everything worked without a problem for about a week or so but after I've done a reboot of the server, it wont start anymore. Post code is showing 7A most of the time, sometimes it's showing 7b or 76 dont know if that's a "b" or a "6" The manual says "Chipset initialization error. Clear CMOS or reset". It didn't work. I also tried to remove the battery. Boot with one stick of ram but same problem. Removed also every PCIe device and changed the PSU, still hangs with the same 2 post codes. Should I try to re-flash the BIOS? BTW the latest BIOS is installed

agent-orange Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 25 May 2021 Status: Offline Points: 35	Post Options Post Reply Quote agent-orange Report Post Thanks(0) Quote Reply Posted: 25 May 2021 at 9:29pm
	Found the problem, damn CPU was the problem :-(