Everything has been running well but had 6 errors today across 3 diffrent cards (9800GT's)

1 of these:

ERROR: c:\cygwin\home\speechserver\gpumd2\src\pme\CPME_cufft.cu, line 84: cufftExecC2C (gridCalc2.2)
]]>

1 of these:

Cuda error: Kernel [shake_step_2] failed in file 'shake.cu' in line 128 : unknown error.

4 of these:

Cuda error: Kernel [PmeRealSpace_compute_forces] failed in file 'PmeRealSpace.cu' in line 172 : unknown error.

What's going on?
____________

I have a "PmeRealSpace" error too, with a 8800GT here http://www.gpugrid.net/result.php?resultid=631932

Same here, meRealSpace error, running an 8800GT. "IBUCH_KID" WU's. Do I see a pattern forming, or just a coincidence?

Error WU 634715

I have the same error on three WU. GPU is a 8800GT....

Cuda error: Kernel [fft_data_swizzle_in] failed in file 'c:\cygwin\home\speechserver\gpumd2\src\pme\CPME_cufft.cu' in line 44 : unknown error.

More errors ... :(
____________

I had three go quickly one after the other in a 40 mins period today on a 9800GTX+ errors were similar to the above:

Two were the same:
Cuda error: Kernel [shake_step_1] failed in file 'shake.cu' in line 79

The third was:
Cuda error: Kernel [PmeRealSpace_compute_forces] failed in file 'PmeRealSpace.cu' in line 172 : unknown error.

Had a replacement running for about three hours - no problems so far, see what we shall see in the morning :)

Regards
Zy

I have a thread about failed jobs as well, one machine lost 5 jobs and I thought it was machine specific but then one of my other machines got the same error, and had some that were valid but listed warnings messages that seem related to the actual errors, but this is after it finished but a real time system would be impossible not to mention useless unless you could sit and monitor your apps 24/7. they have come out with quite a few new software updates and problems can always arise, and not making it manditory to use the new version would not work either. If we post the errors and make the people who actually understand the software aware of errors I have found this site to be about the best for getting help when you do encounter any type of problem.

Same here. Its the new 7000 Credit WU´s, IBUCH_KID_shao.
Here the failed tasks: 1 and 2

I guess they dont get along well with OC:

I really think there is some issue related to "IBUCH_KID" and "KASHIF_HIVPR" WU's. I have had 4 errors today and those have also errored out for other users.

My Tasks


Error tasks:

KASHIF_HIVPR

IBUCH_KID

IBUCH_KID

IBUCH_KID



<edit>

I've turn back clocks to stock to see if that matters. I've had them OC'd for 8 months, but we'll see if the new WU's are more sensitive.

</edit>

I really think there is some issue related to "IBUCH_KID" and "KASHIF_HIVPR" WU's. I have had 4 errors today and those have also errored out for other users.

My Tasks


Error tasks:

KASHIF_HIVPR

IBUCH_KID

IBUCH_KID

IBUCH_KID



<edit>

I've turn back clocks to stock to see if that matters. I've had them OC'd for 8 months, but we'll see if the new WU's are more sensitive.

</edit>

Another one last night

ERROR: c:\cygwin\home\speechserver\gpumd2\src\pme\CPME_cufft.cu, line 84: cufftExecC2C (gridCalc2.2)

There is an issue lurking somewhere with these WUs.

For me it started when the new ones with the Amber facility came out, shortlky after the failures started.

I am trying one more - if that fails, I stop until this is resolved

Zy

There can be bad "batches" or tasks within a batch that are just plain bad. The good news such as it is, is that here at GPU Grid the tasks tend to die fairly quickly. I will note that they have just changed and are using some new tool and this may be part of the problem.

I have seen similar issues in other projects where a change in direction can lead to significant issues with tasks failing. Rosetta when they went in the direction of starting up the effort on Mini-Rosetta caused me to leave the project for a long time as far as major support because so many tasks failed. Now they have most of the bugs out and I am back again.

Keep reporting the bad tasks and I am sure they will figure it out ...

I got a bunch of errors also and was wondering if we add system specs (including driver version) wold it help narrow down were the real issue is?

i7-920 HT, 4 GHz on P6T
Corsair Dominator 1600 2Gx3
EVGA GTX 295 (626/1496/1036) 185.81
Corsair TX750W, WD Caviar Black 1TB
Cool Master HAF 932
Xigmatek Dark Knight-S1283V
BOINC 6.6.20 for WCG + GPUGrid 24/7/365

