What mode to run Prime95

NYJohn413 · 04-28-2008, 11:13 PM

Hey Ho fellow TSFers.

How should I run Prime95. Do I run it in Small FFTs, Large FFTs, or Blend? I currently have it running on Small FFTs for 3hrs, about the longest gone w/o error.

(see link)

Anyways, am I wasting my time on this mode? Should I use another to prove stability and if so which?

P.S. I'm pretty sure I set the CPU Voltage at 1.33v but CPUID reports it never going past 1.3v and mostly at 1.25v. I ask in effort to go to a higher FSB which I did initially until Prime95 told otherwise. That is the value for CPU Voltage is it not?

P.P.S. This is my absolute first build. So much fun!!!

Underclocker · 04-29-2008, 05:40 AM

I use Blend and let it run for 24 hours, but that's just me. Some people prefer to run a custom torture test with Min FFT set to 8K and time set to 600 minutes to test the CPU and Min FFT 4096K for another 600 minutes for RAM.

Increasing the voltages helps to stabilise the system. CPU-Z detecting lower values could mean your power is fluctuating a lot, which destabilises.

NYJohn413 · 04-29-2008, 06:30 AM

Thanks for the response Underclocker. There are conflicting reports on which to use, the knack against blend is that is sometimes pre-allocates too much memory and writes to the pagefile. The CPU wouldn't be under full load during disk access and the test would be skewed. The article didn't specify what version of P95 was running.

Some say Small, some large, custom....

I take it from these mixed reviews that any test would prove stability given the right amount of time. If there is any semblance to the blend test, I'll probably run a custom test and just manually allocate like 90% of my memory to be used.

*UPDATE*
10hrs of P95, No error. Temps spiked to 57°c but kept to 53°c throughout. Do you think temps are too high for a "moderate" overclock?

Underclocker · 05-01-2008, 03:23 AM

Those temps are good, no need to worry about them.

04-29-2008, 05:40 AM	#2 (permalink)
Underclocker Tech Hardware Team Join Date: Aug 2007 Location: A land girt by sea. Posts: 430 OS: Windows XP Pro SP3 My System	Re: What mode to run Prime95 I use Blend and let it run for 24 hours, but that's just me. Some people prefer to run a custom torture test with Min FFT set to 8K and time set to 600 minutes to test the CPU and Min FFT 4096K for another 600 minutes for RAM. Increasing the voltages helps to stabilise the system. CPU-Z detecting lower values could mean your power is fluctuating a lot, which destabilises. __________________ Win•dows: n. A thirty-two bit extension and graphical shell to a sixteen-bit patch to an eight-bit operating system originally coded for a four-bit microprocessor which was written by a two-bit company that can't stand one bit of competition. Last edited by Underclocker : 04-29-2008 at 05:42 AM.

04-29-2008, 06:30 AM	#3 (permalink)
NYJohn413 Registered User Join Date: Mar 2007 Posts: 13 OS: Win XP MCE SP2	Re: What mode to run Prime95 Thanks for the response Underclocker. There are conflicting reports on which to use, the knack against blend is that is sometimes pre-allocates too much memory and writes to the pagefile. The CPU wouldn't be under full load during disk access and the test would be skewed. The article didn't specify what version of P95 was running. Some say Small, some large, custom.... I take it from these mixed reviews that any test would prove stability given the right amount of time. If there is any semblance to the blend test, I'll probably run a custom test and just manually allocate like 90% of my memory to be used. UPDATE 10hrs of P95, No error. Temps spiked to 57°c but kept to 53°c throughout. Do you think temps are too high for a "moderate" overclock?

05-01-2008, 03:23 AM	#4 (permalink)
Underclocker Tech Hardware Team Join Date: Aug 2007 Location: A land girt by sea. Posts: 430 OS: Windows XP Pro SP3 My System	Re: What mode to run Prime95 Those temps are good, no need to worry about them. __________________ Win•dows: n. A thirty-two bit extension and graphical shell to a sixteen-bit patch to an eight-bit operating system originally coded for a four-bit microprocessor which was written by a two-bit company that can't stand one bit of competition.