Gigabyte z370 gaming 7 post code 66?

Simon Belmont · 14 Oct 2017 at 11:53

Everytime I start from a cold boot it comes up with code 66. If I restart the PC it then shows A0 only when I restart. Is post code 66 ok? I re-setted the chip and doing the AIO again and it's still the same?

I've reset the cmos also and still does it? Is this a bios issue?

z0n3y · 14 Oct 2017 at 12:30

63~67 CPU DXE initialization is started.
Worth a quick read http://www.tomshardware.co.uk/forum/336587-31-motherboard-stuck-error-code-stands-initialized
http://www.tomshardware.co.uk/forum/336587-31-motherboard-stuck-error-code-stands-initialized

Simon Belmont · 14 Oct 2017 at 12:45

z0n3y said:
63~67 CPU DXE initialization is started.
Worth a quick read http://www.tomshardware.co.uk/forum/336587-31-motherboard-stuck-error-code-stands-initialized

I tried that and it's still doing it. I don't think it matters, could be a bios issue. The system is fine. I know it's still early days on the bios.

Thanks anyways mate.

Danielfm · 1 Nov 2017 at 12:40

Hey I have the same issue, did you find a fix?

Simon Belmont · 10 Nov 2017 at 18:10

Here is the new bios for z370 gaming 7. F5C, but doesn't seem to fix 66 code.

Direct from gigabyte
https://drive.google.com/file/d/1KilCcz1tgAS7lY6Jm5gXA5rF_Im4Tf8I/view

8 Pack · 11 Nov 2017 at 14:46

Come on man if it's working fine who cares what is says on the post code reading??

If the performance and stability is the same then no issue worth worrying about exists.

Simon Belmont · 12 Nov 2017 at 08:11

I talked to Gigabyte about it seems they're using a more aggressive profile on the memory with very tight timings. It seems fine so I'll just leave it.

GIGA-Man · 14 Nov 2017 at 12:10

There will be a new retail BIOS out later this week or weekend, this again is for better memory support with tighter timings.

Candan · 5 Dec 2017 at 16:52

Hi All

Same board for me and the same issue. Last night I flashed the latest BIOS F5e and it still has the same issue. Anyone seeing the same thing still or did you get it fixed? Again, no issue with performance.

stulid · 5 Dec 2017 at 17:17

Mine says 66, does it still work....yes.

AthlonXP1800 · 5 Dec 2017 at 17:44

Yes I have the same debug code 66 so it is not a issue with BIOS, nothing wrong with BIOS so everything is fine.

You obviously not read the manual fully properly so you will see 66 is not an error code, actually 63-67 CPU DXE initialization is started are regular boot code. The debug code list has 4 sections Regular Boot, S3 Resume, Recovery and Error.

Candan · 5 Dec 2017 at 18:56

Yes it still works!

Does that stop it from being annoying. Nope.

I know it's not formally written as an error code, but Gigabyte have suggested they're looking into a fix. If it ain't broke, then why fix it?

stulid · 5 Dec 2017 at 19:43

IF the board didnt have a post code LED then none of you would be here now.

Candan · 5 Dec 2017 at 20:18

stulid said:
IF the board didnt have a post code LED then none of you would be here now.

True dat!

Davanius · 5 Dec 2017 at 23:45

Good thing I saw this thread as I have this board in my hands. Waiting on my 8700k which should be here in the morning.

Lance · 10 Dec 2017 at 17:13

Same error code and nothing has been going wrong for the past month - 6 weeks

wouldn't worry tbh

canuseemygrapes · 12 Feb 2018 at 18:41

My friend is getting this error also on his new build from the weekend. F5f bios. Then I found this on a reddit post.

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. The board, when cold, will retrain the memory on boot. It will go from tightest -> relaxed until something sticks. 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 I'll check with our BIOS guys but I believe its working as intended."

its at this moment I realize this is a gaming 7 thread. my friends is a gaming 5... oops

GIGA-Man · 12 Feb 2018 at 20:02

Okay try the board with one memory stick at a time to rule out a dead stick, there is now an F5M BIOS for that board I would recommend using that as it has new RAM support too. It could be the board just needs a BIOS update to support the RAM. Does you friend have any older ram to try?

Can you let me know the RAM model and serial number too... ?

Bugbait · 13 Feb 2018 at 11:40

I have the same code, 66 on cold boot but it does change to AO after a soft restart (I usually don't bother). Memtest passed on RAM but as others have mentioned, it appears to be working perfectly even with custom timings. My RAM is: Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 DRAM 4000MHz C19 Memory Kit - Black (CMK32GX4M2F4000C19). It only runs at 3600Mhz though since I can't get it to boot at 4000Mhz.

GIGA-Man · 13 Feb 2018 at 11:48

Okay I will get that looked at, are you using the F5M BIOS as the last revision had DDR XMP profiles added for high speed memory?