What about this:
...
12:22:30 (4172): wrapper: running dnetc518-win32-x86-stream.exe (-ini dnetc.ini -runoffline -multiok=1) - attempt 10/10
12:22:31 (4172): input buffer 3 packets (560 bytes), checkpoint file 0 packets (0 bytes), output buffer 0 packets (0 bytes)
12:22:31 (4172): premature exit detected, app exit status: 0x0
12:22:31 (4172): no progress detected during last retry
12:22:31 (4172): too many retries (max 10), cancelling
12:22:31 (4172): called boinc_finish
</stderr_txt>
]]>
/ 
Is the card a 5970? What are the GPU and memory settings that you are running it with?
Regards
Zy
/ Looks like the CPU app is crashing too, so his issue might not be GPU related.
/
...
12:22:30 (4172): wrapper: running dnetc518-win32-x86-stream.exe (-ini dnetc.ini -runoffline -multiok=1) - attempt 10/10
12:22:31 (4172): premature exit detected, app exit status: 0x0
</stderr_txt>
]]>
That's odd, it's like something is preventing the Distributed.net Client from running but both starting and return code from it suggest everything is fine. :(
One thing that comes to mind and that is that your antivirus program is preventing the client to run. Please, could you try to run the mentioned exe file manually from the command line and see if there's more help full error message? And possibly check your Windows and antivirus logs for any clues?
If you need help to test this or more specific instructions on what to try then please don't hesitate to ask. :)
-w
/ I am wondering if there is a card problem in a hardware sense - hence the question on Clock settings and how far its been pushed, there is a high GFLOPS reading (2720) and whilst that reading is a bit of a BOINC artificiality, it has meaning in a relative sense - a GPU pushed that high almost certainly indicates a big overclock. There was a successfull WU on 3 May so his setup can do the job, but from the task messages it doesnt get to the stage of even loading up any more.
Without more information I have a feeling its either a card thats possibly on its way out, or there is a main memory issue somewhere.
Drivers are fine, unless they have become corrupt - however the failures go back a while and the latest driver(only released recently) is loaded. Would be worth doing a reload of the driver, it would at least eliminate that as an issue.
If a driver reload does not do it, and a retry at card default settings does not then work, I would go for a card integrity test, and second if still an issue, test main memory.
Regards
Zy
/ The GPU is ATI 5870 but i've also this problem at my laptop with NVidia GT8600M.
There is no OC at the GPU at the moment.
There is no file dnetc.ini but there is dnetc-1.00.ini & dnetc-cpu-1.2.ini
/ Interesting .... :)
Is there common ground between the two machines on the anti-virus you run (see Teemu's suggestion above) ?
The fact that both AMD and NVidia apps are reacting the same way does point more to the anti-v suggestion if you use the same on both, and BOINC directories are not explicitly exempted as exceptions.
I cant see it being the Core Application from DNET, too many machines run it ok, and the BOINC Wrapper for both apps will be slightly different in detail, yet the same symptoms surface. Which points back to some common software install / config that both machines use.
Another thought - and I am on slightly shakey ground as I am not certain it would cause your problem ..... wierd issues can occur if BOINC is loaded as a protected Windows Service, not a straight app.
Regards
Zy
/ I'll check the AV software... because I'm sure that BOINC is not running as protected application / windows service.
I've 25kk points in DNETC and there was not such a problems :)
Edit:
I checked AV logs on both computers and there is nothing about this application.
At the laptop I also turned AV off but the problem still occures...
/ I have the same ini file (dnetc-1.00) so that looks ok, but thats outside my competance, thats Teemu territory :)
Would be an idea to quickly run a WU from (say) Collatz & Milkyway - that would nail in a general sense card health and main memory - although it is looking more like some kind of install/config issue common to both machines.
Its a wierd one thats for sure ..... :)
Regards
Zy
/ I just done 1 WU but form DNETC.net...
http://dnetc.net/result.php?resultid=29056167
/ http://dnetc.net/result.php?resultid=29056167
That result is gone already but one difference is that they are using the older distributed.net client build while we are using the latest one. It's possible that this newer version has changed something that doesn't like your system or driver versions. :(
What core did you select in your project preferences here? It might be out-of-bounds or set to a core that's crashing on your system.
-w
/