Chavah
The red LED blinks to represent the major error category (long blinks). The white LED blinks to represent the minor error category (short blinks). For example, ‘3.5’ indicates 3 long red blinks and 5 short white blinks to communicate the processor is not detected.
Category
Major/minor code
Issue description
Troubleshooting Steps
BIOS
2.2
The main area (DXE) of BIOS has become corrupted and there is no recovery binary image available. Also happens when updating BIOS.
Typically no steps needed.
1. Allow the system to complete its updates and changes.
2.If updates are stalling, attempt Sure Start Recovery.
BIOS
2.3
The embedded controller policy requires the user to enter a key sequence.
1.Follow any prompts given.
2.If issue persists, attempt Sure Start recovery.
BIOS
2.4
The embedded controller is checking or recovering the boot block.
1.Allow the computer to attempt to recover the BIOS.
2. If after several minutes the issue persists, attempt Sure Start recovery.
Hardware
3.2
The embedded controller has timed out waiting for BIOS to return from memory initialization.
Indicates potential memory failure.
1.Reseat memory.
2.Correct memory configuration (correct DIMM placement and size/type matching).
3.Test with known good memory.
4.Replace affected component.
Hardware
3.3
The embedded controller has timed out waiting for BIOS to return from graphics initialization.
Indicates potential graphics chip failure.
For integrated configuration:
1. For integrated configuration, confirm if graphics is on processor or system board.
2.For integrated where graphics is on the CPU, swap known good processor.
3. For integrated configuration, replace system board and/or processor as appropriate.If the add-in card requires additional power, verify the cord is plugged in.
For non-integrated configuration:
1.Reseat card if able.
2.Test known good card if able.
3.Replace affected component.
Hardware
3.4
The system board displays a power failure (crowbar).*
Indicates potential power system failure.
1. Reduce to minimum config (CPU, System board, PSU, 1 DIMM of memory) and isolate failed component.
2. Reduce further if issue persists.
3.Test known good PSU.
4. Replace affected component.
5. If unable to confirm source, replace CPU, System Board, PSU.
Hardware
3.5
The processor is not detected.*
Indicates potential CPU failure.
1. If able, reseat CPU.
2. If able, test known good CPU.
3. Replace affected component.
4.Replace both CPU and system board if unable to perform steps.
Hardware
3.6
The processor does not support an enabled feature.
CPU being asked to support feature it does not have.
1. Clear CMOS of unit and do not use the chosen setting.
2. If CPU is verified to support setting, replace CPU.
Thermal
4.2
A processor over temperature condition has been detected.*
CPU overheat is detected.
1. Verify fan(s) are working as expected.
2. Clean fans.
3. Reset CMOS.
4. Replace thermal grease.
5. Replace CPU.
Thermal
4.3
An ambient temperature over temperature condition has been detected.
Computer overall temperature is too high.
1. Verify fans are working.
2. Clean fans.
3. Reset CMOS.
4. Replace thermal sensor.
5. Replace system board if issue persists.
Thermal
4.4
An MXM over temperature condition has been detected.
The MXM Graphics card has overheated.
1. Verify system fan(s) are working.
2. Clean fans.
3. Reset CMOS.
4. Replace MXM card.
System Board
5.2
The embedded controller cannot find valid firmware.
Controller is missing appropriate ROM.
1. Remove any recently inserted Hardware.
2. Reset CMOS.
3. Update BIOS while affected components are removed.
4.Test known good component.
5.Replace component or system board as needed.
System Board
5.3
The embedded controller has timed out waiting for the BIOS.
Component is not reachable by BIOS in certain time limit.
1. Reseat component.
2.Test known good component.
3. Replace component or system board as needed.
System Board
5.4
The embedded controller has timed out waiting for BIOS to return from system board initialization.
System board isn’t initializing quickly enough for component.
1. Verify the correct power supply being used.
2. Reset CMOS.
3. Reseat components,
4. Test known good components.
5. Replace defective parts found.
System Board
5.5
The embedded controller rebooted the system after a possible lockup condition had been detected through the use of a System Health Timer, Automated System Recovery Timer, or other mechanism.
Component caused system to hang and/or reboot.
1. Reset CMOS.
2. Reseat component.
3. Verify BIOS, Chipset, drivers updated.
4. Test known good component.
5. Replace defective part.
https
/support.hp.com/ca-en/document/bph07107#AbT1