Stackwalker not initialized (or was not able to initialize)!
2 May 2005 20:13:46 UTC
Topic 189095
(moderation:
Hi, I'm sure you have already discussed this problem here... but I just have to ask...
I've got 2 PCs:
1. AuthenticAMD AMD Athlon(tm) XP 2600+ (WinXP Pro)
2. GenuineIntel Intel(R) Celeron(R) CPU 2.40GHz (WinXP Pro)
I don't have any problems with the first one, but in contrast I have still some with the second one.
I have only invalid results from this PC and I'm still getting one message:
4.25
- exit code -1073741819 (0xc0000005)
detected finished Fstat file - skipping Fstat run 1
Resuming computation at 3179/102858/102858
Failed to open checkpoint-file for writing. Exiting.
***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x7C91433A read attempt to address 0x00ED0166
0: Stackwalker not initialized (or was not able to initialize)!
I have no idea where the problem [Stackwalker ???] could be and I don't know what to do...
Thanks for any help.
[url=http://einstein.phys.uwm.edu/team_display.php?teamid=2993" title="Fans of Lexa Doig][/url]
Stackwalker not initialized (or was not able to initialize)!
)
Hi, I'm sure you have already discussed this problem here... but I just have to ask...
I've got 2 PCs:
1. AuthenticAMD AMD Athlon(tm) XP 2600+ (WinXP Pro)
2. GenuineIntel Intel(R) Celeron(R) CPU 2.40GHz (WinXP Pro)
I don't have any problems with the first one, but in contrast I have still some with the second one.
I have only invalid results from this PC and I'm still getting one message:
4.25
- exit code -1073741819 (0xc0000005)
detected finished Fstat file - skipping Fstat run 1
Resuming computation at 3179/102858/102858
Failed to open checkpoint-file for writing. Exiting.
***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x7C91433A read attempt to address 0x00ED0166
0: Stackwalker not initialized (or was not able to initialize)!
I have no idea where the problem [Stackwalker ???] could be and I don't know what to do...
Thanks for any help.
Stack walker is part of the debugging code that is in various pieces of the client, it walks back up the stack generating some error output that helps the developers find the location of a trap.
I would try downloading and installing BOINC again. If it still happens after that, I am going to suggest that you create a bug for the developers to follow. They are probably going to need quite a bit of information.
BOINC WIKI