Problem with motherboard? Debug led 64 and AE.

SharkBaitGG

Reputable
Jan 28, 2015
11
0
4,510
Alright, so iv'e been having troubles with my gigabyte soc force. Awhile ago it would randomly go into a physical memory dump, giving me an error code on the debug led (cant remember it). I never did anything about it and it hasn't happened to me in a long time. However, i go to turn on my computer today and it black screens, giving me an error code of "64" on the debug led. It then gave me an error code of RE or AE (think it was AE). I restarted my computer and its fine now. I just want to know, should i be worried? or was that just minuscule problem that i shouldn't worry about? Thanks anyways.
(BTW i have the Gigabyte z97 SOC-FORCE motherboard, thanks again).
 
Solution
I think you might of read the display upside down. Could the error be:

E0 S3 - Resume is stared (called from DXE IPL).

DXE means Drive Execution Enviroment
IPL means Initial Program Load

What I found on the internet on this is...

...-memory initialization Post-Memory System Agent initialization is started Post-Memory PCH initialization is started OEM post memory initialization codes DXE IPL is started Memory initialization error. Invalid memory type or incompatible memory speed Unspecified memory initialization error Memory not installed Invalid ... Reset PPI is not available Reserved for future AMI error codes S3 Resume is stared (S3 Resume PPI is called by the DXE IPL) S3 Boot Script execution Video repost OS S3 wake vector call...

JimF_35

Distinguished
The system failed to get past POST. This is usually fixed by updating the BIOS. Get the latest BIOS update for your computer and it should fix the problem. I would do some hardware test too like Mem Test 86 and try stress testing your CPU.

http://www.memtest86.com/

Here is something else that could help.

http://rog.asus.com/forum/showthread.php?12386-Stuck-at-Debug-Code-AE-after-first-boot/page2

Some suggest that it could be a hard drive about to fail. Try doing a SMART test on your drive...

http://support.hp.com/us-en/document/c00386164
 

SharkBaitGG

Reputable
Jan 28, 2015
11
0
4,510

Right, so i have i have done a test on my drive using a program called hddscan, i did an extended and a short test and both came back with no errors. But when looking at the smart report for the program, it shows everything as alright other than UltraDMA CRC Errors. This is marked with a yellow warning signal which the website says "Yellow icon marks important attributes which may indicate malfunction.". Anyways, could you link a tutorial of updating the bios ive tried looking some up, but they use a tool to do it and not within the actual computer (which i hope there is a way). Ill run memtest right now. Thanks again and sorry im kind of a computer noob :p
 

Alectfenrir

Reputable
Jun 26, 2014
489
0
4,960


He's got a Gigabyte mobo, not an ROG Asus one, the Q-codes will be different.

@OP can you check your manual for the de-bug codes? Each code comes with its own description of what it is, and maybe we could find the root cause of this problem.
 

SharkBaitGG

Reputable
Jan 28, 2015
11
0
4,510

Alright well hello again. SO, i did a full memtest86 test and everything checked out okay. Before updating the BIOS i checked the version of my BIOS to see if i even needed to, turns out i don't. Its on version F6 which is the second latest version but, F7 is a beta BIOS and i don't want to risk updating my bios with a beta one. Haven't run Prime95 though, so i will try that. Also, another black screen happened last night, this time giving an error code of 03 which isn't on the manual website that you linked above. Anyways thanks for your help and also thank you Alectfenrir for helping.
 

JimF_35

Distinguished
I think you might of read the display upside down. Could the error be:

E0 S3 - Resume is stared (called from DXE IPL).

DXE means Drive Execution Enviroment
IPL means Initial Program Load

What I found on the internet on this is...

...-memory initialization Post-Memory System Agent initialization is started Post-Memory PCH initialization is started OEM post memory initialization codes DXE IPL is started Memory initialization error. Invalid memory type or incompatible memory speed Unspecified memory initialization error Memory not installed Invalid ... Reset PPI is not available Reserved for future AMI error codes S3 Resume is stared (S3 Resume PPI is called by the DXE IPL) S3 Boot Script execution Video repost OS S3 wake vector call Reserved for future AMI progress codes S3 ...

That error is pointing to your memory. Because you are getting different codes for different items that you have tested as good, I now believe you may have a bad motherboard. Does it have a warranty on it? You may be able to use all these codes as evidence that your board is bad and get a new one or at the very least see what they suggest doing.

Also just to be sure you are not doing any BLCK (Base Clock) over clocking are you? What is your BLCK set in your bios. I think it should be 100 MHz. I would have to double check your manual though.
 
Solution

SharkBaitGG

Reputable
Jan 28, 2015
11
0
4,510


Damn i was hoping it wasn't the mb, but now that you say that, when i turn on my computer the ports for the mice and keyboard stop working and i gotta plug em out and back in (which might mean that my mb is faulty? idk). Also, I might have read the display upside down as you said. Yeah my BLCK is at 100MHz. As for a warranty, this computer is new and i bought the parts seperately from canada computers so im pretty sure this mb has atleast a 1 year warranty if not a 3 year. However, i probably wont be replacing the mb anytime soon (unless the crashes get to the point where its unusable) as i am going on a vacation pretty soon. Anyways thanks alot for the help.
PS If you have no other suggestions and noone else helps, ill put you as the solution, just let me know. Thanks again!
 

SharkBaitGG

Reputable
Jan 28, 2015
11
0
4,510
It seem that the problem is memory. As i was looking through the internet and found that the debug code i was looking at was, in fact 03. This code appears when a component (seems to be the graphics card or ram) isn't seated properly. I haven't reseated my components yet, but if that does not work it has to be a problem with the motherboard.