Running:
P4, 2.8G, 1MB L2, 512MB - WinXP SP2

MOINC Manager v5.4.9
SETI / Beta SE v5.15

Symptoms:
Twice in a week, BOINC Manager tells me it cannot connect with a BOINC client. I bring up Task Manager and lo and behold, the BOINC client is no longer running. It's not even in the process list. It has just mysteriously vanished. This is indeed the weirdest thing I have seen yet.

Any ideas.... \\-:<

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Running:
P4, 2.8G, 1MB L2, 512MB - WinXP SP2

MOINC Manager v5.4.9
SETI / Beta SE v5.15

Symptoms:
Twice in a week, BOINC Manager tells me it cannot connect with a BOINC client. I bring up Task Manager and lo and behold, the BOINC client is no longer running. It's not even in the process list. It has just mysteriously vanished. This is indeed the weirdest thing I have seen yet.

Any ideas.... \\-:<

Hi Siran,
You know me, I'm not a Windows man, but I do run Windows XP occasionally. Does your "event logger" show any messages? Something is bound to be causing the app to die and it might leave a message somewhere.

---

Jim

Some people plan their life out and look back at the wealth they've had.
Others live life day by day and look back at the wealth of experiences and enjoyment they've had.

I agree with Jim. If you have it installed as a service and the service will brak for some reason, it'll tell in Event Viewer.

If you have it installed as a single/multi user install, please tell.
Then say what other programs you may be running at that same time, how much RAM you have on how many CPUs and how many projects you have running and if you see the same thing on others.

---

I see this occasionally on one of my machines. I think it may have to do with a science application crashing and taking BOINC with it.

---

BOINC WIKI

Does stderrdae.txt contain anything useful?

If a crash happened, that is where the diagnostic output will be logged.

---

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

Does stderrdae.txt contain anything useful?

If a crash happened, that is where the diagnostic output will be logged.

Funny you should mention this. I was just looking at it and I copy/pasted an excerpt from it. Hang on while I transfer it to this PC.... Ok, I'm back. This is what I found:

--------------------------------------------------------------------


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

*** Dump of the (offending) thread: ***
eax=00c2f990 ebx=00b342c8 ecx=00000000 edx=00b343d0 esi=00c2f910 edi=00b343d0
eip=004cb014 esp=0122fee0 ebp=00ee9ad0
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010202

ChildEBP RetAddr Args to Child
0122fee0 004cadcd 00b343d0 00000000 00c2f910 0000001b libcurl!Curl_llist_insert_next+0x5 (c:\\boincsrc\\sdks\\curl\\lib\\llist.c:78) FPO: [3,0,0]
0122ff00 004bf7b3 00b342c8 00b343d0 0000001b 00ee9ad0 libcurl!Curl_hash_add+0xb (c:\\boincsrc\\sdks\\curl\\lib\\hash.c:165) FPO: [4,0,0]
0122ff24 004bfae5 00edd758 00ee9a98 00ee9fe8 00000050 libcurl!Curl_cache_addr+0x19 (c:\\boincsrc\\sdks\\curl\\lib\\hostip.c:361) FPO: [4,1,0]
0122ff48 004bfb52 00538af8 004bfd7c 00c1aaa8 00000000 libcurl!addrinfo_callback+0x15 (c:\\boincsrc\\sdks\\curl\\lib\\hostasyn.c:131) FPO: [0,1,0]
0122ff50 004bfd7c 00c1aaa8 00000000 00538af8 0012ef54 libcurl!Curl_addrinfo4_callback+0x12 (c:\\boincsrc\\sdks\\curl\\lib\\hostasyn.c:161) FPO: [3,0,0]
0122ff80 7c349565 00000000 0012ef54 000e000c 00b39fd0 libcurl!gethostbyname_thread+0x0 (c:\\boincsrc\\sdks\\curl\\lib\\hostthre.c:335) FPO: [1,4,0]
0122ffb4 7c80b50b 00b39fd0 0012ef54 000e000c 00b39fd0 MSVCR71!__endthreadex+0x0 (c:\\boincsrc\\sdks\\curl\\lib\\hostthre.c:335)
0122ffec 00000000 7c3494f6 00b39fd0 00000000 000000c8 kernel32!_BaseThreadStart@8+0x0 (c:\\boincsrc\\sdks\\curl\\lib\\hostthre.c:335)

