I hate 1808!

VeNT

VeNT

VeNT

Soldato
Joined
9 Jan 2003
Posts
21,086
Location
Cornwall
ok, I've got ANOTHER sodding 1808 , but this REALY takes the biscuit.
FAHMon tells me that I downloaded this WU at 17:48 on the 8th of aug, that I've only done 10% of the WU and that its going to take another 35 days 21 hours 40 mins (and rising) at this rate.
now I've just checked that rig (3200 XP, 1gig ram) FahCore_82.exe IS using 99% of the CPU, BUT System Idle Process seems to have 10-20x the CPU time :confused:
I just don't get it! if the core is getting 99% of the CPU time, how can SIP have MORE hours logged (and its way more, the core is showing 40 mins where as SIP has hours logged)
I've rebooted the client to see if that helps, but I dunno, I may have to re-install FAH on here :mad:
 
rich99million said:
The ETA of 10 days now will be based on the rubbish previous performance so is obviously going to be way out. Sounds like it's running fine now so unlikely that the core/client or WU is corrupt in any way.

MGP - What is the FAHlog showing? It's not unknown for the client to stop reporting progress properly whilst it's still actually working and making progress. However a restart should have sorted that - is it possible you have a new core or WU that FahMon doesn't recognise (or even an older version of FahMon?)
Click to expand...

there was about 4-5 pages (or more) of checkpoints (15 mins) between two steps when I was having that uber long ETA
its down to 2 days now with 1% an hour atm (strangly slow?)

Project : 1808
Core : Amber
Frames : 100
Credit : 153

-- Hal 9000 --

Min. Time / Frame : 13mn 58s - 157.75 ppd
Avg. Time / Frame : 52mn 00s - 42.37 ppd

-- Brenda --

Min. Time / Frame : 14mn 09s - 155.70 ppd
Avg. Time / Frame : 14mn 41s - 150.05 ppd


-- Bot 001 --

Min. Time / Frame : 14mn 25s - 152.82 ppd
Avg. Time / Frame : 14mn 33s - 151.42 ppd

Hal is the one with the issue as you can see, 3200 1gig
brenda is a 3500 Athlon 64 with 1gig
Bot 001 is a Athlon XP 2500 barton with 512.

just goes to show how little difference there is somtimes.
 
Last edited:
rich99million said:
I've had WUs stall like that before but only when another higher priority process has gone awry and nicked all the CPU time itself (my USB wireless adapter used to do it - turned out to be some form of virus) like you said they just kept checkpointing but the core wasn't getting any CPU time.

In case it's the core itself you could stop the client, delete the offending core, then restart the client and it'll download a fresh copy. The same goes for the client - you can just download a fesh copy and overwrite the current one. If it's neither of those and you're fed up of this WU then delete the Work folder and the queue.dat file and restart the client to make it download a new WU (which may or may not be the same as the one you just got)

However I fear this sounds like something that could be windows messing about - probably worth doing a thorough scan to make sure you've not got any nasties
Click to expand...
nod 32s not showing anything
I think it was just playing up as it seems ok now.
 
You must log in or register to reply here.
Back
Top Bottom