Fatal1ty X370 Gaming-ITX/ac - boot loop
Printed From: ASRock.com
Category: Technical Support
Forum Name: AMD Motherboards
Forum Description: Question about ASRock AMD motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=9100
Printed Date: 26 Jul 2025 at 8:23pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: Fatal1ty X370 Gaming-ITX/ac - boot loop
Posted By: nix
Subject: Fatal1ty X370 Gaming-ITX/ac - boot loop
Date Posted: 08 Jul 2018 at 12:38pm
|
" rel="nofollow - I have had this motherboard for 11 months and it has been working fine until today. When I power it on the fan spin up but nothing appears on my monitor. After around 5-10 seconds it reboots. I have done the following tests:
I do not own a second cpu, video card, or ram to test. I also don't know if testing without the video card or ram connected were valid tests, maybe boot looping in those situation is expected behaviour. The system has never beeped once, I suspect it has no speaker. I also cant see any leds that might indicate fault codes. How else can I troubleshoot this issue?
|
Replies:
Posted By: nix
Date Posted: 14 Jul 2018 at 10:17am
|
Update. I found out the motherboard has a header for a speaker. I bought one and connected it. There are no beeps. I took out all of the ram just to be sure it works, it does. With all the ram removed it beeps an ram error.
|
Posted By: D4rk5ide
Date Posted: 14 Jul 2018 at 1:52pm
|
I have this exact scenario with the ASRock z370 Killer SLI/AC. The difference is, I know mine bricked after trying to update the BIOS through Windows yesterday. I took all the actions you listed as well as, I unplugged everything and left the CMOS battery out all night, downloaded the bios to a fat32 formatted USB and pretty much exhausted my resources. I ordered a replacement BIOS chip off ebay and requested RMA from ASRock. I'll give the replacement BIOS chip a try and if that doesnt work, hopefully they will accept the RMA.
------------- ASRock z370 Killer SLI/AC i7 8700k LC Titan Xp LC |
Posted By: SYS64738
Date Posted: 22 Jul 2018 at 4:03pm
|
" rel="nofollow - How long have you waited for the system to boot? A bug presumably fixed in the latest UEFI updates for the ATX boards and still present in the latest ITX UEFI versions leeds to the system turning on and off for about three times after you disconnected it from mains power. You might just wait a bit longer for the boot loop to end. ------------- https://valid.x86.fr/wgjzle" rel="nofollow"> 
|
Posted By: nix
Date Posted: 22 Jul 2018 at 5:46pm
| " rel="nofollow - Thanks for the response SYS64738. I haven't timed it but I've probably left it boot looping for over 20 minutes. Exactly how long should I be leaving it for to test that bug? |
Posted By: SYS64738
Date Posted: 22 Jul 2018 at 10:01pm
" rel="nofollow - [URL=][/URL]
Oh, that doesn't seem right. I am not able to test this myself at the moment but I'm pretty sure my machine rebooted three times with fans spinning up staying on a short time, shutting off and restarting again. The whole procedure might take over an minute but nowhere near 20. I was told this was the ram training program so maybe your ram is the issue and not compatible with the board? Do you have the opportunity to test other memory? Edit: Looked at your post again. If you had the board in operation with no changes (bios update? Which version du you use?) maybe your ram died. I suppose you have no means to get to the UEFI and reset to factory defaults? ------------- https://valid.x86.fr/wgjzle" rel="nofollow">
|
nix wrote:Posted By: nix
Date Posted: 23 Jul 2018 at 1:00am
|
I don't have any other ddr4 ram to test unfortunately. For what its worth the ram passed a memtest I happened to run about 2 weeks prior to this issue. I hadn't done a bios update in months, unfortunately I can't recall what version I was using. Edit: I have purchased a new cpu and motherboard (different brand) to help me test, which should arrive in about a week.
|
Posted By: nix
Date Posted: 30 Jul 2018 at 9:37am
| Followup, I have purchased a new CPU, that has not fixed the problem. |
Posted By: JustRay
Date Posted: 03 Feb 2019 at 1:01am
| Have you ever solved this issue? |
Posted By: nix
Date Posted: 03 Feb 2019 at 7:08am
|
I did. Unfortunately it was the motherboard that was faulty. The board developed this fault after 11 months. It took me an extra month to save up enough money to buy duplicates of every part in my system in order to prove the fault was in the motherboard. At that point it had been just over 1 year. Unfortunately it only had a 1 year warranty. I have since thrown that board out and bought something by a brand with a better warranty service. |