I think LinX is also a very good RAM tester. I'm not totally sure about how it works, I think Ruby or N7 know more about it but id go out on a limb and say LinX > all
Generally you want to run more than 25 passes at the max RAM you can use.
Generally use OCCT. It's a modified prime algorithm that finds errors many times faster than p95. It also has realtemp and occt built in lol
Does anyone have a link to the latest version of LinX? I downloaded Prime95 but after seeing what you guys are saying about that vs LinX, I think I'll go with LinX.
Do both tests. LinX first though, since it's typically a better and faster indicator.
I have had an overclock pass 100 passes of LinX only to fail Prime 95 blend after a few hours.
/bonk i didnt see i mistyped OCCT where i meant to put LinX. yea i would normally use LinX as well, but it's not safe to run on my system since my CPU goes past 80c and thermal reboots on me with current cooling. havent got around to installing my water loop yet, been to lazy LOL.It's a very good memory subsystem tester. It's filling up your RAM, so if your memory is incorrectly storing or retrieving data, LinX will throw an error.
It's not as good as HCI's memtest for testing RAM though.
I like 100 passes, which at 7000mb RAM usage can take almost all night. It's rather arbitrary which number of passes you choose to prefer.
While it does seem to find errors faster than Prime, it still does not compare to LinX.
So how does a LinX error look like?
