Z170 Extreme6 - debug code 99
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=4357
Printed Date: 13 Sep 2025 at 4:51am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: Z170 Extreme6 - debug code 99
Posted By: batch
Subject: Z170 Extreme6 - debug code 99
Date Posted: 04 Feb 2017 at 10:40pm
|
Hi, I'm using an 1-year old Z170 Extreme6 with a 6700K CPU. All is working fine with BIOS v1.20 Now I did a BIOS update to the newest v7.20 in order that I can use a 7700K on this board. The update has been done properly. After reboot, the bootscreen holds with debug code 99 and there is no keyboard command possible. I can reset and hit F2 to load the BIOS.. thats working. After I went back to BIOS v1.20 all is fine. Win is booting and no probs at all. Next thing I tried was to plug off all SATA drives, ext. USB drives, M.2 SSD, graphic card and 3 of 4 RAM moduls. Only the 6700K and one RAM is pluged. (RAM is G.Skill Ripjaws F4-3200C16Q-16GRKD / 4x4GB). After switching on, the BIOS is loading automatically without pressing F2. If I plug in at least one storage device e.g. the M.2 SSD .. it freezes with code 99 After this, I replaced the RAM module with another one. (G.Skill TridentZ F4-3400C16D-16GTZ / 2x8GB) - same state.. code 99. Maybe you have a clue because I'm out of ideas.. the funny thing is that all is working properly with BIOS v1.20. But I have to update if I want to use the 7700K.  Here some screens: https://www.hardwareluxx.de/community/attachments/f326/390144d1486198336-asrock-z170-extreme6-debug-code-99-foto-1.jpg" rel="nofollow">  https://www.hardwareluxx.de/community/attachments/f326/390145d1486198357-asrock-z170-extreme6-debug-code-99-foto-2.jpg" rel="nofollow"> |
Replies:
Posted By: wardog
Date Posted: 04 Feb 2017 at 11:44pm
|
Try this, as the 7.xx BIOS are intended for Kaby Lake support. You may have something toggled in the "older' 1.xx that 7.20 is coughing on. This is somewhat commonplace, that a completely new BIOS has a different option for a particular setting. 1. Reset BIOS to Defaults via the Exit tab in the BIOS 2. Let it reboot and immediately re-enter the BIOS 3. Use Instant Flash from within the Tools tab to upflash with 4. Let it reboot and immediately re-enter the BIOS 5. Make the necessary changes in there as needed, then Save Changes and Exit Post back the results please. |
Posted By: parsec
Date Posted: 04 Feb 2017 at 11:48pm
Your links to the pictures show what I think is a registration screen in German for hardwareLUXX. What method did you use to update the BIOS? Code 99 is a problem related to PCIe devices, which is in your board's manual. I don't understand why you tried different memory. Normally when POST fails and a code is displayed, you cannot get into the BIOS at all. That you have been able to get into the BIOS, before you removed your drives (I think) hints at a BIOS setting changed from its default value, compared to BIOS 1.20. I don't know if that is true or not. I'm going by the sequence of things you wrote in your post, which I assume is correct. What M.2 SSD are you using? Is that the OS drive? Did you configure any BIOS settings for the M.2 SSD? I know the CPU support list has BIOS 7.20 needed for an i7-7700K, but any of the 7.xx BIOS versions should work with it. Such as, 7.00 or the 7.10 Beta. The M.2 slot shares resources with the SATA3_0 and SATA3_1 ports, in case you are trying to use both at the same time. ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
batch wrote:Posted By: batch
Date Posted: 05 Feb 2017 at 12:46am
|
Sorry for the black screens: http://imgh.us/Foto_1_34.jpg" rel="nofollow - http://imgh.us/Foto_1_34.jpg http://imgh.us/Foto_2_2.jpg" rel="nofollow - http://imgh.us/Foto_2_2.jpg I know that code 99 is related to PCIe devices. After I pluged off all devices - except CPU and one RAM modul - I just tried another RAM modul to be sure that this curiosity is not caused by the RAMs. I'm using a Samsung SM951 with 512 GB as M.2 with an installed Win10 PRO system Like I said.. with BIOS v1.20 all is working and the OS is booting up. I just tested v2.xx. It causes the same like v7.20 .. freezing with code 99. I cannot do any keyboard actions until I do a hard reset. If I'm quick enough, I can press F2 to enter the BIOS. But dunno what I have to change there to get this working. SATA3_0 and SATA3_1 is not in use. Only CPU, 1 RAM and the SM951. When I remove the SM951, the system will activate the BIOS automatically. I supose that's okay because the board can't find any storage devices.. dunno. |
Posted By: wardog
Date Posted: 05 Feb 2017 at 1:07am
Why, it shouldn't be behaving that way in a Fractal Design case. Of all the cases.  |
Posted By: batch
Date Posted: 05 Feb 2017 at 1:35am
|
well. maybe something is broken. i cannot say it. Just tried v7.10 and v7.0 .. same freeze when any storage device is pluged in. Guess I have to send it back to the supplier to take an eye at this. Maybe they know what to do. |
Posted By: parsec
Date Posted: 05 Feb 2017 at 1:13pm
Wait... wait... Your first picture show the prompt to enter the BIOS, Press F2 or DEL, right? That is the normal prompt seen after updating the UEFI/BIOS. I've seen that screen 100 times. http://imgh.us/Foto_1_34.jpg" rel="nofollow - http://imgh.us/Foto_1_34.jpg The 99 code should mean nothing. If you are prompted to enter the UEFI/BIOS, POST completed successfully. For some reason, your keyboard is not responding after any BIOS update after 1.20. Do you have another keyboard you can use? What keyboard are you using? I assume it is connected to a USB 3.0 port? Is it wireless? Try putting the keyboard connection into another USB port, such as one at the top of the IO panel. Yes, when the SM951 is removed, there is no boot device, so it takes you directly into the BIOS. ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: batch
Date Posted: 05 Feb 2017 at 8:14pm
|
@parsec: good point. I'm using a MS SideWinder X4 wire keyboard as standard. It responses if I'm quick enough and press F2 to enter the BIOS. That's what it works. If I press nothing the keyboard freezes and code 99 is active. I tried several USB ports - no change. I tried two other keyboards, with USB/PS2 - no change .. every time code 99. I'll dream from 'code 99' when I proceed with this nonsense :> |
Posted By: batch
Date Posted: 05 Feb 2017 at 8:19pm
|
I can also press F11 to enter the boot menu. I can take a pick so the keyboard is working within this menu. When I press Enter after I have been choose a boot device - it freezes. |
Posted By: batch
Date Posted: 05 Feb 2017 at 10:21pm
|
" rel="nofollow - I just tried BIOS v1.40 .. freezing like v7.xx Maybe the Board Revision 1.04 has problems with BIOS version higher than 1.20 ? ^^ |
Posted By: wardog
Date Posted: 06 Feb 2017 at 1:35am
|
batch, please list out all the hardware your computer is made up of, using Make and Model. Also state how old your PSU is. |
Posted By: batch
Date Posted: 06 Feb 2017 at 4:36pm
|
- 6700K and 7700K - G.Skill Ripjaws F4-3200C16Q-16GRKD / 4x4GB and G.Skill TridentZ F4-3400C16D-16GTZ / 2x8GB - Samsung SM951 M.2 SSD 512 GB - Samsung 850 Pro 1 TB - HGST 4 TB HDD - PSU Seasonic SS-750KM (750 W) .. it is 1,5 years old But I dont believe on a components fault. If I install an Z170 OCF all is working properly - with BIOS v7.30 or v7.40 .. Win10 is booting up and no problems with code 99 ^^ |
Posted By: wardog
Date Posted: 06 Feb 2017 at 5:11pm
" rel="nofollow -
I'm leaning towards it being the memory you have there. Any friend(s) with some rather mundane low ball DDR4 you can borrow to test using? Both those G.Skill kits you have don't show up on G.Skills own Compatibility List for the Extreme6. The TridentZ show up on the OCFs QVL list, and the Ripjaws4 kit you have is only listed for X99 boards. And then not even an ASRock X99 board. Z170 Extreme6 Compatible List - Tested on and Guaranteed Compatible by G.Skill http://www.gskill.com/en/configurator?manu=52&chip=2484&model=2513 F4-3200C16Q-16GRKD QVL http://www.gskill.com/en/product/f4-3200c16q-16grkd#tabs-qvl F4-3400C16D-16GTZ QVL http://www.gskill.com/en/product/f4-3400c16d-16gtz#tabs-qvl Now. That both kits function on your OCF isn't surprising to me. Between the OCF and Extreme6, we're talking apples to oranges. Different animals altogether. |
Posted By: wardog
Date Posted: 06 Feb 2017 at 5:44pm
|
After re-reading your posts......... Reset the BIOS, then .. using only two of the Ripjaws4 sticks in A2 and B2 slots, boot, go into the BIOS and set them up manually, not via XMP. 3200 16-16-16-36-2N(CR) 1.35v If that fails move them to A1 and B1, reset the BIOS, boot, go into the BIOS and set them up manually, not via XMP. 3200 16-16-16-36-2N(CR) 1.35v Post back your results of those two tests would you please. |
Posted By: batch
Date Posted: 07 Feb 2017 at 4:03am
" rel="nofollow -
Hi, I tested this some days before. I tried 2 pieces to get dual channel, I tried 1 piece in A1, in B1.. always with the same result. I know that there is no official support for my RAMs. But why there's no fault until BIOS v1.2 ? Maybe I'm wrong with this.. but if the board would have problems with the RAMs, the codes 0d or b0 should displayed .. -> http://asrock.com/support/faq.asp%3Fid=334" rel="nofollow - http://asrock.com/support/faq.asp?id=334 |
Posted By: parsec
Date Posted: 07 Feb 2017 at 11:48am
Was this PC sold to you as a package by a company?
If we check the description for the next UEFI/BIOS version after 1.20, 1.40, it has changes for DRAM compatibility. While we may think the description, Improve DRAM compatibility, means we can use more models of memory, that is not what it means. It really means that memory compatibility has been modified to match what it should be for a Skylake processor. I just remembered something else about changing to the Kaby Lake compatible UEFI/BIOS version (7.xx). Did you update the INF files, and the IME software for a Kaby Lake (i7-7700K) processor? That would be the INF driver ver:10.1.1.38, and Intel Management Engine driver ver:11.6.0.1126, from your board's download page: http://www.asrock.com/mb/Intel/Z170%20Extreme6/?cat=Download&os=Win1064 Even if you are still using a Skylake processor (i7-6700K) in the board, the IME firmware that is part of the UEFI/BIOS file, was updated in the 7.xx update. The matching IME software (backward compatible) must be installed. Another thing that worries me now is the number of UEFI/BIOS updates that batch has done. Some of them have CPU microcode updates for various reasons, and IME firmware, which is NOT updated by every update. So who knows what state or combination of them he now has in place. To answer your question about the memory compatibility not being shown as a POST check failure, your memory worked, but was probably not as stable as it should be. Then as the other UEFI/BIOS versions (1.40, etc), made the compatibility worse but not enough to fail completely, other aspects of the CPU could have problems, such as the PCIe lanes. The M.2 SSD uses PCIe lanes, and when it was removed, the 99 code was not shown. We forget that DDR4 memory is very new, only two platforms so far use it, X99 and Skylake/Kaby Lake. I combine those because they are not at all different compared to X99. DDR4 compatibility has been one of the worst problems we have seen in this forum, and it's not getting better... ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: batch
Date Posted: 08 Feb 2017 at 2:52am
No, I selled the components and assembled it.
In the BIOS is IME 11.6.0.1126 installe. This was taken during BIOS update to 7.xx automatically. The M.2 SSD is not the cause. It doesnt matter if there is the M.2 or one/more SATA SSD/HDD plugged in. Even one USB stick with a bootable OS is enough to get the code 99 freezing. I sadly have no other RAM. I think that I will open a RMA ticket. :-) I will post here again, when I know the cause. Maybe it is just RAM incompatibility. Thanks anyway for your help guys. |
Posted By: batch
Date Posted: 18 Feb 2017 at 8:04pm
|
Hi, just want to inform you. Got new board from supplier with rev. 1.05 and all is working properly. BIOS update to 7.20 and Win10 is booting. My old board was rev. 1.04. Dunno what they have changed. |
Posted By: wardog
Date Posted: 18 Feb 2017 at 8:09pm
Terribly sorry for your headaches, whatever they were discovered to be. Unfortunately it sounds like we'll never know. On the Good side, you have a working computer  |
Posted By: batch
Date Posted: 18 Feb 2017 at 8:15pm
|
Right, but well. I got no headaches from testing this out. Only RAM or board were left. So I'm just happy that I don't have to buy new RAMs ^^ |