ASRock.com Homepage
Forum Home Forum Home > Technical Support > AMD Motherboards
  New Posts New Posts RSS Feed - Dr Debug Error Code 07
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

Dr Debug Error Code 07

 Post Reply Post Reply
Author
Message
Balzac View Drop Down
Newbie
Newbie


Joined: 29 Jul 2017
Status: Offline
Points: 4
Post Options Post Options   Thanks (0) Thanks(0)   Quote Balzac Quote  Post ReplyReply Direct Link To This Post Topic: Dr Debug Error Code 07
    Posted: 29 Jul 2017 at 4:12pm
Asrock Taichi X370, Gskill Flare X.
PC booted and started successfully after building. After successfully updating the bios to 3.00, I rebooted the PC and got the Dr Debug Error code 07. I got into a bootloop and let it loop more then 7 times and it seems like an infinite boot loop. I have done the following:
1. Reset the cmos
2. Remove cmos battery
3. Powered down the pc and held it down for awhile to drain the battery
4. Removed the ram
5. Removed all the parts from the motherboard and left it overnight
6. Reseated all the parts back to the motherboard the next day
7. Put 1 stick of ram in A2
8. Tried the other stick of ram in A2
9. Tried them both on B2
Nothing has worked. Any advice on what I can do without returning this to Asrock and getting a new Taichi? I'm worried that even if I get a new motherboard from them, and I update to bios version 3.00 that the same thing will happen again. It was working fine before the bios update. And the latest bios should be more stable with Ram. I got the gskill flare x because I knew about ryzens ram problems and I wanted something is supposed work out of the box. Also, I'm not doing anything fancy, no overclocking or anything like that. What could be causing the problem bios 3.0? Anyone else experienced this? What other things can I try? I cannot try different ram or other pc parts because I don't have any spare parts. Also I get error 07 almost immediately when powering up the pc

Please help. Appreciate it. Thank you very much.
Back to Top
parsec View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 04 May 2015
Location: USA
Status: Offline
Points: 4996
Post Options Post Options   Thanks (1) Thanks(1)   Quote parsec Quote  Post ReplyReply Direct Link To This Post Posted: 29 Jul 2017 at 9:47pm
Originally posted by Balzac Balzac wrote:

Asrock Taichi X370, Gskill Flare X.
PC booted and started successfully after building. After successfully updating the bios to 3.00, I rebooted the PC and got the Dr Debug Error code 07. I got into a bootloop and let it loop more then 7 times and it seems like an infinite boot loop. I have done the following:
1. Reset the cmos
2. Remove cmos battery
3. Powered down the pc and held it down for awhile to drain the battery
4. Removed the ram
5. Removed all the parts from the motherboard and left it overnight
6. Reseated all the parts back to the motherboard the next day
7. Put 1 stick of ram in A2
8. Tried the other stick of ram in A2
9. Tried them both on B2
Nothing has worked. Any advice on what I can do without returning this to Asrock and getting a new Taichi? I'm worried that even if I get a new motherboard from them, and I update to bios version 3.00 that the same thing will happen again. It was working fine before the bios update. And the latest bios should be more stable with Ram. I got the gskill flare x because I knew about ryzens ram problems and I wanted something is supposed work out of the box. Also, I'm not doing anything fancy, no overclocking or anything like that. What could be causing the problem bios 3.0? Anyone else experienced this? What other things can I try? I cannot try different ram or other pc parts because I don't have any spare parts. Also I get error 07 almost immediately when powering up the pc

Please help. Appreciate it. Thank you very much.


The 07 Dr Debug POST code is a problem with memory. The POST process is the first thing that runs when a PC starts, so it is normal for POST issues to occur quickly.

What method did you use to update to 3.00? Seems like Instant Flash was used?

I use G.SKILL FlareX memory with a different ASRock Ryzen board, with the 3.00 UEFI, and I did not have your problem.

User reports with the 3.00 UEFI version with AGESA 1.0.0.6a vary, some find it better with memory, others don't. So nothing is a given regarding memory compatibility with these updates, meaning that it will be improved. But it should not have made your memory incompatible.

