Need Help on Errors

AcidSlide
AcidSlide
Joined: 21 Jul 05
Posts: 14
Credit: 27082
RAC: 0
Topic 189607

I've been reading some of the threads and it seems a lot of people are having problems with Einstein@Home compared to the other Boinc projects.

I keep getting error results from one of the computers that I'm using. Below are just some of errors encountered.

4.45
- exit code -1073741819 (0xc0000005)

***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x7C918FEA write attempt to address 0x00000010

-----------------------------------------------------------------------------
4.45
- exit code -1073741819 (0xc0000005)

Failed to open checkpoint-file for writing. Exiting.

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

0: Stackwalker not initialized (or was not able to initialize)!

-----------------------------------------------------------------------------
4.45
- exit code -1073741819 (0xc0000005)

Failed to open checkpoint-file for writing. Exiting.

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

0: Stackwalker not initialized (or was not able to initialize)!

-----------------------------------------------------------------------------
4.45
- exit code -1073741819 (0xc0000005)

Resuming computation at 2301/148235/149145
Resuming computation at 3258/193643/195281

***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x7C918FEA write attempt to address 0x00000010

I'm still waiting from the results of my other computers for Einstein@Home. I've checked my other running projects and everythings ok, no error encountered at all.

I don't think that its the client, since i'm sure it is working on the other projects. Hope somebody can shed light on this.

Regards to all Boincers :)

Blank Reg
Blank Reg
Joined: 18 Jan 05
Posts: 228
Credit: 40599
RAC: 0

Need Help on Errors

AcidSlide
AcidSlide
Joined: 21 Jul 05
Posts: 14
Credit: 27082
RAC: 0

RE: read all about it in

Message 14577 in response to message 14576

Quote:
read all about it in the WIKI

I've tried looking for it in the WIKI but all I got is that it might be a Software Bug!

I'm looking at the other projects that are running in all my servers that are running the Boinc. But it is only that E@H are getting the errors.

Blank Reg
Blank Reg
Joined: 18 Jan 05
Posts: 228
Credit: 40599
RAC: 0

You might want to try

You might want to try memtest86 to check out your memory.... http://www.memtest86.com/

Heffed
Heffed
Joined: 18 Jan 05
Posts: 257
Credit: 12368
RAC: 0

RE: You might want to try

Message 14579 in response to message 14578

Quote:
You might want to try memtest86 to check out your memory.... http://www.memtest86.com/


Actually, memtest86 is outdated. Memtest86+ is what you should run.

Bernd Machenschalk
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4332
Credit: 251746029
RAC: 36135

I would suggest to try the

I would suggest to try the App that is currently in our Public Beta Test. Seems that some people having problems with the 4.45 client and our "official" App, which was built with a rather old version of the BOINC library.

The failing address is deep down in the system libs, might be somewhat got broken down there on your installation. A hardware problem I would consider to be rather unlikely (though not impossible), as the error happens always in the same region of the process' memory space.

BM

BM

AcidSlide
AcidSlide
Joined: 21 Jul 05
Posts: 14
Credit: 27082
RAC: 0

RE: RE: You might want to

Message 14581 in response to message 14579

Quote:
Quote:
You might want to try memtest86 to check out your memory.... http://www.memtest86.com/

Actually, memtest86 is outdated. Memtest86+ is what you should run.

Thanks, i'll try it but I'm don't think its a memory problem (or hardware problem) since I do regular maintenance check on all my systems. Thanks again I hope it will help me find out what could be really causing it. :)

AcidSlide
AcidSlide
Joined: 21 Jul 05
Posts: 14
Credit: 27082
RAC: 0

RE: I would suggest to try

Message 14582 in response to message 14580

Quote:

I would suggest to try the App that is currently in our Public Beta Test. Seems that some people having problems with the 4.45 client and our "official" App, which was built with a rather old version of the BOINC library.

The failing address is deep down in the system libs, might be somewhat got broken down there on your installation. A hardware problem I would consider to be rather unlikely (though not impossible), as the error happens always in the same region of the process' memory space.

BM

Thanks for the info Bernd, i'll check the Beta Test and see if it will work. I'll inform everybody of the progress by next week since I'll be in vacation mode for the next couple of days.. :)

AcidSlide
AcidSlide
Joined: 21 Jul 05
Posts: 14
Credit: 27082
RAC: 0

RE: RE: I would suggest

Message 14583 in response to message 14582

Quote:
Quote:

I would suggest to try the App that is currently in our Public Beta Test. Seems that some people having problems with the 4.45 client and our "official" App, which was built with a rather old version of the BOINC library.

The failing address is deep down in the system libs, might be somewhat got broken down there on your installation. A hardware problem I would consider to be rather unlikely (though not impossible), as the error happens always in the same region of the process' memory space.

BM

Thanks for the info Bernd, i'll check the Beta Test and see if it will work. I'll inform everybody of the progress by next week since I'll be in vacation mode for the next couple of days.. :)

:( I'm still getting errors:

***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x7C918FEA write attempt to address 0x00000010

I'm using the Public Beta Test already but still the same error. So far only two (2) of the 5 Boinc Projects running (the other is LHC@Home) on my WinXP Machine is getting the error results, the other 3 are successful results always. I have 2 more machines running the same 5 projects on Linux and their results are all returning Successful results.

I'll do a full system check when I get back. I'm currently hundreds of miles away from my systems. I'm checking the results via online only.

Again, I'll inform everybody the results of the system checks.

AcidSlide
AcidSlide
Joined: 21 Jul 05
Posts: 14
Credit: 27082
RAC: 0

Hello everybody! After

Message 14584 in response to message 14583

Hello everybody!

After doing all possible test on my WinXP machine (including the Memtest86+), I didn't find a single problem in the winxp machine. I have tried all the suggesting given here but compared to my other machines running various boinc projects, it is only the winxp machine that is always giving/getting error results from E@H and L@H.


***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x7C918FEA write attempt to address 0x00000010

This is my winxp machine specs:
Boinc Client 4.45
Running E@H using Public Beta (and original version)
WinXP Pro SP2
P4 2.4Ghz HT (GenuineIntel Family 15 Model 2 2.4 GHz Stepping 9 (2 CPUs))
1.27Gb RAM
40GB Hard Disk plus 80GB Removable

Quote:
Quote:
Quote:

I would suggest to try the App that is currently in our Public Beta Test. Seems that some people having problems with the 4.45 client and our "official" App, which was built with a rather old version of the BOINC library.

The failing address is deep down in the system libs, might be somewhat got broken down there on your installation. A hardware problem I would consider to be rather unlikely (though not impossible), as the error happens always in the same region of the process' memory space.

BM

Thanks for the info Bernd, i'll check the Beta Test and see if it will work. I'll inform everybody of the progress by next week since I'll be in vacation mode for the next couple of days.. :)

:( I'm still getting errors:

***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x7C918FEA write attempt to address 0x00000010

I'm using the Public Beta Test already but still the same error. So far only two (2) of the 5 Boinc Projects running (the other is LHC@Home) on my WinXP Machine is getting the error results, the other 3 are successful results always. I have 2 more machines running the same 5 projects on Linux and their results are all returning Successful results.

I'll do a full system check when I get back. I'm currently hundreds of miles away from my systems. I'm checking the results via online only.

Again, I'll inform everybody the results of the system checks.


Bernd Machenschalk
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4332
Credit: 251746029
RAC: 36135

Oh - not only Einstein@Home,

Oh - not only Einstein@Home, but LHC@Home, too? Sounds like a client problem to me. Do you want to give it another try with the 4.19?

BM

BM

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.