The EZ Debug LEDs help determine whether the problem is with your DRAM, VGA, CPU, or a boot issue. They illuminate and indicate which component is faulty. As a result, you can inspect the affected component using the illuminated LED indicator.
Turning on a PC after building can be quite stressful. This is because, most times, the display will show nothing. You might have carefully assembled all the components. Yet there could be some mistakes here and there. Figuring out what the mistake is can be a difficult task.
You must, however, be certain that your motherboard comes with EZ Debug LEDs. You can verify this from your motherboard’s manufacturer manual. You can also check the right-hand corner near the DIMM slots.
MSI Debug LED Code List and Description
| EC Progress Codes | Description |
|---|---|
| 01 | Power on. Reset type detection (soft or hard). |
| 02 | AP initialization before microcode loading |
| 03 | System Agent initialization before microcode loading |
| 04 | PCH initialization before microcode loading |
| 06 | Microcode loading |
| 07 | AP initialization after microcode loading |
| 08 | System Agent initialization after microcode loading |
| 09 | PCH initialization after microcode loading |
| 0B | Cache initialization |
| SEC Error Codes | Description |
|---|---|
| 0C – 0D | Reserved for future AMI SEC error codes |
| 0E | Microcode not found |
| 0F | Microcode is not loaded. |
| PEI Progress Codes | Description |
|---|---|
| 10 | PEI Core has started. |
| 11 | Pre-memory CPU initialization is started. |
| 12 – 14 | Pre-memory CPU initialization (CPU module specific) |
| 15 | Pre-memory system agent initialization is started. |
| 16 – 18 | Pre-Memory System Agent Initialization (System Agent module specific) |
| 19 | Pre-memory PCH initialization has started. |
| 1A – 1C | Pre-memory PCH initialization (PCH module specific) |
| 2B | Memory initialization. Serial Presence Detect (SPD) data reading |
| 2C | Memory initialization. Memory presence detection |
| 2D | Memory initialization. Programming memory timing information |
| 2E | Memory initialization. Configuring memory |
| 2F | Memory initialization (other) |
| 31 | Memory Installed |
| 32 | CPU post-memory initialization has started. |
| 33 | CPU post-memory initialization Cache initialization |
| 34 | CPU post-memory initialization Application Processor (AP) initialization |
| 35 | CPU post-memory initialization Boot Strap Processor (BSP) selection |
| 36 | CPU post-memory initialization System Management Mode (SMM) initialization |
| 37 | Post-Memory System Agent Initialization is started. |
| 38 – 3A | Post-Memory System Agent Initialization (System Agent Module Specific) |
| 3B | Post-memory PCH initialization is started. |
| PEI Progress Codes | Description |
|---|---|
| 3C – 3E | Post-memory PCH initialization (PCH module specific) |
| 4F | DXE IPL has started. |
| PEI Error Codes | Description |
|---|---|
| 50 | memory initialization error. Invalid memory type or incompatible memory speed |
| 51 | memory initialization error. The SPD reading has failed. |
| 52 | memory initialization error. Invalid memory size or memory modules do not match |
| 53 | memory initialization error. No usable memory was detected. |
| 54 | Unspecified memory initialization error |
| 55 | Memory not installed |
| 56 | Invalid CPU type or speed |
| 57 | CPU mismatch error |
| 58 | CPU self-test failed or possible CPU cache error |
| 59 | CPU micro-code is not found, or the micro-code update failed. |
| 5A | Internal CPU error |
| 5B | Reset PPI is not available. |
| 5C – 5F | Reserved for future AMI error codes |
| DXE Progress Codes | Description |
|---|---|
| 60 | DXE Core has started. |
| 61 | NVRAM initialization |
| 62 | Installation of the PCH Runtime Services |
| 63 | CPU DXE initialization has started. |
| 64 – 67CPU DXE initialization (CPU module specific)68PCI host bridge initialization69System Agent DXE initialization has started. | |
| 6A | System Agent DXE SMM initialization has started. |
| 6B – 6F | System Agent DXE initialization (System Agent module specific) |
| 70 | PCH DXE initialization has started. |
| 71 | PCH DXE SMM initialization has started. |
| 72 | PCH device initialization |
| 73 – 77 | PCH DXE Initialization (PCH module specific) |
| 78 | ACPI module initialization |
| 79 | CSM initialization |
| 7A – 7F | Reserved for future AMI DXE codes |
| 90 | The Boot Device Selection (BDS) phase has started. |
| 91 | Driver connection has been started. |
| 92 | PCI Bus initialization is started. |
| 93 | PCI Bus Hot Plug Controller Initialization |
| 94 | PCI bus enumeration |
| DXE Progress Codes | Description |
|---|---|
| 95 | PCI Bus Request Resources |
| 96 | PCI Bus Assigned Resources |
| 97 | Console output devices connect |
| 98 | Console input devices connect |
| 99 | Super IO Initialization |
| 9A | USB initialization has started. |
| 9B | USB Reset |
| 9C | USB Detect |
| 9D | USB Enable |
| 9E – 9F | Reserved for future AMI codes |
| A0 | IDE initialization has been started. |
| A1 | IDE Reset |
| A2 | IDE Detect |
| A3 | IDE Enable |
| A4 | SCSI initialization has started. |
| A5SCSI ResetA6SCSI DetectSCSI EnableA7A8Setup Verifying PasswordA9Start of SetupABSetup Input WaitADReady to BootAELegacy BootAFExit Boot ServicesB0Runtime Set Virtual Address MAP BeginB1Runtime Set Virtual Address MAP EndB2Legacy Option ROM InitializationB3System ResetB4USB hot plugB5PCI bus hot plug/clean-up of NVRAMB6B7Configuration Reset (reset of NVRAM settings) B8 – BFReserved for future AMI codes |
| DXE error codes | Description |
|---|---|
| D0 | CPU initialization error |
| D1 | System Agent initialization error |
| D2 | PCH initialization error |
| Some of the architectural protocols are not available. |
| S3 Resume Progress Codes | Description |
|---|---|
| E0 | S3 Resume is started (the S3 Resume PPI is called by the DXE IPL). |
| E1 | S3 Boot Script execution |
| E2 | Video repost |
| E3 | OS S3 wake vector call |
| E4 – E7 | Reserved for future AMI progress codes |
| S3 Resume Error Codes | Description |
|---|---|
| E8 | S3 Resume Failed |
| E9 | S3 Resume PPI not found. |
| EA | S3 Resume Boot Script Error |
| EB | S3 OS Wake Error |
| EC – EF | Reserved for future AMI error codes |
| Recovery Progress Codes | Description |
|---|---|
| F0 | Recovery condition triggered by firmware (auto recovery) |
| F1 | Recovery condition triggered by the user (forced recovery) |
| F2 | The recovery process started |
| F3 | A recovery firmware image is found. |
| F4 | The recovery firmware image is loaded. |
| F5 – F7 | Reserved for future AMI progress codes |
| recovery error codes | Description |
|---|---|
| F8 | Recovery PPI is not available. |
| F9 | The recovery capsule was not found. |
| FA | Invalid recovery capsule |
| FB – FF | Reserved for future AMI error codes |
| ACPI State Codes | Description |
|---|---|
| 01 | The system is entering the S1 sleep state. |
| 02 | The system is entering the S2 sleep state. |
| 03 | The system is entering the S3 sleep state. |
| 04 | The system is entering the S4 sleep state. |
| 05 | The system is entering the S5 sleep state. |
| 10 | The system is waking up from the S1 sleep state. |
| 20 | The system is waking up from the S2 sleep state. |
| 30 | The system is waking up from the S3 sleep state. |
| 40 | The system is waking up from the S4 sleep state. |
| AC | The system has transitioned into ACPI mode. The interrupt controller is in PIC mode. |
| AA | The system has transitioned into ACPI mode. The interrupt controller is in APIC mode. |
| CPU Temperature | Description |
|---|---|
| 00 – 99 | displays the current CPU temperature after the system has fully booted into the OS. |
how to troubleshoot and fix EZ Debug LEDs
The LEDs on your motherboard come in the following order:
- CPU: indicates the CPU is not detected or has failed
- DRAM: This indicates that DRAM is not detected or has failed.
- VGA: indicates that the GPU is not detected or has failed.
- BOOT: indicates the boot device is not detected.
They usually appear on your motherboard in that sequence. You will also see it written out. Now that we know what EZ Debug LEDs represent let’s see how to fix the errors they indicate.
You first need to make sure that your motherboard can handle the parts you want to add. You can just check MSI’s website. You will see the support tab in the top right-hand corner. You will see a list of all the components supported by the motherboard.
Putting a good and meticulous plan in place in building your computer is important. It helps ensure that the components have no issues with compatibility. It also makes sure that they work hand in hand to optimize performance.
Related: What Is MSI Game Boost
So, let’s look towards troubleshooting each component.
1. CPU EZ LED (Red Light )
The first thing to verify is if the CPU’s 4-pin or 8-pin power connector has been properly installed. You should then remove the CPU and check for any damages. There might be dirt blocking the connection to the socket. Clean and re-install the CPU.
You also need to verify if there are any broken or bent pins. You can fix bent pins with a needle. You also must verify if the motherboard and BIOS are compatible with the CPU.
How to Fix Ez Debug Led CPU
- Check that you have connected the 8-pin CPU power connector.
- Make sure all the RAMs are pushed all the way into the
- Check that you haven’t unseated the VGA card. If you’ve tried the RAM, try reseating the video card.
- Double-check to make sure you don’t have any bent CPU pins.
- Take out the Cmos battery on the motherboard and boot without it, and see if it starts. If it does boot, put the Cmos battery back in and boot again like normal and see if it works.
- Update your bios to the latest version.
- If you have spare parts, swap the VGA, CPU, RAM, and PSU to narrow down the problem.
- If none of these fixes work, then you have a friend’s motherboard; go ahead and RMA the board as soon as possible.
2. DRAM EZ LED
This usually indicates a problem with the RAM, either they are not properly seated or they are corrupted. There might also be a problem with the pins on the ram slot.
How to Fix Ez Debug Led Dram
Before troubleshooting the DRAM, you should know that bent CPU pins can illuminate DRAM LEDs. So, a good place to start is to ensure that the DRAM has been properly installed. Remove the RAM modules and check for any obstructions to the connection.
Then, install the DRAM stick into the memory slot from the CPU. Work with the second memory slot. Ascertain that it is securely fastened in place. You also need to check if the RAM fits the motherboard’s configuration. If you use multiple RAM sticks, ensure they are not in the wrong slots.
3. VGA
So, if the VGA light is the one appearing, it is a pretty straightforward issue. It is quite simple if your CPU comes with an integrated graphics processor. Just work with the information we have provided.
If it comes with a separate graphics card, ensure it is well connected to the PCIe socket. You can try out the socket closest to the CPU first. If it does not work out, then try the other sockets. The 8-pin connector has to be plugged into the graphics card properly. Make sure the pins are clean, though, before you install.
How to Fix Ez Debug Led VGA
1) Unplug the MotherBoard’s components and devices before reinstalling the CPU, RAM (one piece), VGA card, and power supply. Please apply thermal gel to the CPU before reinstalling the fan properly and tightly. To ensure the motherboard’s stability, connect JPWR1 and JPWR2 to proper ATX power supplies. Please ensure that the 6 or 8 pin power connectors on your VGA are connected to a power supply.
2) Clear the CMOS (consult the manual for instructions).
3) If the problem persists, please replace the VGA with a different VGA slot and test again.
I solved the problem by unplugging every PCI card from the motherboard. Then I reset the CMOS by short-circuiting the two pins with a screwdriver for 10 seconds (as instructed in your motherboard manual), and the situation improved slightly. I was then able to enter the BIOS and update it. Remember to wait at least 30 seconds after pressing the power button. The Windows 10 installation program then booted up without a hitch from the USB.
4. BOOT
The Boot EZ Debug LED has to do with the storage unit of your computer. You have to ascertain that all storage devices have been properly connected. For M.2 SSDs, you have to check if the pins are clean. They must also be properly installed. Verify that the SSD has been locked in place by the screws.
How to Fix Ez Debug LED Boot
Check the storage devices connected via the SATA ports. Remove the SATA cable from the motherboard and storage device. Then plug it back, ensuring that it fits properly. If it does not work, try using a different port. You could even work with a different cable.
You can also try out a new storage device entirely.
5. Other Issues
Other options exist if all of the above fail to resolve the problem. You can start by resetting the BIOS. Once you are in the BIOS settings, update the BIOS. Reset any overclocking settings to the default. You should also check for the DRAM overclock settings. Reset it to default.
Related: MSI Motherboard Beep Codes
Frequently Asked Questions (FAQs)
Motherboard Debug Led Not Lighting Up
This may most likely be an issue related to your power supply unit. So, the first point of the call will be to verify the connections. Ensure that the 24-pin ATX power supply connector is securely plugged into the motherboard. You can check to see if the RGB lights on your motherboard are illuminated.
Other ways to fix this include:
- Check the power jumper on the front panel.
- Check CPU compatibility
- Check computer hardware
- Check the display screen.
- Check the EZ Debug LED indicator.
- Perform a POST test.
- Discharge to clear CMOS
Is the color code of the LED light always the same?
The LED lights may be colored or not. This depends entirely on the model of the motherboard. Sometimes, the error on the CPU may be red; other times, it may be white.
Conclusion
Building a new computer might come with its issues. One of which is the EZ Debug LED appearing. This LED light might be confusing at first. However, we know that this guide would have given you sufficient information to help you with that.
So, fix the issues and get your computer up and running.
