ok, I am trying to track down a problem on my gtx 295.

it will crunch a wu, then suddenly the wu will error out with this message:

Cuda error in file '..\cuda/cutil.h' in line 968 : initialization error.
Memory usage: host: bytes device: bytes
Assertion failed: 0, file ..\cuda/cutil.h, line 968

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

system is running XP64 with driver version 181.20.

after this, The driver stops working and all wu's will immediately error out.

any help would be greatly appreciated.

just upgraded to 182.50. lets hope that is the problem.

BTW: the beta 185.68 drivers for XP64 have a problem as they are missing files.

upgrading drivers did not fix anything :(

any other suggestions?

What changed between the 23rd and 24th as jobs where running ok then suddenly errors.
Windows updates?
New hardware or drivers?

Are you running stock speeds on your gtx295 or tweaking a little.

I added a few to clock and memory and returned 2 errors. Dropped it back down to stock and everythings fine again.

nope, no overclock.

I have gotten it down to a Bad Video Card :(

stuck it into another computer with Different type CPu, OS and drivers and it gives same error.

So, only thing left is a bad Gtx 295

Fingers crossed for mine then :)

glad you have solved the problem though

I have a new bad one, too. It's a Gainward GTX295...
The "Multi-GPU-Mode" is disabled and one core is ok - no problems to finish a WU. The other isn't ok and makes a lot of errors... There are still errors in the Multi-GPU-Mode...
I try to give back the card...

Kind regards

Joe

PS Both of my Point of View GTX295 are error free...

There's a Vista issue where the second core is unavailable to do CUDA work, hence the errors. There are suggested reg fixes and other tricks such as dummy monitor connectors that can possibly fix it. Though they didn't work in my case.

I have errors too.

01/05/2009 19:09:56 GPUGRID Computation for task 36-KASHIF_HIVPR_dim_ba2-2-100-RND7433_0 finished
01/05/2009 19:09:56 GPUGRID Output file 36-KASHIF_HIVPR_dim_ba2-2-100-RND7433_0_1 for task 36-KASHIF_HIVPR_dim_ba2-2-100-RND7433_0 absent
01/05/2009 19:09:56 GPUGRID Output file 36-KASHIF_HIVPR_dim_ba2-2-100-RND7433_0_2 for task 36-KASHIF_HIVPR_dim_ba2-2-100-RND7433_0 absent
01/05/2009 19:09:56 GPUGRID Output file 36-KASHIF_HIVPR_dim_ba2-2-100-RND7433_0_3 for task 36-KASHIF_HIVPR_dim_ba2-2-100-RND7433_0 absent

I believe not.
It work fine with driver 185.20, on the 2 graphic cards.
and now with higher driver, I have these problem.

I try to return on the 185.20. But I lost ambiant occlusion on game. (for more information : http://www.hardware.fr/articles/756-1/dossier-nvidia-ameliore-qualite-graphique-avec-l-occlusion-ambiante.html
But it's in french.

Well, either you try one of them (downclock or loose ambient occlusion) or I'm afraid we can't help you any further. We could speculate until next century about what might be going on, but that's not worth much without some actual tests.

MrS

Yeah.

I finish the wu who zre launched, and I try 185.x

There's a Vista issue where the second core is unavailable to do CUDA work, hence the errors. There are suggested reg fixes and other tricks such as dummy monitor connectors that can possibly fix it. Though they didn't work in my case.

There's a Vista issue where the second core is unavailable to do CUDA work, hence the errors. There are suggested reg fixes and other tricks such as dummy monitor connectors that can possibly fix it. Though they didn't work in my case.

That explains why the second core I think I have isn't used, then. Thanks for the information.