I\'m running Boinc Client 5.2.13 (Windows), and every Workunit finishes with this error. I\'am running SETI besides Climateprediction. What is this

Hi,


der erste Versuch waere, das komplette BOINC-Verzeichnis vom Virenscan auszuschliessen. Es gibt bekannte Inkompatibilitaeten zwischen verschiedenen Virenscannern und BOINC, besonders bei ClimatePrediction.

Eine Empfehlung in dem Zusammenhang, die ich an anderer Stelle auch \'mal gesehen habe, war das Aktualisieren des Grafiktreibers.

Ich wuerde aber erstmal den Virenscanner probieren.


Viel Glueck
Volker

hello

first of all, thank You for answering my question.

second, I don\'t speak German, so I used Google\'s translate tool to try to understand what You where telling me :)

If I\'m right, You\'re saying that virus scanner can cause error to BOINC projects, especially climateprediction.

however, for now, it seems I have found the cause of problem. It looks like running ANYTHING using Microsoft\'s DirectDraw routine crashes climateprediction. Weird, huh?

currently, my climateprediction workunit is at 20.74% (that\'s about 110 hours of CPU time), without crash, still running overclocked machine, still running all my regular programs in foreground, and BOINC as a background, low-priority program, just avoiding any DirectDraw or Direct3D games, programs, screensavers etc. Anti-virus is active, it seems that it is not a problem in my case.

I hope that this is it, and hope that this will help the others who might have the same problem.

Best regards,
Nikola

---

Whatever the reason for the crash(es), they leave the WU \"unrecoverable\", unless the user does a manual backup of the entire BOINC folder.

I do a full backup about every 10% of the WU, so *if* something happens, I can always restart from the last backup point. (You *must* suspend the project work and exit BOINC manager before starting the backup).

@Nikola: The thread header says it has been started by Erich Anzböck, that\'s why I replied in german.


Just yesterday I got the idea, that all crashes I lately had have been caused by DirectX, I used the \"old\" board for it.

The problems must have started with one of the later CPDN versions, the old HADSM3 did fine on this computer.

I hope one of the developers gets the time to look at it sometimes.

@Nikola: The thread header says it has been started by Erich Anzböck, that\'s why I replied in german..

Yes, I see now... but don\'t know why :) maybe servers went crazy these past few days? ;)

Just yesterday I got the idea, that all crashes I lately had have been caused
by DirectX, I used the \"old\" board for it.

that definitely looks like DirectX. today my computer ran climateprediction for another 4 hours, and still everything works fine. just avoiding DirectDraw. :) i allways close Boinc before running D3D, so have no idea how D3D impacts on Boinc.

The problems must have started with one of the later CPDN versions, the old HADSM3 did fine on this computer.

I have this problem for quite some time, but I didn\'t look much around :) But I think I had the same problem with the old versions, too.

anyway, thanx for help.

best regards,
Nikola

---

Whatever the reason for the crash(es), they leave the WU \"unrecoverable\", unless the user does a manual backup of the entire BOINC folder.

I do a full backup about every 10% of the WU, so *if* something happens, I can always restart from the last backup point. (You *must* suspend the project work and exit BOINC manager before starting the backup).

I started using this method few weeks ago, when I realized that my ClimatePrediction ran into problems. With the difference of doing full backup every day, because I had errors allmost every day. now, when avoiding running DirectX (direct draw to be precise), everything works fine, currently at about 22% of WU, without error.

but still, thanx for the tip. :)

best regards,
Nikola

Hi,


der erste Versuch waere, das komplette BOINC-Verzeichnis vom Virenscan auszuschliessen. Es gibt bekannte Inkompatibilitaeten zwischen verschiedenen Virenscannern und BOINC, besonders bei ClimatePrediction.

Eine Empfehlung in dem Zusammenhang, die ich an anderer Stelle auch \'mal gesehen habe, war das Aktualisieren des Grafiktreibers.

Ich wuerde aber erstmal den Virenscanner probieren.


Viel Glueck
Volker

---

Hi,


der erste Versuch waere, das komplette BOINC-Verzeichnis vom Virenscan auszuschliessen. Es gibt bekannte Inkompatibilitaeten zwischen verschiedenen Virenscannern und BOINC, besonders bei ClimatePrediction.

Eine Empfehlung in dem Zusammenhang, die ich an anderer Stelle auch \'mal gesehen habe, war das Aktualisieren des Grafiktreibers.

Ich wuerde aber erstmal den Virenscanner probieren.


Viel Glueck
Volker

Danke Volker,

ich werde das mal probieren.