memtest86 results

[ddlo92]

Hi all,

Been experiencing crashes to desktop in certain games but not others, and it led me down the rabbit hole of diagnosing what might be wrong. My desktop runs fine without any crashes if I don't run games. I decided to run memtest86, but I'm having trouble interpreting the results even after reading the "troubleshooting page". Any help determining if my RAM is bad would be greatly appreciated, and let me know if I can provide any details.

Thanks.

Here are the results below:

Report Date	2019-10-19 14:27:53
Generated by	MemTest86 V8.2 Free (64-bit)
Result	FAIL

System Information

EFI Specifications	2.60
System
Manufacturer	EVGA INTERNATIONAL CO.,LTD
Product Name	134-KS-E379
Version	Default string
Serial Number	Default string
BIOS
Vendor	American Megatrends Inc.
Version	1.09
Release Date	11/09/2018
Baseboard
Manufacturer	EVGA INTERNATIONAL CO.,LTD
Product Name	134-KS-E379
Version	1.0
Serial Number	Default string
CPU Type	Intel Core i7-8700K @ 3.70GHz
CPU Clock	3734 MHz [Turbo: 4411.9 MHz]
# Logical Processors	12 (6 enabled for testing)
L1 Cache	4 x 64K (230328 MB/s)
L2 Cache	4 x 256K (100353 MB/s)
L3 Cache	12288K (41651 MB/s)
Memory	16214M (23778 MB/s)
DIMM Slot #0	8GB DDR4 XMP PC4-23900
	Corsair / CMK16GX4M2B3000C15
	15-17-17-35 / 2998 MHz / 1.350V
DIMM Slot #1	8GB DDR4 XMP PC4-23900
	Corsair / CMK16GX4M2B3000C15
	15-17-17-35 / 2998 MHz / 1.350V

Result summary

Test Start Time	2019-10-19 11:34:29
Elapsed Time	2:43:55
Memory Range Tested	0x0 - 446800000 (17512MB)
CPU Selection Mode	Parallel (All CPUs)
ECC Polling	Enabled
# Tests Passed	34/48 (70%)

Lowest Error Address	0x218E7142C (8590MB)
Highest Error Address	0x223472F6C (8756MB)
Bits in Error Mask	0000000088000000
Bits in Error	2
Max Contiguous Errors	1

Test	# Tests Passed	Errors
Test 0 [Address test, walking ones, 1 CPU]	4/4 (100%)	0
Test 1 [Address test, own address, 1 CPU]	4/4 (100%)	0
Test 2 [Address test, own address]	4/4 (100%)	0
Test 3 [Moving inversions, ones & zeroes]	4/4 (100%)	0
Test 4 [Moving inversions, 8-bit pattern]	3/4 (75%)	1
Test 5 [Moving inversions, random pattern]	4/4 (100%)	0
Test 6 [Block move, 64-byte blocks]	4/4 (100%)	0
Test 7 [Moving inversions, 32-bit pattern]	2/4 (50%)	4
Test 8 [Random number sequence]	1/4 (25%)	8
Test 9 [Modulo 20, ones & zeros]	0/4 (0%)	14
Test 10 [Bit fade test, 2 patterns, 1 CPU]	4/4 (100%)	0
Test 13 [Hammer test]	0/4 (0%)	36

Last 10 Errors

2019-10-19 14:12:44 - [Data Error] Test: 13, CPU: 0, Address: 220E767D4, Expected: 99A5325C, Actual: 91A5325C

2019-10-19 14:12:44 - [Data Error] Test: 13, CPU: 0, Address: 220E753D4, Expected: F5EB155C, Actual: FDEB155C

2019-10-19 14:12:44 - [Data Error] Test: 13, CPU: 0, Address: 220E74E94, Expected: A185B48C, Actual: A985B48C

2019-10-19 14:12:44 - [Data Error] Test: 13, CPU: 0, Address: 220E73E04, Expected: 83BD6C28, Actual: 8BBD6C28

2019-10-19 14:12:44 - [Data Error] Test: 13, CPU: 0, Address: 220E7353C, Expected: 9D74598E, Actual: 1D74598E

2019-10-19 14:12:44 - [Data Error] Test: 13, CPU: 0, Address: 220E7325C, Expected: 5F41EE56, Actual: 5741EE56

2019-10-19 14:12:44 - [Data Error] Test: 13, CPU: 0, Address: 220E72F04, Expected: FA72D268, Actual: F272D268

2019-10-19 14:12:44 - [Data Error] Test: 13, CPU: 0, Address: 220E70A2C, Expected: C7BEBCEA, Actual: 47BEBCEA

2019-10-19 14:12:44 - [Data Error] Test: 13, CPU: 0, Address: 220E7064C, Expected: E0DF76F2, Actual: E8DF76F2

2019-10-19 14:12:24 - [Data Error] Test: 13, CPU: 0, Address: 218E771EC, Expected: 75EEA1A3, Actual: 7DEEA1A3

[David (PassMark)]

Looks like the RAM is bad.

[ddlo92]

Looks like the RAM is bad.

Thanks. Anything in particular that led you to think so? I see others with hundreds or thousands of errors, but I was thinking that the 50ish errors might be the result of (hopefully not) something else.

[David (PassMark)]

RAM errors generally mean the RAM is bad.
Even one error can be bad enough to make a PC completely unusable. Depends a bit on luck as to what piece of software uses the bad byte.

Yes, you can clean contacts & slots, adjust voltages, upgrade firmware, lower clock speeds and maybe fix the problem (or hide the problem). But generally not.