Besides trying a different model of memory, given what you said you did, really nothing else to do.
Back to Top
Balzac View Drop Down
Newbie
Newbie


Joined: 29 Jul 2017
Status: Offline
Points: 4
Post Options Post Options   Thanks (0) Thanks(0)   Quote Balzac Quote  Post ReplyReply Direct Link To This Post Posted: 30 Jul 2017 at 4:35am
Yes Instant Flash was used. Is it better to use Dos or Windows? What did you use to update to 3.00?

So, do you think I need to replace the motherboard or the ram?

Thanks for the reply!
Back to Top
parsec View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 04 May 2015
Location: USA
Status: Offline
Points: 4996
Post Options Post Options   Thanks (0) Thanks(0)   Quote parsec Quote  Post ReplyReply Direct Link To This Post Posted: 30 Jul 2017 at 9:39am
Originally posted by Balzac Balzac wrote:

Yes Instant Flash was used. Is it better to use Dos or Windows? What did you use to update to 3.00?

So, do you think I need to replace the motherboard or the ram?

Thanks for the reply!


I only use Instant Flash at all times. I've never had a failure using Instant Flash, with many different ASRock boards.

No it is not better to use the Windows version. The DOS version actually runs Instant Flash within DOS, so might as well just use Instant Flash.

As I said, if you had another set of DDR4 memory to use for testing, that could be worth trying, in case your memory died for some reason. But that seems rather far fetched and quite a coincidence. I'm very reluctant to suggest buying more DDR4 memory at its current prices, only for you to have the same result of the 07 POST code. We aren't seeing other reports of FlareX memory not working with the X370 Taichi and UEFI 3.00. If you could try using your FlareX memory in another PC, that is the only way to know if it is working or not.

I have no way of knowing if the FlareX memory cannot work with the X370 Taichi and the 3.00 UEFI version. My FlareX memory works with my X370 Killer SLI/ac board's 3.00 UEFI.

Please understand it is very difficult trying to diagnose or know what happened during or after the 3.00 UEFI update just with your description. Even if I was sitting in front of the monitor at the time, I might not have seen anything that told me what happened.

Did you try removing the memory completely, and see what debug code you get?
Back to Top
RhapsTheRed View Drop Down
Newbie
Newbie
Avatar

Joined: 08 Dec 2019
Location: Dallas
Status: Offline
Points: 3
Post Options Post Options   Thanks (2) Thanks(2)   Quote RhapsTheRed Quote  Post ReplyReply Direct Link To This Post Posted: 09 Dec 2019 at 12:20am
So I have an official solution for the Debug Error code 07 on post. YES it is a RAM related issue. I struggled with this problem for a week before I came to a realization. So let me tell you the trouble steps I took.

So here's the issue I was running into:

First, The specs of my brand new build:

Ryzen 7 3800x
Wraith Prism (Stock heatsink for the CPU)
MSI MEG x570 Ace (Don't get me wrong, yes it's MSI but the debug codes I think are all the same)
32GB DDR4 3600 G.Skill TridentZ Neo RGB (2x16GB)
AMD PowerColor Red Devil 5700xt
ThermalTake ToughPower Grand 80+ Gold 750w
1TB Inland m.2 Gen4 drive
Windows 10 64-bit Pro
1st Bios to Newest Bios (tested each one for flaws/issues)

The issue I was running into:
As I built the system, I put my RAM into A2/B2 slots according to the Mainboard Manual specifications for Dual Channel operation. Hooking everything else up and turning the system on for the first time, the Debug LCD went through a variety of debug codes quite fast then paused at 07, went through more codes, stopped at 07 and the diagnostic LED for the DRAM next to the 24pin power port on the mainboard was on as well. System would not boot or complete the post.

Steps took towards resolution

I obviously did some research online for a week straight to find no help whatsoever in solving the problem. The advice I got from doing my due diligence and researching the hell out of the Debug Error 07 code, I found the below answers.

It's a RAM issue, right? So it's OBVIOUSLY Bad Ram. This IS a possibility, but if you've already tried the below steps, read on. It was NOT my solution.