Steve

On the new IBUCH_KID batch errors...
They don't fail completely, but the error rate is apparently higher.

We are stopping them for safety at the moment.

thanks for your patience,
ignasi

Yes Steve WCG,

Posting the specs (driver ver, boinc ver, gpu, gpu overclock, os), help to narrow down where your issue may be.

But 'un-hiding' your computers so the MODS can look at your output files also helps (they may ask for this sometimes), when you have a problem. That and enabling 'debugging' if you have a pesky problem...
____________


Consciousness: That annoying time between naps......

Experience is a wonderful thing: it enables you to recognize a mistake every time you repeat it.

Specs including versions are in my sig. I will also try to provide more specifics when I post about errors but it sounds like this round is semi-global so I doubt they need any more info at this time. If mods want details of my logs all they need to do is ask and I will "unhide". Interesting way to phrase that ... I prefer to think of it as "Public" or "Private" and in general I like to keep "Private" as much is possible.
____________
Thanks - Steve

Specs including versions are in my sig. I will also try to provide more specifics when I post about errors but it sounds like this round is semi-global so I doubt they need any more info at this time. If mods want details of my logs all they need to do is ask and I will "unhide". Interesting way to phrase that ... I prefer to think of it as "Public" or "Private" and in general I like to keep "Private" as much is possible.

Keep reporting the bad tasks and I am sure they will figure it out ...

My first 2 errors ever AFAIK, the 1st a 76-KASHIF_HIVPR WU and the 2nd one of the infamous 76-IBUCH_KID WUs.
Two different cards, both 9600 GSO. Notice a similarity in the error messages?:

<core_client_version>6.6.24</core_client_version>
<![CDATA[
<message>
- exit code 98 (0x62)
</message>
<stderr_txt>
# Using CUDA device 0
# Device 0: "GeForce 9600 GSO"
# Clock rate: 1674000 kilohertz
# Total amount of global memory: 402325504 bytes
# Number of multiprocessors: 12
# Number of cores: 96
# Amber: readparm : Reading parm file parameters
# PARM file in AMBER 7 format
# Encounter 10-12 H-bond term
WARNING: parameters.cu, line 568: Found zero 10-12 H-bond term.
WARNING: parameters.cu, line 568: Found zero 10-12 H-bond term.
MDIO ERROR: cannot open file "restart.coor"
ERROR: c:\cygwin\home\speechserver\gpumd2\src\pme\CPME_cufft.cu, line 50: cufftExecC2C (gridcalc2.1)
called boinc_finish

</stderr_txt>
]]>



<core_client_version>6.6.20</core_client_version>
<![CDATA[
<message>
- exit code 98 (0x62)
</message>
<stderr_txt>
# Using CUDA device 0
# Device 0: "GeForce 9600 GSO"
# Clock rate: 1458000 kilohertz
# Total amount of global memory: 804978688 bytes
# Number of multiprocessors: 12
# Number of cores: 96
# Amber: readparm : Reading parm file parameters
# PARM file in AMBER 7 format
# Encounter 10-12 H-bond term
WARNING: parameters.cu, line 568: Found zero 10-12 H-bond term.
WARNING: parameters.cu, line 568: Found zero 10-12 H-bond term.
MDIO ERROR: cannot open file "restart.coor"
ERROR: c:\cy
</stderr_txt>
]]>

Got one through ok, then the next went bang after 30 mins.

Successful one was:
http://www.gpugrid.net/result.php?resultid=636960 A GIANNI

The one that failed this time - a KASHIF_HIVPR
http://www.gpugrid.net/result.php?resultid=639025
ERROR: c:\cygwin\home\speechserver\gpumd2\src\pme\CPME_cufft.cu, line 104: cufftExecC2R (gridcalc3)

With this one I was at the PC when it went. There was a system warning popup message, didnt get it word for word, only saw a flash as it disappeared , " something something could not be contacted, video driver restarted", dont hang your hat off that word for word, but essentially it looks as though the Video Driver lost connection, and the system auto restarted the video driver, when it did that, instant computation error.

I will ferret in the log files, I have the PC logged to death, hopefully I can dig something up about it.

Two more downloaded, A GIANNI and a KASHIF, I suspended the GIANNI, and will try another KASHIF, see what happens.

