RAM test - Error verifying data in RAM

[Andy_Chen]

Dear Passmark team,

I got "Error verifying data in RAM" when running Memory (RAM) test only (set to 80%), may I know how to identify the root cause and resolve the error message?

Test configuraiton:
Platform: Dell laoptop (Dell Pro 14 Plus PB14250)
CPU: Intel(R) Core(TM) Ultra 7 268V (Lunar Lake)
Graphics: Intel Arc 140V GPU (16GB)
RAM: LPDDR5 32GB (Integrated in SoC)
SSD: NVMe Micron 2550 1024GB
OS: Windows 11 24H2
BurnIn tool: 10.2 1013 (64-bit)


**************
RESULT SUMMARY
**************
Test Start time: Tue Feb 4 16:10:38 2025
Test Stop time: Tue Feb 4 16:11:08 2025
Test Duration: 000h 00m 30s

Test Name Cycles Operations Result Errors Last Error
Memory (RAM) 6 359 Billion FAIL 4 Error verifying data in RAM
TEST RUN FAILED

******************
DETAILED EVENT LOG
******************
LOG NOTE: 2025-02-04 16:10:38, Status, PassMark BurnInTest 10.2 1013 (64-bit)
LOG NOTE: 2025-02-04 16:10:40, Status, Main Tests started
SERIOUS: 2025-02-04 16:10:45, RAM, Error verifying data in RAM
LOG NOTE: 2025-02-04 16:10:45, Memory (RAM), Process 2, Data verify error: virtual address 0x00000000E7FDA3E8, read 0x00000000007f847d, expected 0x00000000007fd47d
LOG NOTE: 2025-02-04 16:10:45, Memory (RAM), Process 2, Current pattern: 64-bit Sequence (0,1,2...), bits in error 0x0000000000005000
LOG NOTE: 2025-02-04 16:10:45, Memory (RAM), Process 2, Current Cycle: 0, BufferPattern inital: 0x0000000000000000, bigloops: 511, smallloops: 5245
LOG NOTE: 2025-02-04 16:10:45, Memory (RAM), Process 2, ChunkIndex: 36, NumBufferChunks: 55, Blocks 55, virtual address start 0x00000000E3FF0000
SERIOUS: 2025-02-04 16:10:53, RAM, Error verifying data in RAM
LOG NOTE: 2025-02-04 16:10:53, Memory (RAM), Process 2, Data verify error: virtual address 0x00000000E7FDA3E8, read 0x5555555555550555, expected 0x5555555555555555
LOG NOTE: 2025-02-04 16:10:53, Memory (RAM), Process 2, Current pattern: 64-bit Binary 2 (01010101), bits in error 0x0000000000005000
LOG NOTE: 2025-02-04 16:10:53, Memory (RAM), Process 2, Current Cycle: 2, BufferPattern inital: 0x5555555555555555, bigloops: 511, smallloops: 5245
LOG NOTE: 2025-02-04 16:10:53, Memory (RAM), Process 2, ChunkIndex: 36, NumBufferChunks: 67, Blocks 67
SERIOUS: 2025-02-04 16:10:59, RAM, Error verifying data in RAM
LOG NOTE: 2025-02-04 16:10:59, Memory (RAM), Process 2, Data verify error: virtual address 0x00000000E7FDA3E8, read 0xffffffffffffafff, expected 0xffffffffffffffff
LOG NOTE: 2025-02-04 16:10:59, Memory (RAM), Process 2, Current pattern: 64-bit Ones (11111111), bits in error 0x0000000000005000
LOG NOTE: 2025-02-04 16:10:59, Memory (RAM), Process 2, Current Cycle: 4, BufferPattern inital: 0xffffffffffffffff, bigloops: 511, smallloops: 5245
LOG NOTE: 2025-02-04 16:10:59, Memory (RAM), Process 2, ChunkIndex: 36, NumBufferChunks: 67, Blocks 67
SERIOUS: 2025-02-04 16:11:00, RAM, Error verifying data in RAM
LOG NOTE: 2025-02-04 16:11:00, Memory (RAM), Process 2, Data verify error: virtual address 0x00000000E7FDA3E8, read 0x00000000007f8482, expected 0x00000000007fd482
LOG NOTE: 2025-02-04 16:11:00, Memory (RAM), Process 2, Current pattern: 64-bit Sequence (0,1,2...), bits in error 0x0000000000005000
LOG NOTE: 2025-02-04 16:11:00, Memory (RAM), Process 2, Current Cycle: 5, BufferPattern inital: 0x0000000000000005, bigloops: 511, smallloops: 5245
LOG NOTE: 2025-02-04 16:11:00, Memory (RAM), Process 2, ChunkIndex: 36, NumBufferChunks: 67, Blocks 67, virtual address start 0x00000000E3FF0000
LOG NOTE: 2025-02-04 16:11:09, Status, Test run stopped

[David (PassMark)]

The most common cause of RAM errors is bad RAM (hardware failure).

Normal solution is to replace the RAM. Or if the RAM is in the CPU, replace the CPU. Or of the CPU is soldered to the motherboard, replace the motherboard. Or if the motherboard in glued into a case, then replace the entire laptop.

Might also want to try MemTest86. But I would expect errors with that as well.

[Andy_Chen]

Hi David,

Thank you for prompt reply