RAM Issue: So swapped out the RAM, right? Of course I did. Did I check the QVL compatibility list for my mobo, Of course I did. 100% compatible.

1) I tried swapping the ram from A2/B2 to A1/B1. STILL no post.

2) I tried SWAPPING THE ram modules to A1/A2, HOLY sh*t It posted and booted no problems! Well, one problem existed now. IT WAS ONLY SINGLE CHANNEL!!!!! Which means my ram was running at 2133Mhz instead of 3600Mhz. This is a NO GO.

3) Just for sh*ts and giggles and for further diagnostic testing, I swapped the RAM to B1/B2 slots, It's a Code 07 again with the DRAM Diagnostic LED on.

4) The system had no problems or crashes or stutters running on A1/A2 in single channel, so I didn't think it was the ram, but the easiest resolution was to swap out the ram at the store, so I did. STILL the exact same issue. No Post/Boot and Code 07 with the Diagnostic LED for DRAM on.

The DRAM diagnostic LED was still on, the Post code on the LCD display was still 07, no post/boot. Couldn't get past 07 or the DRAM led with the new RAM either or forced to run in single channel only, which was not gonna be acceptable.

So if it's not the RAM and the mobo is having the exact same issue with the new ram in every step, it MUST be the Mainboard, right? It's a VERY Good possibility, but again STILL not the solution for me. Here's the steps I took for the mobo:

1) I swapped out the mobo, plugged in all the cables. flashed the firmware using the Flashback USB port.

2) I repeated all the steps in the RAM testing above with the new pair of RAM modules.

I got the exact same results as above. So What the HECK! If it's not the RAM and it's not the motherboard, what else is there? It's a RAM issue, right? So it's gotta be EITHER the RAM modules themselves or the Ram slots on the motherboard are bad, right? Well, read on.

After doing some more research, I discovered that the "MEMORY CONTROLLER" is built onboard the CPU of the newer Intel and AMD CPU's...

Could it be? Could it possibly be that the Memory Controller on the CPU itself is bad and that is why the B-Channel of my RAM slots would never function and would prevent the system from booting/posting successfully?

Infact, the answer to this question is YES!!! A Resounding YES!!!

I swapped out my Brand new (week old) Ryzen 7 3800x with a brand new one exchanged at the store and all my problems are GONE!! System works flawlessly, I now have my RAM working not only at 3600Mhz but they're overclocked to 4400Mhz with no issues whatsoever.

I know this is an older post, but it's one of the first that pops up on google and apparently this problem still exists from time to time, so I wanted others to be able to see it, whether you run a Gigabyte, Asus, ASRock, MSI board, etc...Hopefully I can help put this problem to rest for a LOT of people.

Now granted, I speak of B-Channel slots only because that was MY case scenario. In all honesty, If the Memory controller of the CPU is bad/defective or goes bad along the way, It can cause any variety of RAM problems, such as BSoD's, crashes, memory errors, DRAM diagnostic LED and even post codes relating to the RAM.
-*-*-*-*-*-*-*-*-*-*
Where you are I've been
Where you're going I've already gone
What you're doing I've already done
What you're looking at I've already seen
-*-*-*-*-*-*-*-*-*-*
TJ The DJ of Tech
Back to Top
Xaltar View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 16 May 2015
Location: Europe
Status: Offline
Points: 25298
Post Options Post Options   Thanks (1) Thanks(1)   Quote Xaltar Quote  Post ReplyReply Direct Link To This Post Posted: 09 Dec 2019 at 12:54am
I have said the same myself on these and other forums more times than I care to count.
With modern systems RAM issues often come down to the IMC on the CPU. It also appears
to be getting worse as frequencies and core counts increase. So many people go through
hell troubleshooting and RMAing everything but the CPU to no avail, typically ending
up blaming the motherboard (and manufacturer thereof) when the CPU was the issue
the entire time. Thanks for sharing.
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.04
Copyright ©2001-2021 Web Wiz Ltd.

This page was generated in 7.125 seconds.