How long do I need to run OCCT with medium and large data sets to be considered stable?

See UPDATE below.

Does anyone know if the memory test in OCCT 6.2.2 is actually reliable?

I noticed in their changelog that they recently changed how it works in 6.2.0.

After hours of running it will sometimes show that it found 2, 4 or 6 errors, and sometimes I've restarted and used the same settings that previously gave errors with no errors for 22h+. I also previously tested the memory with the same settings with memtest86 pro 8.3 for > 34h with no errors.

I'm testing using an AMD Ryzen 9 3900x, Asus ROG Strix B550-I Gaming, GSkill Ripjaws V 64GB DDR4 3600 C18.

UPDATE: Under Linux running Linpack I saw an correctable MCE, which appears to be related to Infinity Fabric. But since it was correctable it didn't cause an error in Linpack. So the rare error the sometimes shows up under OCCT might be uncorrectable IF errors. That would potentially explain why it seems so random. I'll to see if I can make the errors go away entirely by increasing the voltage for IF. According to the developer OCCT 6.x doesn't report MCEs but version 7.x will.

Alright, this is difficult to write and contain my own, personal and genuine excitement for this. I hope this doesn't get flagged and sworded by the mods !

OCCT v17 is available in beta, for Windows and Linux, and needs testing. The major update ? A new Memory test. I like to call it internally "The test where YOU are the hero !". It's not every day you launch a new free stress test, hence the excitement !

Instead of coming with yet another black box where you do not know what's happening, we took a new approach : a fully modular and configurable memory stress test. We rewrote individual tests from our own and other popular memory stress tests : TM5 and Memtest86 pattern-like algorithms mainly. I must insist we did our OWN implementation - the code is drastically different, much more modern (primarily for TM5), and more configurable. There's NO code theft. We just write the same patterns in memory or move data the same way.

You have access to 16 different blocks to pile up and come up with your own memory stress test : Walking 0s, Walking 1s, MirrorMove, ...

You control everything :

• Which test is used

• The seed used for generating random numbers

• When error detection occurs

• The number of loops and iterations

• the instruction set used

The result is a fully modular, fully configurable memory stress test where you can tinker around, find your own working block order ( much like we were doing with TM5 with the Anta777 / etc. presets ), and tailor it to your needs.

But not everyone has the time to go that deep into configuration, right ? Well, you can export, import tests, share them and we want to embed presets in OCCT. Of course we give credit where it's due (and ask for permission ofc). This means that you can rely on other works for testing your memory in depth without building your own test if you don't want to.

We've been in private beta for 3 weeks now and the results are astounding. PaimonRen, a community member even found a few combinations really useful for heating up the sticks. We even made a tutorial on how to port an existing TM5 preset to OCCT using this guide :

And yes, this is available in the free edition of OCCT, because that's what we do. Windows and Linux versions available of course.

We need feedback on this : testing, opinions, etc. We'll monitor this thread so feel free to react and share your thoughts.

GG to Dracau from our team for coming up with such an amazing test in such a short time !

You can find the app on ocbase as usual, just make sure you select "Test" instead of "Stable" in our download page :)

EDIT : if you wish to port a TM5 preset to OCCT, you can follow this guide here : https://www.ocbase.com/resources/TM5-to-OCCT-conversion-guide.pdf . It will not be 100% identical, but should produce similar (and hopefully better) results.

Hi everyone,

I'm meeting a local seller tomorrow to pick up a 32GB (2x16) G.Skill Trident Z RGB 3200MHz kit. The price is a steal, so I want to make sure I'm not getting scammed.

I know MemTest86 is the gold standard for stability, but running 4 passes at the seller's house is out of the question as it takes too long.

My plan is to bring a USB drive with OCCT and run the Memory Test (Instruction set: AVX2, 80% of RAM) for about 15 minutes.

• Is 15 minutes of OCCT enough to catch 90% of "broken" modules?

• Should I change any specific settings in OCCT to make the test more aggressive for a short duration?

• Is there any other "quick" tool (under 20 mins) that you'd recommend over OCCT for on-the-spot testing?

Hi what test should I run on a new pc/build that everything is fine and is the 1 hour enough?