Exiting...

--------------------------------------------------------------------

I'm sure this will reveal a clue or 2.... (-:<

[edit] Oh, one other thing. This is not SETI-centric. The first time this happened was when Einstein was crunching. [/edit]

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

@ Jim, Jord and John:

Thanks for the help guys. I checked the event logger before finding the information I posted for Rom. I was on Skype with Celtic Wolf and he said to check the error logs for BOINC. That's when I found what I did. Let's hope a fix can come around soon.... (-:<

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

I've seen it as well. WIN XP, 512MB RAM, BOINC 5.4.9 installed as a service, Malaria Control 100%. Memory usage 490MB (lot's running) IE crashed. Running Azureus - which has caused a few crashes due to a dodgy usb dsl modem driver (dlink200 - common problem no fix to date).

more of this style of notification.
.
.
.
.
.
ModLoad: 00a70000 00031000 C:\\Program Files\\BOINC\\srcsrv.dll (6.5.3.7) (-exported- Symbols Loaded)
File Version : 6.5.0003.7 (vbl_core_fbrel(jshay).050527-1915)
Company Name : Microsoft Corporation
Product Name : Debugging Tools for Windows(R)
Product Version: 6.5.0003.7
.
.
*** UNHANDLED EXCEPTION ****
Reason: Access Violation (0xc0000005) at address 0x771B3674 read attempt to address 0x014C01CC

*** Dump of the (offending) thread: ***
eax=014c0000 ebx=00000032 ecx=00000000 edx=001a0003 esi=00169558 edi=00000000
eip=771b3674 esp=0087f264 ebp=0087f264
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246

ChildEBP RetAddr Args to Child
0087f264 771b36bc 00000000 0087f2c4 00000000 00000000 WININET!+0x0
0087f2a4 771b73d8 00000000 0087f2c4 0087f2c8 771b738d WININET!+0x0
0087f2b4 771b738d 0087f2c4 00000000 00000000 0087f36c WININET!FindNextUrlCacheEntryA+0x0
0087f2c8 771b82ad 00000000 00000000 00000000 00000000 WININET!FindNextUrlCacheEntryA+0x0
0087f36c 771c57ee 00000000 00000032 0087f38c 0087f388 WININET!InternetQueryOptionA+0x0
0087f390 771d03d2 0087f71c 00000000 7c34f744 00000000 WININET!HttpAddRequestHeadersA+0x0
0087f6e0 771d73f4 0087f710 00000000 00000000 00000000 WININET!InternetGetConnectedStateExW+0x0
0087f6f8 00886595 0087f710 00000000 ffffffff 0044bc20 WININET!InternetGetConnectedState+0x0
00000000 00000000 00000000 00000000 00000000 00000000 boinc!BOINCIsNetworkAlive+0x0

Exiting...
Another instance of BOINC is running

----------------

Live long and crunch.

I've had it happen several times on several of my machines. It's windows, :)

---

Could this kind of problem become more common when M$ rolls out Vista or is the amount of free RAM not an issue? I try to keep as much memory free and limit background processes to the minimun (even if it is only "chipping" away at cpu cycles 1 or 2% at a time) as I have just the one box to crunch with. I can't OC (proprietary mobo) so I try to squeeze as much as I can out of it.

OK! This is rediculous! I am sending back nothing but errored WU's to all my projects. I have set them to get no new work and until this situation is cleared up, BOINC is taking a hiatus.... )-:<

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

This is what my returned results are saying:

<core_client_version>5.4.9</core_client_version>
<message>
- exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>

</stderr_txt>
)-:<

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

This is what my returned results are saying:

<core_client_version>5.4.9</core_client_version>
<message>
- exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>

</stderr_txt>
)-:<

This sounds like a Windows error message. It's not one from Boinc. If it's running as a service, you might could try running it just from the GUI to see if it happens. If it does, you may get an error window pop up with more info.

Sorry I'm not more familiar with Winows. Good luck!

---

Jim

