B450 Gaming-ITX/ac+ 3600 no POST on 10.50

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

   ASRock started releasing yet another set of new BIOS (10.60) for the 400-series boards, including the PG-ITX/ac boards.  I wonder if they figured something out.  The release note just says, "Optimized system stability and compatibility."

The bigger issue is, what was wrong with 10.50?  Did they destroy CPUs or motherboards?  If they did, that'd be horrible, because all these boards are so old, I doubt any are still under warranty.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
eccential Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 10 Oct 2022 Location: Nevada Status: Offline Points: 6985	Post Options Post Reply Quote eccential Report Post Thanks(0) Quote Reply Topic: B450 Gaming-ITX/ac+ 3600 no POST on 10.50 Posted: 12 May 2026 at 2:23am
	ASRock started releasing yet another set of new BIOS (10.60) for the 400-series boards, including the PG-ITX/ac boards. I wonder if they figured something out. The release note just says, "Optimized system stability and compatibility." The bigger issue is, what was wrong with 10.50? Did they destroy CPUs or motherboards? If they did, that'd be horrible, because all these boards are so old, I doubt any are still under warranty.

apbarlow4 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 10 May 2026 Status: Offline Points: 45	Post Options Post Reply Quote apbarlow4 Report Post Thanks(1) Quote Reply Posted: 10 May 2026 at 9:41pm
	I have tried going back to a plethora of BIOS versions with the instant flash tool and used the CH341a for 7.40, 10.50, and 10.31 with no luck. Starting to think it will never work again for those chips. I have tried so many things

Xaltar Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 16 May 2015 Location: Europe Status: Offline Points: 39433	Post Options Post Reply Quote Xaltar Report Post Thanks(0) Quote Reply Posted: 10 May 2026 at 3:30pm
	Hi darren2026, if you haven't gotten a response for over 14 working days you should go ahead and open a new ticket. I believe ASRock was having some issues with their support ticket system not long ago. I don't have any confirmation from them on the matter but given the number of reports I have seen about unanswered tickets I strongly suspect that they had an issue. Send them a fresh one and let me know if you haven't gotten a reply in 7 working days. I am wondering if this is a particular issue with your specific board model.


darren2026 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 27 Apr 2026 Status: Offline Points: 90	Post Options Post Reply Quote darren2026 Report Post Thanks(0) Quote Reply Posted: 10 May 2026 at 11:23am
	Hello apbarlow4, Sorry to hear you are having a similar issue. Your boot loop symptom sounds exactly like the issue I was having. I have reached out to Asrock support on April 26 2026, but have not gotten a response (nothing in my inbox or junk folder). So unfortunately no progress there. At this point, I'm not sure when or if they will get back to me. If they do I'll be sure to reply here. As for my system, I stuck with the AMD Ryzen 5 5500 as my system was able to POST with that CPU. Not really a great solution per say, but a work-around that got my system working again. Some thoughts that come to mind: 1) Have you tried flashing the BIOS chip to an older BIOS version? (nice, you have a CH341a programmer) 2) It's curious that the Ryzen 5 1600 POSTs but none of the others work. They are all chiplet-based. (Ryzen 5 1600 is PCIe3.0 only?) It makes me curious if the Ryzen 5 5500 would POST on your system (I know you don't have it unfortunately).

apbarlow4 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 10 May 2026 Status: Offline Points: 45	Post Options Post Reply Quote apbarlow4 Report Post Thanks(0) Quote Reply Posted: 10 May 2026 at 10:34am
	Chiming in here, as I am having the same/similar issue. I have the Fatal1ty AB350 ITX board, was running 10.31 for the last year with a 3700x. I wanted to run a 5500x3d (this is a secondary system for me thankfully). I upgraded to 10.50 and it has not posted since. I even used a CH341a to erase the bios chip and put the 10.50 bios on clean. The only cpu that posts is my old ryzen 5 1600. I have tried the 3700x, 5500x3d, and even a 5800x. When I change settings in the bios with the 1600 (i.e. turning of global c state control, setting pcie gen 3, or turning off fTPM) the cpu fan spins on intial power and then stops, clearing the CMOS leads to a boot loop every 30s. Hoping maybe you have made some progress here.

Xaltar Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 16 May 2015 Location: Europe Status: Offline Points: 39433	Post Options Post Reply Quote Xaltar Report Post Thanks(0) Quote Reply Posted: 30 Apr 2026 at 4:16am
	Good luck, hopefully they can get you sorted out. Let us know how it goes.


darren2026 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 27 Apr 2026 Status: Offline Points: 90	Post Options Post Reply Quote darren2026 Report Post Thanks(0) Quote Reply Posted: 30 Apr 2026 at 1:27am
	Unfortunately I don't have a second set of RAM to attempt. I have sent something to ASRock - hopefully they respond soon. Thank you Xaltar and eccential for your support!

Xaltar Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 16 May 2015 Location: Europe Status: Offline Points: 39433	Post Options Post Reply Quote Xaltar Report Post Thanks(0) Quote Reply Posted: 29 Apr 2026 at 6:13pm
	Yeah, something is off with the BIOS ROM, a corruption of some sort maybe. You will probably need to open a support ticket with ASRock and ask them to look into it for you. I don't have the tools or resources they do to try and replicate the issue myself. The only other thing I can think of to try is different RAM, it could be that the update changed how the RAM is being handled and it doesn't like your RAM now with the effected CPUs.


darren2026 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 27 Apr 2026 Status: Offline Points: 90	Post Options Post Reply Quote darren2026 Report Post Thanks(0) Quote Reply Posted: 29 Apr 2026 at 11:15am
	I should clarify that rolling back the BIOS to P4.80 appeared to be successful. BIOS/UEFI did say version P4.80 on the main screen. By "was unsuccessful", I meant that rolling back the BIOS to P4.80 did not resolve the issue.

darren2026 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 27 Apr 2026 Status: Offline Points: 90	Post Options Post Reply Quote darren2026 Report Post Thanks(0) Quote Reply Posted: 29 Apr 2026 at 11:12am
	During my attempts, only a USB keyboard was plugged into the motherboard. No other USB peripherals. Correct, I am not seeing a boot screen or ASROCK logo. USB keyboard lights also don't turn on, so system doesn't reach the state where USB power is enabled. The 9070XT was a recent upgrade from a few months ago :). I was planning to upgrade the CPU/motherboard/RAM later since RAM prices are so expensive now. But now this problem has me reconsidering. I did try rolling back the BIOS to P4.80 using the R5-5500. Was unsuccessful. - 3600 with P4.80: failed to POST, same symptoms as before - 5600 with P4.80: failed to POST, same symptoms as before - 5500 with P4.80: POSTs immediately with no issues I chose P4.80 because I can be sure it supports the R5-5500. I worry if I roll back too far, I might lose support for the 5500. Now unfortunately, even with BIOS P4.80, the 3600 failed to POST. My theories: 1. Maybe rolling back BIOS versions is not as simple as I thought? Maybe there's some attributes of the AGESA that can't be rolled back? 2. The 3600 CPU got damaged? Although I think this is unlikely. 3. Or something on the motherboard got corrupted or damaged - making it incompatible with the 3600 / 5600. Maybe something to do with the memory controller on the IOD side? This seems to be the most likely theory so far. To summarize: - 3600 was working originally on P5.20. After updating to P10.50, system failed to POST. - 3600 and 5600 now fail to POST on both P10.50 and P4.80 (it is expected to work on both) - 5500 will POST with no issues on both BIOS versions.