F5F Stay Refreshed Hardware Desktop Test results show MemTest succeeded on 3300x but failed on 5950x.

Test results show MemTest succeeded on 3300x but failed on 5950x.

Test results show MemTest succeeded on 3300x but failed on 5950x.

S
Sans231
Junior Member
1
12-14-2016, 03:20 PM
#1
Hi, I own a G.Skill Ripjaws v 128GB DDR4 3200Mhz CL16 setup with four 32GB sticks on a Gigabyte Aero G570 motherboard. One stick stopped working in Memtest86, but all other sticks passed in their slots. After returning it, the replacement failed too, though it was a different issue. The seller at AusPCMarket ran mem tests on this memory and saw no problems, but they’re using a slower CPU (Ryzen 3 3300X) and a different case. I noticed cache and memory speeds vary between my build and theirs: mine (single stick) is 36.8GB/s L3, 21.8GB/s Mem; four sticks hit 43.5GB/s L3, 40.5GB/s Mem. Their build (two sticks) averages 27GB/s L3, 17.8GB/s Mem. I suspect the speed difference might be due to CPU or cache latency, not just memory bandwidth. Should I ask them to improve their testing or check my hardware? Let me know how to proceed without extra gear. Thanks, Luke
S
Sans231
12-14-2016, 03:20 PM #1

Hi, I own a G.Skill Ripjaws v 128GB DDR4 3200Mhz CL16 setup with four 32GB sticks on a Gigabyte Aero G570 motherboard. One stick stopped working in Memtest86, but all other sticks passed in their slots. After returning it, the replacement failed too, though it was a different issue. The seller at AusPCMarket ran mem tests on this memory and saw no problems, but they’re using a slower CPU (Ryzen 3 3300X) and a different case. I noticed cache and memory speeds vary between my build and theirs: mine (single stick) is 36.8GB/s L3, 21.8GB/s Mem; four sticks hit 43.5GB/s L3, 40.5GB/s Mem. Their build (two sticks) averages 27GB/s L3, 17.8GB/s Mem. I suspect the speed difference might be due to CPU or cache latency, not just memory bandwidth. Should I ask them to improve their testing or check my hardware? Let me know how to proceed without extra gear. Thanks, Luke