Code on my gigabyte mobo

[JayBee805]

So I get this code 66 on my gigabyte master MOBO is it normal ? 

[Derkoli]

7 minutes ago, JayBee805 said:

So I get this code 66 on my gigabyte master MOBO is it normal ? 

Aparently it happens after the pc has been put to sleep then woke up, the system will be 100% fine in windows.

[Automobili3XF]

Sometimes motherboards stick codes, for example all Biostar X370/X470 owners i know (including myself) have a permanent "33" code on the code reader.

Check your manual, probably has the code guide near the end.

[Imbellis]

Error code 66 is " CPU DXE initialization is started". That code, from what I understand, is basically the motherboard saying that it's trying to turn on. Nothing to be worried about.

 

 

Some Tom's Hardware post:

Quote

DXE (Driver Execution Environment) phase during POST and represented by Qcodes 63-67.

The (DXE) phase is where most of the system initialization is performed. Pre-EFI Initialization (PEI), the phase prior to DXE, is responsible for initializing permanent memory in the platform so that the DXE phase can be loaded and executed. The state of the system at the end of the PEI phase is passed to the DXE phase through a list of position-independent data structures called Hand-Off Blocks (HOBs). HOBs are described in detail in the Platform Initialization Hand-Off Block Specification.

There are several components in the DXE phase: “DXE Foundation”,“DXE Dispatcher”, and a set of “DXE Drivers”

The Dxe Core produces a set of Boot Services, Runtime Services, and DXE Services. The DXE Dispatcher is responsible for discovering and executing DXE drivers in the correct order. The DXE drivers are responsible for initializing the processor, chipset, and platform components as well as providing software abstractions for system services, console devices, and boot devices.
These components work together to initialize the platform and provide the services required to boot an operating system. The DXE phase and Boot Device Selection (BDS) phases work together to establish consoles and attempt the booting of operating systems. The DXE phase is terminated when an operating system is successfully booted.
The Dxe Core is composed of boot services code, so no code from the Dxe Core itself is allowed to persist into the OS runtime environment. Only the runtime data structures allocated by the Dxe Core and services and data structured produced by runtime DXE drivers are allowed to persist into the OS runtime environment."

Hope this helps.? and if system is running OK and post does not halt then you have nothing to worry about. The last phase of post is Qcode AA indicating a successful hand over to the OS.

 

[JayBee805]

Thanks guys