Some people plan their life out and look back at the wealth they've had.
Others live life day by day and look back at the wealth of experiences and enjoyment they've had.

I suspect you are having problems with your RAM. Try running memtest and see if it generates errors.
http://www.memtest.org/

---

Proud member of Team Starfire World BOINC

This is what my returned results are saying:

<core_client_version>5.4.9</core_client_version>
<message>
- exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>

</stderr_txt>
)-:<

This sounds like a Windows error message. It's not one from Boinc. If it's running as a service, you might could try running it just from the GUI to see if it happens. If it does, you may get an error window pop up with more info.

Sorry I'm not more familiar with Winows. Good luck!

Hi Jim,

The only popups I'm seeing is "[insert client app here] has encounter a problem and needs to shut down. We regret the inconvenience". The other I see is something about writing or not writing to a memory address. I don't remember which it is now. I still have one Beta WU crunching, all others have gone to their respective projects as errored out. Let me see what I have in my error logs and get back to you.... )-:<

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Hi Jim,

The only popups I'm seeing is "[insert client app here] has encounter a problem and needs to shut down. We regret the inconvenience". The other I see is something about writing or not writing to a memory address. I don't remember which it is now. I still have one Beta WU crunching, all others have gone to their respective projects as errored out. Let me see what I have in my error logs and get back to you.... )-:<

Hi Siran,
I've looked at your wu's and man are they a weird lot! Do you have "keep work units in memory when preempted" or whatever it says set to "yes"? Are you stopping and starting either Windows or boinc? the reason I'm asking is I see some wu's that crunched perfectly with only a single entry in the log, while others have several log entries but still crunched, then others bombed out with either no log entries or from one to several! So it's not consistent. I'm beginning to agree with Mookie that you might have a memory problem (which your above error message points to) or your computer is overheating, or possibly something has happened to reset your cmos settings and thrown off your memory timings?
Just throwing around some ideas! Good luck!

---

Jim

Some people plan their life out and look back at the wealth they've had.
Others live life day by day and look back at the wealth of experiences and enjoyment they've had.

Hi Jim,

The only popups I'm seeing is "[insert client app here] has encounter a problem and needs to shut down. We regret the inconvenience". The other I see is something about writing or not writing to a memory address. I don't remember which it is now. I still have one Beta WU crunching, all others have gone to their respective projects as errored out. Let me see what I have in my error logs and get back to you.... )-:<

Hi Siran,
I've looked at your wu's and man are they a weird lot! Do you have "keep work units in memory when preempted" or whatever it says set to "yes"? Are you stopping and starting either Windows or boinc? the reason I'm asking is I see some wu's that crunched perfectly with only a single entry in the log, while others have several log entries but still crunched, then others bombed out with either no log entries or from one to several! So it's not consistent. I'm beginning to agree with Mookie that you might have a memory problem (which your above error message points to) or your computer is overheating, or possibly something has happened to reset your cmos settings and thrown off your memory timings?
Just throwing around some ideas! Good luck!

Well, sorry it took so long to get back, had some errands to run and had to clean my floppy drive so I could make the disk for MemTest86.

Ok, here's the scoop:

• I have disabled all BOINC and BOINC related apps, BoincView etc.
  
• I ran Kaspersky, a suite of apps for virus, ad/spyware, the whole nine yards. It reported everything clean.
  
• I downloaded MemTest86, and made the floppy disk for it and ran it. Memory passes.
  
• Since disabling BOINC, I have seen no problems at all, it's even running better, faster, stronger....
  

I have "Keep in memory...." set to "no".
I do remember seeing that MemTest86 reported my Ram and FSB at only 199Mhz when I have an 800Mhz motherboard. Maybe the CMOS idea isn't so far fetched. I'll look at it when I'm finished with this reply.
That computer is only about a year and a half old, with all new components installed at build time.

@Tony:
I do not run a screensaver unless I'm away for an extended period, such as when I'm at work. I do set the blank one, no graphics. I also have the *nix box shut off the monitor.

