Gigabyte Gaming 7 Z370 Rgb Stuck Code From Showing

Gigabyte Gaming 7 Z370 Rgb Stuck Code From Showing

I never have issues when it says 66, and I have no clue why going into my BIOS first upon start up prevents that error code from showing.

Press question mark to learn the rest of the keyboard shortcuts Log In Sign Up User account menu 0 Gigabyte Z370 Gaming 7 Error Code 66.

Per the Gigabyte website, codes 63-67 stand for CPU DXE initialization started.

When I get this code the system still boots all the way and I have no trouble while using the system.

There are also no other LEDs lit up, like the ones that light up in sequence as it checks each component, on the board to indicate an issue.

Since it works when I get this code, I would like to just ignore it.

But I want to be certain there isnt something Im missing.

Upvoted This thread is archived New comments cannot be posted and votes cannot be cast Sort by best.

No other issues detected 2 Share Report Save level 2 Original Poster 3 years ago I dont ever use sleep, I properly shut down my system each night.

Share Report Save level 1 1 9900kRTX 2080 2 8600kRTX 2070 8gb 3 8400 RTX 2060 3 years ago Is the BIOS current Does the issue happen when youre not overclocked 2 Share Report Save level 2 Original Poster 3 years ago BIOS is up to date.

I cant say for certain that it doesnt happen when not overclocked, because its completely random when it happens.

I can boot normally and not get the code even with the overclock applied, so I cant say for certain that removing the overclock is what fixes it.

Since, again, I can get boots where it doesnt show even with the OC applied.

So technically yes it hasnt shown up yet when not overclocked.

But I havent tried numerous boot cycles with the OC removed to accurately test if it never shows up with the OC removed.

Share Report Save level 2 Original Poster 3 years ago Update on this.

If I go into my BIOS upon booting, either from a shut down or a restart, then save and exit for it to load into Windows, I dont get the error.

I just hit delete to enter the BIOS, then immedetly exit.

Share Report Save Continue this thread level 1 3 years ago Also, to everyone having this issue, I found this post from a gigabyte staff member on their US forums.

He said the following about code 66: Not sure if it needs to be fixed, as its working as intended.

If the tightest timing works then you should see A0 (boot successful).

If it fails even once it will show 66 (atleast one failed boot).

On a soft reboot it already has the timings trained, thus it clears the code and shows A0.

The only way to fix this would be to boot successfully on tightest timings.

We could fix this by creating a less aggressive profile, however those who are booting with the most aggressive profile would lose performance.

That being said Ill check with our BIOS guys but I believe its working as intended.

So it seems it isnt an issue, which is why none of us have actual issues when using our PCs:) 2 Share Report Save level 1 3 years ago I have this same exact error on my Gaming 7.

I dont see anything wrong at all with my system, and functions fine.

It used to say A0, but I did recently force my timings on my RAM, so maybe thats why 1 Share Report Save level 2 Original Poster 3 years ago AO is what it should say.