Unhandled exception errors

Author	Message
Rob Send message Joined: 10 Nov 08 Posts: 4 Credit: 60,350,898 RAC: 0 Level Scientific publications	Message 9983 - Posted: 20 May 2009, 1:21:11 UTC The last few days I've been getting dozens of unhandled exception errors "Reason: Breakpoint Encountered (0x80000003) at address 0x7C90120E" Whats more these are wu's that aren't even running at the time, I've often spotted one or more while my comp is in the middle of crunching a 50 plus hour wu. Here are a few of the latest: http://www.gpugrid.net/result.php?resultid=693177 http://www.gpugrid.net/result.php?resultid=691019 http://www.gpugrid.net/result.php?resultid=691018 I wouldn't worry so much as they error out before they even start, but it's meant that a few times I've been without work because I've hit my quota of work for the day. I have a 8600GT on Win XP with Boinc 6.6.23 & 185.85 drivers ID: 9983 · Rating: 0 · rate: / Reply Quote

naja002 Send message Joined: 25 Sep 08 Posts: 111 Credit: 10,352,599 RAC: 0 Level Scientific publications	Message 9985 - Posted: 20 May 2009, 1:45:55 UTC Same here on the 17th (13) and 18th (7). They just errored right out one after another. Strangely they are not all the same type of wu. Seems to have gone away now...for me anyway. ID: 9985 · Rating: 0 · rate: / Reply Quote

popandbob Send message Joined: 18 Jul 07 Posts: 67 Credit: 43,351,724 RAC: 0 Level Scientific publications	Message 9990 - Posted: 20 May 2009, 4:39:58 UTC The breakpoint encountered happens when the app is shut-down incorrectly. I'd suggest it was a boinc scheduling bug which said "hey run this wu now! now run this one!" and the wu errored because it was shut down again so fast. Bob ID: 9990 · Rating: 0 · rate: / Reply Quote

Rob Send message Joined: 10 Nov 08 Posts: 4 Credit: 60,350,898 RAC: 0 Level Scientific publications	Message 10013 - Posted: 21 May 2009, 6:08:19 UTC Hmm, could be a Boinc 6.6.23 thing. I started getting the errors about the time I upgraded. I'm downloading 6.6.28 now so I'll see how that goes :) ID: 10013 · Rating: 0 · rate: / Reply Quote

ExtraTerrestrial Apes Volunteer moderator Volunteer tester Send message Joined: 17 Aug 08 Posts: 2705 Credit: 1,311,122,549 RAC: 0 Level Scientific publications	Message 10023 - Posted: 21 May 2009, 10:20:07 UTC Wasn't some "silent WU start" bug recently mentioned in the 6.6.2x code base? That could cause exactly these issues. Not seeing anything like this on 6.5.0 ;) MrS Scanning for our furry friends since Jan 2002 ID: 10023 · Rating: 0 · rate: / Reply Quote

Paul D. Buck Send message Joined: 9 Jun 08 Posts: 1050 Credit: 37,321,185 RAC: 0 Level Scientific publications	Message 10037 - Posted: 21 May 2009, 14:47:06 UTC - in response to Message 10023. Wasn't some "silent WU start" bug recently mentioned in the 6.6.2x code base? That could cause exactly these issues. Not seeing anything like this on 6.5.0 ;) MrS Yes, what I mean by this is that the task stops for whatever reason. But it is supposed to be running. So, the next pass through the Resource Scheduler the task is simply started again. The problem is that there is no message in the normal log indicating that this is happening. I turned on a flag a few days ago and I am collecting a log to go looking for this situation. The problem is that it is dependent on an unknown event happening so it looks to be a hard one to find. Oh, and this is another bug that may have been in the code base for years too ... so no telling which versions it will affect ... again, the issue is that some other change makes this bug surface more than other versions... ID: 10037 · Rating: 0 · rate: / Reply Quote