[SOLVED] Mem test on 128GB DDR4,

[skycaptn]

should I use windows 10 mem test or is there a better 3rd party test? faster?
I was planning on taking out 3 strips and testing 1 strip at a time
suggestions are always welcome

 

[kanewolf]

should I use windows 10 mem test or is there a better 3rd party test? faster?
I was planning on taking out 3 strips and testing 1 strip at a time
suggestions are always welcome

MEMTEST -- https://www.memtest86.com/
But testing 1 stick at a time is only appropriate if you are having problems with 1, 2, or 4.
If you purchased all 4 sticks in a matched set, then you will have to RMA the entire set.

 

[skycaptn]

They are 5 years old so I doubt I'll get to RMA them, I don't know which one is a problem that's why I was going to test one at a time. The system crashes if the test goes too long with no report

 

[kanewolf]

They are 5 years old so I doubt I'll get to RMA them, I don't know which one is a problem that's why I was going to test one at a time. The system crashes if the test goes too long with no report

A lot of memory has a lifetime warranty. If you still have proof of purchase, you might still get some benefit.

 

[geofelt]

Memtest86 is a good comprehensive test.
Yes, it takes time.
But, if you have a defect, it will likely show up quickly.
Even one error is cause for replacement.
What is the make/model of your ram kit and motherboard?
Is this something new?

Test the complete 4 sticks because that is what you ultimately want.
Identifying a single bad stick is not particularly useful since all 4 sticks of the kit should be replaced if one is defective.

On lifetime ram, purchase date and documentation is moot.
If you think the ram has gone bad, contact the ram maker support for RMA.
No doubt, they will want you to rum memtest86 first.

 

[SamirD]

So I had to test 16x 32GB modules once (yep, 512GB of ram). They were all expected to be good so I tested them in batches of 256GB which took 37 hours each batch. I used the memtest that's available on the ultimate boot cd straight into dos. This is the test I would recommend.

Since you know or suspect a single module is bad, you could test each module individually. But if you test each one individually and it's the last module that's bad, you will have spend N*4 time for testing. If there is even a chance that all 4 are good, I would first try testing all at once. It should fail fast enough and then you can go individual if need be.

I also recommend testing overnight so you're able to use the system--otherwise unless it's a dedicated system--then I recommend testing 24x7.