Prime errors

Kesnel said:
I've had CPUs pass S&M but not Prime. I find the fastest and toughest test is OCCT; if it passes OCCT it will always pass Prime in my experience.

Now we have another program, the fact is that short tests are only good enough for quick testing. Day/week/month is required for complete stabilty.

From my experience F@H has been the toughest test of a PC, yes it may have to be run for a while to show errors but those errors are better than one during some important work!?

Two instances on a Single CPU, and Four on a Dual Core with a Tinker and GB Gromacs on each one tests the CPUs FPU, SSE, SSE2 and 3, plus whatever else it uses. Then play a game for 12 hours, or loop 3D Mark 2006 or something.

Anyhoo, long testsing for final clocks > short tests for overclock
 
Sorry, I don't think I was too clear in what I was trying to say. I was meaning to say that OCCT is the best quick test, I'd still run at 24 hour Prime for my day to day clock.

It seems to me that OCCT will give you a very good indication as to whether or not a CPU is going to pass Prime. Errors that take nearly an hour to show in Prime will show within a few minutes in OCCT. I find it's preferable to do this before starting a Prime run as there's nothing more annoying than to get a few hours through testing before getting an error and having to start over. In addition to this a 32m pass usually equates to a 3dmark pass for CPU and mem.

My order for CPU testing will go: SPi 1m, SPi 32m, OCCT, Prime Small FTT.

I can't speak for F@H though as I've never used it. :)
 
Back
Top Bottom