I just noted that I had a task crash with an exception. No idea why ... I don't suppose it is terribly important ... it happened nearly a week ago ... but I just noticed it ...

And another:

ERROR: tclutil.cu, line 23: get_Dvec() not a 3 vector

Yes, thanks.
That was already fixed.

ignasi

Yes, thanks.
That was already fixed.

Way cool! Thanks ...

I just was not sure I, or others, reported it ...

Like the problems over at Rosetta ... though they too seem to (finally) be getting a handle on the problems ...

New task crash with exception Reason: Breakpoint Encountered (0x80000003) at address 0x7C90120E

New task crash with exception Reason: Breakpoint Encountered (0x80000003) at address 0x7C90120E

I received two of these this morning also.

---

And another one

A lot of wasted crunching. :(

---

Though they do not always comment, the project is pretty good about tracking crashing series. I have one canceled result which I would bet is from the bad series.

Anyway, one out of several hundred is not that bad ...

My WU's keep crashing easily. Everytime I need my videocard for playing, I select "suspend BOINC for one hour". If I'm in the middle of game when the BOINC starts, the WU fails immediately. Anyone else having the same problem? BOINC version is 6.5.0 and is otherwise working great.

My WU's keep crashing easily. Everytime I need my videocard for playing, I select "suspend BOINC for one hour". If I'm in the middle of game when the BOINC starts, the WU fails immediately. Anyone else having the same problem? BOINC version is 6.5.0 and is otherwise working great.

Yes, others have reported this problem.

You would be better served to use the hard suspend on the project instead.

Promised in later versions will be better suspend and use detection. But, GPU computing in the general computing universe like BOINC is only a few months old ... expect difficulties ... :)

My WU's keep crashing easily. Everytime I need my videocard for playing, I select "suspend BOINC for one hour". If I'm in the middle of game when the BOINC starts, the WU fails immediately. Anyone else having the same problem? BOINC version is 6.5.0 and is otherwise working great.

Yes, others have reported this problem.

You would be better served to use the hard suspend on the project instead.

Promised in later versions will be better suspend and use detection. But, GPU computing in the general computing universe like BOINC is only a few months old ... expect difficulties ... :)

Thanks Paul, just wanted to verify if someone had found a solution for this already. There is always the possibility that something is wrong with OC'ed system, forceware or BOINC version :)

---

An alternative, that I've started using recently is a file called cc_config.xml, it lives in the the main data directory (normally BOINC_Data nowadays). If the file is not there create one. Edit it using notepad or similar basic editor NOT Word! The contents need to be like:

<cc_config>
<options>
<exclusive_app>mygame1.exe</exclusive_app>
<exclusive_app>mygame2.exe</exclusive_app>
<exclusive_app>mygame3.exe</exclusive_app>
</options>
</cc_config>

Change "mygame1" "mygame2" "mygame3" to whatever you are playing - no folders or drive letters needed, just the application name (as you would see it in Windows task manager). Add or delete lines as needed. Save the file and go into Boinc manager select "Advanced" and "Read config file".

The advantage of this method is it re-starts Boinc processing a few seconds after the game ends and you don't have to remember to do that yourself!

More details here.

Phoneman1