New AM5 BIOS updates now available

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

   I know it's a known issue. I also know it is a KingBank issue. The info about
what the problem is can be found with a quick google search. I am afraid I don't
know if ASRock has resolved the issue with newer BIOS updates (4.10 was still effected).
Unfortunately people tend not to bother reporting when an issue is fixed. Most people
effected simply rolled back to BIOS version 3.50 and I suspect KingBank has since
corrected the issue on newly produced modules.

If you have tried the latest BIOS for your board and it still won't POST with
an effected KingBank RAM kit then your only option may be to use BIOS 3.50 or
look into getting an RMA from KingBank themselves. I know it's frustrating but
this issue is 100% KingBank's mistake. ASRock's BIOS implementation is not broken
or defective in this case, it simply exposed a mistake in the effected RAM module's
firmware. 

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Xaltar Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 16 May 2015 Location: Europe Status: Online Points: 41898	Post Options Post Reply Quote Xaltar Report Post Thanks(0) Quote Reply Posted: 9 hours 47 minutes ago at 4:38pm
	I know it's a known issue. I also know it is a KingBank issue. The info about what the problem is can be found with a quick google search. I am afraid I don't know if ASRock has resolved the issue with newer BIOS updates (4.10 was still effected). Unfortunately people tend not to bother reporting when an issue is fixed. Most people effected simply rolled back to BIOS version 3.50 and I suspect KingBank has since corrected the issue on newly produced modules. If you have tried the latest BIOS for your board and it still won't POST with an effected KingBank RAM kit then your only option may be to use BIOS 3.50 or look into getting an RMA from KingBank themselves. I know it's frustrating but this issue is 100% KingBank's mistake. ASRock's BIOS implementation is not broken or defective in this case, it simply exposed a mistake in the effected RAM module's firmware.