Regards
Zy

The KASHIF lasted 37 mins and went bang. A GIANNI is now running
The failed KASHIF: http://www.gpugrid.net/result.php?resultid=640997
Error was: Cuda error: Kernel [fft_data_swizzle_out] failed in file 'c:\cygwin\home\speechserver\gpumd2\src\pme\CPME_cufft.cu' in line 94 : unknown error.

(Not seen a "swizzle_out" error before)

Started this one - a GIANNI - and on past performance it will probably go through ok:
http://www.gpugrid.net/result.php?resultid=641393

[Edit] Any debuging switch or log file - whatever - that I can enable this end that will help, please let me know and I will. If you want me to run a series of suspect ones (etc) let me know how, I will [/Edit]

Regards
Zy

I have gotten another error of a 2-KASHIF_HIVPR-WU (result). The error appeared after more than 16 hours of computation on a 8800GT. Now I have three errors in a row. In my opinion is this unacceptable!!!!!!

boinc 6.6.24 x64

By KoDAkthebest
and some ERRORS (
http://www.gpugrid.net/results.php?hostid=31714
____________

We are digging into these problems.

thanks,
ignasi

Hi Ignasi

I had a look at all my computation error ones this morning now that most have finally gone through. All the KASHIF one's when crunched by a 9800GTX+ or below go bang. If the wingman is a 260 inclusive and above, they go through. I am aware is a crude deduction on my part as I have a very limited overview of the problems, however it does now seem pretty solid that KASHIF's dont through on cards rated 9800GTX+ and below.

If thats starting to be the case, do you still want the cards of 9800GTX+ and below to run the KASHIF's? If you do, fine, I just hate running ones that will go bang as it only delays their crunching by cards that can do it.

If you dont, I can just abort a KASHIF if I spot one coming through.

Regards
Zy

Additional to my post at 9444 above.

Just remembered, and its only a part of it - its real annoying that I only got a flash of it as it went away - the error message referred to a file "nv???????" it maybe a DLL reference, cant remember. NV is probably no stunning revelation, but there it is for what its worth. Whatever the final full name, the error message claimed it had "stopped", and the system had restarted it. Instatantly I had the WU go bang. All cpu based models for other projects I run, have been unaffected by all this whether during normal running or when the KASHIFs go bang.

I seem to remember another post about a week ago, where there was a suspicion voiced about the memory size possibly being too small for these. ie at present maybe it needs 1GB cards, and goes bang on 512mb cards?

Regards
Zy

Just had another KASHIF go bang, it lasted 57 mins

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

Error message:
Cuda error: Kernel [fft_data_swizzle_out] failed in file 'c:\cygwin\home\speechserver\gpumd2\src\pme\CPME_cufft.cu' in line 94 : unknown error.

swizzle_out is starting to be a common one for me.

Got to go out now and meet a Client, wont be back until around 4pm UTC.

Regards
Zy

I have had random failures on all my cards[8800gt/9600gso/9800gt/gts250] except the gtx260-192/216.

Some fail in a short period others linger much longer.
____________
mike

Yup, similar issue here.

Yesterday got a WU that got stuck at 18% on my 8800GT. No error messages though, the Boinc manager thought the process was still running but remained for at least 12 hours at the same progress...

Cancelled the WU manually and started another one 18 hours ago. Usually WU's tend to take little less than 13 hours, and the current one hasn't been reporting yet (nor a new WU got uploaded, I keep my queue very short...). Propbably this evening I will see a similar issue.

See this thread also. I had hanging WUs using 6.6.17 and installing 6.6.23 didn't help. Installing Nvidia driver 185.85 fixed the hanging problem but haven't had a WU process successfully since (though may not be a driver issue - currently running a GIANNI WU and is at 67% and looking OK)

I am right to say that all the problems are related to older cards, like 8800,9800 and so on?
Did anyone experience repeated failures on those workunits with a 260,275,295 or 285?

gdf

I have had random failures on all my cards[8800gt/9600gso/9800gt/gts250] except the gtx260-192/216.

I hate to be a wet blanket.

But my 9800GT has five (5) total successful runs on just page one of my task list so it is NOT the card unless related to memory as this card has 1M VRAM ...

I am using driver 182.50, so it may be THAT ... WIn XP Pro, 32-bit is the other variant that may be an issue. BOINC Version 6.5.0 ...

The 6.6x versions did have some scheduler problems from something in the teens at least to 6.6.22 ... 6.6.23 and later seems to have cured that issue.

Above I mentioned a file that was "stopped" and restarted at the same moment the WU went bang. I found the error message for it. I have no idea whether it means anything to the current problem, or what it means in itself ...... however, posted for completeness as it did happen at the exact moment the WU went bang. "nvlddmkm" was what I was struggling to remember on the system error message at the time the WU went bang.

The error message reads:

"The description for Event ID 4101 from source Display cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

nvlddmkm "

It was located in:
Event Viewer/Custom Views/Administrative Events
Source: display.

At the time it said it was "restarted" presumably referring to nvlddmkm - whatever that is :)

