Asus Maximus Hero VII Manual

							1-27
1.2.6 Onboard buttons
Onboard buttons allow you to fine-tune performance when working on a bare or open-case system. This is ideal for overclockers and gamers who continually c\
hange settings to enhance system performance.
1. Power-on button \(START\)
The motherboard comes with a power-on button that allows you to power up\
 or wake up the system. The button also lights up when the system is plugged to a\
 power source indicating that you should shut down the system and unplug the power cab\
le before removing or installing any motherboard component. 
2. RESET button \(RESET\)
Press the reset button to reboot the system.
ASUS MAXIMUS VII HERO  
Chapter 1  
						

							1-28
• Refer to section Onboard LEDs for the location of the MEMOK_LED.
• The DRAM_LED also lights up when the DIMM is not properly installed. Turn off the system and reinstall the DIMM before using the MemOK! function.
• The MemOK! button does not function under Windows® OS environment.
• During the tuning process, the system loads and tests failsafe memory settings. It takes about 30 seconds for the system to test one set of failsafe settin\
gs. If the test fails, the system reboots and test the next set of failsafe settings. Th\
e blinking speed of the MEMOK_LED increases, indicating different test processes.
• Due to memory tuning requirement, the system automatically reboots when each timing set is tested. If the installed DIMMs still fail to boot after th\
e whole tuning process, the DRAM_LED lights continuously. Replace the DIMMs with ones recommended in the Memory QVL (Qualified Vendors Lists) in this user manual or on the ASUS website at www.asus.com.
• If you turn off the computer and replace DIMMs during the tuning process, the system continues memory tuning after turning on the computer. To stop memory tu\
ning, turn off the computer and unplug the power cord for about 5–10 seconds.
• If your system fails to boot up due to BIOS overclocking, press the MemOK! button to boot and load the BIOS default settings. A message will appear during\
 POST reminding you that the BIOS has been restored to its default settings.
• We recommend that you download and update to the latest BIOS version from the ASUS website at www.asus.com after using the MemOK! function.
3.  MemOK! button \(MemOK!\)
Installing DIMMs that are not compatible with the motherboard may cause \
system boot failure, and the DRAM_LED near the MemOK! button lights continuously. Pr\
ess the MemOK! button until the MEMOK_LED memory compatibility tuning for succes\
sful boot.
Chapter 1: Product introduction 
Chapter 1  
						

							1-29
4. Clear CMOS button \(CLR_CMOS\)
Press this button to clear the BIOS setup information only when the syst\
ems hangs due to overclocking.
5. KeyBot button \(KeyBot\)
Press this button to activate the KeyBot feature.  
•  The KeyBot feature supports USB keyboards only.
•  For more information about the KeyBot feature, refer to the Software Sup\
port chapter of this user guide.
ASUS MAXIMUS VII HERO  
Chapter 1  
						

							1-30
6. Sonic SoundStage button \(SOUNDSTAGE\)
Press this button to activate the Sonic SoundStage feature. 
• The debug code on the Q-Code LED shows the current Sonic SoundStage profile when you press the Sonic SoundStage button.
• For more information about Sonic SoundStage, refer to the Software Support chapter of this user guide.
Chapter 1: Product introduction 
Chapter 1  
						

							1-31
1.2.7 Onboard LEDs
1. Hard Disk LED \(HD_LED\)
The Hard Disk LED is designed to indicate the hard disk activity. It bli\
nks when data is being written into or read from the hard disk drive. The LED does not\
 light up when there is no hard disk drive connected to the motherboard or when the har\
d disk drive does not function.
2. Q LEDs \(BOOT_DEVICE_LED, VGA_LED, DRAM_LED, CPU_LED\)
Q LEDs check key components (CPU, DRAM, VGA card, and booting devices)\
 in sequence during motherboard booting process. If an error is found, the c\
orresponding LED flashes until the problem is solved. This user-friendly design provides an intuitive way to locate the root problem within seconds.
ASUS MAXIMUS VII HERO  
Chapter 1  
						

							1-32
3. KeyBot LED \(KEYBOT_LED\)
This LED lights up when the KeyBot button is pressed.
4. USB BIOS Flashback LED \(FLBK_LED\)
This LED flashes when you press the BIOS Flashback button for BIOS update.
Chapter 1: Product introduction 
Chapter 1  
						

							1-33
