Gauntlet 2009 Joiners Thread!

Don't start that off again! Last time I read the animal-borging thread I almost ended up with a hernia from laughing so much.

It's a shame a lot of the pictures have gone and weren't archived. That thread (and the follow up) was one of this forum's finest moments.

Don't know the breed, don't think it'd appreciate Cat5 in any orifice either. :p

It nearly all went pear shaped just now. Room light in the office just burned out - literally. I thought it was a power cut but the TV was on. Went for the off switch and got there in time but there's a noticeable smell of burnt plastic. Guess I'll have to try and find the spare tomorrow (it's a special bulb, though I can use an ordinary one for now).
 
Last edited:
Have flashed all the bios now so the clocks will be steady at 676/1457/1100 giving an estimated 125Gflops each :D


Cheers, Simon.
 
Is that @ stock voltage?

Yes stock volts 1.03v, temps have gone up to 58c from 54c with the clock increase.

I have had them as high as 725/1563/1200 to do a few Vantage runs as a quad setup and needed to raise it to 1.15v for stability.

Cheers, Simon.
 
What cards are you running?

Sorry for the bothersome questions.

My bad.....It's the 295's innit.
 
Last edited:
My rig seems to be running ok now......

Well, it has been for the past 2 hours or so with no issues running SETI.

Speeds:

Q6600 @ 3.2Ghz & 2 x 1Gb DDR2 @ 1066Mhz (CPU @ 43c)

3 x GTX260's @ 693/1502/1155 (stock voltages) (GPU's @ 79c, 84c & 75c)

Air Cooled - All fans on auto speed.

Hopefully it will still be running in the morning. :p
 
Question:

Why would SETI go slower when I inreased the Shader clock from 1400 to 1500?

A work unit that normally took about 12mins took nearly 20mins to complete.....

not all WU are made equally, some just take longer than others, however you should get more points, look at how much credit that unit got compared to the ones that took 12 mins. just a thought.
 
For your appreciation ... :)

cpartcert1.php
 
Question:

Why would SETI go slower when I inreased the Shader clock from 1400 to 1500?

A work unit that normally took about 12mins took nearly 20mins to complete.....

:(

Stock Speeds are:

Core - 650
Shader - 1400
Memory - 1000

There have been some example in the graphics section whereby when overclocking on GTX 260/280/285 etc cards that it can actually lower the performance of your card. This may be what's happening here, just try pushing it a bit more, or knocking it back a bit.
 
Erm Biffa......

I do believe that you have just been demoted to fifth place in the Gauntlet.

La de da de da

Bah temporary abberration :p

You'll have to do better to keep ahead :)

And as for br83taylor.. wtf!?@# :eek: how do you get a 12K average on a E4400 with a single GTX260?

C'mon guys lets PUSH harder! :D
 
Bah temporary abberration :p

You'll have to do better to keep ahead :)

And as for br83taylor.. wtf!?@# :eek: how do you get a 12K average on a E4400 with a single GTX260?

C'mon guys lets PUSH harder! :D

sorry lost ability to read, were you trying to imply 12k is high or low? either way not sure what i can do about it, the CPU is at 3 gig, and the GPU at 700 core, can't remember the others. when i compare it to what Stuart Gibson gets out of his 9800GTX+'s it seems low, but compared to my workstation it seems good.

i am a little unhappy about my performance from my workstation, i can only assume sharing 8 CPU tasks on the memory bandwidth is constraining it, plus the GPU isn't overclocked, as its an FX i have no idea if the clocks are locked or something, if i try ntune, it fails the test just 1 mhz above stock.
 
C'mon guys lets PUSH harder! :D

I got the same prob as Mr Loudbob, every time I push harder it takes longer. While the results page is turned off I can't tell if the longer time is giving more credit. And worse, I'm going to be away until the end of the race so this is no time be experimenting. I'll have to trust the auto rescheduler to keep the GPU fed.

Good luck to all for the final lap.
 
Yes unless you are constantly nursing the rig then set it to a safe level and let it go. No need to overdo it :)
 
Update.....

My system was stable using the new clock settings for the GPU.

But..........

Everytime I try to overclock the CPU to 3.2Ghz or above the same thing happens......

The rig is stable for between 6 - 8 hours then it just hangs.

Had to knock the CPU back to 3Ghz to see if it makes a difference.

Oh well :(
 
At this point stability > *

I just had my Mac Mini powered down for 10 minutes so I could adjust the BIOS on another (headless) PC. Should be able to make up the PPD for that. :)
 
Back
Top Bottom