Regards
Zy

I am right to say that all the problems are related to older cards, like 8800,9800 and so on?
Did anyone experience repeated failures on those workunits with a 260,275,295 or 285?

gdf

I have 7 9800GT's and one 8800GT. All have experienced failures. I'm on 6.6.20 and 185.85. I'm shutting them down until this problem is fixed. Good Luck!

I have had my fair share of those also and installed all latest drivers Win7 185.85 which include cuda 2.2 on this machine and boinc 6.6.28.
To my surprise i see now in boinc that my 9600 GT seems only be able todo cuda 1.0 instructions.
So maybe the errors created by these workunits are related to instruction which only can be performed by the newest 2x5 models.
Since non of them seem to have much errors on these units
But somehow i have had less problems with my machine since the latest drivers am installed, it runs kinda rock solid (only BF2 and gameguard games are an issue)
BUT i'll remind you guys everything i run is BETA so problems can occur.
That it runs almost without a problem on my machine is no garantee it will on yours.

I guess if you have a 2X5 card you probably will see a gain in processing speed if some of the cuda 2.2 intructions can or/and are implemented

Some positives for comparison as the KASHIFs are going bang with me, I've left the hardware/software setup alone so there is fair comparison.

GIANNIs seem to run fine. I am 7hrs into a TONI_HIVPR, so touch wood that seems like it will go through, will finish in about 5/6 hours. I have a IBUCH_HIVPR lined up as the next to go.

Regards
Zy

I have aborted all:

KASHIF_HIVPR
and
IBUCH_KID

and will now continue to do so.

I have 5x 8800GS and 1x 8800GT--those WUs do not complete on my rigs and most of them hang. Yesterday I completed ONE WU instead of 9-11. 5K ppd instead of 50Kppd.

Was on 6.6.17, 3 rigs 185.26, 1 rig 182.50

As of last night all rigs are: 6.6.28 and 3x 185.26, 1x 185.85--seems to have helped some.

This is an "across the farm" thing for me now. Problems initially started on the dual gpu rigs, but now it's across the board....

My rigs are not hidden. The Phunam-PC is a new setup--the intial errors are from setup, OCing, etc. I understand those. The new ones are part of this mess.

Hoping it gets sorted out soon....

EDIT: I have kept 1 KASHIF_HIVPR that appears to be running ok on a single Gpu rig. However, 1st sign of trouble and it's history.....

Likewise here, failures on

KASHIF_HIVPR
and
IBUCH_KID

Two different machines. One with 32 bit Vista, 8800GT (O/C), client 6.6.20 & 185.86 driver. The other with 64 bit Vista, 9800 GX2 (Not O/C), client 6.6.20 & 182.50 driver. I have now updated both drivers to 185.85, which is latest release.

Ahh the "never ending wu" bug. What version of BOINC are you running? It seems to have been fixed in 6.6.23 onwards.

Well again had a unit error out of 13 hours of work, and looks like the big gun machines run them all fine.
I can't go on like this i lost hundreds of hours of time and money for nothing.
For the time being i am also shutting down the gpugrid till this issue is solved.

I am aware that there is hard work going on re finding the cause/fix. If its possible that someone could timeout for 2 mins to advise us all whether you still want the KASHIFs run by lower based cards, I suspect it would help enourmously as we could then abort to leave them to the big guns knowing its not going to cause issues in the bug-finding, and we carry on with the other WUs.

At present it seems lots are shutting down from doing anything in the absense of any advice, understandably, but the other WUs seem ok.

Just a gentle suggestion ...

Regards
Zy

The last KASHIF_HIVPR did in fact error out.....No more for me. I'm just going to have to check my rigs 1-2x/day and send them back....

