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

I have no errors with 182.50.
I said that from beginning.

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.

Profanateur wrote:

I have no errors with 182.50.
I said that from beginning.

Actually you said "And for my pbs ? with driver other than 182.5." Which I understand as "I'm not interested in my problems with 182.50, only in the problems with other drivers".

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?" Now that I know I understand you.

So if you know 182.50 works, why don't you use it?

MrS

---

Scanning for our furry friends since Jan 2002

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

Then you'll be glad to hear about this ;)

MrS

---

Scanning for our furry friends since Jan 2002

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?

I have the version 181.22 driver

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.

MarkJ:

Thanks, I will test it. :)

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

That may be me. If so, the many errors are from 2 sources: my fault and not my fault ;) Some of these WUs are a nightmare and I don't accept responsibility for that. However, I have had an issue or 3 on my end...those things I understand and accept responsibility for...;) The i7 upgrade produced a lot of initial errors, because of driver compatibility. I've produced 1 successful WU after another for long periods of time. When I start to develop issues--I try to sort it out and get it straight, but when the issues are really not on my end...there's not much that I can do except ride it out.


But I can say that I've used the 185.26 driver on 3 rigs (initially 4) for a month before all these issues arose. So, the issue is with the WUs being incompatible with the driver v. the Driver being incompatible with the WUs. In other words, any incompatibility change is in the WUs....not the driver. I cannot speak for any other version of 185.xx though...


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

HTH

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

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

p3400000-IBUCH_pYIpYVkp01_0705-4-10-RND9113

p1390000-IBUCH_pYIpYVkp01_0705-3-10-RND2928

p2200000-IBUCH_pYIpYVk52804-9-10-RND5157


I'm not sure what the quadro cards are equivalent to....8 series, 9, 200.....

Please look at the driver thread.
gdf