Killer SLI/AC Boot Loop/No Video
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=4811
Printed Date: 05 Jul 2025 at 5:53pm Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: Killer SLI/AC Boot Loop/No Video
Posted By: Chae
Subject: Killer SLI/AC Boot Loop/No Video
Date Posted: 10 Apr 2017 at 5:33am
" rel="nofollow - Just as the title says. My Killer mobo is trapped in a never ending boot loop. There's also no video signal.
My memory is a G.Skill Fortis 8gbx2. I checked G.Skill's forum and it says it's compatible with this mobo.
This forum even list the Fortis as compatible.
So what's wrong?
Is it a bad mobo, bad mem modules?
One more thing. One of the wifi things in the back came loose and is all wiggly. Is that affecting booting somehow?
|
Replies:
Posted By: wardog
Date Posted: 10 Apr 2017 at 7:40am
I see everything there except you mentioning a graphics cad, which is req'd for Ryzen as Ryzen doesn't have a dGPU built in.
|
Posted By: Chae
Date Posted: 10 Apr 2017 at 7:47am
Sorry. My GPU is an MSI 1080 GTX.
My problem has been solved by using different memory. A PNY Anarchy 8gbx2 allowed me to post and start the rig.
My mobo has BIOS 1.50 came right out of the box.
Either my G.Skill mem are defective or 1.50 version doesn't support the Fortis.
And the Internet Flash option is missing from the Tools menu list.
|
Posted By: wardog
Date Posted: 10 Apr 2017 at 7:56am
" rel="nofollow - Don't use anything but Instant Flash from within the BIOS itself.
Are you 100% positive BOTH Fortis sticks were fully seated into the slots? You should hear 2 clicks when they seat properly. G.Skill uses IIRC an 8-layer PCB that is sometimes tricky to fully seat.
|
Posted By: Chae
Date Posted: 10 Apr 2017 at 8:01am
100% certain. Heard the click.
The Fortis ram would not allow the system to boot. It would get stuck in a boot loop; restarting itself over and over again.
I'm going to update the BIOS now and see if the 2.00 version works with my Fortis.
|
Posted By: Chae
Date Posted: 10 Apr 2017 at 8:15am
Ok. Instant Flash isnt available in the Tools menu. All I see is driver update and some other options. Nothing about Instant Flash or similar.
|
Posted By: Chae
Date Posted: 10 Apr 2017 at 8:18am
" rel="nofollow - Is it safe to update the BIOS using the windows utility update version?
|
Posted By: parsec
Date Posted: 10 Apr 2017 at 9:48am
Chae wrote:
Ok. Instant Flash isnt available in the Tools menu. All I
see is driver update and some other options. Nothing about Instant Flash
or similar.
|
Chae wrote:
" rel="nofollow - Is it safe to update the BIOS using the windows utility update version?
|
The Instant Flash tool is added in UEFI version 1.60. But to install 1.60 the only options are the DOS and Windows methods, as you know.
I guess you don't feel like using the DOS method, since that requires a bootable USB flash drive.
Actually, the DOS method runs Instant Flash within DOS, if you check the DOS instructions, here (Sorry, the forum link tool fails on some URLs like this one, so text only. Just highlight it, right click and select an Open option):
http://www.asrock.com/support/BIOSIG.asp?cat=DOS8
The Windows update method simply seems to have the most failures. I'm not sure why, I get the feeling people use it with the CPU and/or memory over clocked, and who knows what programs running at the same time. All of that is a mistake.
I can't say it would be better to use the Windows method for the 1.60 version, in order to get the Instant Flash feature, and then update to 2.00 with Instant Flash. I trust Instant Flash, never had a failure yet, but the choice is yours.
If you use the Windows method, no over clock of the CPU or memory, stock/default UEFI settings only, unless you have RAID enabled, don't boot with the SATA mode changed to AHCI if you installed Windows in RAID mode. Actually this advice applies to any type of UEFI update.
Instructions for using the Windows method are here, please read them first:
http://www.asrock.com/support/BIOSIG.asp?cat=Windows9
Super important thing at the bottom of the instructions. IF the update fails for some reason, DO NOT TURN OFF THE PC! That will guarantee a bricked board!! Try to get into Windows again to repeat the process, or consider your other options.
I'm not trying to scare you out of doing the update, just coaching you about things I've known other users have done in the past, and their bad results.
PLEASE have no other programs running! If you have whatever programs auto-starting, kill them with Task Manager first. You want a super stable Windows environment. I don't care if it is CPU-Z or a hardware monitoring program, don't have anything running.
Two things I will add are, copy the Windows update download file to your OS drive if it is not already there. Unzip the file and go into the folder created and follow the instructions. When you run the UpdateBIOS batch file as shown in the instructions, right click on it and select Run as administrator.
Please let us know how it goes.
------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: Chae
Date Posted: 10 Apr 2017 at 9:50am
Updated using the windows utility method. BIOS updated successfully, no problems.
|
Posted By: parsec
Date Posted: 10 Apr 2017 at 11:19am
Great, thanks!
I still don't understand why some users have trouble with it.
------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: Chae
Date Posted: 21 Apr 2017 at 5:53am
" rel="nofollow - Ok. RMAd and got a new pair of Fortis dimms.
I'm at BIOS ver. 2.10.
The new pair of Fortis no longer leads to a never ending post cycle. However. It doesn't allow me to post either. I have no video and my keyboard and mouse are inactive suggesting that post has failed.
And yes. I did the CMOS jumper clear.
I forgot to mention the Fortis I have are 2666 and the PNY Anarchy are 2400. With the Anarchy everything is peachy. With the Fortis 2666... No go.
This means the maximum memory support of the Killer is 2400 even with the latest BIOS or are I'm I just having bad luck with Fortis?
|
Posted By: parsec
Date Posted: 21 Apr 2017 at 10:38am
Chae wrote:
" rel="nofollow - Ok. RMAd and got a new pair of Fortis dimms.
I'm at BIOS ver. 2.10.
The new pair of Fortis no longer leads to a never ending post cycle. However. It doesn't allow me to post either. I have no video and my keyboard and mouse are inactive suggesting that post has failed.
And yes. I did the CMOS jumper clear.
I forgot to mention the Fortis I have are 2666 and the PNY Anarchy are 2400. With the Anarchy everything is peachy. With the Fortis 2666... No go.
This means the maximum memory support of the Killer is 2400 even with the latest BIOS or are I'm I just having bad luck with Fortis?
|
I have the X370 Killer SLI/ac board, and use G.SKILL FlareX 3200 memory. The default memory speed is 2400, and currently the best I can run it at is 2933:
http://www.gskill.com/en/product/f4-3200c14d-16gfx" rel="nofollow - http://www.gskill.com/en/product/f4-3200c14d-16gfx
The default speed for most DDR4 memory designed for Ryzen is 2400. Check the specs for my FlareX memory, the default speed is 2400.
Is this your Fortis memory?
https://www.newegg.com/Product/Product.aspx?Item=N82E16820232515&ignorebbr=1
Apparently so new it is not shown on G.SKILL's website. The maximum speed for Fortis memory currently listed is 2400 on G.SKILL's website.
Your memory seems to default to 2666 according to a review I read about it. That is unusual but apparently is true. No spec page at G.SKILL's website so impossible to check.
http://www.gskill.com/en/finder?cat=31&series=2953&prop_14=0&prop_2=0&prop_6=0&prop_3=0&prop_4=0&prop_1=0
You're using the 2.10 UEFI correct? Did you check that in the UEFI itself, or in Windows?
Did you use the 2.10 UEFI with your first (RMA'd) kit of Fortis?
Not sure what to tell you, it is a new model but being Ryzen specific it should work IMO. Do you have a POST beep speaker installed, and the POST beep option enabled in the UEFI? When I have memory problems with an unsupported speed, I get three POST beeps. That's about the only way I can think of to determine if POST is failing to complete because of a memory issue.
I've run my FlareX at 2666 and 2933, so 2666 is not the maximum memory speed of this board. No POST and three beeps at 3200 so far for me.
Increasing the SOC voltage above the default 0.900V is suggested to help with Ryzen memory over clocks. But you need to get into the UEFI to do that, right? 
Memory compatibility with Ryzen has been such a mess. Ridiculous your first set did not work at all. G.SKILL support claims that the Ryzen memory controller in the CPU may not be able to reach 3200, since that is an OC. 2666 is considered an OC as well.
------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
|