I am aware that there is hard work going on re finding the cause/fix. If its possible that someone could timeout for 2 mins to advise us all whether you still want the KASHIFs run by lower based cards, I suspect it would help enourmously as we could then abort to leave them to the big guns knowing its not going to cause issues in the bug-finding, and we carry on with the other WUs.

At present it seems lots are shutting down from doing anything in the absense of any advice, understandably, but the other WUs seem ok.

Just a gentle suggestion ...

Regards
Zy

Nothing will likely be done until sometime Monday, I am also at No New Work until problem is resolved.
____________
mike

I have a big problem with my new asus 260:

hostid=35303

I downgraded all drivers, and now waiting to get more task.
"reached daily quota of 4 results" heh ;),
Any suggestion? Seti gpus working fine.......
____________
"Silakka"
Hello from Turku > Åbo.

Sadly yes the famous units which we discussing all over the forum

I have a big problem with my new asus 260:

hostid=35303

I downgraded all drivers, and now waiting to get more task.
"reached daily quota of 4 results" heh ;),
Any suggestion? Seti gpus working fine.......

I am right to say that all the problems are related to older cards, like 8800,9800 and so on?
Did anyone experience repeated failures on those workunits with a 260,275,295 or 285?

gdf

I am on 6.4.5 and use either 177.82 or 180.22 on Ubuntu 64.

I have had many failures on all cards Except my 260's[192/216]
____________
mike

Well, I just had a crash on the i7 67-KASHIF_HIVPR_n1_for_ba3-2-100-RND8737, this is a task that died at least twice before.

The thing is, I was playing a game at the time. Low intensity turn based strategy game. But, I cannot say if that had any effect. THe game seemed to die and the graphics driver crashed. That said, the other tasks in progress seemed to stay Ok ...

More interesting is that there were three different errors ...

Of course, the task was run on three different class cards.

And I am running BOINC 6.6.28 on that machine ... still 182.50 drivers though.

I have been having a closer look at my errors , and a few from others. This bares some checking, but it appears on the face of it that the crashed ones do have a common element "signal 11". The "h-bond" message is a red herring to this. as it refers to the "Amber" processes (is that right ?), no matter the detail, it was cleared up in another thread as a non issue, just a text message re the internal processes in the WU, not its validity as a successful WU.

"Signal 11" does appear vertually every time from the ones I looked at. I am aware signal 11 is an issue way down in the Communication Layer - which in itself rings a bell considering the way current problems effects some cards and not others - some operating systems not others - but I have no idea of where to take that logic further, or even if indeed it has validity, I dont have that level of knowledge. Signal 11 I am aware can appear for many many reasons, and can be difficult to work out what the reason is, but if its the case this time, at least its the start down the right road.

Regards
Zy

I have a big problem with my new asus 260:

hostid=35303

I downgraded all drivers, and now waiting to get more task.
"reached daily quota of 4 results" heh ;),
Any suggestion? Seti gpus working fine.......

The ones crashing on that machine are not the suspect WUs that they have now stopped issuing, those crashing on that machine usually run fine. He also has a 260 which is outside the problems, its the lower cards that did have issues in the past. Something else lurketh. No idea what personally, over to the Gurus for that.

Regards
Zy

And for my pbs ? with driver other than 182.5.

Success on 52-KASHIF_HIVPR_mon_ba3-7-100-RND3244_0. 64 bit Vista, 9800 GX2 (Not O/C), client 6.6.20 & 182.85 driver.

pbs =problems=failure.
sorry but I'm french.

I'm new here.

Have errors with this:

75-IBUCH_HIVPR_mon_ba8-4-100-RND5234 id: 451357

100-KASHIF_HIVPR_n1_for_ba4-4-100-RND3172 id: 448737

Shuttle XPC
Vista Enterprise 64 bit 2 Gb ram
AMD Opteron 2.4 GHz model 180
Geeforce 9400GT 1 Gb ram newly bought
Boinc 6.6.20

ComputerID: 35365

The Boincwoman

xp/32 + [email protected] + BOINC6.4.5 cannot survive!

Errors todays :

