i dont recall seeing this error before and its a first for me..
2/21/2008 8:58:44 AM|Einstein@Home|Task h1_0873.55_S5R3__423_S5R3b_0 exited with a DLL initialization error.
2/21/2008 8:58:44 AM|Einstein@Home|If this happens repeatedly you may need to reboot your computer.
2/21/2008 8:58:46 AM|Einstein@Home|Restarting task h1_0873.55_S5R3__423_S5R3b_0 using einstein_S5R3 version 432
2/21/2008 9:55:16 AM|Einstein@Home|Task h1_0873.55_S5R3__423_S5R3b_0 exited with a DLL initialization error.
2/21/2008 9:55:16 AM|Einstein@Home|If this happens repeatedly you may need to reboot your computer.
2/21/2008 9:55:17 AM|Einstein@Home|Restarting task h1_0873.55_S5R3__423_S5R3b_0 using einstein_S5R3 version 432
runing windows xp home edition with sp2, 1GB of ram and about 80GB's of free disk space.
Now that's interesting. I think the error condition would be the rather frequent "0xC0000142" DLL loading problem, the new thing is that BOINC will let the app restart after such an error. I think older BOINC versions used to trash a workunit after such an incident.
Is this correct? This would help to reduce trashed WUs on Windows.
i dont recall seeing this error before and its a first for me..
2/21/2008 8:58:44 AM|Einstein@Home|Task h1_0873.55_S5R3__423_S5R3b_0 exited with a DLL initialization error.
Which version of BOINC are you running? (not the science ap version)
One of my hosts, a Q6600 quad running Windows XP SP2 with BOINC 5.10.30 is getting a DLL initilization error killing all four current running science ap instances roughly two hours after each time I reboot the computer. In my case, the general pattern is that all four tasks restart successfully (generally either four Einsteins or three Einsteins and one SETI, or even three Einsteins, one SETI, then a second later another Einstein, which had been paused). So all BOINC science ap instances in memory fail, then the restarts work. I posted on this a few weeks ago, and Bernd pointed to a Windows page, which in turn suggested an ap I could download to check whether I was running low on some kind of Windows space. I was not. The fact that I fail soon after boot, rather than days later with lots of excess tasks consuming resources, is also evidence that the commonly expected cause is not at hand.
In my case the logged error is
error - 1073741502(0xC0000142)
My personal speculation is that a newish BOINC bug is generating this message and these restarts. But that is just speculation.
And, to comment on Bikeman's comment, this host was not routinely trashing four results each time I rebooted before this behavior started, so in my case it is not an improvement.
Which version of BOINC are you running? (not the science ap version)
5.10.30
I also have good reasons to believe that many recent versions of BOINC are misbehaved. In other words: problems that you are seeing sometimes are not caused by the science app, i.e. Einstein.xx, but rather by the BOINC software that coordinates application launching, transfers, etc.
Not good, but most likely that too will pass ... eventually.
i dont recall seeing this error before and its a first for me..
2/21/2008 8:58:44 AM|Einstein@Home|Task h1_0873.55_S5R3__423_S5R3b_0 exited with a DLL initialization error.
2/21/2008 8:58:44 AM|Einstein@Home|If this happens repeatedly you may need to reboot your computer.
2/21/2008 8:58:46 AM|Einstein@Home|Restarting task h1_0873.55_S5R3__423_S5R3b_0 using einstein_S5R3 version 432
2/21/2008 9:55:16 AM|Einstein@Home|Task h1_0873.55_S5R3__423_S5R3b_0 exited with a DLL initialization error.
2/21/2008 9:55:16 AM|Einstein@Home|If this happens repeatedly you may need to reboot your computer.
2/21/2008 9:55:17 AM|Einstein@Home|Restarting task h1_0873.55_S5R3__423_S5R3b_0 using einstein_S5R3 version 432
runing windows xp home edition with sp2, 1GB of ram and about 80GB's of free disk space.
The same thing happenend a couple a days ago on one of my hosts. After some checking I found that it had lost its netwerk connection.
Maybe a developer can tell if there is a netwerk call in this DLL.
Which version of BOINC are you running? (not the science ap version)
5.10.30
I also have good reasons to believe that many recent versions of BOINC are misbehaved. In other words: problems that you are seeing sometimes are not caused by the science app, i.e. Einstein.xx, but rather by the BOINC software that coordinates application launching, transfers, etc.
Not good, but most likely that too will pass ... eventually.
Not Einstein but same also with 5.10.30:
22.02.2008 13:56:46|lhcathome|Task wm7nwpb2_m7nwpb2__50__64.28_59.31__12_14__6__45_1_sixvf_boinc335399_2 exited with a DLL initialization error.
22.02.2008 13:56:46|lhcathome|If this happens repeatedly you may need to reboot your computer.
I've got first that failed: 37057616
This is a Pentium D930 with WinXP, it has also one succesful WU, both were started with stock 4.26 and finished with 4.32.
This machine had a few incidents of similar errors when S5R3 started with stock applications, those errors did not happen with stock 4.26 application anymore.
Got an other one that failed on the same host with the same error (0xC0000005). No point of using this version on this host, reverting back to stock 4.26.
I've got first that failed: 37057616
This is a Pentium D930 with WinXP, it has also one succesful WU, both were started with stock 4.26 and finished with 4.32.
This machine had a few incidents of similar errors when S5R3 started with stock applications, those errors did not happen with stock 4.26 application anymore.
Got an other one that failed on the same host with the same error (0xC0000005). No point of using this version on this host, reverting back to stock 4.26.
Could it be that 4.32 needs a newer boinc-version than your installed 5.8.15?
I think on Rieselsieve. They recommended 5.10.20 for further usage...
RE: i dont recall seeing
)
Now that's interesting. I think the error condition would be the rather frequent "0xC0000142" DLL loading problem, the new thing is that BOINC will let the app restart after such an error. I think older BOINC versions used to trash a workunit after such an incident.
Is this correct? This would help to reduce trashed WUs on Windows.
CU
Bikeman
RE: i dont recall seeing
)
Which version of BOINC are you running? (not the science ap version)
One of my hosts, a Q6600 quad running Windows XP SP2 with BOINC 5.10.30 is getting a DLL initilization error killing all four current running science ap instances roughly two hours after each time I reboot the computer. In my case, the general pattern is that all four tasks restart successfully (generally either four Einsteins or three Einsteins and one SETI, or even three Einsteins, one SETI, then a second later another Einstein, which had been paused). So all BOINC science ap instances in memory fail, then the restarts work. I posted on this a few weeks ago, and Bernd pointed to a Windows page, which in turn suggested an ap I could download to check whether I was running low on some kind of Windows space. I was not. The fact that I fail soon after boot, rather than days later with lots of excess tasks consuming resources, is also evidence that the commonly expected cause is not at hand.
In my case the logged error is
error - 1073741502(0xC0000142)
My personal speculation is that a newish BOINC bug is generating this message and these restarts. But that is just speculation.
And, to comment on Bikeman's comment, this host was not routinely trashing four results each time I rebooted before this behavior started, so in my case it is not an improvement.
RE: Which version of BOINC
)
5.10.30
seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.
RE: RE: Which version of
)
I also have good reasons to believe that many recent versions of BOINC are misbehaved. In other words: problems that you are seeing sometimes are not caused by the science app, i.e. Einstein.xx, but rather by the BOINC software that coordinates application launching, transfers, etc.
Not good, but most likely that too will pass ... eventually.
RE: i dont recall seeing
)
The same thing happenend a couple a days ago on one of my hosts. After some checking I found that it had lost its netwerk connection.
Maybe a developer can tell if there is a netwerk call in this DLL.
RE: Maybe a developer can
)
The problem is to figure out which DLL is meant.
The Trac ticket ([trac]#336[/trac]) is still open on this.
RE: RE: RE: Which
)
Not Einstein but same also with 5.10.30:
22.02.2008 13:56:46|lhcathome|Task wm7nwpb2_m7nwpb2__50__64.28_59.31__12_14__6__45_1_sixvf_boinc335399_2 exited with a DLL initialization error.
22.02.2008 13:56:46|lhcathome|If this happens repeatedly you may need to reboot your computer.
I just finished 2 more WUs on
)
I just finished 2 more WUs on my HT P4 Prescott 3.4ghz with version 4.32. Times are a lot faster with 4.32.
88000 seconds with 4.26 stock
59000 seconds with 4.32 sse
2 workunits running consecutivly both times with hyperthreading on.
RE: I've got first that
)
Got an other one that failed on the same host with the same error (0xC0000005). No point of using this version on this host, reverting back to stock 4.26.
RE: RE: I've got first
)
Could it be that 4.32 needs a newer boinc-version than your installed 5.8.15?
I think on Rieselsieve. They recommended 5.10.20 for further usage...