I get the following error every so often on This Box It's a BFG 8800GT OC running at the speed when I bought it ...

Cuda error: Kernel [frc_sum_kernel_dihed] failed in file 'force.cu' in line 252 : unspecified launch failure.

Cuda error: Kernel [frc_sum_kernel_dihed] failed in file 'force.cu' in line 252 : unspecified launch failure.

My first error with this log on 8800GT 1GB:

http://www.ps3grid.net/result.php?resultid=124548

Any solution or info about this error yet?

Just found out that my WU which crashed this morning (near before it was finished!) had the same error:

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

My card is a 9600GT.
And it seems it crashed my Windows too! As I came back some hours later I just found out my comp had a reboot to Linux (I have a dual-boot and Linux is standard).
____________
Member of BOINC@Heidelberg and ATA!

Another one killed itself with such a message.

What's wrong with them?
It gets really annoying, that costs me almost an entire day of crunching every time...
>:-\
____________
Member of BOINC@Heidelberg and ATA!

It's driver version 177.84, no change since I started crunching here.
I have no clue what could be wrong, crunched two other WUs right before without any problems:
http://www.gpugrid.net/result.php?resultid=126657
http://www.gpugrid.net/result.php?resultid=125288

Edit:
Just found out on the NVidia page that version 180.48 is now recommended for my card.
I will install and try it out, maybe it fixes the problem...
Will take some days to discover that. ;-)
____________
Member of BOINC@Heidelberg and ATA!

2 observations:

1. WUs which give this error generally run fine on other machines

2. All who reported this error in this thread are running (factory) overclocked GPUs.

I think it's worth testing if there's a link between 1. and 2. DrNow, you seem to get the errors most frequently. Could you take the core and shader clock of your card back a bit?

Next one:
http://www.ps3grid.net/result.php?resultid=131339

driver 178.24 WinXP, RivaTuner 2.20

I cannot explain me why?! And after loosing many hours, why this error is not coming on start ^^

Before I run older version of RivaTuner to decrease the speed of the fan, around 57°C on 8800GT, so no problem. My first week all WUs are fine, but after 3-4d 2 times same error, something must be wrong somewhere but where?

Edit:
Checked all results, the error came with 6.3.21, before 6.3.19 all ok.

If anyone run >6.4 or <6.3.21, pls me know if you get the same error or not!

As I have read and heard many times Riva is not best software and can make problems with Nvidia graphic cards. Specially with newest GPU. I`ve get similar problems as long as I`ve used Riva. I would like to suggest you to use nTune which can give you bigger chance for `correct` OC. This software makes my GPUs really stable after hard OC (3x280GTX 600@702MHz).
____________

As I have read and heard many times Riva is not best software and can make problems with Nvidia graphic cards. Specially with newest GPU. I`ve get similar problems as long as I`ve used Riva. I would like to suggest you to use nTune which can give you bigger chance for `correct` OC. This software makes my GPUs really stable after hard OC (3x280GTX 600@702MHz).

- people got the error before 6.3.21

- Rebirther, your card is factory overclocked (shader at 1.67 GHz instead of 1.50
GHz)

I cannot explain me why?! And after loosing many hours, why this error is not coming on start ^^

It is a temporary error on your machine. That means normally your machine is fine and the WUs are (normally) fine for others. That the error occurs after many hours of crunching tells you that probably something goes wrong during the calculations. It's not a permanent error, it's a "transient" one.

Such errors may be caused by really weird software constellations, bit-flips in the chip due to cosmic rays, hardware design faults which only occur in rare, exceptional situations (e.g. for CPUs several interrupts at the same time etc.) or by a chip which is just borderline to become unstable in the balance between clock frequency, voltage and operating temperature.

Saying "but it was stable for ..." does not really help. It could be that a few transistors are worse than the others (or have degraded more over time) and fail every 10^15 cycles or so, leading to a "mean time between failures" of days.

- And I don't think the mere presence of RivaTuner causes these errors. I mean, it's not even running all the time, is it? Also Rebirthers GPU is *old* enough (G92) to be supported properly.

I`ve get similar problems as long as I`ve used Riva.

Which problems do you mean exactly? The "unspecified launch failure"?

I would like to suggest you to use nTune which can give you bigger chance for `correct` OC

