Содержание
- Thread: [ISSUE] Maximus VIII Gene Q-code 69: System agent DXE initialization started
- [ISSUE] Maximus VIII Gene Q-code 69: System agent DXE initialization started
- Maximus Gene VII Q Code 15 (Pre-memory System Agent initialization is started)
- stpierren90
- Thread: [ISSUE] Maximus VIII Gene Q-code 69: System agent DXE initialization started
- [ISSUE] Maximus VIII Gene Q-code 69: System agent DXE initialization started
- Что делать при ошибке .NET Framework: «Initialization error»
- Почему возникает ошибка Microsoft .NET Framework: «Initialization error»?
- Microsoft .NET Framework не установлен
- Установлена не правильная версия компонента
- Повреждение компонента Microsoft .NET Framework
Thread: [ISSUE] Maximus VIII Gene Q-code 69: System agent DXE initialization started
Thread Tools
Search Thread
Display
[ISSUE] Maximus VIII Gene Q-code 69: System agent DXE initialization started
first, specs:
Motherboard model: ASUS Maximus VIII GENE
UEFI Version: I have updatet the bios a few times before, i believe last one is version 2202. Might be 3007.
CPU: Intel core i7 6700K
Memory kit part number (s) and amount in GB: 2 times 4GB corsair 2400 MHz ddr4
GPU: MSI gaming GTX 970
SSD/HDDs/Optical drives: samsung 830 series SSD (boot, obviously) and two WD hdd’s
PSU: SEASONIC G550 (550W)
USB Devices (model/version number): NZXT kraken X61 internal usb, roccat mouse, corsair keyboard and dell display USB hub.
Monitor: dell U2515H via displayport and iiyama prolite via hdmi
CPU Cooler: NZXT kraken X61
PC CASE: Bitfenix aegis
Operating system: Microsoft windows 10 educational, legal and activated.
I build this pc in summer 2015 and have had no trouble untill now.
issue
Last Saturday, i walked away from a working pc. When i came back maybe 15 mins later, the only thing indicating life was the fans still running. The display said no signal, lights on the mouse and keyboard were off. So i assume the usb was powered down like when the pc is off.
After a long press on the on/off button everything is shut down and I try to boot again. Then the fans start spinning again, I can hear the hdd’s spinning. However, the seven digit displays stop at code 69. My displays are still off, no lights on the keyboard and mouse. I looked up the code in the manual, it says: » System agent DXE initialization started». By this time, the yellow DRAM LED is off. Unfortunately i couldn’t find much about this with google. Some people reporting the same codes could apparently still enter their bios/uefi or even windows. I think it was on this forum that some guy reported almost the same symptoms but solved it by removing the cmos battery for 5 minutes. I did find that DXE could stand for Driver Execution environment, but it is still cryptical to me.
And so i started to debug the system. I will sum up the most rigorous tests i have done so far:
— I unplugged every usb device (did not forget the internal ones), unplugged ethernet and got the graphics card out and unplugged all the sata cables. Still the same problem. Note that I kept the pc like this in the next tests.
— I checked if it would start with either one of the ram sticks. still the same.
— Tried booting without ram. I got error 55 which indicates ram not installed. so results as expected.
— Tried to boot in safe boot with no result.
— Tried the memOK! button. It goes up to code 35 or something like that and reboots a few times. the DRAM LED will go off, indicating that there is no error there. then it advances to stop at code 69 again.
— Then I tried to clear cmos with the button on the I/O panel. I also tested removing the cmos battery and left the pc powerless overnight. Also didn’t change a thing.
I didn’t try to update the bios yet, as i am not sure what the problem is I don’t like risking it. Also not sure if it would do anything since the other usb devices don’t do anything and USB initialization comes in later stage according to the Q-codes.
I have no idea if this is a cpu or bios problem, or if it is related to anything else on the motherboard.
I need to check the cpu in another desktop to see what generation it is for an eventual swap.
I have a fluke multimeter, so i want to measure the voltages at the ProbeIT points on the motherboard. However I don’t know what they should be, so if someone knows, please mention.
The pc chose quite a bad moment to break down, so I can only continue my troubleshooting this weekend.
I hope that this is enough information, let me know if I forgot anything.
Last edited by Gmount; 06-26-2017 at 07:46 PM .
Источник
Maximus Gene VII Q Code 15 (Pre-memory System Agent initialization is started)
stpierren90
Reputable
So I’ve gone though just about all the troubleshooting steps I can think of at this point before coming here.
So it all started when I noticed my PC had just shut off on its own. Tried to reboot and started doing the 00 «board will not post» loop. Reset the bios and booted to Windows Error Recovery. So I did a recovery boot and it would hang at «windows starting». My OS (Windows 7 64-bit) is on an SSD so I thought it was a bit odd that it was hanging there for as long as it did. After 30 seconds or so I would get a blue screen flash and it would shut down. The screen flashes so quickly I can’t determine what it says. I try a safe mode boot but it hangs on classpnp.sys. Did my research on that and went through those troubleshooting steps. Most common issues were a bad HDD/SSD or the GPU driver was bad. I try putting my SSD in another PC and it’ll get to the Windows Recovery, which the non-working PC won’t. So I’ve ruled out a bad SSD. I try to boot again and now I’m stuck at Q Code 15. At this point I start playing musical chairs with all my RAM and video cards (2 GTX 760’s in SLI). I tried every configuration. Both GPU’s in, one in each PCI, the other in each PCI, 3 different sets of RAM (1866, 2133, and 2400) in every DIMM configuration, did a complete teardown checking all pins and parts for damage, which I didn’t notice anything, reassembled it all, double checked to make sure PSU was all connected properly, and STILL Code 15. The last thing I have yet to try is swapping out the CPU from the other system (both are 1150’s). Other than swapping out the CPU to determine if that’s the cause, is there anything else I’m missing? I have a tendency to miss obvious troubleshooting steps, but at this point I think I’ve tried everything minus the CPU swap.
Also before I got stuck on Q Code 15 I tried doing a fresh install of windows via USB. When it got to the actual install screen, the mouse and keyboard would stop working preventing me to actually install windows (they were plugged into USB 2.0 ports). Tried a PS/2 keyboard as well and would do the same thing.
System Specs (including all RAM used):
OS: Windows 7 64-bit
CPU Cooler: Cooler Master Hyper 212 EVO
RAM: G.Skill TridentX (2 x 8GB) 2400, Corsair Dominator Platinum 8GB (2 x 4GB) 2133, G.Skill Sniper Series 8GB (2 x 4GB) 1866
Mobo: ASUS ROG MAXIMUS VII GENE
GPU: EVGA SuperClocked GeForce GTX 760 2GB 2-way SLI
PSU: CORSAIR AX860
SSD: Kingston SSDNow V300 Series 2.5″ 240GB SATA III
HDD: Seagate Barracuda STBD3000100 3TB 7200 RPM SATA 6.0Gb/s
Источник
Thread: [ISSUE] Maximus VIII Gene Q-code 69: System agent DXE initialization started
Thread Tools
Search Thread
Display
[ISSUE] Maximus VIII Gene Q-code 69: System agent DXE initialization started
first, specs:
Motherboard model: ASUS Maximus VIII GENE
UEFI Version: I have updatet the bios a few times before, i believe last one is version 2202. Might be 3007.
CPU: Intel core i7 6700K
Memory kit part number (s) and amount in GB: 2 times 4GB corsair 2400 MHz ddr4
GPU: MSI gaming GTX 970
SSD/HDDs/Optical drives: samsung 830 series SSD (boot, obviously) and two WD hdd’s
PSU: SEASONIC G550 (550W)
USB Devices (model/version number): NZXT kraken X61 internal usb, roccat mouse, corsair keyboard and dell display USB hub.
Monitor: dell U2515H via displayport and iiyama prolite via hdmi
CPU Cooler: NZXT kraken X61
PC CASE: Bitfenix aegis
Operating system: Microsoft windows 10 educational, legal and activated.
I build this pc in summer 2015 and have had no trouble untill now.
issue
Last Saturday, i walked away from a working pc. When i came back maybe 15 mins later, the only thing indicating life was the fans still running. The display said no signal, lights on the mouse and keyboard were off. So i assume the usb was powered down like when the pc is off.
After a long press on the on/off button everything is shut down and I try to boot again. Then the fans start spinning again, I can hear the hdd’s spinning. However, the seven digit displays stop at code 69. My displays are still off, no lights on the keyboard and mouse. I looked up the code in the manual, it says: » System agent DXE initialization started». By this time, the yellow DRAM LED is off. Unfortunately i couldn’t find much about this with google. Some people reporting the same codes could apparently still enter their bios/uefi or even windows. I think it was on this forum that some guy reported almost the same symptoms but solved it by removing the cmos battery for 5 minutes. I did find that DXE could stand for Driver Execution environment, but it is still cryptical to me.
And so i started to debug the system. I will sum up the most rigorous tests i have done so far:
— I unplugged every usb device (did not forget the internal ones), unplugged ethernet and got the graphics card out and unplugged all the sata cables. Still the same problem. Note that I kept the pc like this in the next tests.
— I checked if it would start with either one of the ram sticks. still the same.
— Tried booting without ram. I got error 55 which indicates ram not installed. so results as expected.
— Tried to boot in safe boot with no result.
— Tried the memOK! button. It goes up to code 35 or something like that and reboots a few times. the DRAM LED will go off, indicating that there is no error there. then it advances to stop at code 69 again.
— Then I tried to clear cmos with the button on the I/O panel. I also tested removing the cmos battery and left the pc powerless overnight. Also didn’t change a thing.
I didn’t try to update the bios yet, as i am not sure what the problem is I don’t like risking it. Also not sure if it would do anything since the other usb devices don’t do anything and USB initialization comes in later stage according to the Q-codes.
I have no idea if this is a cpu or bios problem, or if it is related to anything else on the motherboard.
I need to check the cpu in another desktop to see what generation it is for an eventual swap.
I have a fluke multimeter, so i want to measure the voltages at the ProbeIT points on the motherboard. However I don’t know what they should be, so if someone knows, please mention.
The pc chose quite a bad moment to break down, so I can only continue my troubleshooting this weekend.
I hope that this is enough information, let me know if I forgot anything.
Last edited by Gmount; 06-26-2017 at 07:46 PM .
Источник
Что делать при ошибке .NET Framework: «Initialization error»
Ошибка Microsoft .NET Framework: «Initialization error» связана с невозможностью использовать компонент. Причин этому может быть несколько. Возникает она на этапе запуска игр или программ. Иногда пользователи наблюдают ее при старте Виндовс. Эта ошибка никаким образом не связана с оборудованием или другими программами. Возникает непосредственно в самом компоненте. Давайте рассмотрим подробнее причины ее появления.
Почему возникает ошибка Microsoft .NET Framework: «Initialization error»?
Если вы увидели такое сообщение, например, при старте Windows, это говорит о том, что некоторая программа стоит в автозагрузке и обращается к компоненту Microsoft .NET Framework, а тот в свою очередь выдает ошибку. Тоже самое при запуске определенной игры или программы. Существует несколько причин и вариантов решения проблемы.
Microsoft .NET Framework не установлен
Это особо актуально после переустановки операционной системы. Компонент Microsoft .NET Framework нужен не для всех программ. Поэтому, пользователи зачастую не обращают внимания на его отсутствие. Когда устанавливается новое приложение с поддержкой компонента, возникает следующая ошибка: «Initialization error».
Посмотреть наличие установленного компонента .NET Framework можно в «Панель Управления-Установка и удаление программ».
Если ПО действительно отсутствует, просто переходим на официальный сайт и качаем .NET Framework оттуда. Затем устанавливаем компонент как обычную программу. Перегружаем компьютер. Проблема должна исчезнуть.
Установлена не правильная версия компонента
Заглянув в список установленных программ на компьютере, вы обнаружили, что .NET Framework там присутствует, а проблема по прежнему возникает. Скорее всего компонент необходимо обновить до последней версии. Сделать это можно вручную, скачав нужную версию с сайта Microsoft или же с помощью специальных программ.
Маленькая утилита ASoft .NET Version Detector позволяет быстро загрузить необходимую версию компонента Microsoft .NET Framework. Нажимаем на зеленую стрелку напротив интересующей версии и скачиваем ее.
Также, с помощью этой программы, можно посмотреть все версии .NET Framework установленные на компьютере.
После обновления, компьютер должен быть перегружен.
Повреждение компонента Microsoft .NET Framework
Последняя причина появления ошибки «Initialization error», может быть связана с повреждением файлов компонента. Это может быть последствием вирусов, неправильной установкой и удалением компонента, очисткой системы различными программами и т.п. В любом случае, Microsoft .NET Framework из компьютера нужно удалить и поставить заново.
Чтобы правильно деинсталлировать Microsoft .NET Framework, используем дополнительные программы, например утилиту .NET Framework Cleanup Tool.
Затем, с сайта Microsoft качаем нужную версию и устанавливаем компонент. После, еще раз перезапускаем систему.
После проведенных манипуляций ошибка Microsoft .NET Framework: «Initialization error» должна исчезнуть.
Источник
Куратор(ы):
DrDEVIL666
| Автор | Сообщение | |||
|---|---|---|---|---|
|
||||
Куратор темы Статус: Не в сети |
Прочтите FAQ При обсуждении просьба соблюдать правила как Конференции, так и раздела Материнские платы. Прежде чем задать вопрос, заполните Конфигурацию компьютера в Профиле, включая ОС Последний раз редактировалось ADDD 14.05.2012 1:06, всего редактировалось 14 раз(а). |
Добавлено: 25.05.2011 9:17 | Реклама | |
|
Партнер |
|
MiG73 |
|
|
Member Статус: Не в сети |
smiley92 |
|
smiley92 |
|
|
Member Статус: Не в сети |
MiG73 писал(а): на вашей плате есть доп. чип ASMedia (1 синий SATA-3 и 1 eSATA-3) не знаю… подключил ССД в синий порт но нужное приложение также криво устанавливается (( |
|
MiG73 |
|
|
Member Статус: Не в сети |
smiley92 Если ознакомиться с темами про SSD, то станет понятно, что крайне нежелательно подключать его к сторонним контроллерам. Подключите к первому белому чипсетному SATA-3, а на ASMedia повесте разве что DVD. И что за программа вас смущает? сдается мне что с MB и чипсетом все впорядке. |
|
smiley92 |
|
|
Member Статус: Не в сети |
MiG73 писал(а): Если ознакомиться с темами про SSD, то станет понятно, что крайне нежелательно подключать его к сторонним контроллерам Ну я хотел хоть вполовину работающую материнку получить. Чипсетные порты точно глючат. |
|
MiG73 |
|
|
Member Статус: Не в сети |
smiley92 |
|
MilligramSmile |
|
|
Заблокирован Статус: Не в сети |
Подскажите, что-то на плате Asus RoG Maximus IV Extreme-Z глючат USB порты. красным — не определяется флешка usb 2.0 на 8 гигов, флешка usb 3.0 на 32 гига, телефон (S4) хотя зарядка телефона идет, мышка так же не определяется В диспетчере какая-то шляпа неизвестная, дрова на которую не могу определить. ИД оборудования: USBUNKNOWN Последний раз редактировалось MilligramSmile 01.07.2016 16:49, всего редактировалось 1 раз. |
|
NanaCeres |
|
|
Member Статус: Не в сети |
kimster08 |
|
MilligramSmile |
|
|
Заблокирован Статус: Не в сети |
NanaCeres да установлены, вот посоветовали на чипсет и юсб 3.0 переустановить Добавлено спустя 11 минут 28 секунд: Добавлено спустя 47 минут 17 секунд: |
|
Kclick |
|
|
Junior Статус: Не в сети |
Вопрос! |
|
MiG73 |
|
|
Member Статус: Не в сети |
Kclick Ошибка инициализации системного агента после загрузки микрокода. |
|
Kclick |
|
|
Junior Статус: Не в сети |
MiG73 писал(а): Kclick Ошибка инициализации системного агента после загрузки микрокода. Комп собирал сам, через некоторое время чистил его от пыли, полная разборка и сборка, все работало, спустя 15 дней простоя ( комп отключен был) такая ерунда(((( |
|
MiG73 |
|
|
Member Статус: Не в сети |
Kclick p.s. И не надо больше для чистки от пыли делать разборку. |
|
DonCarleone |
|
|
Member Статус: Не в сети |
Kclick Попробуй вынуть все переферийные устройства, видеокарту вытащи, монитор подключи к hdmi на материнки, все жесткие диски отключи, оставь только системный, оставь 1 планку оперативки. Может слот под видео глючит, попробуй в другой слот воткни. В общем ищи методом исключения, начни с видеокарты, оперативки. Возможно как вариант села батарейка на мамке. |
|
Elochka |
|
|
Junior Статус: Не в сети |
Всем привет. |
|
MiG73 |
|
|
Member Статус: Не в сети |
Elochka Должна встать, но я бы не переплачивал за такую DDR3 с заводским разгоном. Лучше обычную DDR3 1300 и выставить в BIOS 1600MHz (Samsung, Kingston или Hinix). Или обычную 1600 выставить 1800MHz (у меня так гарантировано работает Samsung). |
|
Lenivezz |
|
|
Member Статус: Не в сети |
Elochka |
|
Elochka |
|
|
Junior Статус: Не в сети |
Спасибо, кто ответил. Буду пробовать, по результату отпишусь (вдруг поможет кому в будущем). По поводу переплаты: так получается, что такой комплект выходит чуть ли не дешевле, чем две отдельные планки от прочих производителей. Вот такая ценовая политика)) |
|
AHDPEY198329477 |
|
|
Member Статус: В сети |
На моей профильной матери можно обороты корпусных вентилей опустить ниже 60%? |
|
Vetalar |
|
|
Member Статус: Не в сети |
AHDPEY198329477 |
|
AHDPEY198329477 |
|
|
Member Статус: В сети |
Vetalar А обороты кулера видюхи подключенного к мат. плате можно настроить в зависимости от температуры видюхи? |
—
Кто сейчас на конференции |
|
Сейчас этот форум просматривают: Google [Bot] и гости: 70 |
| Вы не можете начинать темы Вы не можете отвечать на сообщения Вы не можете редактировать свои сообщения Вы не можете удалять свои сообщения Вы не можете добавлять вложения |
Лаборатория
Новости
| Автор |
|
|||
|---|---|---|---|---|
|
[ТС] |
Заголовок сообщения: ASUS Rampage IV Extreme потеряла часть ОЗУ
|
|||
Сообщения: 4 |
Господа, прошу прощения, сам я от ремонта матерей далековат, официалы говорят неси в СЦ и кидают ссылку, по ссылке СЦ как оказалось сейчас ремонтом материнских плат не занимается, тупо меняют. Но так как у меня гарантия кончилась, найти СЦ который занимался бы ремонтом МП, даже в Москве, оказалось не так просто. Перейду к делу. Проблема: Asus Rampage IV Debug Codes Экран монитора ничего не показывает. |
|||
|
|
|
|||
 |
Добавлено: 01 сен 2016, 23:02 
|
Sword93 |
Заголовок сообщения: Re: ASUS Rampage IV Extreme потеряла часть ОЗУ
|
|
Сообщения: 332 |
Argentum писал(а): ASUS Rampage IV Extreme Проверьте питающие напряжения во всех слотах оперативной памяти. |
|
|
|
|
|
Argentum |
Заголовок сообщения: Re: ASUS Rampage IV Extreme потеряла часть ОЗУ
|
|
Сообщения: 4 |
Проверил, все в полном порядке, значения идеальные, с мелким разбросом в тысячные. |
|
|
|
|
|
xp_en |
Заголовок сообщения: Re: ASUS Rampage IV Extreme потеряла часть ОЗУ
|
|
Сообщения: 22 |
Запустите плату вообще без памяти. После сигналов об отсутствии памяти выключите и установите всю память. Не знаю чем объясняется, но на P5OL PRO такое помогало в ситуации, когда плата не стартовала и биос не подавал никаких сигналов. |
|
|
|
|
|
remmax |
Заголовок сообщения: Re: ASUS Rampage IV Extreme потеряла часть ОЗУ
|
|
Сообщения: 245 |
вы когда процессор вытаскивали и протирали его спиртом, контакты в сокете процессора не могли погнуть? в вашем случае к процессору лезть нужно было в последнюю очередь, сначала вытащить всю память и заново вставить, если не помогло то поиграться перестановками одной планки по всем слотам чтобы убедится какие работают, а потом уже если не работают какие то, то лезть к процессору и ещё, процессор не разгонялся? в перегретом состоянии не работал? сбрось биос на всякий случай |
|
|
|
|
|
votinovlex |
Заголовок сообщения: Re: ASUS Rampage IV Extreme потеряла часть ОЗУ
|
|
Сообщения: 118 |
1. ещё раз снимаем процессор и смотрим все контакты — не загнуты ли они ? |
|
|
|
|
|
MamontIt |
Заголовок сообщения: Re: ASUS Rampage IV Extreme потеряла часть ОЗУ
|
|
Сообщения: 18 |
Я в подобной ситуации перепрошил биос , не помогло. поменял оперативки нормально стало… |
|
|
|
|
|
Argentum |
Заголовок сообщения: Re: ASUS Rampage IV Extreme потеряла часть ОЗУ
|
|
Сообщения: 4 |
xp_en писал(а): Запустите плату вообще без памяти. После сигналов об отсутствии памяти выключите и установите всю память. Пробовал, не помогало. remmax писал(а): вы когда процессор вытаскивали и протирали его спиртом, контакты в сокете процессора не могли погнуть? Погнуть не мог, это мой далеко не первый ПК собранный собственноручно. remmax писал(а): в вашем случае к процессору лезть нужно было в последнюю очередь, сначала вытащить всю память и заново вставить, если не помогло то поиграться перестановками одной планки по всем слотам чтобы убедится какие работают, а потом уже если не работают какие то, то лезть к процессору Сначала вытащил всю память и заново вставил — не помогло. Решил поиграться перестановкой планок по всем слотам, система не включалась, вернее не загорался дисплей. По совету на форуме переставил цп, просто снял и заново установил, система завелась, но с таким вот побочным эффектом. remmax писал(а): и ещё, процессор не разгонялся? в перегретом состоянии не работал? Нет, систему не разгонял, без охлаждения не включал. remmax писал(а): сбрось биос на всякий случай Пробовал очень много раз, недавно вообще перешил, но результат тот же. votinovlex писал(а): 1. ещё раз снимаем процессор и смотрим все контакты — не загнуты ли они ? 1. Сделал |
|
|
|
|
|
olegkeeeee |
Заголовок сообщения: Re: ASUS Rampage IV Extreme потеряла часть ОЗУ
|
|
Сообщения: 178 |
Argentum писал(а): 1. Сделал Никакой нормальный мастер никогда не посоветует вам что-либо выниматьвставлять внутри системного блока НА ГОРЯЧУЮ! Если это конечно не касается микросхемы БИОСа. Вам бы попробовать найти мать поддерживающую ваш процессор и ткнуть туда проц и ОЗУ дабы проверить и делать выводы. Возможно что-то статикой шлепнуло… |
|
|
|
|
|
votinovlex |
Заголовок сообщения: Re: ASUS Rampage IV Extreme потеряла часть ОЗУ
|
|
Сообщения: 118 |
на горячую вставлять и доставать ничего не надо. а так вам дельный совет уже дали, постарайтесь найти другую мать , дабы полностью убедиться в работоспособности комплектующих |
|
|
|
|
|
remmax |
Заголовок сообщения: Re: ASUS Rampage IV Extreme потеряла часть ОЗУ
|
|
Сообщения: 245 |
есть сокет тестер слотов памяти, я с китая заказывал, там линейка со светодиодами и батарейкой как от биоса, иногда облегчает задачу, также есть такие же тестеры сокетов процессора, но в вашем случае покупать всё это не рентабельно |
|
|
|
|
|
Argentum |
Заголовок сообщения: Re: ASUS Rampage IV Extreme потеряла часть ОЗУ [РЕШЕНО]
|
|
Сообщения: 4 |
Проблема похоже обнаружилась. |
|
|
|
|
-
10-12-2013 11:26 PM
#1
ROG Member
Array
Error Code 15 pre memory system agent initialization is started?
So I have had my system up and running for about three weeks now, teaking here and there, but I have been out of the game for a long time so it has taking me some catching up to do.
Current systems specs:
Maximus vi Extreme
4770k Delidded
G Skill trident X 32gb 2800
2 x MSI GTX 780 Lightning (SLI)
Samsung evo 250gb SSD
EVGA G2 1300w PSUSystem is under a Single stage phase change unit.
The system was running perfectly fine at 4.8ghz before I decided to instal a probe type k.
I was concerned with the cpu temp not being what the type k probe attached to the evap was so I ordered a spare and placed it under the processor. It is sitting ontop of a piece of insulation and taped down to it to cover all the metal up.
AFter this I have not been able to post, nothing even comes on screen. I get error code 15 and that is listed pre memory system agent initialization is started?
Can someone please help me?
-
10-13-2013 03:14 AM
#2
ROG Guru: Grand Master
Array
Have you tried removing the probe?
-
10-13-2013 03:23 AM
#3
ROG Member
Array
Yup pulled the probe. Still nothing.
Tried reseating the DIMM’s one by one, and swapping between all 4 sticks.
I afraid it might be a bent pin or something. The CPU LED is lit up.
I read somewhere that Asus will replace the socket? for a fee?
-
10-13-2013 03:25 AM
#4
ROG Guru: Grand Master
Array
Before you jump to conclusions, you can remove your CPU and inspect the CPU socket carefully for any bent or missing pins.
-
10-13-2013 03:31 AM
#5
ROG Member
Array
I plan on it in the morning, when there is more light. I live in a ****ty apt, so light is not my firend until the sun comes up. I have taken the thing apart three different times today trying to square it away, fingers crossed I will check the socket tomorrow.
-
10-13-2013 03:42 AM
#6
ROG Guru: Grand Master
Array
After you’ve checked the socket, try using the stock heatsink instead of your chiller. And also clean the memory slots just in case and insert just one stick of RAM into the DIMM_A2 slot. Verify that it’s installed correctly and inserted all the way down into the slow until you hear the click sound.
-
10-13-2013 01:19 PM
#7
ROG Member
Array
Well it likes somehow my art eraser go pushed into the socket. Dont know how I missed that when I installed the probe. its pushing th pins, but cant say for sure how far out of the way.
-
10-14-2013 10:53 AM
#8
ROG Guru: Grand Master
Array
No worries you should be able to resolve the bent pins. Just need a steady hand some good light
and a very thin blade, simply nudge the pins back in line very gently. Remember they are made of spring like metal so you need to do the movements in small amounts.
To help us help you — please provide as much information about your system and the problem as possible.
-
10-14-2013 06:08 PM
#9
ROG Member
Array
So I pulled it all apart ready to RMA it, got the number from Asus and everything. Decided to give it one last wack and straightening the pins, and attached one stick of ram and the stock cooler and bamm it fired right up.
MAKE UP YOUR MIND!!!!! lol
So now I have to call asus back and be like nevemind,
Did lose my OC though, sad face…
-
10-14-2013 06:15 PM
#10
ROG Guru: Grand Master
Array
Ah rather loose the OC and have the board working my friend.
We can work on the OC no worries with that.
To help us help you — please provide as much information about your system and the problem as possible.
and a very thin blade, simply nudge the pins back in line very gently. Remember they are made of spring like metal so you need to do the movements in small amounts.
00 — Not used
01 — Power on. Reset type detection (soft/hard)
02 — AP initialization before microcode loading
03 — System Agent initialization before microcode loading
04 — PCH initialization before microcode loading
05 — OEM initialization before microcode loading
06 — Microcode loading
07 — AP initialization after microcode loading
08 — System Agent initialization after microcode loading
09 — PCH initialization after microcode loading
0A — OEM initialization after microcode loading
0B — Cache initialization
SEC Error Codes
0C — Reserved for future AMI SEC error codes
0D — Reserved for future AMI SEC error codes
0E — Microcode not found
0F — Microcode not loaded
PEI Phase
10 — PEI Core is started
11 — Pre-memory CPU initialization is started
12 — Pre-memory CPU initialization (CPU module specific)
13 — Pre-memory CPU initialization (CPU module specific)
14 — Pre-memory CPU initialization (CPU module specific)
15 — Pre-memory System Agent initialization is started
16 — Pre-Memory System Agent initialization (System Agent module specific)
17 — Pre-Memory System Agent initialization (System Agent module specific)
18 — Pre-Memory System Agent initialization (System Agent module specific)
19 — Pre-memory PCH initialization is started
1A — Pre-memory PCH initialization (PCH module specific)
1B — Pre-memory PCH initialization (PCH module specific)
1C — Pre-memory PCH initialization (PCH module specific)
1D — OEM pre-memory initialization codes
1E — OEM pre-memory initialization codes
1F — OEM pre-memory initialization codes
20 — OEM pre-memory initialization codes
21 — OEM pre-memory initialization codes
22 — OEM pre-memory initialization codes
23 — OEM pre-memory initialization codes
24 — OEM pre-memory initialization codes
25 — OEM pre-memory initialization codes
26 — OEM pre-memory initialization codes
27 — OEM pre-memory initialization codes
28 — OEM pre-memory initialization codes
29 — OEM pre-memory initialization codes
2A — OEM pre-memory initialization codes
2B — Memory initialization. Serial Presence Detect (SPD) data reading
2C — Memory initialization. Memory presence detection
2D — Memory initialization. Programming memory timing information
2E — Memory initialization. Confi guring memory
2F — Memory initialization (other)
30 — Reserved for ASL (see ASL Status Codes section below)
31 — Memory Installed
32 — CPU post-memory initialization is started
33 — CPU post-memory initialization. Cache initialization
34 — CPU post-memory initialization. Application Processor(s) (AP) initialization
35 — CPU post-memory initialization. Boot Strap Processor (BSP) selection
36 — CPU post-memory initialization. System Management Mode (SMM) initialization
37 — Post-Memory System Agent initialization is started
38 — Post-Memory System Agent initialization (System Agent module specific)
39 — Post-Memory System Agent initialization (System Agent module specific)
3A — Post-Memory System Agent initialization (System Agent module specific)
3B — Post-Memory PCH initialization is started
3C — Post-Memory PCH initialization (PCH module specific)
3D — Post-Memory PCH initialization (PCH module specific)
3E — Post-Memory PCH initialization (PCH module specific)
3F — OEM post memory initialization codes
40 — OEM post memory initialization codes
41 — OEM post memory initialization codes
42 — OEM post memory initialization codes
43 — OEM post memory initialization codes
44 — OEM post memory initialization codes
45 — OEM post memory initialization codes
46 — OEM post memory initialization codes
47 — OEM post memory initialization codes
48 — OEM post memory initialization codes
49 — OEM post memory initialization codes
4A — OEM post memory initialization codes
4B — OEM post memory initialization codes
4C — OEM post memory initialization codes
4D — OEM post memory initialization codes
4E — OEM post memory initialization codes
4F — DXE IPL is started
PEI Error Codes
50 — Memory initialization error. Invalid memory type or incompatible memory speed
51 — Memory initialization error. SPD reading has failed
52 — Memory initialization error. Invalid memory size or memory modules do not match
53 — Memory initialization error. No usable memory detected
54 — Unspecifi ed memory initialization error
55 — Memory not installed
56 — Invalid CPU type or Speed
57 — CPU mismatch
58 — CPU self test failed or possible CPU cache error
59 — CPU micro-code is not found or micro-code update is failed
5A — Internal CPU error
5B — reset PPI is not available
5C — Reserved for future AMI error codes
5D — Reserved for future AMI error codes
5E — Reserved for future AMI error codes
5F — Reserved for future AMI error codes
DXE Phase
60 — DXE Core is started
61 — NVRAM initialization
62 — Installation of the PCH Runtime Services
63 — CPU DXE initialization is started
64 — CPU DXE initialization (CPU module specific)
65 — CPU DXE initialization (CPU module specific)
66 — CPU DXE initialization (CPU module specific)
67 — CPU DXE initialization (CPU module specific)
68 — PCI host bridge initialization
69 — System Agent DXE initialization is started
6A — System Agent DXE SMM initialization is started
6B — System Agent DXE initialization (System Agent module specific)
6C — System Agent DXE initialization (System Agent module specific)
6D — System Agent DXE initialization (System Agent module specific)
6E — System Agent DXE initialization (System Agent module specific)
6F — System Agent DXE initialization (System Agent module specific)
70 — PCH DXE initialization is started
71 — PCH DXE SMM initialization is started
72 — PCH devices initialization
73 — PCH DXE Initialization (PCH module specific)
74 — PCH DXE Initialization (PCH module specific)
75 — PCH DXE Initialization (PCH module specific)
76 — PCH DXE Initialization (PCH module specific)
77 — PCH DXE Initialization (PCH module specific)
78 — ACPI module initialization
79 — CSM initialization
7A — Reserved for future AMI DXE codes
7B — Reserved for future AMI DXE codes
7C — Reserved for future AMI DXE codes
7D — Reserved for future AMI DXE codes
7E — Reserved for future AMI DXE codes
7F — Reserved for future AMI DXE codes
80 — OEM DXE initialization codes
81 — OEM DXE initialization codes
82 — OEM DXE initialization codes
83 — OEM DXE initialization codes
84 — OEM DXE initialization codes
85 — OEM DXE initialization codes
86 — OEM DXE initialization codes
87 — OEM DXE initialization codes
88 — OEM DXE initialization codes
89 — OEM DXE initialization codes
8A — OEM DXE initialization codes
8B — OEM DXE initialization codes
8C — OEM DXE initialization codes
8D — OEM DXE initialization codes
8E — OEM DXE initialization codes
8F — OEM DXE initialization codes
90 — Boot Device Selection (BDS) phase is started
91 — Driver connecting is started
92 — PCI Bus initialization is started
93 — PCI Bus Hot Plug Controller Initialization
94 — PCI Bus Enumeration 32
95 — PCI Bus Request Resources
96 — PCI Bus Assign Resources
97 — Console Output devices connect
98 — Console input devices connect
99 — Super IO Initialization
9A — USB initialization is started
9B — USB Reset
9C — USB Detect
9D — USB Enable
9E — Reserved for future AMI codes
9F — Reserved for future AMI codes
A0 — IDE initialization is started
A1 — IDE Reset
A2 — IDE Detect
A3 — IDE Enable
A4 — SCSI initialization is started
A5 — SCSI Reset
A6 — SCSI Detect
A7 — SCSI Enable
A8 — Setup Verifying Password
A9 — Start of Setup
AA — Reserved for ASL (see ASL Status Codes section below)
AB — Setup Input Wait
AC — Reserved for ASL (see ASL Status Codes section below)
AD — Ready To Boot event
AE — Legacy Boot event
AF — Exit Boot Services event
B0 — Runtime Set Virtual Address MAP Begin
B1 — Runtime Set Virtual Address MAP End
B2 — Legacy Option ROM Initialization
B3 — System Reset
B4 — USB hot plug
B5 — PCI bus hot plug
B6 — Clean-up of NVRAM
B7 — Confi guration Reset (reset of NVRAM settings)
B8 — Reserved for future AMI codes
B9 — Reserved for future AMI codes
BA — Reserved for future AMI codes
BB — Reserved for future AMI codes
BC — Reserved for future AMI codes
BD — Reserved for future AMI codes
BE — Reserved for future AMI codes
BF — Reserved for future AMI codes
C0 — OEM BDS initialization codes
C1 — OEM BDS initialization codes
C2 — OEM BDS initialization codes
C3 — OEM BDS initialization codes
C4 — OEM BDS initialization codes
C5 — OEM BDS initialization codes
C6 — OEM BDS initialization codes
C7 — OEM BDS initialization codes
C8 — OEM BDS initialization codes
C9 — OEM BDS initialization codes
CA — OEM BDS initialization codes
CB — OEM BDS initialization codes
CC — OEM BDS initialization codes
CD — OEM BDS initialization codes
CE — OEM BDS initialization codes
CF — OEM BDS initialization codes
DXE Error Codes
D0 — CPU initialization error
D1 — System Agent initialization error
D2 — PCH initialization error
D3 — Some of the Architectural Protocols are not available
D4 — PCI resource allocation error. Out of Resources
D5 — No Space for Legacy Option ROM
D6 — No Console Output Devices are found
D7 — No Console Input Devices are found
D8 — Invalid password
D9 — Error loading Boot Option (LoadImage returned error)
DA — Boot Option is failed (StartImage returned error)
DB — Flash update is failed
DC — Reset protocol is not available
S3 Resume Progress Codes
E0 — S3 Resume is stared (S3 Resume PPI is called by the DXE IPL)
E1 — S3 Boot Script execution
E2 — Video repost
E3 — OS S3 wake vector call
E4 — Reserved for future AMI progress codes
E5 — Reserved for future AMI progress codes
E6 — Reserved for future AMI progress codes
E7 — Reserved for future AMI progress codes
S3 Resume Error Codes
E8 — S3 Resume Failed
E9 — S3 Resume PPI not Found
EA — S3 Resume Boot Script Error
EB — S3 OS Wake Error
EC — Reserved for future AMI error codes 31
ED — Reserved for future AMI error codes 31
EE — Reserved for future AMI error codes 31
EF — Reserved for future AMI error codes 31
Recovery Progress Codes
F0 — Recovery condition triggered by firmware (Auto recovery)
F1 — Recovery condition triggered by user (Forced recovery)
F2 — Recovery process started
F3 — Recovery fi rmware image is found
F4 — Recovery fi rmware image is loaded
F5 — Reserved for future AMI progress codes
F6 — Reserved for future AMI progress codes
F7 — Reserved for future AMI progress codes
Recovery Error Codes
F8 — Recovery PPI is not available
F9 — Recovery capsule is not found
FA — Invalid recovery capsule
FB — Reserved for future AMI error codes
FC — Reserved for future AMI error codes
FD — Reserved for future AMI error codes
FE — Reserved for future AMI error codes
FF — Reserved for future AMI error codes
ACPI/ASL Checkpoints
01 — System is entering S1 sleep state
02 — System is entering S2 sleep state
03 — System is entering S3 sleep state
04 — System is entering S4 sleep state
05 — System is entering S5 sleep state
10 — System is waking up from the S1 sleep state
20 — System is waking up from the S2 sleep state
30 — System is waking up from the S3 sleep state
40 — System is waking up from the S4 sleep state
AC — System has transitioned into ACPI mode. Interrupt controller is in APIC mode
AA — System has transitioned into ACPI mode. Interrupt controller is in APIC mode
Leaving this here so everyone, moderators and users, can have the benefit of having a single place to go look for reference. If anyone notices anything wrong with these, please let me know.
Please keep this topic free of support questions. This is strictly meant for the hex codes for everyone’s benefit.
Progress Codes
00 — Not used
01 — Power on. Reset type detection (soft/hard)
02 — AP initialization before microcode loading
03 — System Agent initialization before microcode loading
04 — PCH initialization before microcode loading
05 — OEM initialization before microcode loading
06 — Microcode loading
07 — AP initialization after microcode loading
08 — System Agent initialization after microcode loading
09 — PCH initialization after microcode loading
0A — OEM initialization after microcode loading
0B — Cache initialization
SEC Error Codes
0C — Reserved for future AMI SEC error codes
0D — Reserved for future AMI SEC error codes
0E — Microcode not found
0F — Microcode not loaded
PEI Phase
10 — PEI Core is started
11 — Pre-memory CPU initialization is started
12 — Pre-memory CPU initialization (CPU module specific)
13 — Pre-memory CPU initialization (CPU module specific)
14 — Pre-memory CPU initialization (CPU module specific)
15 — Pre-memory System Agent initialization is started
16 — Pre-Memory System Agent initialization (System Agent module specific)
17 — Pre-Memory System Agent initialization (System Agent module specific)
18 — Pre-Memory System Agent initialization (System Agent module specific)
19 — Pre-memory PCH initialization is started
1A — Pre-memory PCH initialization (PCH module specific)
1B — Pre-memory PCH initialization (PCH module specific)
1C — Pre-memory PCH initialization (PCH module specific)
1D — OEM pre-memory initialization codes
1E — OEM pre-memory initialization codes
1F — OEM pre-memory initialization codes
20 — OEM pre-memory initialization codes
21 — OEM pre-memory initialization codes
22 — OEM pre-memory initialization codes
23 — OEM pre-memory initialization codes
24 — OEM pre-memory initialization codes
25 — OEM pre-memory initialization codes
26 — OEM pre-memory initialization codes
27 — OEM pre-memory initialization codes
28 — OEM pre-memory initialization codes
29 — OEM pre-memory initialization codes
2A — OEM pre-memory initialization codes
2B — Memory initialization. Serial Presence Detect (SPD) data reading
2C — Memory initialization. Memory presence detection
2D — Memory initialization. Programming memory timing information
2E — Memory initialization. Confi guring memory
2F — Memory initialization (other)
30 — Reserved for ASL (see ASL Status Codes section below)
31 — Memory Installed
32 — CPU post-memory initialization is started
33 — CPU post-memory initialization. Cache initialization
34 — CPU post-memory initialization. Application Processor(s) (AP) initialization
35 — CPU post-memory initialization. Boot Strap Processor (BSP) selection
36 — CPU post-memory initialization. System Management Mode (SMM) initialization
37 — Post-Memory System Agent initialization is started
38 — Post-Memory System Agent initialization (System Agent module specific)
39 — Post-Memory System Agent initialization (System Agent module specific)
3A — Post-Memory System Agent initialization (System Agent module specific)
3B — Post-Memory PCH initialization is started
3C — Post-Memory PCH initialization (PCH module specific)
3D — Post-Memory PCH initialization (PCH module specific)
3E — Post-Memory PCH initialization (PCH module specific)
3F — OEM post memory initialization codes
40 — OEM post memory initialization codes
41 — OEM post memory initialization codes
42 — OEM post memory initialization codes
43 — OEM post memory initialization codes
44 — OEM post memory initialization codes
45 — OEM post memory initialization codes
46 — OEM post memory initialization codes
47 — OEM post memory initialization codes
48 — OEM post memory initialization codes
49 — OEM post memory initialization codes
4A — OEM post memory initialization codes
4B — OEM post memory initialization codes
4C — OEM post memory initialization codes
4D — OEM post memory initialization codes
4E — OEM post memory initialization codes
4F — DXE IPL is started
PEI Error Codes
50 — Memory initialization error. Invalid memory type or incompatible memory speed
51 — Memory initialization error. SPD reading has failed
52 — Memory initialization error. Invalid memory size or memory modules do not match
53 — Memory initialization error. No usable memory detected
54 — Unspecifi ed memory initialization error
55 — Memory not installed
56 — Invalid CPU type or Speed
57 — CPU mismatch
58 — CPU self test failed or possible CPU cache error
59 — CPU micro-code is not found or micro-code update is failed
5A — Internal CPU error
5B — reset PPI is not available
5C — Reserved for future AMI error codes
5D — Reserved for future AMI error codes
5E — Reserved for future AMI error codes
5F — Reserved for future AMI error codes
DXE Phase
60 — DXE Core is started
61 — NVRAM initialization
62 — Installation of the PCH Runtime Services
63 — CPU DXE initialization is started
64 — CPU DXE initialization (CPU module specific)
65 — CPU DXE initialization (CPU module specific)
66 — CPU DXE initialization (CPU module specific)
67 — CPU DXE initialization (CPU module specific)
68 — PCI host bridge initialization
69 — System Agent DXE initialization is started
6A — System Agent DXE SMM initialization is started
6B — System Agent DXE initialization (System Agent module specific)
6C — System Agent DXE initialization (System Agent module specific)
6D — System Agent DXE initialization (System Agent module specific)
6E — System Agent DXE initialization (System Agent module specific)
6F — System Agent DXE initialization (System Agent module specific)
70 — PCH DXE initialization is started
71 — PCH DXE SMM initialization is started
72 — PCH devices initialization
73 — PCH DXE Initialization (PCH module specific)
74 — PCH DXE Initialization (PCH module specific)
75 — PCH DXE Initialization (PCH module specific)
76 — PCH DXE Initialization (PCH module specific)
77 — PCH DXE Initialization (PCH module specific)
78 — ACPI module initialization
79 — CSM initialization
7A — Reserved for future AMI DXE codes
7B — Reserved for future AMI DXE codes
7C — Reserved for future AMI DXE codes
7D — Reserved for future AMI DXE codes
7E — Reserved for future AMI DXE codes
7F — Reserved for future AMI DXE codes
80 — OEM DXE initialization codes
81 — OEM DXE initialization codes
82 — OEM DXE initialization codes
83 — OEM DXE initialization codes
84 — OEM DXE initialization codes
85 — OEM DXE initialization codes
86 — OEM DXE initialization codes
87 — OEM DXE initialization codes
88 — OEM DXE initialization codes
89 — OEM DXE initialization codes
8A — OEM DXE initialization codes
8B — OEM DXE initialization codes
8C — OEM DXE initialization codes
8D — OEM DXE initialization codes
8E — OEM DXE initialization codes
8F — OEM DXE initialization codes
90 — Boot Device Selection (BDS) phase is started
91 — Driver connecting is started
92 — PCI Bus initialization is started
93 — PCI Bus Hot Plug Controller Initialization
94 — PCI Bus Enumeration 32
95 — PCI Bus Request Resources
96 — PCI Bus Assign Resources
97 — Console Output devices connect
98 — Console input devices connect
99 — Super IO Initialization
9A — USB initialization is started
9B — USB Reset
9C — USB Detect
9D — USB Enable
9E — Reserved for future AMI codes
9F — Reserved for future AMI codes
A0 — IDE initialization is started
A1 — IDE Reset
A2 — IDE Detect
A3 — IDE Enable
A4 — SCSI initialization is started
A5 — SCSI Reset
A6 — SCSI Detect
A7 — SCSI Enable
A8 — Setup Verifying Password
A9 — Start of Setup
AA — Reserved for ASL (see ASL Status Codes section below)
AB — Setup Input Wait
AC — Reserved for ASL (see ASL Status Codes section below)
AD — Ready To Boot event
AE — Legacy Boot event
AF — Exit Boot Services event
B0 — Runtime Set Virtual Address MAP Begin
B1 — Runtime Set Virtual Address MAP End
B2 — Legacy Option ROM Initialization
B3 — System Reset
B4 — USB hot plug
B5 — PCI bus hot plug
B6 — Clean-up of NVRAM
B7 — Confi guration Reset (reset of NVRAM settings)
B8 — Reserved for future AMI codes
B9 — Reserved for future AMI codes
BA — Reserved for future AMI codes
BB — Reserved for future AMI codes
BC — Reserved for future AMI codes
BD — Reserved for future AMI codes
BE — Reserved for future AMI codes
BF — Reserved for future AMI codes
C0 — OEM BDS initialization codes
C1 — OEM BDS initialization codes
C2 — OEM BDS initialization codes
C3 — OEM BDS initialization codes
C4 — OEM BDS initialization codes
C5 — OEM BDS initialization codes
C6 — OEM BDS initialization codes
C7 — OEM BDS initialization codes
C8 — OEM BDS initialization codes
C9 — OEM BDS initialization codes
CA — OEM BDS initialization codes
CB — OEM BDS initialization codes
CC — OEM BDS initialization codes
CD — OEM BDS initialization codes
CE — OEM BDS initialization codes
CF — OEM BDS initialization codes
DXE Error Codes
D0 — CPU initialization error
D1 — System Agent initialization error
D2 — PCH initialization error
D3 — Some of the Architectural Protocols are not available
D4 — PCI resource allocation error. Out of Resources
D5 — No Space for Legacy Option ROM
D6 — No Console Output Devices are found
D7 — No Console Input Devices are found
D8 — Invalid password
D9 — Error loading Boot Option (LoadImage returned error)
DA — Boot Option is failed (StartImage returned error)
DB — Flash update is failed
DC — Reset protocol is not available
S3 Resume Progress Codes
E0 — S3 Resume is stared (S3 Resume PPI is called by the DXE IPL)
E1 — S3 Boot Script execution
E2 — Video repost
E3 — OS S3 wake vector call
E4 — Reserved for future AMI progress codes
E5 — Reserved for future AMI progress codes
E6 — Reserved for future AMI progress codes
E7 — Reserved for future AMI progress codes
S3 Resume Error Codes
E8 — S3 Resume Failed
E9 — S3 Resume PPI not Found
EA — S3 Resume Boot Script Error
EB — S3 OS Wake Error
EC — Reserved for future AMI error codes 31
ED — Reserved for future AMI error codes 31
EE — Reserved for future AMI error codes 31
EF — Reserved for future AMI error codes 31
Recovery Progress Codes
F0 — Recovery condition triggered by firmware (Auto recovery)
F1 — Recovery condition triggered by user (Forced recovery)
F2 — Recovery process started
F3 — Recovery fi rmware image is found
F4 — Recovery fi rmware image is loaded
F5 — Reserved for future AMI progress codes
F6 — Reserved for future AMI progress codes
F7 — Reserved for future AMI progress codes
Recovery Error Codes
F8 — Recovery PPI is not available
F9 — Recovery capsule is not found
FA — Invalid recovery capsule
FB — Reserved for future AMI error codes
FC — Reserved for future AMI error codes
FD — Reserved for future AMI error codes
FE — Reserved for future AMI error codes
FF — Reserved for future AMI error codes
ACPI/ASL Checkpoints
01 — System is entering S1 sleep state
02 — System is entering S2 sleep state
03 — System is entering S3 sleep state
04 — System is entering S4 sleep state
05 — System is entering S5 sleep state
10 — System is waking up from the S1 sleep state
20 — System is waking up from the S2 sleep state
30 — System is waking up from the S3 sleep state
40 — System is waking up from the S4 sleep state
AC — System has transitioned into ACPI mode. Interrupt controller is in APIC mode
AA — System has transitioned into ACPI mode. Interrupt controller is in APIC mode
|
Beeps |
Error Message |
Description |
| 1 short | DRAM refresh failure | The programmable interrupt timer or programmable interrupt controller has probably failed |
| 2 short | Memory parity error | A memory parity error has occurred in the first 64K of RAM. The RAM IC is probably bad |
| 3 short | Base 64K memory failure | A memory failure has occurred in the first 64K of RAM. The RAM IC is probably bad |
| 4 short | System timer failure | The system clock/timer IC has failed or there is a memory error in the first bank of memory |
| 5 short | Processor error | The system CPU has failed |
| 6 short | Gate A20 failure | The keyboard controller IC has failed, which is not allowing Gate A20 to switch the processor to protected mode. Replace the keyboard controller |
| 7 short | Virtual mode processor exception error | The CPU has generated an exception error because of a fault in the CPU or motherboard circuitry |
| 8 short | Display memory read/write error | The system video adapter is missing or defective |
| 9 short | ROM checksum error | The contents of the system BIOS ROM does not match the expected checksum value. The BIOS ROM is probably defective and should be replaced |
| 10 short | CMOS shutdown register read/write error | The shutdown for the CMOS has failed |
| 11 short | Cache error | The L2 cache is faulty |
| 1 long, 2 short | Failure in video system | An error was encountered in the video BIOS ROM, or a horizontal retrace failure has been encountered |
| 1 long, 3 short | Memory test failure | A fault has been detected in memory above 64KB |
| 1 long, 8 short | Display test failure | The video adapter is either missing or defective |
| 2 short | POST Failure | One of the hardware testa have failed |
| 1 long | POST has passed all tests |
Newer AMI EZ-Flex BIOS codes
| 01 | NMI disabled; Start CPU flag test |
| 02 | Power on delay |
| 03 | Initialize system chipset |
| 04 | Check keyboard for soft/hard reset |
| 05 | Enable ROM |
| 06 | ROM BIOS checksum tested |
| 07 | 8042 keyboard controller tested |
| 08 | 8042 keyboard controller tested |
| 09 | 8042 keyboard controller tested |
| 0A | 8042 keyboard controller tested |
| 0B | 8042 protected mode tested |
| 0C | 8042 keyboard controller tested |
| 0D | CMOS RAM shutdown register tested |
| 0E | CMOS checksum tested |
| 0F | CMOS initialization |
| 10 | CMOS/RTC status OK |
| 11 | Disable DMA and PIC |
| 12 | Video display disabled |
| 13 | Chipset and memory initialized |
| 14 | 8254 PIT tested |
| 15 | PIT channel 2 tested |
| 16 | PIT channel 1 tested |
| 17 | PIT channel 0 tested |
| 18 | PIT memory refresh tested |
| 19 | PIT memory refresh tested |
| 1A | Check 15 microsecond refresh (PIT) |
| 1B | Base 64K memory tested |
| 20 | Address lines tested |
| 21 | Base 64K parity memory tested |
| 22 | Memory Read/Write tested |
| 23 | Perform setup’s prior to initialization of the vector table |
| 24 | Initialize BIOS vector table in lower 1KB of system RAM |
| 25 | 8042 keyboard controller tested |
| 26 | Global for keyboard controller tested |
| 27 | Perform setups for vector table initialization |
| 28 | Monochrome video mode tested |
| 29 | Video (CGA) color mode tested |
| 2A | Parity enable tested |
| 2B | Check for optional ROM’s |
| 2C | Check for video ROM |
| 2D | Determine if EGA/VGA is installed |
| 2E | Video memory is tested if non EGA/VGA |
| 2F | Video memory tested |
| 30 | Video adapter tested |
| 31 | Alternate video memory tested |
| 32 | Alternate video adapter tested |
| 33 | Video mode tested |
| 34 | Video mode tested |
| 35 | BIOS ROM data area initialized |
| 36 | Power on display cursor set |
| 37 | Power on message displayed |
| 38 | Cursor position read |
| 39 | Display cursor reference |
| 3A | Display Setup message |
| 40 | Protected mode tested |
| 41 | Build descriptor tables |
| 42 | CPU enters protected mode |
| 43 | Protected mode interrupt enabled |
| 44 | Descriptor tables checked |
| 45 | Memory size checked |
| 46 | Memory read/Write tested |
| 47 | Base 640K memory tested |
| 48 | Memory below 1MB checked for |
| 49 | Memory above 1MB checked for |
| 4A | ROM BIOS data area checked |
| 4B | Memory below 1MB cleared for soft reset |
| 4C | Memory above 1MB cleared for soft reset |
| 4D | Update CMOS memory size |
| 4E | Display base 64K memory test |
| 4F | Memory test on base 640K performed |
| 50 | RAM size updated for shadow operation |
| 51 | Extended memory test performed |
| 52 | System is prepared for real mode |
| 53 | CPU is returned to real mode |
| 54 | CPU registers are returned to real mode |
| 55 | A20 gate disabled |
| 56 | BIOS data area rechecked |
| 57 | BIOS data area check complete |
| 58 | Setup message displayed |
| 59 | DMA register page tested |
| 60 | Display memory verified |
| 61 | DMA #1 tested |
| 62 | DMA #2 tested |
| 63 | Perform BIOS data area check |
| 64 | BIOS data area checked |
| 65 | DMA initialized |
| 66 | 8259 PIC initialized |
| 67 | Keyboard tested |
| 80 | Keyboard reset |
| 81 | Check for stuck key and batch test |
| 82 | 8042 keyboard controller tested |
| 83 | Lock key checked |
| 84 | Memory size compared to CMOS |
| 85 | Password and soft error checked |
| 86 | CMOS equipment checked performed |
| 87 | CMOS setup performed if selected |
| 88 | Main chipset reinitialized after CMOS setup |
| 89 | Power on message displayed |
| 8A | Mouse check and wait message displayed |
| 8B | Any ROM’s attempted to be shadowed |
| 8C | System initialized through CMOS settings |
| 8D | Hard drives and floppy drives reset |
| 8E | Floppy disk setup compared to CMOS settings |
| 8F | Floppy controller initialized |
| 90 | Hard disks setup compared to CMOS settings |
| 91 | Hard disk controller initialized |
| 92 | BIOS data table checked |
| 93 | BIOS data table check complete |
| 94 | Memory size set |
| 95 | Display memory verified |
| 96 | All Interrupts cleared |
| 97 | Optional ROM’s checked for |
| 98 | All Interrupts cleared |
| 99 | Timer data setup |
| 9A | Serial ports checked for |
| 9B | All Interrupts cleared |
| 9C | Math coprocessor checked |
| 9D | All Interrupts cleared |
| 9E | Extended keyboard checked |
| 9F | NumLock set on keyboard |
| A0 | Keyboard reset |
| A1 | Cache memory size tested |
| A2 | Display any soft errors |
| A3 | Typematic rate set |
| A4 | Memory wait states set |
| A5 | Display is cleared |
| A6 | Parity and NMI enabled |
| A7 | All Interrupts cleared |
| A8 | System control is turned over to ROM at E0000 |
| A9 | All Interrupts cleared |
| AA | Displayed configuration |
| 00 | Call to Interrupt 19 for boot loader |