ASROCK Dr. Debug Error Codes help
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=24748
Printed Date: 06 May 2024 at 11:25pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: ASROCK Dr. Debug Error Codes help
Posted By: Antoniioo77
Subject: ASROCK Dr. Debug Error Codes help
Date Posted: 19 Jul 2022 at 6:17pm
|
Hi, My system Windows 11 new in one z690 Asrock velocita It starts very slow and reads Manu error Codes on the motherboard display, when It reaches the Windows logo from there is the fast 1 minute reading Codes before reaching the logo. Accompanied by 12900k, ddr5 32gb vengeance 6000mhz and WD SN 850 2TB Is new installation. 55 The Memory could not be detected. Please re-install the memory and CPU. If the problem still exists, please install only one memory module or try using other memory modules. I'm running the default bios, restart the bios and it's still the same, if I run the fast boot those codes take only about 10 seconds and not 1 minute, also with the fast boot disabled, it shouldn't take so long, right? even my hdd can do it faster 22 - OEM pre-memory initialization codes 69 - System Agent DXE initialization is started 22 - OEM pre-memory initialization codes 7F - Reserved for future AMI DXE codes 00 - Not used 99 - Super IO Initialization 98 - Console input devices connect B6 - Clean-up of NVRAM 9A - USB initialization is started 88 - OEM DXE initialization codes 28 - OEM pre-memory initialization codes not safe 29 - OEM pre-memory initialization codes not safe 9C - USB Detect A8 - Setup Verifying Password 99 - Super IO Initialization 98 - Console input devices connect |
Replies:
Posted By: Antoniioo77
Date Posted: 19 Jul 2022 at 6:19pm
| I have more codes error. I dont can upload video here? |
Posted By: Xaltar
Date Posted: 19 Jul 2022 at 6:43pm
|
The debug display is supposed to show those codes. It's basically telling you what part of the POST process is happening. The only time a code indicates an error is if the system freezes or does not boot, then whatever code is frozen on the debug display will tell you what part of the POST (power on self test) failed. A slow booting system is another issue entirely and the debug codes won't tell you what the problem is directly. The only way it can be useful (debug codes) is to see what code remains on the display longest. For example, if your debug display shows a 9A code for 30 seconds then you might have a faulty or incompatible USB device connected to your system that is causing that part of the POST process to be slower than normal. A 99 code could indicate a faulty keyboard or mouse etc. I have seen systems boot slowly because a key on the keyboard was stuck. The debug codes will usually clear by the time your desktop loads. So long as they clear there is no problem. Sometimes a code might persist after waking from sleep but that isn't cause for concern, it will typically clear when you reboot the system. ------------- 
|
Posted By: Antoniioo77
Date Posted: 19 Jul 2022 at 7:27pm
|
Thanks, I tried to disconnect a sata cable that was not in use, the cable was only connected to the motherboard without the SSD, it also did a reading of it or something and it was the cause of the slow problem Startup is great now, thanks. if you could help me with this If I activate the xmp profile of the ram, that slow startup occurs again and I get this screen before the windows logo the system failed to boot several times before Then I let the 10 seconds pass and windows starts. |