Just started...

[3.0charlie]

Either the OC is too high and unstable, or the WU was corrupted. It happens.

[chrisk]

I would slightly roll back the OC (~50mhz). There are OCs that will pass the other WUs, pass OCCT/ATITools/Furmark, but fail on a 511.

I personally don't consider a GPU OC stable until it can handle a couple of 511s no problems.

[somecanadianguy]

Running strong again... haven't gotten another 511 yet though so who knows?
I was trying 648/1688/1166 with fan @ 85% and temp was around 75c.
I haven't thoroughly tested my card with these settings so it very well may be unstable.
Well, too unstable for the 511s anyway.
I don't know much about OCing a vid card... I'll keep messing with it though.
Right now it's @ 666/1688/1199, fan @ 85%, temp 60 - 64c doing a 1888pt WU.

I've dropped my OC to around 3.5GHz until I see how it handles folding.

Realtemp shows my cores around 60c...

Everest Ultimate shows...
Northbridge: 49c
CPU: 44c
Motherboard:45c

I'm curious how long I can expect my rig to survive running like this.
Normally it gets a fair amount of use rendering and stuff, but this is pushing my hardware quite a bit harder for longer periods than normal.
I want to help, but I need my computer to live a while too.

[3.0charlie]

Don't worry, it will survive. It's made for running at 100%.
Indeed, FAH pushes a rig like like any other app out there. And it will find out very rapidly if it's unstable - and forget the 511s. A lot were bugged.

[Soultribunal]

Those Temps are good, so don't worry too much.
The GPU stuff, Charlie Knows best in that field.
I keep my Cards Dialed in nicely.

In the end, Folding will make or break weak hardware.
So far, I have only killing one thing Folding, and that was my HIS2600.
Other than that, Solid so far.

ST

[somecanadianguy]

Having another issue with the GPU client...

[03:41:05] + Attempting to get work packet
[03:41:05] - Connecting to assignment server
[03:41:06] - Successful: assigned to (171.64.65.106).
[03:41:06] + News From Folding@Home: Welcome to Folding@Home
[03:41:06] Loaded queue successfully.
[03:41:06] - Couldn't send HTTP request to server
[03:41:06] (Got status 503)
[03:41:06] + Could not connect to Work Server
[03:41:06] - Attempt #7 to get work failed, and no other work to do.
Waiting before retry.

What do I do?
Just wait and let it keep trying?

[LCB001]

Originally Posted by somecanadianguy

Having another issue with the GPU client...

[03:41:05] + Attempting to get work packet
[03:41:05] - Connecting to assignment server
[03:41:06] - Successful: assigned to (171.64.65.106).
[03:41:06] + News From Folding@Home: Welcome to Folding@Home
[03:41:06] Loaded queue successfully.
[03:41:06] - Couldn't send HTTP request to server
[03:41:06] (Got status 503)
[03:41:06] + Could not connect to Work Server
[03:41:06] - Attempt #7 to get work failed, and no other work to do.
Waiting before retry.

What do I do?
Just wait and let it keep trying?

Stanford has problems with their servers, they are switching over to a new system.
It will eventualy connect, but since the intervals between connecting attempts get quite long after the 7th or 8th try you can try restarting the client to keep the interval shorter.

Status 503 usually means a problem at their end...

[somecanadianguy]

Seems to be working fine now...
I was starting to get impatient.

[LCB001]

Originally Posted by somecanadianguy

Seems to be working fine now...
I was starting to get impatient.

One of the many ways Stanford likes to keep us entertained...

[chrisk]

Same issue on my end last time I could get at the computer.