What Does Prime Stress That LinX & OCCT Dont??

Associate
Joined
15 Oct 2007
Posts
2,187
Location
Bedfordshire, UK.
OK, i have managed to do 30 passes with LinX and the standard 1 hour test with OCCT all passed without errors. But when i try Prime on Blend, after about 15-30minutes my whole system locks up. So how come i can do 30 passes of Linx (which i though was surpossed to stress the system more than Prime) but fail on Prime. What does Prime Stress that LinX doesnt, memory???
 
Prime blend stress both cpu and memory, so therefor chipset stability too.

But Occt and linx using max memory does that too, it all depends what settings u used for these, allways try and use as much memory as u can when doing stress testing.

In the passed iv had overclocks pass 24hrs of prime (small fft), and as soon as i started the blend test it would fail, untill i sorted the chipset and memory settings.
 
Well thats it im not 100% sure what the problem would be, if i can get no errors on either LinX or OCCT, with max memory settings. The thing i have noticed was when my system locks up whilst stressing with Prime, the lights on my keyboard and mouse go out, if thats of any relevance or not?
 
mmm personally id ignore prime, if ur overclock can pass 30 tests on linx with full settings then to me thats stable, but i know some on here won't say that as they are stuck in the passed and think prime is the be all and end all in stress testing lol.

the no lights on mouse and keyboard to me indicates when it crashes that there is no power to them, hence no lights.

I would'nt worry about prime though, if ur computer dos'nt crash for what you use it for, and it can pass 30 full setting tests on linx then its stable.

*sits back to await some ear bashing from the prime fans*
 
unfortunately Prime as a piece of software is flawed. If you can pass OCCT and 30 passes of LinX with full memory settings then you are as stable as you reasonably need to be. Prime has been to known to hang or crash because of bugs with the software not the OC. it had a bug that failed when using HT on certain CPU's and one used to hang on 256k FFT on sse2 machines and so on.
Just watch the Prime Fanboys have a go tho....
 
my rig recently passed all prime tests in blend mode without issue, but would crash during 3d rendering. conclusion? prime doesn't stress the system as much as 3D Rendering. doesn't push temps as high, for one.
 
i know some on here won't say that as they are stuck in the passed and think prime is the be all and end all in stress testing lol.

if ur computer dos'nt crash for what you use it for, and it can pass 30 full setting tests on linx then its stable.

We are not stuck in the "passed". No one test is sufficient, so run prime, ibt, furmark and anything else you can get your hands on. If you're passing ibt but failing prime then you're not stable.

That it doesn't crash does not mean it's stable. It only means it's stable enough for windows not to go down, it can still be getting calculations wrong. This does not make me a blathering fanboy. Your argument only holds if you redefine "stable" as "seems alright".

Prime has been to known to hang or crash because of bugs with the software not the OC.

This is a different issue. Check by running prime at stock, if it passes then it's your overclock.

For the OP, loosen memory timings, does it still fail?
 
We are not stuck in the "passed". No one test is sufficient, so run prime, ibt, furmark and anything else you can get your hands on. If you're passing ibt but failing prime then you're not stable.

That it doesn't crash does not mean it's stable. It only means it's stable enough for windows not to go down, it can still be getting calculations wrong. This does not make me a blathering fanboy. Your argument only holds if you redefine "stable" as "seems alright".



This is a different issue. Check by running prime at stock, if it passes then it's your overclock.

For the OP, loosen memory timings, does it still fail?



There was a bug that was randomly doing a wrong calculation. So it would pass on one occasion but not others. No system is 100% stable no matter how many hours of prime or runs of LinX you do. As long as it does what you want it to do without crashing or freezing and the like, then it's stable.

Yes Jon it has done the same when at stock. It's just so random and it drives me nuts. OCCT and Linpack for me. 3 hours occt linpack at 90% memory usage should mean it's stable in anyones book. I think in my case it may be another piece of software that is incompatible with Prime.
 
Gaidin, I had a similar issue, but it was LinX that was constantly failing with me, yet my system would pass Prime95 no problem at all, so I downloaded LinX again and when I used the newly downloaded copy my system passed with flying colours.

I figured that the copy I was using that kept failing must have gotten corrupted somehow, I can't think of any other explanation for it..
 
For the OP, loosen memory timings, does it still fail?

there at 8-8-8-24-2 atm, what would you recommend?

I have had, Uncore Frequency set to x17, im going to change it to x16 and see if that helps. But first i have loaded optimal defaults within the bios, and will leave Prime blending over night at stock settings, and see whats happened in the morning
 
Last edited:
That's quite interesting Gaidin. Any chance you have a spare hard drive/usb stick you could put a virgin copy of windows on to see if you can replicate the error? I'm assuming your copy of prime has the same md5 checksum as listed.

I tend to reinstall windows repeatedly while overclocking to reduce the chance of software being the issue, and generally the overclocking install just has windows and the tools on. I can't help wondering if 'no system is ever 100% stable' is a consequence of using windows too much :p

I'd suggest 9-9-9-28-2, and also try 8-8-8-24-2 at the x6 multiplier. I think the issue you have is the imc giving up on you when pushed too hard, which is most likely solved by feeding it more qpi or asking less of it. Gaidin makes a good point though, it may well be software related. Could you try with a fresh windows install (installed at stock speeds, of course)?
 
That's quite interesting Gaidin. Any chance you have a spare hard drive/usb stick you could put a virgin copy of windows on to see if you can replicate the error? I'm assuming your copy of prime has the same md5 checksum as listed.

I tend to reinstall windows repeatedly while overclocking to reduce the chance of software being the issue, and generally the overclocking install just has windows and the tools on. I can't help wondering if 'no system is ever 100% stable' is a consequence of using windows too much :p

Using an updated version of Prime seems to have sorted the problem. As for system stability, I run a company that designs and builds custom mainframes and you should see the stability issues with those. Thats the reason why we build so many redundancies and backups into them and no sign of windows there.
 
That's a good job to have, nicely done mate. Going to go offtopic as a result though :s, apologies to the op

What stability issues do you hit? I was under the impression that the majority of redundant hardware was against hardware fault of failure, hence raid, multiple psus, multiple ethernet ports etc. Do you hit software instability as well? if Io, what operating system(s) are they running?
 
Weapon of choice in a standard installation is the IBM z10. It can utilise multiple OS's. z/OS, TPF, VM, VSE also Linux and systemsolaris albeit specialized for the IBM. also we are playing about with mantissa's z/VOS which allows us to implement x86 architecture like Windows and Linux.

Most of the software problems come not from the OS itself, but the integration of specialized packages, especially on the medical installations. But most of the systems we install are very specialized and use custom unix/linux based OS's which are system designed and inherently problematical.
 
Not a windows only chap then :D

Given me a few things to google there, cheers. Not my field of expertise at all.

I sympathise with linux being unstable. Much as I tend to pretend it never crashes, in practice every time I run a kernel I've compiled it seems shaky, and ubuntu doesn't always behave. I should perhaps instead claim that the tested-to-death debian stable never crashes. Anything less rigorously tested is unfortunately a bit less trustworthy
 
Back
Top Bottom