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: Offline Points: 41928	Post Options Post Reply Quote Xaltar Report Post Thanks(0) Quote Reply Posted: 04 Sep 2026 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.


vedeneef Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 23 Jun 2026 Location: russia Status: Offline Points: 45	Post Options Post Reply Quote vedeneef Report Post Thanks(0) Quote Reply Posted: 48 minutes ago at 1:05am
	I tested the latest BIOS version, but the problem wasn?�t fixed ??I?�m still using version 3.50. New processors are going to be released, and I was planning to upgrade mine, but it seems I won?�t be able to because of the outdated BIOS version. Updating the BIOS on the memory isn?�t possible, so the only solution is to wait for ASRock to fix the issue. Even if KingBank is at fault here. It should be straightforward: the problem is known. The BIOS could detect that the memory is from KingBank and apply the appropriate settings, or they could create a separate BIOS for KingBank.

Xaltar Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 16 May 2015 Location: Europe Status: Offline Points: 41928	Post Options Post Reply Quote Xaltar Report Post Thanks(0) Quote Reply Posted: 24 minutes ago at 1:29am
	It might be worth opening a support ticket with ASRock and asking them: https://tw.asrock.com/events/tsd.asp?kind=MB Their BIOS team may be able to help. Bare in mind that they have no obligation to help so asking as politely as possible and laying out your issue clearly is always a good idea. Other users have had success asking for custom BIOS versions this way in the past, even when the board was no longer supported or, like in this case, ASRock has no obligation to help. Good luck Edited by Xaltar - 23 minutes ago at 1:30am