Prime95

[jack bauer]

Once I cool down my sytem somehow, I will be gin to slowly OC. I downloaded Prime95, how do you use it, just run it? How are the result interpreted? What about the program TSC?

 

[IsDanReally]

Use the tortue test option. If your goal is to heat up your CPU, that shouldn't take too long. To test stability, I usually let it ran for 24 hours or more. The program will t ell you if the results are not correct, indicating the CPU is not computing correctly. If it says everything has passed, than things are good. Others can probably point you to a good OC guide, or give you more tips in that regard.

 

[the cobbler]

to test CPU stability ONLY:
small FFTs test 12-24+ hours

to test whole system stability (RAM, PSU, etc.) and especially memory controller:
Custom test using 1024k-4096k FFT size and 80-90% of RAM
should be run a minimum of 8+ hours

there are no results to interpret really. if small FFTs fails, your CPU is not stable @ voltage/speed. if Custom test fails after you pass small FFTs, then either your RAM or PSU are to blame. Any error means there was a simple error in calculation and the component in question is therefore unstable.

imho, it's best to run small FFTs for 24+ hours to be positive your CPU is stable
then run the Custom test for 8-12+ hours to make sure your mem controller can handle the HTT/RAM speeds

this is all assuming you are using an AMD chips...Intel the Custom test might not make sense...I would run LargeFFTs (in-place) instead of Custom in that case.

 

[Big Lar]

Originally posted by: the cobbler
to test CPU stability ONLY:
small FFTs test 12-24+ hours

to test whole system stability (RAM, PSU, etc.) and especially memory controller:
Custom test using 1024k-4096k FFT size and 80-90% of RAM
should be run a minimum of 8+ hours

there are no results to interpret really. if small FFTs fails, your CPU is not stable @ voltage/speed. if Custom test fails after you pass small FFTs, then either your RAM or PSU are to blame. Any error means there was a simple error in calculation and the component in question is therefore unstable.

imho, it's best to run small FFTs for 24+ hours to be positive your CPU is stable
then run the Custom test for 8-12+ hours to make sure your mem controller can handle the HTT/RAM speeds

this is all assuming you are using an AMD chips...Intel the Custom test might not make sense...I would run LargeFFTs (in-place) instead of Custom in that case.

What he said^, however, unless you use your system for mission critical, cut the times by 4, then enjoy if it passes. Just my Humble opinion.

 

[Davegod]

Is there any kind of tool to "torture test" the GPU? Other than one that makes you sit and stare for glitches, I mean. I've read about some tools for making use of the GPU as a data processor so figure it's possible.

 

[BlueWeasel]

Originally posted by: Davegod
Is there any kind of tool to "torture test" the GPU? Other than one that makes you sit and stare for glitches, I mean. I've read about some tools for making use of the GPU as a data processor so figure it's possible.

If you've got an ATI card, you can use ATITool or ATI Tray Tools to scan for artifacts at stock or overclocked core/memory speeds. I'm not sure if there is an equivalent program that does the same for Nvidia cards.

 

[the cobbler]

Originally posted by: Davegod
Is there any kind of tool to "torture test" the GPU? Other than one that makes you sit and stare for glitches, I mean. I've read about some tools for making use of the GPU as a data processor so figure it's possible.

rthdribl v1.2

nothing heats up the GPU better than this thing

 

[Davegod]

:beer:

 

[the cobbler]

Dave, run rthdribl for a good hour or two with as large a window size as your VGA's vRam will allow. it's even better to do it while running Prime Large FFTs or Custom using 1024-4096k ffts and 80-90% of RAM. obviously run dual instances if you have a dual-core.

if you can make it through that, GPUs are uber-stable :thumbsup:

 

[jack bauer]

How long does this iteration cycle last? I'v had it running for over 12 hours and it says 1.85%, per iteration time 0.077 sec. iteration 510000/27486871


thought it was 24 hours? do I have a setting wrong or should I run torture test instead?

 

[Unkno]

not really sure what your talking about......but the cycle lasts until you stop it and it'd be better if you used the torture test mode implemented into it

 

[jack bauer]

not sure either, thants why I asked. If you just open prime95, it starts automaticly, and run a program that looks like it runs a week!

 

[jack bauer]

Another side note for Prime95 users.


1. what should I set the available memory to?
2. are you suppose to run 2 copies if you have a dual processor for torture testing?
3. run for 24 hours or 1 hour on the first try?


Opteron 170 @ 2.00