153% complete?

[samborarocks]

Hi all,

I have a WU on my second GPU that says it's 153% complete, it's a '925' point. Should I worry about it


-SR

EDIT: the % complete keeps climbing, maybe it's a display error? I'm using 'FAH GPU Tracker V2'...

 

[nimbyfaygo]

I would suggest deleting the WU and moving on. However....if it was me I'd like to keep it running and see just how high it would get.

 

[YamahaAlex37]

stop it windows is gonna asplode!



i'm curious how high it goes too..

 

[Zero82z]

Check the log file directly. If it is actually counting above 100%, stop the client, delete the queue.dat file, and start it up again.

 

[Kendrak]

Stop! Your going to cause a resinance cascade!

 

[sirmonkey1985]

this is the second one reported so far. another one was 1000+% save the log file and post it on folding forum. it might be something wrong with that WU. so the more people that report it means PG can remove it from the WS until its fixed.

 

[samborarocks]

I have copied off the log file, it was at 236% complete.

Do you mean post it on the Stanford folding forums?

Thx,
-SR

 

[YamahaAlex37]

we should have a contest... who can get the highest

 

[APOLLO]

this is the second one reported so far. another one was 1000+% save the log file and post it on folding forum. it might be something wrong with that WU. so the more people that report it means PG can remove it from the WS until its fixed.

This happened to me before and think I posted about it a few months ago. I had to delete the WU.

 

[Brak710]

Stop! Your going to cause a resinance cascade!

It's an Anomalous Workup Unit.

 

[sirmonkey1985]

I have copied off the log file, it was at 236% complete.

Do you mean post it on the Stanford folding forums?

Thx,
-SR

yeah they have a section for reporting WU errors. just throw it on there so they can see it.

http://foldingforum.org/viewforum.php?f=19&sid=e3a674b44f1dc9d6431e5db4eb3df4cb

heres the thread i would post it in.
http://foldingforum.org/viewtopic.php?f=59&t=16533&start=0


Re: 10955 completed 1134%

by friedrim » Thu Nov 11, 2010 7:41 pm
I posted new cores (v2.14) that should fix the problem. However, I am not absolutely sure the issue is resolved since I could not reproduce the problem; the files from derrickmcc helped immensely in targeting where the problem was most likely coming from -- thanks!

anyone that hasnt updated the core. delete the core15.exe and let it redownload see if this fixes your problem.

 

[HighYield]

Stop! Your going to cause a resinance cascade!

Don't worry, a tachyon pulse should be able to counteract that. Assuming of course your dilithium is of high quality.

+1 for deleting the unit....before it is too late...