This is just too weird. I didn't start having problems until the "enhanced" version was released. I have heard of others having to re-format their HD and re-install the OS and software because of "enhanced". Since my XP box is running just fine now, without any memory problems and without any BOINC running, I have to be suspicious of the "enhanced" app. I was running v5.4.9 of the manager long before the "enhanced" app came out.

Going to check my CMOS now.... (-:<

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Hi Jim,

The only popups I'm seeing is "[insert client app here] has encounter a problem and needs to shut down. We regret the inconvenience". The other I see is something about writing or not writing to a memory address. I don't remember which it is now. I still have one Beta WU crunching, all others have gone to their respective projects as errored out. Let me see what I have in my error logs and get back to you.... )-:<

Hi Siran,
I've looked at your wu's and man are they a weird lot! Do you have "keep work units in memory when preempted" or whatever it says set to "yes"? Are you stopping and starting either Windows or boinc? the reason I'm asking is I see some wu's that crunched perfectly with only a single entry in the log, while others have several log entries but still crunched, then others bombed out with either no log entries or from one to several! So it's not consistent. I'm beginning to agree with Mookie that you might have a memory problem (which your above error message points to) or your computer is overheating, or possibly something has happened to reset your cmos settings and thrown off your memory timings?
Just throwing around some ideas! Good luck!

Well, sorry it took so long to get back, had some errands to run and had to clean my floppy drive so I could make the disk for MemTest86.

Ok, here's the scoop:

• I have disabled all BOINC and BOINC related apps, BoincView etc.
  
• I ran Kaspersky, a suite of apps for virus, ad/spyware, the whole nine yards. It reported everything clean.
  
• I downloaded MemTest86, and made the floppy disk for it and ran it. Memory passes.
  
• Since disabling BOINC, I have seen no problems at all, it's even running better, faster, stronger....
  

I have "Keep in memory...." set to "no".
I do remember seeing that MemTest86 reported my Ram and FSB at only 199Mhz when I have an 800Mhz motherboard. Maybe the CMOS idea isn't so far fetched. I'll look at it when I'm finished with this reply.
That computer is only about a year and a half old, with all new components installed at build time.

@Tony:
I do not run a screensaver unless I'm away for an extended period, such as when I'm at work. I do set the blank one, no graphics. I also have the *nix box shut off the monitor.

This is just too weird. I didn't start having problems until the "enhanced" version was released. I have heard of others having to re-format their HD and re-install the OS and software because of "enhanced". Since my XP box is running just fine now, without any memory problems and without any BOINC running, I have to be suspicious of the "enhanced" app. I was running v5.4.9 of the manager long before the "enhanced" app came out.

Going to check my CMOS now.... (-:<

Try another project and see what happens.

....

....

Well, sorry it took so long to get back, had some errands to run and had to clean my floppy drive so I could make the disk for MemTest86.

Ok, here's the scoop:

• I have disabled all BOINC and BOINC related apps, BoincView etc.
  
• I ran Kaspersky, a suite of apps for virus, ad/spyware, the whole nine yards. It reported everything clean.
  
• I downloaded MemTest86, and made the floppy disk for it and ran it. Memory passes.
  
• Since disabling BOINC, I have seen no problems at all, it's even running better, faster, stronger....
  

I have "Keep in memory...." set to "no".
I do remember seeing that MemTest86 reported my Ram and FSB at only 199Mhz when I have an 800Mhz motherboard. Maybe the CMOS idea isn't so far fetched. I'll look at it when I'm finished with this reply.
That computer is only about a year and a half old, with all new components installed at build time.

@Tony:
I do not run a screensaver unless I'm away for an extended period, such as when I'm at work. I do set the blank one, no graphics. I also have the *nix box shut off the monitor.

This is just too weird. I didn't start having problems until the "enhanced" version was released. I have heard of others having to re-format their HD and re-install the OS and software because of "enhanced". Since my XP box is running just fine now, without any memory problems and without any BOINC running, I have to be suspicious of the "enhanced" app. I was running v5.4.9 of the manager long before the "enhanced" app came out.

Going to check my CMOS now.... (-:<

Try another project and see what happens.

The problem happens when running Einstein as well as Beta and SETI. I have returned a boat load of errored results for all three projects. Thanks for the assist, oh Gaseous One.... (-:<

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath