LED Code 76 - How to fix?

[mama]

I'm getting a Code 76 which according to the manual means: "PCH DXE initialization (PCH module specific)". I suspected it might be a chipset issue and so downloaded and reinstalled the chipset software. I kept getting a fail install on the AMD GPIO Driver (for Promontory) driver no matter what I did. I could be on the wrong track but it bugs me that one of the driver's won't install. I haven't noticed any functional issue as yet. Any advice?

 

[don256us]

Two things to help out.
1) what hardware are you using? In this case MB and CPU would be good to know.
2) Looking up AMD Promontory tells me that this chipset hasn't been made since 2011. Unless you have an old system and/or I'm wrong on the date, this may be a non issue.

 

[mama]

Two things to help out.
1) what hardware are you using? In this case MB and CPU would be good to know.
2) Looking up AMD Promontory tells me that this chipset hasn't been made since 2011. Unless you have an old system and/or I'm wrong on the date, this may be a non issue.

Gigabyte Aorus Extreme x670E. 7900x. It's in my system specs. This is the first MD I've had with LED debug. Is there any neutral code? Does the code disappear if there are no errors?

 

[Dsop]

I've got the same board. The driver that caused the debug 76 for me was the graphics driver for the chip. Not sure what the fix is, but for me all is running ok so far.

 

[Deleted member 185158]

I may be late here, but want to help.

This code is vague. So not directly pointing to any particular hardware per say.

This can be a result of ... just a couple examples here....

Bad stick of memory or memory compatibility.
Any piece of hardware not directly controlled by the processor. Meaning could be a drive initialization error or hardware fault.
Keyboard
Mouse
Video card
Rgb lighting controllers
So on and so forth.
And hot swapped OS from a different rig/chipset without removing drivers for the old rig.

You can get direct error beeps from the diagnostic speaker though. Might point you in the right direction also.

Or tear down the rig and build back up one piece at a time and figure out what halts the board at that specific code.
Update the bios if not up to date.

But that code is not a direct indication of error To any one thing. Can't be used for diagnostics At this time.

 

[Dsop]

For me everything was a fresh install. Memory passed memtest86. I've removed each usb connected still showing the same code on boot. Bios is up to date. Unfortunately still getting this 76. But a few times I'm getting EA instead but this is without making any other changes or disconnecting hardware etc. With removal of the driver for chipset graphics it boots with code AA.

 

[mama]

For me everything was a fresh install. Memory passed memtest86. I've removed each usb connected still showing the same code on boot. Bios is up to date. Unfortunately still getting this 76. But a few times I'm getting EA instead but this is without making any other changes or disconnecting hardware etc. With removal of the driver for chipset graphics it boots with code AA.

Same as me. Either 76 or EA errors. Neither seems fatal but I do notice that code 76 disables some reporting in HW info. Some of the board sensors like my water temp sensor are not picked up. Whereas this is not so with the EA error. This is very weird.

 

[dverdier]

Did any of you figure this out? I get 76, ae or ea, a0, 00 and one other I can't remember, all randomly, but everything works fine. I can't wrap my head around it.

 

[Obi2Cool4Kenobi]

For anyone still puzzled or scared over this code, it's a direct result of having integrated graphics enabled in the bios. If you want the code to go away just disable integrated graphics, should be in the IO ports section.

 

[dverdier]

For anyone still puzzled or scared over this code, it's a direct result of having integrated graphics enabled in the bios. If you want the code to go away just disable integrated graphics, should be in the IO ports section.

I'm showing 76 again right now. Everything works so I'd say puzzled. One other thing, is it normal to have a group of random codes. Never knowing which one you're going to get. Everything works fine no matter which code I get.

 

[Obi2Cool4Kenobi]

I'm showing 76 again right now. Everything works so I'd say puzzled. One other thing, is it normal to have a group of random codes. Never knowing which one you're going to get. Everything works fine no matter which code I get.

On boot it is normal (at least for me) to have your your MB cycle through a bunch of codes as it posts. Once it boots it will then become static on a single code. If you're still getting code 76 after disabling integrated graphics then it is puzzling, for me that code was directly correspondent with integrated graphics on my MB, Once I disabled it I only get AA anymore. If I enable integrated graphics again the 76 code will come back. I would troubleshoot more and see if after posting you ever get another code besides 76 to narrow it down further.

 

[emadparkar]

On boot it is normal (at least for me) to have your your MB cycle through a bunch of codes as it posts. Once it boots it will then become static on a single code. If you're still getting code 76 after disabling integrated graphics then it is puzzling, for me that code was directly correspondent with integrated graphics on my MB, Once I disabled it I only get AA anymore. If I enable integrated graphics again the 76 code will come back. I would troubleshoot more and see if after posting you ever get another code besides 76 to narrow it down further.

Even I am facing the same issue. Yes it puzzling and annoying as the whole system works. Did you progress any further in your troubleshoot.

 

[dverdier]

On boot it is normal (at least for me) to have your your MB cycle through a bunch of codes as it posts. Once it boots it will then become static on a single code. If you're still getting code 76 after disabling integrated graphics then it is puzzling, for me that code was directly correspondent with integrated graphics on my MB, Once I disabled it I only get AA anymore. If I enable integrated graphics again the 76 code will come back. I would troubleshoot more and see if after posting you ever get another code besides 76 to narrow it down further.

I'm sorry. I didn't catch you had responded. It cycles through codes while booting like you said. The thing is I never know which one I'm going to get in the end. 76 is the common one but like right now the reason I came across this again is it froze on 30 for like 5 mins then went on like normal. Booted and settled on ea. Normally it boots straight up and I could get ea, ae, AA, a0, 00. Any one of these. I never know which it's going to land on. Everything seems to act normal no matter which one it decides to show.

 

[mama]

For anyone still puzzled or scared over this code, it's a direct result of having integrated graphics enabled in the bios. If you want the code to go away just disable integrated graphics, should be in the IO ports section.

Great. I disabled integrated graphics and the LED code is now sitting at code AA which apparently means "Reserved", whatever that means. I also disabled Gigabyte Downloader and all in all this seems to have made things better. Problems that I didn't realise were problems, like weird resolution formatting on the startup screen and misreporting on HWInfo64 have gone.

 

[NoShock77]

I have a Aorus Master X670E and have the same issue with the igpu enabled. I’m on bios F13. I can’t get a straight answer from gigabyte why this occurs. My pc runs fine but with igpu enabled I get 76 AND Steam takes a long time to open. Such an odd issue.

 

[dverdier]

I have a Aorus Master X670E and have the same issue with the igpu enabled. I’m on bios F13. I can’t get a straight answer from gigabyte why this occurs. My pc runs fine but with igpu enabled I get 76 AND Steam takes a long time to open. Such an odd issue.

I have the exact same board. I stopped getting 76 when I disabled igpu but I turned it back on incase something happens I can just move the HDMI up to the mb. I don't think just because that code is showing means you ness have an error. Steam has always taken forever to load regardless of that selection. Right now for whatever reason I've been getting 08. That's supposed to be CPU not getting enough power. I started getting random crashes too. I had to disable all oc and it's not happening as much now. I'm not looking forward to reinstalling Windows and setting it all back up. It doesn't make sense tho that it happened out of nowhere. I have a 1000w platinum psu and a 7950x/4080. I'm not using too much power. I'm hoping my CPU didn't go bad somehow.

 

[NoShock77]

I have the exact same board. I stopped getting 76 when I disabled igpu but I turned it back on incase something happens I can just move the HDMI up to the mb. I don't think just because that code is showing means you ness have an error. Steam has always taken forever to load regardless of that selection. Right now for whatever reason I've been getting 08. That's supposed to be CPU not getting enough power. I started getting random crashes too. I had to disable all oc and it's not happening as much now. I'm not looking forward to reinstalling Windows and setting it all back up. It doesn't make sense tho that it happened out of nowhere. I have a 1000w platinum psu and a 7950x/4080. I'm not using too much power. I'm hoping my CPU didn't go bad somehow.

Are you on bios version F 20a/F20? F20a used to show codes D8,08 and one other code once I was in windows. Every few seconds I could see the q code display cycle through those codes. I rolled back to F13 and never saw any of those again.

 

[ShrimpBrime]

Post codes are informational only. Yes they could be accompanied by an error.

Direct error accompanied with failed post start would be best diagnosed with the beep codes and little diag speaker.

Also, on some boards you can use the diag panel for cpu temps rather than seeing informational codes. Check your manual/bios for this feature, it's neat to have.

 

[dverdier]

Sorry I stopped following this. I left for out of town that next day. I can't rem which it is exactly. It's f20 something. Whatever the first 20 was. I'll try going back to 13 and see what happens. I don't have a speaker on that board. Pretty sure there isn't a header for one either. As far as I know the only thing I have are the debug codes.

 

[ShrimpBrime]

Sorry I stopped following this. I left for out of town that next day. I can't rem which it is exactly. It's f20 something. Whatever the first 20 was. I'll try going back to 13 and see what happens. I don't have a speaker on that board. Pretty sure there isn't a header for one either. As far as I know the only thing I have are the debug codes.

All boards come equipped with a header. If it's not on FP1 it'll be on FP2, it's own header.

 

[dverdier]

All boards come equipped with a header. If it's not on FP1 it'll be on FP2, it's own header.

I'll look when I get home. I should have a small speaker I can use. You say beeps are better to diagnose with than codes.

 

[ShrimpBrime]

I'll look when I get home. I should have a small speaker I can use. You say beeps are better to diagnose with than codes.

Beeps are always an error related sound except for the single post beep.

The post codes can both be just informational and not always dedicated to an error. Just because the PC halted at code 76, doesn't mean that IS the cause. It's just where the PC halted.

 

[dverdier]

Thx. When I get back home I'll look into that