Woot woot i hit 4GHZ!!!

[manimal]

I would imagine if he did any CPU stress testing CPU would kick into high gear mode anyway.

wrong.

If his chip heats up like during stress test, it will throttle down making him think he passed the stress test when he didnt.

You need to disable Speedstep, and EIST and then run the stress test again.

OTherwise im willing to bet your chip is throttling at those temps your showing on idle.



Is there any links that can explain this any further Aigo? Im very interested why it would throttle at load? I need me some good reading while I pull an allnighter on call ; ;

 

[BigMoosey74]

I would stress test it with Bejeweled II as well.

 

[Rubycon]

Use the new version of OCCT. It is very thorough and provides more information. I've had systems that were error free with Prime/memtest but would puke on OCCT in a few minutes!

 

[Dadofamunky]

Originally posted by: piotrgurin
oooo SETI! good thing you guys reminded me, i forgot what to do with all this extra computing power! 8)

:beer:

Originally posted by: Rubycon
Use the new version of OCCT. It is very thorough and provides more information. I've had systems that were error free with Prime/memtest but would puke on OCCT in a few minutes!

It also has the benefit of not taking so much freakin' time. I rack up another $10 a night when I run a stress test on Prime.

 

[Markfw]

Originally posted by: Rubycon
Use the new version of OCCT. It is very thorough and provides more information. I've had systems that were error free with Prime/memtest but would puke on OCCT in a few minutes!

Same with F@H !!!!

 

[Rubycon]

Originally posted by: Markfw900

Same with F@H !!!!

I've loaded up with boink and let it run all night yet the same system with OCCT failed within 30 minutes due to insufficient chipset voltage.

If you want to get the highest CPU core temps try linpack or superprime. Be warned though, many systems - even those running at stock voltage and speed - often hit 70C or higher with this software! (stock cooler) It literally lights a fire under your cpu.

 

[piotrgurin]

core 0:

Test 9, 800000 Lucas-Lehmer iterations of M141311 using 8K FFT length.
Test 10, 800000 Lucas-Lehmer iterations of M135169 using 8K FFT length.
Test 11, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
Test 12, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
Test 13, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
Test 14, 800000 Lucas-Lehmer iterations of M157695 using 8K FFT length.
Self-test 8K passed!
Test 1, 560000 Lucas-Lehmer iterations of M212991 using 10K FFT length.
Test 2, 560000 Lucas-Lehmer iterations of M210415 using 10K FFT length.
FATAL ERROR: Final result was FFA31AC4, expected: 3FC3CCD7.
Hardware failure detected, consult stress.txt file.
Torture Test ran 33 minutes 42 seconds - 1 errors, 0 warnings.
Execution halted.

Core 1:

More than one CPU detected.
You should run two copies of SP2004 simultaneously.
Type: Blend - stress CPU and RAM Min: 8 Max: 4096 InPlace: No Mem: 1791 Time: 15
CPU: 4014MHz FSB: 446MHz [446MHz x 9.0 est.]
3/25/2008 10:40 AM Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Torture Test ran 0 minutes 17 seconds - 1 errors, 0 warnings.
Execution halted.


doh! my first failure in orthos. it didn't crash or anything though..... i've never crashed yet on my current setting.

What do i do now?

 

[Rubycon]

Originally posted by: piotrgurin
core 0:

Test 9, 800000 Lucas-Lehmer iterations of M141311 using 8K FFT length.
Test 10, 800000 Lucas-Lehmer iterations of M135169 using 8K FFT length.
Test 11, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
Test 12, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
Test 13, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
Test 14, 800000 Lucas-Lehmer iterations of M157695 using 8K FFT length.
Self-test 8K passed!
Test 1, 560000 Lucas-Lehmer iterations of M212991 using 10K FFT length.
Test 2, 560000 Lucas-Lehmer iterations of M210415 using 10K FFT length.
FATAL ERROR: Final result was FFA31AC4, expected: 3FC3CCD7.
Hardware failure detected, consult stress.txt file.
Torture Test ran 33 minutes 42 seconds - 1 errors, 0 warnings.
Execution halted.

Core 1:

More than one CPU detected.
You should run two copies of SP2004 simultaneously.
Type: Blend - stress CPU and RAM Min: 8 Max: 4096 InPlace: No Mem: 1791 Time: 15
CPU: 4014MHz FSB: 446MHz [446MHz x 9.0 est.]
3/25/2008 10:40 AM Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Torture Test ran 0 minutes 17 seconds - 1 errors, 0 warnings.
Execution halted.


doh! my first failure in orthos. it didn't crash or anything though..... i've never crashed yet on my current setting.

What do i do now?

Download OCCT from the link I provided earlier.

It provides graphs stored in your local documents folder like this and this. In the case of the tested machine in this example one can see the factory provided cooling is barely adequate. The 1U copper heatsinks are cooled by airflow inside the case which is really good - but no match for a 3rd party solution. This leaves little to no room for any kind of overclocking.

Another feature with OCCT is after you run it - if a problem crops up down the road you can run it again and compare the graphs as they are timestamped. If the power supply/mb VRM is slipping or the heatsink is just clogging with dust resulting in higher core temps causing instability - you can catch it. Prime and other programs will tell you that you have a problem - but to track other parameters requires other programs running with logging enabled. Then this data may need to be graphed with a spreadsheet software, etc.

 

[nyker96]

why does the cpu tag say 444fsb while the mem tag say 532fsb? is cpuz having problem with reporting the correct fsb here?

 

[kschaffner]

His memory is probably on a divider where its running at ddr2-1066 which is 66mhz over spec of his ram (ddr2-1000).

 

[Assimilator1]

Originally posted by: Dadofamunky

Originally posted by: Markfw900
Thanks aigo !

The problem is, that with all those on, sometimes it hard to get and hold a stable OC (so I have heard) I never use them, since all mine are 100% load 24/7 so I don't need or want it.

So what do you do with all that stuff Mark, try to contact aliens through SETI?

He currently runs Folding@home AFAIK

piotrgurin
Hey good to see you'll be rejoining 'The search', are you in a team?

Awesome o/c btw
What's your loaded temps btw?
And yes you need to run P95 for at 24hrs to start with.

doh! my first failure in orthos. it didn't crash or anything though
No it won't unless your system is really unstable ,you should read the instructions 1st

What do i do now?
Either increase vcore or drop the FSB a little then retest with P95 or OCCT.

Dadofamunky
It also has the benefit of not taking so much freakin' time. I rack up another $10 a night when I run a stress test on Prime
I highly doubt it'll come anywhere near that!, my Q6600 @3GHz running DPAD (so 100% loaded but not quite as heavy as P95) costs me £15 per month running 24/7.And in general energy costs are much higher here in the UK than in the US, last I checked a month or so ago.

Rubycon
Folding@home is far more picky/stringent than any other DC project I've run or heard of (so far,except possible CPDN), & btw it's not yet run through BOINC.
I've passed 24hr small FFTs on P95 & failed F@H within minutes too, maybe OCCT is just as stringent?