10/05/2009 10:53:19 GPUGRID Output file p1760000-IBUCH_pYIpYVkp01_0705-4-10-RND5135_0_1 for task p1760000-IBUCH_pYIpYVkp01_0705-4-10-RND5135_0 absent
10/05/2009 16:56:28 GPUGRID Output file p2750000-IBUCH_pYIpYVkp01_0705-4-10-RND5064_1_1 for task p2750000-IBUCH_pYIpYVkp01_0705-4-10-RND5064_1 absent

ETA:

I aborted them because WUs' progress has not advanced in a long time(at least more than 1 hour). The situation has not changed even I rebooted my computer.

After 2 WUs, I deem if the last number in the task name more than zero, it should be a bad WU.

Details in http://www.gpugrid.net/forum_thread.php?id=1041

My English is not good enough, I hope you can understand what I mean.

:)

ETA,

please tell me how to avoid/recover the case that WU's progress freezes.

You can see not only me who met this case. Before I abandoned them, other GPUGriders have done the same operation.

Hi
I have another error(Kernel [nb_k] failed in file 'nb.cu' in line 202 : unknown error) on a new type of WU http://www.gpugrid.net/result.php?resultid=645509

Have the "EVIL" work units been disabled or deleted?

I have stopped work on 8[250's and below] of my cards. The two 260s are doing OK.
____________
mike

Yes they stopped issuing the suspect ones on Saturday, its not all KASHIF's that are suspect, there are several types of KASHIF WUs, it was only one particular type of KASHIF WU that was giving grief.

See http://www.gpugrid.net/forum_thread.php?id=1034&nowrap=true#9506

Regards
Zy

Profanateur,

your problem is not related to what is being discussed here. Very many of your WUs error, this is different from the "KASHIF_HIVPR" and "IBUCH_KID" issue. You actually completed some, so your software should be fine.

However, you are running a very new driver and two overclocked cards, which are very different. All of these or their combination could lead to problems. I suggest you start a new thread (instead of posting a little in different threads), write down your current config (software versions, clocks, GPU temperatures) and then change some parameters, document the changes and see if it helps. By that I mean

- run only 1 of the cards to see if one is broken
- reduce all clocks to standard values
- run other stability tests
- try well-tested drivers like 182.50 or 182.08
- maybe more

If you do that we (or you yourself ;) should be able to get you going.

Regards,
MrS

My solution on the 260 was Boinc 6.4.7 and driver 178.28, now working as a train.
Slow but getting faster, like a first mosquito this summer today in Turku Finland.

Thomas Bymark
____________
"Silakka"
Hello from Turku > Åbo.

'cause I want last release to have Occlusion ambiant in game.

I had 2 fail on my 8800GT, one on 5th May, and one right now. My screen actually went black for a few seconds and I briefly saw windows error reporting in process explorer! Driver version 182.50 I believe. Card was stock clocks at the time (fine).

5th May one was 159-IBUCH_KID_shao_ba1-0-100-RND5509_1:

and the one just now was 53-KASHIF_HIVPR_n1_for_ba1-2-100-RND0722_1:
which had the swizzle error others have described.

Hi
I have another error(Kernel [nb_k] failed in file 'nb.cu' in line 202 : unknown error) on a new type of WU http://www.gpugrid.net/result.php?resultid=645509

What driver version are you using?

ETA,

please tell me how to avoid/recover the case that WU's progress freezes.

You can see not only me who met this case. Before I abandoned them, other GPUGriders have done the same operation.

@refla:

I would suggest you switch to BOINC 6.6.23.

Your driver version is not shown, but as ETA has said above I would suggest 182.50 drivers as they seem to be reliable.

Well, no. Actually when I read that post I thought something like "Isn't that the guy with many errors and the exotic setup? What does he want to say?"


MrS

Also, IBUCH_pYIpYVkp01_0705-4-10 seems to be another WU with issues, but I think that is already known....

HTH

Just had a KASHIF go bang. Its appears to be the old hassles on the face of it - just highlighting it for the record due to recent hassles with some KASHIFs.

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

It had been running for 11hrs15 so was different from the others I had go - they were early, this was late in processing, almost finished when it went. "One of those things" I suspect.

The network connection was down at the time, a major BT Network fault that had been extant for nearly 24 hrs, the latter should have had no affect, just mentioned for completeness as it was down when the WU went bang.

Regards
Zy

Also, IBUCH_pYIpYVkp01_0705-4-10 seems to be another WU with issues, but I think that is already known....

HTH

This runs fine actually. Are you referring to any error in particular?

ignasi