I'm seeing Unhandled Exceptions with 4.45. The message box says simply this:

An unhandled exception occurred. Press "abort" to terminate the program, "retry" to exit the program normally and "ignore" to try to continue.

It seems to be happening about once a day to one of my 6 computers, not always the same one each time. I have always chosen "retry", and then the Boinc CC exits. I start it up again, and it continues normally.

Here's what's in stderrgui.txt on the machine I'm currently using:

***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x004190C9 read attempt to address 0x00000000

1: 05/14/05 17:24:05



***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x004191E9 read attempt to address 0x00000000

1: 06/06/05 18:39:11



***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x004191E9 read attempt to address 0x00000000

1: 06/07/05 06:59:42



***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x004190B9 read attempt to address 0x00000000

1: 06/17/05 07:13:29

Actually, looking at these dates, only the last one could be from 4.45, so it's been going on for a bunch of versions. I'll have to check the other machines.

---

An unhandled exception occurred. Press "abort" to terminate the program, "retry" to exit the program normally and "ignore" to try to continue.

Hardware fault?

Does that system check out ok with Memtest86+ and GIMPS mprime95 torture test?

Good luck,
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

It is more likely that under some circumstances a null pointer is used.

---

BOINC WIKI

It is more likely that under some circumstances a null pointer is used.

There was a note in one of the mailing lists that there is a possibility that this may occur. I think that the fix will be in the 4.46 version.

Now, if I could just get a 4.45 version of the Macintosh client ...

---

It is more likely that under some circumstances a null pointer is used.

There was a note in one of the mailing lists that there is a possibility that this may occur. I think that the fix will be in the 4.46 version.

Now, if I could just get a 4.45 version of the Macintosh client ...

You would probably get it the same time I geta 4.45 Solaris Client

---

I'd rather speak my mind because it hurts too much to bite my tongue.

American Spirit BBQ Proudly Serving those that courageously defend freedom.

I'm getting this message on a regular basis with 4.45 (although I have had it with other versions as well).

---

Using the information from this page:
http://boinc.berkeley.edu/debug_win.php

Could somebody install the symbol files so the next time you experience the crash, we can track it down and fix it.

Thanks in advance.

---

----- Rom
BOINC Development Team, U.C. Berkeley
My Blog

I was getting them also. What I did and it seems to have fixed the problem, was to clean my registry. After installing several versions I figured there was something in the registry that was left over that it just didn't like. I ran RegSeeker twice and made sure everything was removed that wasn't needed.

---

http://www.teamstarfire.org/

OK, got 'em. I'll stick these in each machine, so next time it happens, we'll be ready!

---

Just got another one. Here's what was in stderrgui.txt:

***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x004190B9 read attempt to address 0x00000000

1: 06/19/05 14:09:14
1: c:\\boincsrc\\main\\boinc_public\\clientgui\\mainframe.cpp(567) +0 bytes (CMainFrame::SaveState)

It looked like it was just starting up a Predictor WU.

---

Here's another I just got, waking up one of my machines at work:

***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x004190B9 read attempt to address 0x00000000

1: 06/20/05 10:04:58

Unfortunately, it happened before I could put the symbols in. It appears from the timestamp that it was the act of waking it up from a "blank screen" condition that triggered it.

I now have symbols installed on all my machines, so I'll be able to catch the next one no matter where it happens.

Edit- looks like the same address as the one from home (below).

---

Here's another one I just got:

***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x004190B9 read attempt to address 0x00000000

1: 06/23/05 07:16:40
1: c:\\boincsrc\\main\\boinc_public\\clientgui\\mainframe.cpp(567) +0 bytes (CMainFrame::SaveState)

By the timestamp, it crashed when I was waking up the machine from a "blank screen" state. This is a third machine. So far, it seems like the ones that crash are either Dual processor or HT. I will check the logs on the non DP machines at work.

---

Here's a revealing clue: the three non-HT machines I have at work have NO entries in the stderrgui.txt file. Individual apps have crashed, but not the GUI. This makes me think there is something not thread-safe in the GUI, since it is only crashing on HT or DP machines.

---

Here's a revealing clue: the three non-HT machines I have at work have NO entries in the stderrgui.txt file. Individual apps have crashed, but not the GUI. This makes me think there is something not thread-safe in the GUI, since it is only crashing on HT or DP machines.

Can you disable the hyperthreading for a few days on one of your machines to see if thats true?

Here's a revealing clue: the three non-HT machines I have at work have NO entries in the stderrgui.txt file. Individual apps have crashed, but not the GUI. This makes me think there is something not thread-safe in the GUI, since it is only crashing on HT or DP machines.

Can you disable the hyperthreading for a few days on one of your machines to see if thats true?

Yes, I can do that over the weekend. The machine here at work is HT, the two at home are true dual processor, so not on those.
-------
OK, HT is now off, we'll see what happens. I would expect to see no exceptions here while it is off.

---

Identical error has happened on my P4 3.2 HT, XP SP2.

***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x004190B9 read attempt to address 0x00000000

1: 06/24/05 07:44:03
1: c:\\boincsrc\\main\\boinc_public\\clientgui\\mainframe.cpp(567) +0 bytes (CMainFrame::SaveState)

[eidt]
and also at time 24//06//05 6.28am (an hour before the exception error) I had the following problems in the stderr.txt file from the slot directories for seti 4.00 and 4.11

No heartbeat from core client for 31.000000 sec - exiting

don't know if they are related but it may help

[/edit]

Identical error has happened on my P4 3.2 HT, XP SP2.

***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x004190B9 read attempt to address 0x00000000

1: 06/24/05 07:44:03
1: c:\boincsrc\main\boinc_public\clientgui\mainframe.cpp(567) +0 bytes (CMainFrame::SaveState)

[eidt]
and also at time 24//06//05 6.28am (an hour before the exception error) I had the following problems in the stderr.txt file from the slot directories for seti 4.00 and 4.11

No heartbeat from core client for 31.000000 sec - exiting

don't know if they are related but it may help

[/edit]

Could it possibly be the optimized 4.11 client you are using? Are you using the same 4.11 client in all the affected boxes?

---

I get the same errors and I'm not running any optimized clients. Also, I run multiple projects, and it's crashed when running things like Predictor.

I did turn off HT on my HT machine, and so far, no exceptions. That's not proof, though, since it might not have crashed even with HT on. But if it DOES crash, even with HT off, then that rules HT out as a cause.

---

I get the same errors and I'm not running any optimized clients. Also, I run multiple projects, and it's crashed when running things like Predictor.

I did turn off HT on my HT machine, and so far, no exceptions. That's not proof, though, since it might not have crashed even with HT on. But if it DOES crash, even with HT off, then that rules HT out as a cause.

I guess I have been fortunate if this is the issue, my HT CPU has not had any errors, just checked. I am only running CP and PP on this machine.

---

I've not been able to get any work since upgrading to 4.45. I even did a reset. Has anyone else experienced this or is it Seti???

---