Jump to content

Hello

i came home today after a week of going away and when i started my computer it was stuck on q code 77 so i googled it and did what was suggested and after everything i was stuck at 76 followed by 13. There is not much on the issue anywhere so i closely inspected motherboard and only unusual thing i found was on middle two mobo mounting hole back side as it was like something shiny flowing out. Please take a look at it suggest what should i do.

mother board : asus maximus VIII ranger
Processor : i5 6500k
Ram : corsair dominator platinum 32 gb
Graphics card : asus rog strix 1070
Cooler : corsair 110i
thanks
mihir

2E31467A-3143-4ED8-86FE-1ACE002BCE11.jpeg

5375D0E9-A940-4792-A814-C73059C058E7.jpeg

FB2FB61D-E740-4B1B-BEF7-E32B1CAF2D3B.jpeg

D1C3DFEF-4E38-4F46-9D66-E8E2FD52A112.jpeg

Link to comment
https://linustechtips.com/topic/1241873-q-code-76-followed-by-13/
Share on other sites

Link to post
Share on other sites

Q_CODE 77/76 = PCH DXE Initialization (PCH Module Specific)

 

Q_CODE 13 = Pre-Memory CPU initialization is started

 

Try booting the computer with bare essentials connected. Keyboard/Mouse only & 1 stick of RAM. See if you get POST.

Link to post
Share on other sites

4 hours ago, Windows7ge said:

Q_CODE 77/76 = PCH DXE Initialization (PCH Module Specific)

 

Q_CODE 13 = Pre-Memory CPU initialization is started

 

Try booting the computer with bare essentials connected. Keyboard/Mouse only & 1 stick of RAM. See if you get POST.

Platform controller hub dxe is just where the board hung during post.

 

The bottons on the board I'd play with after a clear cmos would be memok and retry or safe mode.

Link to post
Share on other sites

6 minutes ago, ShrimpBrime said:

Platform controller hub dxe is just where the board hung during post.

I'm aware. That's how Q codes work. The question is what caused it to hang. Resetting CMOS & checking mem are easy starting points along with stripping the board to bare essentials.

 

Might consider MemTest86 if testing suggests memory issue.

Link to post
Share on other sites

43 minutes ago, Windows7ge said:

I'm aware. That's how Q codes work. The question is what caused it to hang. Resetting CMOS & checking mem are easy starting points along with stripping the board to bare essentials.

 

Might consider MemTest86 if testing suggests memory issue.

The beep codes help take out all that guess work.... but otherwise agree.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×