Well, RivaTuner and (I think) Everest are the only tools which can show you the real clock of your NV card, all others only show you the clock which you request from the system. The real clock is adjusted in steps. So if you can clock higher using nTune it may be that you're just below the next step, where it would become unstable. The internal clocks would be the same, but the number shown to you would be higher, hence it seems to be a higher OC.

MrS

- Where do you get that 20% error rate from?
- I also had another one of these "unspecified launch failure" errors - with app 6.45.
- Switching back to the old app is probably not feasible, since there were changes in the science code.
- Oh, and who's Nicolas?

MrS

Well, you could be right.
First WU after the driver change did run fine so far. I will crunch two, three other WUs to see if the error appears again.
If yes, I will take the shader rate down a bit.

Well, looks like I just had the first of these...http://www.gpugrid.net/result.php?resultid=140145

9600GSO (G92) with factory OC, WinXP Pro 32-bit, 6.3.21 default install. Only one so far from numerous workunits. Only change in the machine was my participation in the PrimeGrid challenge with the 2 CPU cores on this machine. Since the LLR app. from PrimeGrid is extremely CPU intensive, I wonder if this could have caused some issues?

Well, this time it took a little longer, until it appeared again for me - to be precise 4 successful WUs were between, but now I have one again.
All the time they ran with 1700 MHz, with some little breaks between when I wanted to game.
I guess I'm trying to take it down again by 100 MHz, but more isn't very senseful in my eyes, I want to make at least 1 WU per day. ;-)

Anyway, from the regularly times that it appears, I have the feeling now that it's a little hardware problem from my GPU, but nothing really spectacular and uninteresting, at least not so long until it gets worse.

Btw:
I'm happy that you guys don't purge the database and every result is still watchable. :-)
That gives a pretty good overview about the done work.
____________
Member of BOINC@Heidelberg and ATA!

After a while and some finished WUs with an uninstalled RivaTuner, installed ntune + BOINC 6.4.2 I have no more errors seen yet. So a possible error reason could be RivaTuner.

Does anyone of you also chrunch seti@home beta cuda app?

My System crash. The screen was crowded with white an black dot. Than the GPUGrid WU crashes. :( 16 WU dead. 24h no more WU. :(

Know I now Seti or GPUGrid.
____________
Constant dripping wears away the stone. :)

you're still getting many errors and it does not seem to matter much if you run 1.8 or 1.7 GHz shader clock. Did you also downclock core and memory for this test? What's the temperature of your chip while crunching?

And an interesting side note: the error happens at different lines in the force.cu file, so I really don't think it's a software issue.

And the temp while crunching lies at 70° to 75°C, a good value I think. Previous app versions did take my 9600GT up to 90 and 100 degrees.

If I were you I'd lower shader/core/mem clock by 100/50/50 MHz and let it run for at least 10 WUs. If you don't get errors during this time we could be getting somewhere.

Thanx, ETA. :-)
Thought there was a change necessary because of the coming events. ;-)

And I've just finished my newest WU.
I've lowered clock/shader/mem now as you said and downloaded another WU. Let's see how far it brings me...
____________
Member of BOINC@Heidelberg and ATA!

Well, still getting the ULF, no difference from my first test without adjusting memory and GPU clock.
Fortunately it happened very early in this WU.
I'm going down another 100/50/50 now...
____________
Member of BOINC@Heidelberg and ATA!

Wow, already 14 days ago... :-)
Looks like I found the right settings now for my 9600GT, didn't get the error again in the last 7 WUs.
Hope this thread now really can wander into the archive. ;-)
____________
Member of BOINC@Heidelberg and ATA!

And regarding "After that I shutdown BOINC, but being 6.5.0 it didn't terminate the science apps." .. if I remember correctly there has not been any feedback in the thread this was discussed. If I remember correctly I asked for the BOINC version which people were running who experienced this problem and posted that I don't see this behaviour with 6.5.0. So I'm not convinced 6.5.0 is to blamed for your current problems ;)
Just to make sure.. did you just shut down the BOINC manager or did you choose "advanced/shut down connected client"?

MrS

Try Advanced -> Shutdown running science applications. Wait a few seconds and see what happens. In my case it starts them all up again! Best if you also have Task Manager open at the same time so you can see if it does terminate them or not.

I haven't tried 6.6.0 yet. Is it only GPUgrid or does the "can't connect/start" issue also effect other projects?

The window shuts down but are still active in TaskMan (running 100% on one core).
Must stop it manually in TaskMan.