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.

The straight forward suggestion would be a driver update. Either to a 182 series one or to the beta 185.6x.

MrS

---

Scanning for our furry friends since Jan 2002

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

So, only thing left is a bad Gtx 295

They're said to have a rather high overall failure rate.

MrS

---

Scanning for our furry friends since Jan 2002

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

All my wus finish like that (vista 64) GTX260 + 8800 GT Boinc 6.6.20

Profanateur, both of your cards are substantially (factory?) overclocked. Try reverting to stock and see if it helps. Some of yours WU start, so your software setup should be fine.

MrS

---

Scanning for our furry friends since Jan 2002

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

---

Scanning for our furry friends since Jan 2002

I've had a whole bunch of errors since the 1st of May. They seem to be all complaining about "One or more arguments are invalid".

Latest couple are here and here

The 1st couple that started doing this are here and here

Machine is an i7 running two GTX260+ cards. Not overclocked. Driver is 182.50. It seems happy munching on Seti cuda tasks.

---

BOINC blog

I can't find anything wrong with your config. Something you could try:

- reboot
- power off and remove the power cord for >10 min
- try BOINC 6.5.0 or 6.4.7
- upgrade to a 185.6x driver, or maybe the new 185.8x

MrS

---

Scanning for our furry friends since Jan 2002

I can't find anything wrong with your config. Something you could try:

- reboot
- power off and remove the power cord for >10 min
- try BOINC 6.5.0 or 6.4.7
- upgrade to a 185.6x driver, or maybe the new 185.8x

MrS

It was rebooted a couple of days ago after doing windows updates.

I did go up to BOINC 6.6.25 and after noticing the errors back down to 6.6.23.

Strange that my other machines don't seem to be erroring out, although they have single cuda cards (GTS250's). They run the same drivers and BOINC version.

---

BOINC blog

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

Thanks.

apparemment it works fine with driver 182.5. And not with new drivers which support AO. :/

Which new driver did you try? 185.6x? You could give the 185.8x a try, they appeared just a few days ago.

MrS

---

Scanning for our furry friends since Jan 2002

Yeah.

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