Z490 Aqua BIOS Update code 53

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

   Hello,

I updated my Z490 Aqua bios to version 2.10. It will now fail to detect my RAM with a code 53.
Using Corsair CMT32GX4M4Z3200C16W , CPU is I9 10900KF , all settings default apart from boot order (and loaded bios setup defaults)
Flashed bios 1.90 to check the difference and it will boot, but sometimes also get a code 53 (turning off and on the computer will successfully boot after a few tries).
Both 1.90 and 2.10 show a "_" character in the corner of the screen and the POST debug code in the other corner, before showing the Asrock logo.

BIOS 1.60 had no problem at all (boot everytime OK).

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
gmat76 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 14 May 2021 Location: France Status: Offline Points: 20	Post Options Post Reply Quote gmat76 Report Post Thanks(0) Quote Reply Topic: Z490 Aqua BIOS Update code 53 Posted: 14 May 2021 at 2:37pm
	Hello, I updated my Z490 Aqua bios to version 2.10. It will now fail to detect my RAM with a code 53. Using Corsair CMT32GX4M4Z3200C16W , CPU is I9 10900KF , all settings default apart from boot order (and loaded bios setup defaults) Flashed bios 1.90 to check the difference and it will boot, but sometimes also get a code 53 (turning off and on the computer will successfully boot after a few tries). Both 1.90 and 2.10 show a "_" character in the corner of the screen and the POST debug code in the other corner, before showing the Asrock logo. BIOS 1.60 had no problem at all (boot everytime OK).

Danielwhitt Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 13 Oct 2023 Status: Offline Points: 50	Post Options Post Reply Quote Danielwhitt Report Post Thanks(0) Quote Reply Posted: 13 Oct 2023 at 8:52pm
	Hello, I know this was a long time ago, but I'm seeing a similar issue, only happens occasionally and a full power off normally sorts the issue out. Did you ever find out what the issue was ?