I'm trying to get GPUGRID to work on my new laptop with a nVidia GeForce 320 M; VRAM 1GB. However, a few seconds after a GPUGRID-WU starts I get three messages noting absent output files and aborts noting computing error. I know my GPU is cuda-capable since it can compute SETI cuda-WU's just fine. 64bit Windows7.

Every one of you tasks has failed with "Compute error: Exit status 1 (0x1)". That may well be the consequence of your driver version 188.36, as GDF says.

But the application gets far enough to report that your 320M card has 3 multiprocessors, 24 shader cores. If you look in the FAQ: Overview of cards that run the GPUGRID application, you'll see that your card's desktop sibling, the Geforce 320, has 72 shaders and is still considered too slow to run GPUGrid. The tasks here run roughly 40x longer than average SETI tasks, and unlike SETI there is a time imperative to get the results back quickly - they are needed to form the basis of the next run issued to users.

Updating Nvidea drivers through the site of my laptop's manufacturer didn't do a thing.
However, currently I have program 'ACECMD beta version 6.22 (cuda)' and that one doesn't complain about absent output files and computes along just nicely, totally disregarding the 'time to completion' and eclipsing 5 minutes from that time every 10 seconds more or less.
EDIT: that is, until it has to re-start after having been moved to memory to make place for another program, THEN I get the missing output files.

Tried updating drivers through nVidea's site first, didn't work at all. My graphics card wasn't listed anywhere.
Unchecked 'leave in memory while suspended'.

Apart from unchecking the 'Leave in memory' I also changed the 'switch tasks every x minutes'-value. It was on 60 minutes. Since everything went without problems until the switch, and I noticed it was at 44 % done (no way have I gotten one that would take 24 hour, even though they list at 19 h to completion, it doesn't even take half that time) after one hour, I changed it to 150 minutes, so it should be able to 'run its course' without having to switch. The one that managed to get through didn't even need 90 minutes.
So, without using the beta driver, I have completed my first GPUGrid-WU.
Since other projects complain about my GPU I will try the beta driver though, but I seem to remember seeing some of the heading in the page you linked to before so it could well be I tried that before but without any improvement.

Update on the beta update driver: a) as I suspected I had tried that before and it can't help me. b) Had to reboot afterwards as I got strange graphics driver messages and GPUGrid's beta WU's started erroring again too.
Currently fine again. Have one that needs to be computed with 'Full atom molecular dynamics 6.72 (cuda)' up next, listed at 25:03:25 time to completion. Is that one of normal 'size'? However, I have learned not to trust those times, as those times sometimes tend to decrease at a rate faster than 1s/actual s.

Copycat,

I think you use a laptop for this.
Then you still have a wrong nvidia-driver (old).
The beta-one is 197.xx

Good luck

____________
Ton (ftpd) Netherlands

As I have tried to explain several times, I CANNOT update the driver, especially not through nVidea's site. Since it didn't update, I thought I shouldn't have to reboot.
ftpd: please read the first line of my original post in this thread, and all the other replies, don't you think that's what I've been trying all the time?
The 'full atom'-one didn't go as planned, it complained again. However, I got a message from the nVidea-driver again soon afterwards (and no, I had not done anything to it since boot), so that might have been related. Currently a beta-one is running again and has 'survived' a task-switch.

Sorry copycat, i will use my glasses!!
____________
Ton (ftpd) Netherlands

Link!
Maybe the reason why I can't update my driver is 'cos of the Win 64.