5. Q-Code LEDs
The Q-Code LED design provides you with a 2-digit error code that displa\
ys the system status. Refer to the Q-Code table on the following page for details.
ASUS MAXIMUS VII HERO  
Chapter 1  
						

							1-34
Q-Code table
(continued on the next page)
CodeDescription
00Not used
01Power on. Reset type detection (soft/hard).
02AP initialization before microcode loading
03System Agent initialization before microcode loading
04PCH initialization before microcode loading
06Microcode loading
07AP initialization after microcode loading
08System Agent initialization after microcode loading
09PCH initialization after microcode loading
0BCache initialization
0C \226 0DReserved for future AMI SEC error codes
0EMicrocode not found
0FMicrocode not loaded
10PEI Core is started
11 \226 14Pre-memory CPU initialization is started
15 \226 18Pre-memory System Agent initialization is started 
19 \226 1CPre-memory PCH initialization is started
2B \226 2FMemory initialization
30Reserved for ASL (see ASL Status Codes section below)
31Memory Installed
32 \226 36CPU post-memory initialization
37 \226 3APost-Memory System Agent initialization is started
3B \226 3EPost-Memory PCH initialization is started
4FDXE IPL is started
50 \226 53Memory initialization error.  Invalid memory type or incompatible memory\
 speed
54Unspecified memory initialization error
55Memory not installed
56Invalid CPU type or Speed
57CPU mismatch
58CPU self test failed or possible CPU cache error
59CPU micro-code is not found or micro-code update is failed
Chapter 1: Product introduction 
Chapter 1  
						

							1-35
Q-Code table
(continued on the next page)
CodeDescription
10PEI Core is started 
11 \226 14Pre-memory CPU initialization is started
15 \226 18Pre-memory System Agent initialization is started 
19 \226 1CPre-memory PCH initialization is started
2B \226 2FMemory initialization
30Reserved for ASL (see ASL Status Codes section below)
31Memory Installed
32 \226 36CPU post-memory initialization
37 \226 3APost-Memory System Agent initialization is started
3B \226 3EPost-Memory PCH initialization is started
4FDXE IPL is started
50 \226 53Memory initialization error.  Invalid memory type or incompatible memory\
 speed
54Unspecified memory initialization error
55Memory not installed
56Invalid CPU type or Speed
57CPU mismatch
58CPU self test failed or possible CPU cache error
59CPU micro-code is not found or micro-code update is failed
5AInternal CPU error
5BReset PPI is  not available
5C \226 5FReserved for future AMI error codes
E0S3 Resume is stared (S3 Resume PPI is called by the DXE IPL)
E1S3 Boot Script execution
E2Video repost
E3OS S3 wake vector call
E4 \226 E7Reserved for future AMI progress codes
E8S3 Resume Failed
E9S3 Resume PPI not Found
EAS3 Resume Boot Script Error
EBS3 OS Wake Error
EC \226 EFReserved for future AMI error codes
ASUS MAXIMUS VII HERO  
Chapter 1  
						

							1-36
CodeDescription
F0Recovery condition triggered by firmware (Auto recovery)
F1Recovery condition triggered by user (Forced recovery)
F2Recovery process started
F3Recovery firmware image is found
F4Recovery firmware image is loaded
F5 \226 F7Reserved for future AMI progress codes
F8Recovery PPI is not available
F9Recovery capsule is not found
FAInvalid recovery capsule
FB \226 FFReserved for future AMI error codes
60DXE Core is started
61NVRAM initialization
62Installation of the PCH Runtime Services
63 \226 67CPU DXE initialization is started
68PCI host bridge initialization
69System Agent DXE initialization is started
6ASystem Agent DXE SMM initialization is started
6B \226 6FSystem Agent  DXE initialization (System Agent module specific)
70PCH DXE initialization is started
71PCH DXE SMM initialization is started
72PCH devices initialization
73 \226 77PCH DXE Initialization (PCH module specific)
78ACPI module initialization
79CSM  initialization
7AReserved for future AMI DXE codes
90Boot Device Selection (BDS) phase is started
91Driver connecting is started
92PCI Bus initialization is started
93PCI Bus Hot Plug Controller Initialization
94PCI Bus Enumeration
95PCI Bus Request Resources
(continued on the next page)
Q-Code table
Chapter 1: Product introduction 
Chapter 1