Thanks. I lost another 6h of work last night. It will be a day before I have new quota for a download and a while after that to see if this works.
The last time I tried to get help the told me computer was bad. Nonsense. I hope this works.
Nope! Running the beta app (0.18) didn't work. The error is reported on a separate thread. However, this behavior is weird in that about 10% of my E@H wu's complete and are validated, but essentially 100% of my P@H and S@H wu's are successful. Very disappointing.
Thanks. I lost another 6h of work last night. It will be a day before I have new quota for a download and a while after that to see if this works.
The last time I tried to get help the told me computer was bad. Nonsense. I hope this works.
Nope! Running the beta app (0.18) didn't work. The error is reported on a separate thread. However, this behavior is weird in that about 10% of my E@H wu's complete and are validated, but essentially 100% of my P@H and S@H wu's are successful. Very disappointing.
I am surprised and disappointed too. The Beta App worked for me (and others also). Your error report is a new on me. Hopefully, you will get a response from one of the developers soon. A bit of warning - they will probably ask you to "unhide" your computer so they can have access to more info about the problem. If you are a little uneasy about this, I suggest you click on my name and check out the type of information that is made available when you do this. Good luck! I hope you get things straightened out soon.
Thanks. I lost another 6h of work last night. It will be a day before I have new quota for a download and a while after that to see if this works.
The last time I tried to get help the told me computer was bad. Nonsense. I hope this works.
Nope! Running the beta app (0.18) didn't work. The error is reported on a separate thread. However, this behavior is weird in that about 10% of my E@H wu's complete and are validated, but essentially 100% of my P@H and S@H wu's are successful. Very disappointing.
Did you get any 0xC0000005 errors with the .018 version? The one you reported in the other thread looks like a completely different error. It would be nice to know whether your other WU's - the ones with 0xC0000005 errors - were crunched with 0.18 or an earlier version.
I only have one 0.18 attempt, which is the one that failed mentioned below. The earlier failures have to do with the 'standard' version, which ever one that is.
My suspicion is that it has to do with the notebook use model (on/off/hibernate/etc.) but no concrete data to prove it. So maybe boinc is screwing me. Of course the notebook works fine with S@H; and has for months.
Another thing. This poor notebook is being used as a mainframe at times. It runs Norton Ghost (which is a dog of a program) to do back-ups, MS Money on a 100 MB database which takes for ever to close, Excel on a 5MB market trading database, Outlook with a 100MB .pst file, and IE. Sometimes I have all these running, along with Media Player playing King FM in the background. Plus, I only have 512MB so there is a fair amount of paging. I've gotten used to the slow disk access at times. But I suppose boinc might see a slow disk and time out.
Damn! It failed again, with yet another error statement. This time, I put the notebook into hibernation, went home, resumed using the wireless rather than the hardwire network connection, and checked about an hour later. The damn thing bombed again. Now I have a bundle of P@H's to do before the next E@H wu is started. I'm really wasting cycles with this problem.
Here is what it said...
Resuming computation at 3903/180714/204114
No heartbeat from core client for 31 sec - exiting
detected finished Fstat file - skipping Fstat run 1
Resuming computation at 7991/499486/502366
***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x004097A7 read attempt to address 0x2E5EBC90
You are not alone ;) - exactly the same happend to me. I started this project yesterday in the evening and today in the morning I noticed the same message on the screen:
2005-09-30 10:04:03|Einstein@Home|Unrecoverable error for result l1_1317.0__1317.3_0.1_T07_S4lB_3 ( - exit code -1073741819 (0xc0000005))
Did beta test application really resolve this problem ?
All I can say is that it worked for me. I switched in early August and haven't had a problem since. And, from what I have read, it also seems to have worked for others. One word of caution: Is the driver for your graphics card up to date? Apparently, there have been some problems with older drivers.
Thanks for answer. Yesterday, without screensaver mode I had first good result in Einstein@home (wheras LHC@home and SETI@home work continuously without errors). Then I changed to Einstein 0.18 and to newest 7.8.0.1. driver for my NIVIDA Geforce FX 5200 graphic card and leaved project for night working and Unfotunatelly I had the same error messages in the mornig as before:
1.Application error. Memory can't be written.
2.2005-10-02 09:59:41|Einstein@Home|Unrecoverable error for result l1_1317.0__1317.4_0.1_T09_S4lB_2 ( - exit code -1073741819 (0xc0000005))
Einstein obviously does'nt want to work at night ;) and I'm starting to think, that in such cases maby more effectively for humanity science at whole ist switching immediatelly to another project than spending hours on finding some error. I'm asking myself: Why to repair some tool (maby computer??)if it can work as another tool, without any additional effort ?
Thanks for answer. Yesterday, without screensaver mode I had first good result in Einstein@home (wheras LHC@home and SETI@home work continuously without errors). Then I changed to Einstein 0.18 and to newest 7.8.0.1. driver for my NIVIDA Geforce FX 5200 graphic card and leaved project for night working and Unfotunatelly I had the same error messages in the mornig as before:
1.Application error. Memory can't be written.
2.2005-10-02 09:59:41|Einstein@Home|Unrecoverable error for result l1_1317.0__1317.4_0.1_T09_S4lB_2 ( - exit code -1073741819 (0xc0000005))
Einstein obviously does'nt want to work at night ;) and I'm starting to think, that in such cases maby more effectively for humanity science at whole ist switching immediatelly to another project than spending hours on finding some error. I'm asking myself: Why to repair some tool (maby computer??)if it can work as another tool, without any additional effort ?
I am sorry it didn't work. Obviously, the Beta App doesn't fix all the BOINC 4.45/Einstein 4.79 bugs. I suggest you post your problem and error message on the Beta App Message Board [Message boards : Cafe Einstein : NEW: WINDOWS TEST APPLICATION FOR EINSTEIN@HOME]. In the meantime, I guess reverting back to 4.79 without graphics is the way to go.
I am sorry it didn't work. Obviously, the Beta App doesn't fix all the BOINC 4.45/Einstein 4.79 bugs. I suggest you post your problem and error message on the Beta App Message Board [Message boards : Cafe Einstein : NEW: WINDOWS TEST APPLICATION FOR EINSTEIN@HOME]. In the meantime, I guess reverting back to 4.79 without graphics is the way to go.
OK, thank you very much for your help and advice. I'll try now on that Message Board.
***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x806FEF43 read attempt to address 0x806FEF43
1: 10/03/05 16:23:44
It´s the first time I get such result.
Computer: Pentium 4 HT 3,2 GHz
1 MB DDR-3200
ATI Radeon 9200 SE
WinXP Home (SP2)
Einstein 0.18
The second WU in this run results : valid
Chris
*Die Signatur befindet sich aus technischen Gründen auf der Rückseite dieses Beitrages!*
RE: Thanks. I lost another
)
Nope! Running the beta app (0.18) didn't work. The error is reported on a separate thread. However, this behavior is weird in that about 10% of my E@H wu's complete and are validated, but essentially 100% of my P@H and S@H wu's are successful. Very disappointing.
RE: RE: Thanks. I lost
)
I am surprised and disappointed too. The Beta App worked for me (and others also). Your error report is a new on me. Hopefully, you will get a response from one of the developers soon. A bit of warning - they will probably ask you to "unhide" your computer so they can have access to more info about the problem. If you are a little uneasy about this, I suggest you click on my name and check out the type of information that is made available when you do this. Good luck! I hope you get things straightened out soon.
RE: RE: Thanks. I lost
)
Did you get any 0xC0000005 errors with the .018 version? The one you reported in the other thread looks like a completely different error. It would be nice to know whether your other WU's - the ones with 0xC0000005 errors - were crunched with 0.18 or an earlier version.
I un-hid my computer; pretty
)
I un-hid my computer; pretty plain-jane notebook.
I only have one 0.18 attempt, which is the one that failed mentioned below. The earlier failures have to do with the 'standard' version, which ever one that is.
My suspicion is that it has to do with the notebook use model (on/off/hibernate/etc.) but no concrete data to prove it. So maybe boinc is screwing me. Of course the notebook works fine with S@H; and has for months.
Another thing. This poor
)
Another thing. This poor notebook is being used as a mainframe at times. It runs Norton Ghost (which is a dog of a program) to do back-ups, MS Money on a 100 MB database which takes for ever to close, Excel on a 5MB market trading database, Outlook with a 100MB .pst file, and IE. Sometimes I have all these running, along with Media Player playing King FM in the background. Plus, I only have 512MB so there is a fair amount of paging. I've gotten used to the slow disk access at times. But I suppose boinc might see a slow disk and time out.
Damn! It failed again, with
)
Damn! It failed again, with yet another error statement. This time, I put the notebook into hibernation, went home, resumed using the wireless rather than the hardwire network connection, and checked about an hour later. The damn thing bombed again. Now I have a bundle of P@H's to do before the next E@H wu is started. I'm really wasting cycles with this problem.
Here is what it said...
Resuming computation at 3903/180714/204114
No heartbeat from core client for 31 sec - exiting
detected finished Fstat file - skipping Fstat run 1
Resuming computation at 7991/499486/502366
***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x004097A7 read attempt to address 0x2E5EBC90
1: 10/01/05 19:59:55
1: c:cygwinhomebemaeinsteinathomecfswindows_build.18cfslaldemod.c(854) +20 bytes (TestLALDemod)
1: c:cygwinhomebemaeinsteinathomecfswindows_build.18computefstatistic.c(728) +28 bytes (boincmain)
1: c:cygwinhomebemaeinsteinathomecfswindows_build.18computefstatistic.c(3082) +20 bytes (worker)
1: c:cygwinhomebemaeinsteinathomecfswindows_build.18boincapigraphics_impl.c(75) +0 bytes (foobar)
RE: RE: You are not alone
)
Thanks for answer. Yesterday, without screensaver mode I had first good result in Einstein@home (wheras LHC@home and SETI@home work continuously without errors). Then I changed to Einstein 0.18 and to newest 7.8.0.1. driver for my NIVIDA Geforce FX 5200 graphic card and leaved project for night working and Unfotunatelly I had the same error messages in the mornig as before:
1.Application error. Memory can't be written.
2.2005-10-02 09:59:41|Einstein@Home|Unrecoverable error for result l1_1317.0__1317.4_0.1_T09_S4lB_2 ( - exit code -1073741819 (0xc0000005))
Einstein obviously does'nt want to work at night ;) and I'm starting to think, that in such cases maby more effectively for humanity science at whole ist switching immediatelly to another project than spending hours on finding some error. I'm asking myself: Why to repair some tool (maby computer??)if it can work as another tool, without any additional effort ?
RE: RE: Thanks for
)
I am sorry it didn't work. Obviously, the Beta App doesn't fix all the BOINC 4.45/Einstein 4.79 bugs. I suggest you post your problem and error message on the Beta App Message Board [Message boards : Cafe Einstein : NEW: WINDOWS TEST APPLICATION FOR EINSTEIN@HOME]. In the meantime, I guess reverting back to 4.79 without graphics is the way to go.
RE: I am sorry it didn't
)
OK, thank you very much for your help and advice. I'll try now on that Message Board.
Today I ge the same
)
Today I ge the same result
Exit status -1073741819 (0xc0000005)
***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x806FEF43 read attempt to address 0x806FEF43
1: 10/03/05 16:23:44
It´s the first time I get such result.
Computer: Pentium 4 HT 3,2 GHz
1 MB DDR-3200
ATI Radeon 9200 SE
WinXP Home (SP2)
Einstein 0.18
The second WU in this run results : valid
Chris
*Die Signatur befindet sich aus technischen Gründen auf der Rückseite dieses Beitrages!*