Never any valid results
23 Feb 2005 21:32:46 UTC
Topic 187907
(moderation:
It seems that for pretty much every WU I get, it finishes after about 1 minute with a "Client Error". The exit status for every one of these is -1073741515 (0xc0000135). What does this error number indicate?
--
Marcus Kwok
Never any valid results
)
What version of BOINC are you running?
BOINC WIKI
> It seems that for pretty
)
> It seems that for pretty much every WU I get, it finishes after about 1 minute
> with a "Client Error". The exit status for every one of these is -1073741515
> (0xc0000135). What does this error number indicate?
>
Usually means a DLL didn't load.
Does this just show in the error log or do you get a dialog box with the error? The DLL that failed to load would be part of the message displayed.
And is there anything in the system or application event log about the error?
> > It seems that for pretty
)
> > It seems that for pretty much every WU I get, it finishes after about 1
> minute
> > with a "Client Error". The exit status for every one of these is
> -1073741515
> > (0xc0000135). What does this error number indicate?
> >
>
> Usually means a DLL didn't load.
>
> Does this just show in the error log or do you get a dialog box with the
> error? The DLL that failed to load would be part of the message displayed.
>
> And is there anything in the system or application event log about the error?
Walt, I looked up stderr for this user. It looks like the core client is exiting before starting the app, or right after starting the app. There is no message from the APP, and I have no idea what this error code means. Any ideas what dll might be missing?
Bruce
Director, Einstein@Home
> Walt, I looked up stderr
)
> Walt, I looked up stderr for this user. It looks like this:
>
> core_client_version>4.19
> - exit code -1073741515 (0xc0000135)
>
> 1
> 0
>
> There is no message from the APP, and I have no idea what this means. Any
> ideas?
>
> Bruce
Bruce, thanks for the info.
So the question is where that error came from - Windows when loading the Einstein application, or the application passing a bad return code from some Windows call, like when its initializing.
Error code 0x0135 (bits 31 and 32 are the severity - "error") means the application didn't intitialize properly. Thats what you get when a required DLL isn't found and things like that. Question is, which DLL and why can't it get loaded?
Ricecake,
First suggestion is to check the event logs to see if anything got logged. Right-click "My Computer" and click "Manage". Double-click "Event Viewer" in the left pane and select each log in turn looking for errors. Specifically anything around the same time as the Einstein application problems. There might only be one record for an error, with subsequent errors getting counted as "occurred xxx times" instead of details.
Second suggestion is to get DebugView from the System Internals web site, start it, then run BOINC. See if any "debug" messages get sent when the Einstein application tries to start. DebugView is here.
I have more, but it depends on what happens with these two.
Walt
> Ricecake, > First
)
> Ricecake,
> First suggestion is to check the event logs to see if anything got logged.
> Right-click "My Computer" and click "Manage". Double-click "Event Viewer" in
> the left pane and select each log in turn looking for errors. Specifically
> anything around the same time as the Einstein application problems. There
> might only be one record for an error, with subsequent errors getting counted
> as "occurred xxx times" instead of details.
>
> Second suggestion is to get DebugView from the System Internals web site,
> start it, then run BOINC. See if any "debug" messages get sent when the
> Einstein application tries to start. DebugView is href="https://einsteinathome.org/%3Ca%20href%3D"http://www.sysinternals.com/ntw2k/freeware/debugview.shtml">http://www.sysinternals.com/ntw2k/freeware/debugview.shtml">here[/url].
>
> I have more, but it depends on what happens with these two.
Thanks everybody. Actually, I was having some problems with my computer caused by a weird power outage from a few months ago, which happened to have clobbered my DCIMAN32.dll file even though I am connected through a UPS. From a web search I determined that this DLL is used for graphics drawing. I was able to find a replacement for it the other night, and when I checked my BOINC this morning on the way out the door it looked like it was actually computing things, and I can even have it display the graphics (they would not display before). I'll check the event log when I get home from work and see if it was this missing DLL that caused the error. BOINC never gave me an error dialog box.
--
Marcus Kwok
> Thanks everybody.
)
> Thanks everybody. Actually, I was having some problems with my computer
> caused by a weird power outage from a few months ago, which happened to have
> clobbered my DCIMAN32.dll file even though I am connected through a UPS. From
> a web search I determined that this DLL is used for graphics drawing. I was
> able to find a replacement for it the other night, and when I checked my BOINC
> this morning on the way out the door it looked like it was actually computing
> things, and I can even have it display the graphics (they would not display
> before). I'll check the event log when I get home from work and see if it was
> this missing DLL that caused the error. BOINC never gave me an error dialog
> box.
Thats great.
DirectX is based on COM (Component Object Model) which is why you didn't see an error dialog box. It allows applications to recover from problems like this, they can just not use the graphics. The 3d animation in Einstein@home is definitely worth keeping though, the developers did a really good job with it, especially the way you can move the sphere around with the mouse. Thanks guys.
On recovering from the DLL problem, do you take backups? Its not installed with the XP Home Edition by default, but theres a backup utility somewhere in the "valueadd" directory on the CD. The downside is it includes "Automated System Recovery" which doesn't work in the home edition. But the manual backup and restore parts work just fine.
Walt
OK, it seems to be fine now.
)
OK, it seems to be fine now. I just checked and the last result finished successfully, and I now have pending credit :-)
> DirectX is based on COM (Component Object Model) which is why you didn't see
> an error dialog box. It allows applications to recover from problems like
> this, they can just not use the graphics. The 3d animation in Einstein@home
> is definitely worth keeping though, the developers did a really good job with
> it, especially the way you can move the sphere around with the mouse. Thanks
> guys.
Yeah, I must say that the graphics are awesome-looking. In my case though, it seems as though the app wouldn't even start without this graphics DLL.
> On recovering from the DLL problem, do you take backups? Its not installed
> with the XP Home Edition by default, but theres a backup utility somewhere in
> the "valueadd" directory on the CD. The downside is it includes "Automated
> System Recovery" which doesn't work in the home edition. But the manual
> backup and restore parts work just fine.
Thanks for the tip. I've been meaning to start a backup plan but I have nowhere to store the backups (it would take way too many CDs for my taste). At work we just bought these 250 GB Maxtor external drives (the OneTouch II) and I really liked how easy it was to set up those backups. I am planning on getting something similar.
--
Marcus Kwok
Oh yeah, I forgot to mention
)
Oh yeah, I forgot to mention it in my previous post but I did not see any entries in the Event Log relating to my error. I guess the app handled it all internally.
--
Marcus Kwok
> Oh yeah, I forgot to
)
> Oh yeah, I forgot to mention it in my previous post but I did not see any
> entries in the Event Log relating to my error. I guess the app handled it all
> internally.
The app only opens the graphics device, anything dealing with DLL loading and event recording is done by the graphics system.
The "exit code 0xc0000135" shows that the app doesn't deal with the error and exits instead of just turning off graphics. And its part of the initialization stuff so it happens right off. Unfortunately.
It was interesting that the seti app deals with this without any problems. From what I've seen, the seti app only opens the graphics device when its told to "Show Graphics".
> Thanks for the tip. I've
)
> Thanks for the tip. I've been meaning to start a backup plan but I have
> nowhere to store the backups (it would take way too many CDs for my taste).
> At work we just bought these 250 GB Maxtor external drives (the OneTouch II)
> and I really liked how easy it was to set up those backups. I am planning on
> getting something similar.
>
You don't have to back up everything. If all your files are in one partition - the C: drive - then you can be selective. Backing up the System State means just Windows and what it needs in case something gets corrupted. Thats like around 375M on my system (XP Pro). And fits on a CD.
I don't bother to back up the application. Only the data. Thats usually in the "documents and settings" folder, or in separate folders I create on other partitions. Makes it more difficult when a hard drive crashes, takes a few days to reinstall everything.