We get some errors with exit code 0x40010004 from hosts running Windows Vista. Did anyone run this App successfully and reliably on Vista, or is it failing on all such machines? Any clues what precisely might be the reason of this error?
We get some errors with exit code 0x40010004 from hosts running Windows Vista. Did anyone run this App successfully and reliably on Vista, or is it failing on all such machines? Any clues what precisely might be the reason of this error?
I just saw this one: http://einsteinathome.org/task/85401300 and wondered whether the runtime debugger thing should not provide more detail here. Maybe there's still a problem with it? Or maybe it wasn't able to recover from the stack overflow error reported there to be executed properly?
I just saw this one: http://einsteinathome.org/task/85401300 and wondered whether the runtime debugger thing should not provide more detail here. Maybe there's still a problem with it? Or maybe it wasn't able to recover from the stack overflow error reported there to be executed properly?
CU
BRM
5.2.5 is a very old BOINC Core Client. It has been stated that "newer" BOINC CCs are needed for the error reporting, although what "newer" means is a bit fuzzy... Is 5.4.11 ok? How about 5.8.16? Hopefully it doesn't need to be a 5.9.x or 5.10.x release... :-(
Sorry I don't know the exact version myself. it needs to be some version that installs the dbghelp.dll in the BOINC directory. 5.8.x is definitely ok, 5.2 sounds too old, should be something in between where the change occured. Anyone knows the version for sure?
Bernd, the BOINC Windows Debugger was introduced in the 5.2.X series but a newer version was introduced with the 5.4.X series. Rom posted some technical details on the Ralph forum here which may help. Dave
You get a proper trace of an internal error from BOINC_LAL_ErrHand(), which "now calling boinc_finish()", but apparently it's boinc_finish() that failes (which does little more than just exit()) with an access violation. Something has gone really, really wrong on this machine (faulty memory or similar).
RE: The notice on the Home
)
Thanks. However, changing news items later is difficult, it causes trouble not on our site, but on the sites getting the news from xml or rss feeds.
BM
BM
We get some errors with exit
)
We get some errors with exit code 0x40010004 from hosts running Windows Vista. Did anyone run this App successfully and reliably on Vista, or is it failing on all such machines? Any clues what precisely might be the reason of this error?
BM
BM
Success on a Vista Machine
)
Success on a Vista Machine (Mine)
RE: We get some errors with
)
Hi!
Seems to be graphics related, see
some BOINC wiki
I've seen this happen at Rosetta as well, Vista with its new graphics subsystems seems to cause a lot of these errors, I'm afraid.
CU
BRM
Hi! I just saw this one:
)
Hi!
I just saw this one: http://einsteinathome.org/task/85401300 and wondered whether the runtime debugger thing should not provide more detail here. Maybe there's still a problem with it? Or maybe it wasn't able to recover from the stack overflow error reported there to be executed properly?
CU
BRM
RE: Hi! I just saw this
)
5.2.5 is a very old BOINC Core Client. It has been stated that "newer" BOINC CCs are needed for the error reporting, although what "newer" means is a bit fuzzy... Is 5.4.11 ok? How about 5.8.16? Hopefully it doesn't need to be a 5.9.x or 5.10.x release... :-(
Sorry I don't know the exact
)
Sorry I don't know the exact version myself. it needs to be some version that installs the dbghelp.dll in the BOINC directory. 5.8.x is definitely ok, 5.2 sounds too old, should be something in between where the change occured. Anyone knows the version for sure?
BM
BM
Bernd, the BOINC Windows
)
Bernd, the BOINC Windows Debugger was introduced in the 5.2.X series but a newer version was introduced with the 5.4.X series. Rom posted some technical details on the Ralph forum here which may help. Dave
RE: I just saw this one:
)
You get a proper trace of an internal error from BOINC_LAL_ErrHand(), which "now calling boinc_finish()", but apparently it's boinc_finish() that failes (which does little more than just exit()) with an access violation. Something has gone really, really wrong on this machine (faulty memory or similar).
BM
BM
My two AMD boxes (an AMD
)
My two AMD boxes (an AMD Athlon 2200 and an AMD Sempron 2600) are both nearly 25% faster!
Udo
