Help with Ballistix Memory

[William Gaatjes]

Happy to help. I am doing some memory testing my self. 16 hours have past without errors. But this time i will be testing for 50 hours total since it is a moderate memory overclock (2933MHz to 3200 MHz).
50 hours of successful passes with 0 errors before i feel ok with it.

 

[William Gaatjes]

Forgot, memtest86 has now version 7.5. I still had version 5. Version 7 is multhtreaded. It uses all logical cores of a multi core cpu one at as time. So a ryzen 2600 that has 6 cores but 12 logical cores, all 12 logical cores are used one at a time during the testing. And hearing how the fans speed up, there is probably a single core boost going on.
https://www.memtest86.com/download.htm

 

[mtl77733]

After so many days of testing, I have finally found the best timings for my RAM:

8-9-9-24-36-1T

This gives me no errors after 12 hours of testing with MemTest86+. I think 12 hours is good enough for me as my computer use is not mission critical. Besides, I don't have time for a very long test as I need to use my computer every day.

It's strange, though, that before this I tried 8-9-9-24-36-2T, which is a looser timing (2T vs 1T), and I got one error after 7 hours of testing. What could possibly explain why the looser timing 2T gave an error but the tighter timing 1T did not? Out of curiosity, and just for the heck of it, I tried 1T instead of 2T. I'm glad I tried even though it defied logic because with 1T there is no more error!

 

[William Gaatjes]

After so many days of testing, I have finally found the best timings for my RAM:

8-9-9-24-36-1T

This gives me no errors after 12 hours of testing with MemTest86+. I think 12 hours is good enough for me as my computer use is not mission critical. Besides, I don't have time for a very long test as I need to use my computer every day.

It's strange, though, that before this I tried 8-9-9-24-36-2T, which is a looser timing (2T vs 1T), and I got one error after 7 hours of testing. What could possibly explain why the looser timing 2T gave an error but the tighter timing 1T did not? Out of curiosity, and just for the heck of it, I tried 1T instead of 2T. I'm glad I tried even though it defied logic because with 1T there is no more error!

To be honest, i did not do a nonstop trial of 50 hours as well. I took between 8 and 12 hour runs for a total of 50 hours.Running in the evening, at night and in the morning.
I think it is save to say that if my pc runs so much hours without encountering an error, it should be fine.
I can leave my computer powered on when i am at work but i feel more save while being at home at night or being in the neighbourhood.
We had a few power blackouts a year or so back, since then i am kind of cautious.

edit:
It is strange, such late errors, always after a long time of testing.

 

[mtl77733]

To be honest, i did not do a nonstop trial of 50 hours as well. I took between 8 and 12 hour runs for a total of 50 hours.Running in the evening, at night and in the morning.
I think it is save to say that if my pc runs so much hours without encountering an error, it should be fine.
I can leave my computer powered on when i am at work but i feel more save while being at home at night or being in the neighbourhood.
We had a few power blackouts a year or so back, since then i am kind of cautious.

edit:
It is strange, such late errors, always after a long time of testing.

Oh, I thought the trial has to be nonstop. Since I need to use my computer and don't have time for more than 12 hours nonstop, I just limited my testing to 12 hours nonstop and that's it.