This is the second time this has happened the first time it happened was in December this time the WU lasted until it reached 1840.
I was using BOINC 4.06 then and am now using BOINC 4.19 I run Seti and climate prediction.
When the WU crashes the screen flickers and the work unit itself vanishes off the screen and it seems to reset the BOINC client window. All the information on the Messages tab vanishes from the computer. The client looks just like I had restarted the client, with everything on the Messages tab looking just like a new startup. And then a new WU is downloaded.
This time when it crashed nothing else on the computer was running and BOINC hadn't switched programs for at least four hours (Seti had ran out of work). I can't figure out what is causing these crashes.
Does anyone have any ideas on how to prevent this from happening again?

---

I haven't found an explanation of the exit status -1073741502 (0xc0000142).

Do you have a backup of the BOINC directory from before the crash? If so you may be able to have another go at continuing the model.

---

Visit BOINC WIKI for help

And join BOINC Synergy for all the news in one place.

Welcome to the forum, Eve.

I'm at a bit of a loss with this one. The symptoms are strange, and the error code is weird:
exit code -1073741502 (0xc0000142)

Have to start somewhere though.

So, there are 2 text files, (to start with, 4 later), in the BOINC folder which contain the messages you get:

stdout for the messages you see in the gui under Messages, and
stderr for the error messages.

When these get re-written, (when you re-start BOINC), the .txt is renamed to .old, and new .txt files created.
You should still have these, so look there, especially the error file(s).
If there is something which may help, copy and paste them to this thread, and someone will be 'along' to have a look.

Les

edit
Missed it by that much!

> stdout for the messages you see in the gui under Messages, and
> stderr for the error messages.
>
> If there is something which may help, copy and paste them to this thread, and
> someone will be 'along' to have a look.

I found the file you requested but my computer can't "read" the file for me.
That is it won't show the file. So I believe that I'm out of luck, unless someone can tell me where a program can be found that would allow me to see this type of file.

BTW the file wasn't backed up..

---

They are .txt files so you should be able to read them with notepad or whatever.
If you can't, I'd guess they're empty.

---

Forum search Site search

Eve,
If they are empty, then, when you put the mouse pointer over one, the file size should be 0.
Double-clicking on one should open it in whatever program you have selected to open all text files.
My computer is set to use NotePad.

edit
I just remembered how to 'associate' programs with files. (So many problems, so little time.)
If you double-click on a file and the computer doesn't know which program to use to open it, you get a window with suggestions.
Choose Notepad.
There should also be an option somewhere to ALWAYS use this program with this type of file.

Les

Eve,
Another user now has a problem which returns this long error code. In his case, 5 times.

We may have to discuss this a bit.

Watch this space.

Les

Les

I finaly got notepad to open the files and they didn't contain anything older than the 23rd. Not any help at all.



I sure will keep an eye on this thread.

---

Good news and bad news.
The good news is that another user has found a reference to this error code.
The bad news is that it's a Windows problem, so it's up to you to fix.

The thread is <a href="http://climateapps2.oucs.ox.ac.uk/cpdnboinc/forum_thread.php?id=2028"> here</a>, and to make it easy, the Microsoft KDB item is <a href="http://aumha.org/win5/kbestop.php"> here</a>.

The relevant part is at the end.
Go right to the bottom, and it should then be at the top of the screen, or a little above that.

If you have been running Easy CD Creator, click on that link and see what it says. I didn't bother.

Perhaps suspending BOINC before running it will stop it happening, but you may have something wrong with Windows.
The 1st screenfull of text at the top of the info page may help.
Good luck.

Les