Klepel, as you say you've been running these Nathan KIDc22 WUs just fine before in 59ks. Check if the GPU clock is still up to where it should be. After driver resets it sometimes stays too low without throwing an error at GPU-Grid. In this case a reboot would help.

MrS

---

Scanning for our furry friends since Jan 2002

The computer it failed on was a titan (which cannot run these WU's):

Coprocessors NVIDIA GeForce GTX TITAN (4095MB) driver: 314.22

Good catch! It seems I was too quick to blame the WU.

---

Oh, and I just noticed the up-load file does have a size of 107.88 MB (so more or less the double as before)

Sounds too long. Maybe wrong compression.

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

The strange WU is up-loaded: http://www.gpugrid.net/result.php?resultid=6930954

All seems normal. Only that it took nearly twice as long: 101,479.54 s
Stderr output: 57186.919 s

The next WU crashed, because of a electricity cut.

I will inform about the next WU after it's finished.

I've completed 18 NATHAN_KIDc22s, nine of the SODcharge variety for 134000 credits each, and nine of the RND variety for 167500 credits each EXCEPT...

The RND that completed this morning, well within 24 hours, gave 111700 credits:

http://www.gpugrid.net/result.php?resultid=6933145

That was a surprise!

Your 2nd wingman handed the WU in after it got sent to you, but before you could send your in. In this case the bonus credit doesn't trigger for both of you, sadly an old problem.

MrS

---

Scanning for our furry friends since Jan 2002

Your 2nd wingman handed the WU in after it got sent to you, but before you could send your in. In this case the bonus credit doesn't trigger for both of you, sadly an old problem. MrS

Ah! I did not notice I had a wingman. I had thought GPUGrid's quorum was one. Why did it get sent to me before the wingman's try had run out of time?

It's a known issue with the credit system at GPUGrid. Basically it happens only when a WU is resent and after being resent is returned by the first recipient and validates. Subsequent to the validation bonuses are not awarded. It's a fairly rare event but apparently too difficult to fix.

No Bonus for finishing within 24 hours

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

The WU was sent to the wingman first, but he didn't return it within a few days. At some point GPU-Grid needs the results to generate the next WU in this string / time iteration. So the WU was sent to you (not sure if this was before the deadline for the wingman or not), but the other guy evetually handed the result in. This is why GPU-Grid is not suitable for low-end hardware and why the deadline is rather short.

MrS

---

Scanning for our furry friends since Jan 2002

FYI, there are two new batches of simulations that are among the same research project I just sent out yesterday and today. Names are NATHAN_KIDc22_full and NATHAN_KIDc22_noPhos.

Boy, this place is turning in to you're own private Idaho, nobody else wants to run work units? Not that there's anything wrong with yours.

It's the circumstances. We are missing people to conferences, paternity and also summer is coming. So these weeks might end up being a bit unstable, but there is definitely more stuff to simulate! (We just need to get the people back :D)

After 23 successful Nathan_KIDc22s, I just got an error on my first noPhos, after 8h29m:

http://www.gpugrid.net/result.php?resultid=6944425

Just finished my first noPhos. Looks like no problemo.

http://www.gpugrid.net/result.php?resultid=6944390

Yes 5 phos done, no problems.

---

DSKAG Austria Research Team: http://www.research.dskag.at

I was working on two Nathan Phos WU's. After 16 hours and 99,617% done freezes my computer.

@#$%^&*@#$%^&@#$%^&#$%^& :'( not funny!!! :@

Why not? because it isn't the first time, no it is the third week have those problems. Only with GPUGRID for what I know... and it is very annoying.
From anger I've after restart all GPUGRID tasks aborted in BOINC, that is what you see at the task/client status now... -_-'


Last WU: http://www.gpugrid.net/workunit.php?wuid=4514859
Second last WU: http://www.gpugrid.net/workunit.php?wuid=4514763[/url]

Why do you guys hide you're computers? I've never been able to figure that out, I haven't had any lockups in a while on any of my 4 rigs, couldn't say what the problem is with yours. I disabled my onboard USB 3.0 and all my issue's went away.

I disabled my onboard USB 3.0 and all my issue's went away.

Do you have an Eltron chip? They had serious driver issues last year, leading to unstable transfer rates, devices dropping and unstable computers. Drivers from this spring are fine, though (using it myself.. guess why I know about the problems).

MrS

---

Scanning for our furry friends since Jan 2002

I was working on two Nathan Phos WU's. After 16 hours and 99,617% done freezes my computer.

What do you mean by that, did you run 2 WUs concurrently? If so be aware that you're alpha testing that functionality. It's not suggested or approved by the project in any way, so do it at your own risk.

MrS

---

Scanning for our furry friends since Jan 2002

Going by this post he has two GPU's.

Also,
Coprocessors [2] NVIDIA GeForce GTX 570 (2559MB) driver: 314.22

Outcome Computation error
Client state Aborted by user
Exit status 203 (0xcb) EXIT_ABORTED_VIA_GUI

(a process exit code used by the core client/app). More commonly found at CPU projects such as ABC, Asteroids, Physics@home, Constellation, Quake-Catcher...

I92R9-NATHAN_KIDc22_noPhos-1-10-RND9632_0 4514859 11 Jun 2013 | 23:11:29 UTC 12 Jun 2013 | 16:20:04 UTC Aborted by user 56,038.62 10,735.35 --- Long runs (8-12 hours on fastest card) v6.18 (cuda42)
I93R9-NATHAN_KIDc22_noPhos-1-10-RND7759_0 4514763 11 Jun 2013 | 23:11:29 UTC 12 Jun 2013 | 16:20:04 UTC Aborted by user 55,998.47 10,639.65 --- Long runs (8-12 hours on fastest card) v6.18 (cuda42)

http://www.gpugrid.net/show_host_detail.php?hostid=152224

The NATHAN_KIDc22_noPhos WU's take ~12h on a GTX660. Some finish under 12h on GTX570's on Linux but others are ~13.6h on W7.
Either 2 GPU's running slow (most likely) or one GPU running 2 WU's fast until they crash (less likely). Quite a few failures on that system though,
http://www.gpugrid.net/results.php?hostid=152224&offset=0&show_names=1&state=0&appid=

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help