Memory errors
30 errors. Choose the message that matches your computer.
Memory errors appear as blue screens such as MEMORY_MANAGEMENT, random restarts or failed memory tests. Testing each module and turning off XMP or EXPO profiles are the usual first steps.
MEMORY_MANAGEMENT
Windows stopped because it found a severe error in how memory is managed, such as damaged page tables or memory records that no longer match. Microsoft describes several of its specific error types as probably…
MemoryBAD_POOL_HEADER
Windows stopped because it found damaged bookkeeping data (a pool header) in the kernel's memory pool, the shared memory drivers use. Microsoft notes that the pool was already corrupted when the crash happened, so…
MemoryMEMTEST-ERR-8
A memory test such as MemTest86 or Windows Memory Diagnostic reported errors: data written to RAM did not read back correctly. Errors like this can cause crashes, blue screens and corrupted files.
MemoryXMP-INSTABILITY
Activated XMP/EXPO profile causes instability or non-booting. This usually traces back to RAM incompatible with board, need for higher voltage and BIOS bug.
MemoryRAM-NOT-DETECTED
Motherboard doesn't recognize RAM - reports low memory or won't boot. Typical causes include module incorrectly inserted, oxidized contacts and defective DIMM slot.
MemoryRAM-ECC-ERROR
The ECC memory detected and corrected the error, but there is a risk of an uncorrectable error when retrying. Common triggers are aging of RAM modules, cosmic Rays, electrostatic discharges and unstable power supply.
MemoryPAGE-FAULT-BOOT
BIOS/UEFI detected a fatal page fault during operating system startup. Windows won't load.
MemorySPD-CORRUPTION
The Serial Presence Detect (SPD) chip on the RAM module has corrupted data, the system does not know what timing and frequency to set. It sometimes comes down to SPD read/write voltage failure.
MemorySPD-CHK-ERR
The motherboard cannot read the timing from the memory module. It's most often caused by poor quality CPU controller, frequency too high and dust in slot.
MemoryBNK-INT-ERR
Communication problem between the front and back of the memory module. The usual suspects are different modules in one board, poor quality CPU controller, frequency too high and dust in slot.
MemoryXMP-BOOT-FAIL
Memory cannot run at factory overclocked values. Typical causes include different modules in one board, poor quality CPU controller, frequency too high and dust in slot.
MemoryVDDQ-U-VOLT
The modules lack the voltage to maintain the set frequencies. It's most often caused by poor quality CPU controller, frequency too high and dust in slot.
Memory1T-CMD-FAIL
The memory controller does not have time to process commands with a delay of only 1 clock. Common triggers are different modules in one board, frequency too high and dust in slot.
MemoryECC-LIM-EXC
Server memory is fixing so many bugs that it can't keep up. It's most often caused by different modules in one board, poor quality CPU controller, frequency too high and dust in slot.
MemoryROW-HAM-DET
Dangerous charge spillage between memory cells noted. It's most often caused by different modules in one board, poor quality CPU controller, frequency too high and dust in slot.
MemoryDCH-ASYNC
Although the memories run in Dual-Channel, they are poorly matched, which limits throughput. Typical causes include different modules in one board, frequency too high and dust in slot.
MemoryPIN-OXIDATION
Contact with the socket is broken due to dirt or oxidation on the pin. The usual suspects are different modules in one board, poor quality CPU controller, frequency too high and dust in slot.
MemoryREF-TIMEOUT
Memory cells have lost their charge before the next refresh cycle. The usual suspects are different modules in one board, poor quality CPU controller, frequency too high and dust in slot.
MemoryGEAR-MD-FAIL
The motherboard cannot run stably in split controller frequency mode. It sometimes comes down to dust in slot.
MemorySUBTIM-CORRUPT
The board set too aggressive sub-timings (eg tFAW, tRRD). The usual suspects are poor quality CPU controller, frequency too high and dust in slot.
MemoryDDR5-PMIC-TMP
The Power Integrated Controller (PMIC) on the DDR5 memory has overheated. This usually traces back to different modules in one board, frequency too high and dust in slot.
MemoryIMP-CAL-FAIL
The motherboard is stuck in a loop while calibrating the memory signal impedance. The usual suspects are poor quality CPU controller, frequency too high and dust in slot.
MemoryMCE-MEM-READ-ERR
The processor detected an unrecoverable error while reading data from memory and wrote it to the MCE log. Common triggers are physically damaged RAM module and unstable XMP/EXPO profile.
MemoryRAM_MEMORY_LEAK_SYSTEM
The system kernel's non-paged memory pool expands continuously without releasing memory, consuming all physical RAM and causing severe freezes, micro-stutters, and eventual crash/BSOD. The usual suspects are faulty…
MemoryDRAM_POST_TIMEOUT
The motherboard BIOS takes an excessive amount of time training the DDR5 memory channels on boot, eventually timing out and reporting a POST failure or resetting the memory frequency back to 4800MHz. See the…
MemoryXMP_PROFILE_BOOT_LOOP
Enabling Intel XMP or AMD EXPO profiles causes the PC to fail POST, resulting in a series of boot loops before resetting settings to BIOS defaults. The usual suspects are incompatible RAM modules with motherboard…
MemoryDOUBLE_FAULT
DOUBLE_FAULT (Stop Code 0x00000008) occurs when the processor generates an exception while already handling an exception, or when the exception handler itself raises an exception. This is a catastrophic kernel state…
MemoryRAM-DUAL-CHANNEL-FAIL
The system is operating in single-channel memory mode instead of the expected dual-channel configuration. Dual-channel mode doubles the effective memory bandwidth by using two RAM channels simultaneously.
MemoryECC-MEMORY-ERROR
Error-Correcting Code (ECC) memory has detected a bit error in RAM. Correctable single-bit errors (SECE) are automatically fixed by ECC logic, but uncorrectable multi-bit errors (MECE) cause system crashes.
Memory0x0000002E
A DATA_BUS_ERROR occurs when a parity error in system memory is detected, indicating memory bus communication failure. Most commonly caused by defective RAM modules, dusty DIMM slots, motherboard trace damage, or…