Dr.debug error 00 on z170 extreme6
Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=1989
Printed Date: 27 Dec 2024 at 3:58pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: Dr.debug error 00 on z170 extreme6
Posted By: Greatgatsbi
Subject: Dr.debug error 00 on z170 extreme6
Date Posted: 13 Feb 2016 at 12:57am
| Assembled a new pc.booted it up .loaded wondows 10.every thing worked fine.went to run some errands.while updates were being installed .came back windows crashed saying some error has occured .tried to reset the the pc.nothing happened.motherboard dr.debug led shows 00.case fans connected to psu are working .cpu cooler (noctua nh-d15)fans are not working.specs:i7 6700k,asrock z170 extreme6, gskill 16gb 3200mhz (8+8)ram,seasonic 750 w 80+gold psu,noctua nhd-15 cpu cooler, |
Replies:
Posted By: parsec
Date Posted: 13 Feb 2016 at 1:15am
|
The Dr Debug 00 error indicates a dead CPU, or the CPU is not getting power, so not working. Try clearing the BIOS/UEFI with the jumper or switch on the board, after removing power from the PC. Check the connections of the power cables to the board, particularly the 4/8 pin CPU power cable. A 00 error code might indicate the board has a problem, such as in the CPU's VRMs. New parts can fail shortly after they are used for the first time. Are all the parts new? Did you check the CPU temperature in the UEFI or Windows, to insure the CPU cooler is mounted correctly? ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
Posted By: wardog
Date Posted: 13 Feb 2016 at 8:19am
|
00 on Z170 boards has also been pointing to incompatible or defective/dead memory. |
Posted By: wardog
Date Posted: 13 Feb 2016 at 8:27am
Hmmm you say: ""cpu cooler (noctua nh-d15)fans are not working"" Where they spinning when you initially installed the parts on first power up? Check that you have the fan(s) connected to the proper CPU Fan header. Check that their wiring is maybe kinked up and creating an open. |
wardog wrote:Posted By: Greatgatsbi
Date Posted: 13 Feb 2016 at 3:21pm
| Yes they were,everything was working on first switch |
Posted By: Xaltar
Date Posted: 13 Feb 2016 at 3:46pm
|
Disconnect everything from the board and reconnect it again making sure everything is seated correctly. Remove and reseat the CPU as well. While you have the CPU out make sure it is not warped and that there are no damaged/bent pins on the motherboard socket. I have always hated problems like this, the kind where you leave the PC alone for a while only to return and find a problem. It is very difficult to discover what went wrong in this situation. My first suspicion would be a power surge/outage. After you have tried the above lets move one to checking other possibilities. Because there are a fairly large number of reasons you could be getting the 00 code I would start with eliminating power as the issue, if at all possible try with a different PSU. By the sound of it the system is refusing to power the board (CPU fan not turning) which may well be due to a damaged PSU. ------------- 
|
Posted By: Greatgatsbi
Date Posted: 15 Feb 2016 at 5:13pm
|
Motherboard is dead .i have a ups and power surge protector on the line .still this has happened .cpu pins are fine.any precautions advised |
Posted By: Dubhead
Date Posted: 21 Feb 2016 at 9:13am
|
Hello, I noticed this thread when searching for some insight on the Dr. Debug error code "00". I am currently receiving this error and beyond frustrated with troubleshooting for it. First some context: - Have built 7 PCs, most recent before current was X99 platform, no issues - This is a brand new build and includes the following components:
- This was first assembled on 2/13/16 and upon this first assembly, the Dr.Debug code "00" appeared. Upon further troubleshooting, it was noted that there were 3 bent pins on ASRock mobo. After a few attempts to put them back into place with magnifier and needle, a second replacement ASRock Z170 Extreme 7+ mobo was ordered to replace one with bad pins (not sure this board has any use or salvage available) Current problem: - Still receiving the Dr. Debug code "00" after performing CMOS reset (via jumpers and button) and trying both A and B BIOS options. See the two videos to watch the startup and the codes it is cycling through. Initially, I test without any additional PCIe cards added "A" BIOS selected ( http://1drv.ms/1SIB3Gt" rel="nofollow - Video 1 )and the second boot is with cards added and using "B" BIOS selected ( http://1drv.ms/1SIB9xZ" rel="nofollow - Video 2 ). The net result is the same. I am suspicious of the processor at this point but am not sure how the processor could be damaged as it has never been used and potentially it is defective (which seems even more unlikely) but I will be attempting to get an exchange with it. Would appreciate any troubleshooting steps that would be relevant here as I see some options in this thread that may be worthwhile but hoping that this build isn't a total bust as it is turning out. Haven't been impressed yet by the ASRock mobos and haven't had any troubles like this before on previous builds. Thanks, ~Dubhead  |
Posted By: parsec
Date Posted: 21 Feb 2016 at 1:13pm
|
Your memory is missing from you list of components. If no memory is installed in the board, it won't start or POST. I use a Z170 Extreme7+ board, since August of 2016. Never had any problems with it. Besides not having the 4/8 pin CPU power cable connected, or your memory being not compatible, it does seem to be a defective CPU. We both know that is very rare, but so would receiving two bad boards in a row. Unless the retailer you are using was the source of both boards, and they received a bad production run of boards. We are not aware of any such thing from information in this forum. I imagine you checked the second board for bent pins in the CPU socket. Given a 00 Dr Debug (POST) code, the board, processor, memory, etc, has never even started the POST process yet. It is possible for some CPU coolers to be over-tightened to the point that they damage the CPU, or cause the socket pins to not contact the bottom of the processor. The Corsair H series coolers are normally not of that type, although their backplates can be mounted incorrectly and cause uneven pressure on the CPU and socket. I would try using just two memory DIMMs to start, in slots A2 and B2. If you have 8 or 16GB DIMMs, try using just one in the B2 slot. If everything is new, do you feel that the PSU is working correctly? Do you have a spare PSU to try as a test? With power from the PSU applied to the board, try connecting an active network cable to one of the network jacks. If you see any of the two LEDs on either side of the jack light up, the board is getting power and the network chip is working. A new board that has never been powered up might not show any activity from the network chips, so no LEDs lighting up is not a definitive sign the board is bad or not receiving power. I would try to verify that the CPU is not defective and the PSU is working as it should. Rather difficult to be impressed with a mother board that has not been able to start yet. I've been using ASRock boards since the Z77/Ivy Bridge days, and I've never had one that was defective out of the box. I've never returned or had to RMA one of the nine boards I've used yet. ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: Dubhead
Date Posted: 22 Feb 2016 at 3:28am
|
Parsec, Thanks for the bump about the memory as I had forgotten it in my list for my post earlier (updated now). Not sure if the 4 sticks were visible in the videos, but they were installed and seated properly. I understand this memory to be Z170 chipset compatible but I will give shot to the removal of two of the sticks to see if there is any change in behavior for the debug code. I am suspect of the CPU still as you mention and had read the Skylake processors can be more sensitive to pressure from cooling fans (the taller kind that present greater leverage against the chip) and perhaps not as much from a liquid CPU cooler like the H100i that I am using although it is possible to damage as you said from backplate being installed incorrectly. I did check the socket for bent pins again on the new mobo due to the first board having this issue and did not note any obvious bent pins or damage. I did this in between the two videos I posted. I ordered both of these boards from Newegg. I do feel the PSU is performing fine and do not have a second to really test with in this case. I continue to remain hopeful that a few more troubleshooting steps might reveal a culprit for this code but am running low on time to send defective components in for exchanges or otherwise. Will check out the memory stick changes to see if that does anything, hopefully I got compatible and non-defective memory sticks as I didn't realize the Dr. Debug code "00" also implied potentially that memory may be at issue. The manual states CPU for this code and a number of other codes that are related to memory issues. ~Dubhead |
Posted By: Dubhead
Date Posted: 29 Feb 2016 at 6:36am
|
Received a new Intel i7-6700K processor and installed it today. The Dr. Debug error code "00" is now gone. I am receiving a new error indicating "99" which according to the manual is a PCI-E device issue. Interestingly I have no PCI-e devices installed when receiving this error. I added the Intel 750 PCIe SSD card and same error, then added the graphics card (Zotac) and got the same error. I feel some slight progress may have been made since apparently I did have a bad processor (or so it appeared with the disappearance of the "00" code). I am investigating what to do next regarding this error since it is vague. Any suggestions would be welcome. EDIT: I found someone with similar issue in Tom's Hardware forums and tried a few more things. This could be a display issue. Unfortunately I have a display with both VGA and DVI-I connections and only HDMI cable available...using HDMI-DVI-I adapter on both ends I am still not seeing anything. Ironically I gave away a few DVI-I cables recently so only have some at office now. I held down DEL when booting again, saw the "A9" error code show for a while then it switched over to "Ab". Apparently this may be normal (at least according to the poster on Tom's) and I should be seeing BIOS screen at this point. Maybe it is POST'ing properly after all, but my screen set up sucks and cannot verify as yet. Here is link to post I am referring to: http://www.tomshardware.com/answers/id-2482790/asrock-z97-extreme6-error.html EDIT 2: Wow, I could not be much more frustrated with this board and build. After deducing that my issue may just be my display issue as mentioned previously, I went to my home office with this new build and rewired some things just to get my 30" Apple Cinema Display (DVI-I Dual Link) attached to the machine to see if I can actually see BIOS and managed to get a few things different to happen. Upon first boot with just the monitor and USB Keyboard/Mouse hooked in, the mobo booted and displayed "b4". I took this to mean I may not need the extra USB cable that is part of the ACD plugged in (feeds USB hub in monitor) and rebooted after disconnecting. Afterwards, it booted and ran through codes and finally stayed on and displayed no codes! I thought I might have been making progress but still not seeing anything on screen. I rebooted, held down DEL key to get to BIOS and it ended up by showing "Ab" again which is where I was at before hooking up to this different monitor. So, I shut down and cleared BIOS (with button this time) after removing power cable from power supply and then rebooted. Most unfortunately, I am seeing the "00" code again now. Shut down, unplugged, cleared CMOS with jumper and rebooted, same "00" code. I have made zero progress after replacing mobo and processor. I don't know where to go from here but I may need to take a break from this a bit because I am simply out of time for this. Occupied two full weekends and that is a lot for me. As I have said before, I don't think I have ever had so much trouble with a build before and this is the first time using ASRock, I don't know if the correlation even matters, just not impressed. I see this issue as very common as well in forums so I am wondering if there is really an issue with this board. I don't think the processor just went bad with me plugging it in again. I have already dealt with the mobo and processor returns which was a hassle also. I am not getting it and am spent. Thanks, ~Dubhead |