X370 Gaming K4
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=4599
Printed Date: 22 Dec 2024 at 3:01pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: X370 Gaming K4
Posted By: EpicPants
Subject: X370 Gaming K4
Date Posted: 13 Mar 2017 at 4:41am
|
" rel="nofollow - Hi everyone, I have just finished building my new ryzen build and after boot up, Dr debug stays lit with the code IE/1E. im not sure if that is showing 1 or I. I have looked through the manual and could not find what the code represents. What does this code mean? If this isnt an actual issue, Is there an option to turn off dr debug after the computer boots up? Motherboard: Asrock X370 Gaming K4 CPU: Ryzen R7 1700 Bios version: 1.60 |
Replies:
Posted By: Xaltar
Date Posted: 13 Mar 2017 at 4:56am
|
1E which would be a memory error but if the system is booting and running fine then it is probably a glitch with the Debug display. The Debug LED should clear as soon as post completes unless set not to in the UEFI. You should be able to disable it (the Debug LED) in the UEFI but I don't see the setting in your manual, that doesn't mean it isn't there just that it wasn't at the time manual was written, updates may have added it. You can try clear CMOS, that may sort it out. I would download CPUz and check the RAM tabs to make sure your RAM is properly detected and working in dual channel mode. ------------- 
|
Posted By: EpicPants
Date Posted: 13 Mar 2017 at 5:09am
|
I just checked CPU-Z and can the memory seems to be working fine; i could not clock my ram to anything over 2400mhz though; it would just not boot at all. Which seems to be a XMP/RAM compatibility issue right now with ryzen. i will try clearing CMOS and lets see how that goes. i could not find a option for dr. debug though in the bios. which is a little strange |
Posted By: EpicPants
Date Posted: 13 Mar 2017 at 5:17am
|
" rel="nofollow - Attempted to clear cmos. dr. debug showed code 24 while i was going through windows login and after displayed 1E again. Could this be a ryzen memory issue? |
Posted By: Xaltar
Date Posted: 13 Mar 2017 at 5:25am
|
If the system is stable I wouldn't worry about it. If it were an actual memory error the system would be unstable at the very least, most likely it wouldn't pass post. These boards and their BIOSes are very new and likely buggy. So long as everything is working and you are not having any issues I wouldn't worry about it. If the debug LED is bothering you (interfering with LED themes) you can stick a little bit of electrical tape over it for now. There will probably be a BIOS update that fixes the issue later on. I would hold off on updating for now until the platform is a little more mature and more fixes are available. -------------
|
Posted By: EpicPants
Date Posted: 13 Mar 2017 at 5:27am
|
Thanks Xaltar! Really appreciate your speedy responses and clarification. I was going to attempt the beta bios update but i think i should hold it off for now; since everything is running smoothly. Thanks again! |
Posted By: EpicPants
Date Posted: 16 Mar 2017 at 7:39pm
|
alright, for everyone else that may be facing this, i have just updated my bios to 1.64 which is the latest version and its showing 24 on the debugger all day long after booting it up; which is very strange |
Posted By: wardog
Date Posted: 16 Mar 2017 at 7:46pm
|
" rel="nofollow - May I ask what memory kit? |
Posted By: EpicPants
Date Posted: 18 Mar 2017 at 3:27am
|
Corsair Vengeance 16GB (2x8GB) DDR4 3000 (PC4-24000) C15 for DDR4 Systems, White LED (CMU16GX4M2C3000C15) Currently using this one; got it off amazon |
Posted By: wardog
Date Posted: 18 Mar 2017 at 6:51am
|
" rel="nofollow - I'm not sure the 1E is NOT related yet your board seemingly is running w/o issue(minus the 1E). So you're aware, Ryzen isn't cognizant of 3000 and 3400 dividers. That, w/o me having the same get up you do, leaves some suspicion that it may be related. That leaves me to ask you if this kit is in fact running at 3000?? Or maybe a tad lower or higher? |
Posted By: EpicPants
Date Posted: 18 Mar 2017 at 2:40pm
|
I got it running on the XMP profile at 2400mhz, anything higher and it crashes. I also edited the vram voltage to 1.300v. The xmp profile has it running at 1.35v, which I assume can be brought down Still, it would only do 2400mhz. If I attempt 2667mhz, it will not post at all |
Posted By: wardog
Date Posted: 18 Mar 2017 at 4:54pm
Always ALWAYS know the Specs of the component you're about to change. I can't say this enough. Blindly changing away from Spec is like shooting clay pigeons with both eyes covered. http://www.corsair.com/en-us/vengeance-led-16gb-2-x-8gb-ddr4-dram-3000mhz-c15-memory-kit-white-led-cmu16gx4m2c3000c15" rel="nofollow - http://www.corsair.com/en-us/vengeance-led-16gb-2-x-8gb-ddr4-dram-3000mhz-c15-memory-kit-white-led-cmu16gx4m2c3000c15 |
EpicPants wrote:Posted By: EpicPants
Date Posted: 18 Mar 2017 at 9:04pm
|
" rel="nofollow - Damn, in that case I should leave it at 1.35? And try to up the frequency as much as I can? I should have known better than to mess with voltage. I have done that and after a couple of restarts, the debugger either shows 24 or FF, seems to work perfectly fine though even with benchmarks |
Posted By: parsec
Date Posted: 18 Mar 2017 at 9:59pm
|
If you check the Memory QVL list for your board, or any ASRock Ryzen board, we will find this: Note1: Each RAM whose frequency is 3000 will downgrade to 2933 with Fatal1ty X370 Gaming K4. Note2: Each RAM whose frequency is 2800 will downgrade to 2666 with Fatal1ty X370 Gaming K4. http://www.asrock.com/mb/AMD/Fatal1ty%20X370%20Gaming%20K4/index.asp#Memory" rel="nofollow - http://www.asrock.com/mb/AMD/Fatal1ty%20X370%20Gaming%20K4/index.asp#Memory As wardog said, these are examples of the "memory dividers" that a Ryzen system does not support. Apparently, the "downgrade" to the slightly lower memory speed is not happening automatically, or another memory problem is the reason you cannot run your memory near 3000. Ryzen memory compatibility is probably the number one issue we are seeing so far. I just read about a tweak for getting memory to work on Ryzen systems that I'll describe, that I cannot guarantee will work but will offer it if you feel like trying it out. First, stay with a maximum memory speed of 2666/2667, which is the maximum, non-OC memory speed for a Ryzen processor. Do not apply the XMP profile in the DRAM Configuration screen. Now the fun part... The default settings for memory options is of course, Auto. The tweak I read about said to set each and every memory option manually, from the Auto setting. If you have a memory option highlighted and set to Auto, if you press the '+' key once, a numeric value will appear. While that should be the Auto value, apparently using the numeric value makes a difference. Doing this to the many memory options is a lot of work, and may result in nothing. A review of Ryzen I read described this as the method used to get their memory to 2666. Again, I cannot guarantee it will work for you, so please don't hate me too much if you try this, and it fails.  ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
Posted By: jed2i
Date Posted: 29 Mar 2017 at 7:42pm
| " rel="nofollow - Will this board support memory faster than 2933 mhz? |
Posted By: jdhardware
Date Posted: 01 Apr 2017 at 8:27pm
|
I have this board and compared to the gigabyte ax370 board the memory seems to run at one speed lower on the asrock gaming k4 Me and my friend have various sets of ram and we have tried them on each others board. Both boards are running the latest bios updates, current of today. Sets tested are Cosair LPX 3000 CMK16GX4M2B3000C15 Cosair LPX 3000 CMK16GX4M2B3000C15R Boths sets run on gigabyte ax370 at 2666mhz XMP On the asrock 2400mhz, with all manual settings work on bios 1.91 and 2.0 1.7 almost worked at 2666 and booted into windows when I raised volts to 1.45 on 2 times out of 6. 1.91 it never booted once. Cosair Vengence LED CMU16GX4M2C3200C16R This set works on both boards at 2666mhz XMP It almost boots on the asrock gaming 4 at 2933, when i mean almost it does not go into a rebooting cycle of 4 times before dropping to 2133 speeds and booting when set too high. I have loosened the timings and pumped voltages to suicide levels and it still won't boot, its on the edge of working. It may have worked on a previous bios, 1.91 and 2.0 bios seem to worse. However the gigabyte board, boots into windows if ram is set to 2933 XMP and voltage to 1.4 volts. So in both cases you can see the asrock is one speed lower and the gigabyte and new bios make no difference, it anything it makes it worse as now sometimes i cannot get into the UEFI on boot as the memory training is doing a strange double reboot on startup which start bios 1.91 and also on 2.0 From the website asrock only claim 2933 support overclocked, while gigabyte claim 3200, which as you can see is one bin lower :D Now all modules tested are HYNIX. I have Samsung b-die, G-Skill amd specific memory on its way. If anything is going to do 3200mhz on the asrock it will be that. I am no confident though as that is above the asrocks quoted spec. The asrock may be among the worst X370 board for memory compatibility. |