Dr. Debug display AA |
Post Reply |
Author | ||
Tum
Newbie Joined: 26 Jul 2016 Location: Brasil Status: Offline Points: 3 |
Post Options
Thanks(0)
Posted: 26 Jul 2016 at 1:11am |
|
========================
ASRock > Fatal1ty Z170K6 i76700K > i36100 @4.2Ghz GTX 970 ZOTAC AMP OMEGACore Corsair HX1000W/Sdd 240Gb Raid 1TBvs1TB/Aerocool StrikeX>Corsair Hydro Series >SLI GTX 970 |
||
wardog
Moderator Group Joined: 15 Jul 2015 Status: Offline Points: 6447 |
Post Options
Thanks(0)
|
|
How far into the boot screen(s?) do you get atm ?
|
||
parsec
Moderator Group Joined: 04 May 2015 Location: USA Status: Offline Points: 4996 |
Post Options
Thanks(0)
|
|
Dr Debug, or really POST codes, are not error codes. Each code number identifies a specific test done during the POST (Power On Self Test) process, that happens before the OS begins to load/boot. POST verifies the basic operation of the hardware on a mother board, and the hardware connected to a mother board. If a POST test fails, the code number for the test is displayed on the Dr Debug display. The code is a clue regarding which essential part of the PC is not working correctly. Booting/loading the OS does not/cannot happen if POST does not complete successfully. If you have a POST beep speaker connected to the board, and the POST beep option enabled in the UEFI/BIOS, when we hear a single short beep when a PC starts or restarts, that means POST completed successfully, and the OS boot process has started. If we hear nothing, or multiple short or long beeps, POST failed and the OS boot process was not started. If a PC does not start/boot the OS, and a POST code is displayed, there is a problem with the hardware the POST code refers to. For example, POST codes 01 - 54 (hexadecimal) are various DRAM memory problems. If a PC starts fine, and boots the OS normally, any POST code shown on the display is simply the code of the last POST test. The last set of POST tests checks the IDE, SATA, PCIe, and now NVMe drives connected to the PC. The codes for those tests start with A0, and might go to AF. I've seen one of my PCs in a certain situation stuck on A9. Sometimes the Dr Debug display will show the last POST code sent to it, even though POST has completed and the OS is loading, or we are using the UEFI/BIOS UI. That happens when the Dr Debug display had not received the signal to turn off yet, for some reason. Did you ever notice that when you start the UEFI/BIOS UI, sometimes you'll hear the single POST Ok beep before the UEFI/BIOS screen appears, and sometimes not? Or if you click on Discard Changes and Exit, you'll hear the single beep a moment after the click? A similar thing happens with the Dr Debug display, is what I think happens.
wardog, my guess is the OP's PC booted, but he saw the AA (A8?) code, and is concerned there is a problem. Tum, care to tell us more about what happens with your PC when you see AA on the Dr Debug display? |
||
wardog
Moderator Group Joined: 15 Jul 2015 Status: Offline Points: 6447 |
Post Options
Thanks(0)
|
|
AA is handed off to ACPI, yet with what little the OP has given I though it best to just ask what and how I did. Most likely it runs fine, just with the AA displayed. Which doesn't necessarily indicate any issue. |
||
Post Reply | |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |