Had two tasks resultid=93055302 and resultid=93057731 error out. reason; exit code -1073741819 (0xc0000005) when trying to set up graphics process.
Thought it might have been me, tweaking new computer, but latest was at 2 in the morning, zzzzz time. And another task has completed since then with no problems.
My E@H 4.36 WU did not restart after BOINC benchmarks were run. System was 99% idle (1% task monitor).
I restarted BOINC and it took off again. Still 7 hrs left to run. This WU.
This may be a BOINC issue, not E@H.
Could it be possible that you had a problem with checkpointing on your host. This could explain for myself why you have now still 7hrs left to run.
add:
My actual checkpoint-file needs ~400KB of diskspace.
Naahh, that system is an XP 1700+ and normally runs 13-15 hrs on WUs from that datapack. It finished in <14.5 hrs. I may have lost an hour during the freeze-up.
- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x7C91218E read attempt to address 0xFFFFFFFA
Engaging BOINC Windows Runtime Debugger...[/pre]
It restarted successfully from ckpt 164 and finished. (validated too). Strange, no debug info in stderr.txt
BTW, disk space is not an issue. The partition on that system is using just under 7GB of a 30GB partition. That 7GB includes Windows, swapfile, Firefox, Antivir, Zonealarm, etc.
Other failures for my account are due to failed attempts to switch back to the official app but I sorted it by detaching and re-attaching. Just removing app_info.xml didn't work.
Exit BOINC.
Navigate to your BOINC\\projects\\einstein.phys.edu\\ directory and deleting the app_info.xml file and the Einstein executables.
Restart BOINC.
Reset Einstein@Home.
I think I recognize that error as the one generated on my Core 2 Duos when I was using a too optimistic combination of clock rate and CPU voltage. When I was just a little too aggressive, the failures could be hours, and even up to a week, apart. For one release of the Einstein ap, the Einstein ap was considerably more demanding in this respect than either the then-current SETI ap or just running Windows.
Unfortunately, I don't think it is highly specific at all, so your problem might differ.
But you might want to consider the possibility that from the point of view of your sample of your processor, the 4.36 ap was a little more demanding than the other things it is running.
People here have actually observed diffences in core temperature when switching to more recent (faster) apps.
What I noticed for the host in question was that there are a lot of "no heartbeat for xx secobds, exiting" events, even before the update took place. This happens when the app stops to get the regular "I'm alive" messages from the >BOINC core client. Under Linux we had a similar problem where these conditions could crash the app with a "signal 11". Could this be something similar?
I think I recognize that error as the one generated on my Core 2 Duos when I was using a too optimistic combination of clock rate and CPU voltage. When I was just a little too aggressive, the failures could be hours, and even up to a week, apart. For one release of the Einstein ap, the Einstein ap was considerably more demanding in this respect than either the then-current SETI ap or just running Windows.
Unfortunately, I don't think it is highly specific at all, so your problem might differ.
But you might want to consider the possibility that from the point of view of your sample of your processor, the 4.36 ap was a little more demanding than the other things it is running.
Is it overclocked, by any chance?
In post 82134 I reported the same error code, seen on two tasks. The stderr looks to me, a non-programmer, like it is trying to set up a graphics output. I don't use screensavers, go to blank screen only, and at 2 in the morning, I was firmly in the land of nod.
The other projects run on this computer are Seti, with no graphics optimised app and SetiBeta which is now testing a BOINC V6 graphics enabled app, where the graphics are a separate exe.
So at the moment cannot tell wether it is an Einstein or a computer graphics/memory problem.
It is new cpu, mobo and RAM, but no testing with usual programs and games that run DirectX and openGL have indicated any problems.
Had two tasks
)
Had two tasks resultid=93055302 and resultid=93057731 error out. reason; exit code -1073741819 (0xc0000005) when trying to set up graphics process.
Thought it might have been me, tweaking new computer, but latest was at 2 in the morning, zzzzz time. And another task has completed since then with no problems.
My E@H 4.36 WU did not
)
My E@H 4.36 WU did not restart after BOINC benchmarks were run. System was 99% idle (1% task monitor).
I restarted BOINC and it took off again. Still 7 hrs left to run. This WU.
This may be a BOINC issue, not E@H.
Seti Classic Final Total: 11446 WU.
RE: My E@H 4.36 WU did not
)
Could it be possible that you had a problem with checkpointing on your host. This could explain for myself why you have now still 7hrs left to run.
add:
My actual checkpoint-file needs ~400KB of diskspace.
RE: RE: My E@H 4.36 WU
)
Naahh, that system is an XP 1700+ and normally runs 13-15 hrs on WUs from that datapack. It finished in <14.5 hrs. I may have lost an hour during the freeze-up.
stderr.txt shows:
[pre]Unhandled Exception Detected...
- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x7C91218E read attempt to address 0xFFFFFFFA
Engaging BOINC Windows Runtime Debugger...[/pre]
It restarted successfully from ckpt 164 and finished. (validated too). Strange, no debug info in stderr.txt
BTW, disk space is not an issue. The partition on that system is using just under 7GB of a 30GB partition. That 7GB includes Windows, swapfile, Firefox, Antivir, Zonealarm, etc.
Seti Classic Final Total: 11446 WU.
Running an Athlon XP2800
)
Running an Athlon XP2800 Barton core with 1.5GB memory on XP SP2, dedicated BOINC partition of 3GB
I installed this SSE app and have two failures so I switched back.
Error code: -1073741819 (0xc0000005)
The results concerned:
http://einsteinathome.org/task/93101627
http://einsteinathome.org/task/92914078
Other failures for my account are due to failed attempts to switch back to the official app but I sorted it by detaching and re-attaching. Just removing app_info.xml didn't work.
RE: Just removing
)
No, the best thing to do is:
Exit BOINC.
Navigate to your BOINC\\projects\\einstein.phys.edu\\ directory and deleting the app_info.xml file and the Einstein executables.
Restart BOINC.
Reset Einstein@Home.
That will usually do it for you.
RE: Error code: -1073741819
)
I think I recognize that error as the one generated on my Core 2 Duos when I was using a too optimistic combination of clock rate and CPU voltage. When I was just a little too aggressive, the failures could be hours, and even up to a week, apart. For one release of the Einstein ap, the Einstein ap was considerably more demanding in this respect than either the then-current SETI ap or just running Windows.
Unfortunately, I don't think it is highly specific at all, so your problem might differ.
But you might want to consider the possibility that from the point of view of your sample of your processor, the 4.36 ap was a little more demanding than the other things it is running.
Is it overclocked, by any chance?
Hi! People here have
)
Hi!
People here have actually observed diffences in core temperature when switching to more recent (faster) apps.
What I noticed for the host in question was that there are a lot of "no heartbeat for xx secobds, exiting" events, even before the update took place. This happens when the app stops to get the regular "I'm alive" messages from the >BOINC core client. Under Linux we had a similar problem where these conditions could crash the app with a "signal 11". Could this be something similar?
Puzzled
Bikeman
My computer isn't
)
My computer isn't overclocked.
However I do get a lot of
This latest one happened while I was away from the computer and nothing else CPU intensive was happening.
If I play a game or something highly CPU intensive I always shut down BOINC first.
RE: RE: Error code:
)
In post 82134 I reported the same error code, seen on two tasks. The stderr looks to me, a non-programmer, like it is trying to set up a graphics output. I don't use screensavers, go to blank screen only, and at 2 in the morning, I was firmly in the land of nod.
The other projects run on this computer are Seti, with no graphics optimised app and SetiBeta which is now testing a BOINC V6 graphics enabled app, where the graphics are a separate exe.
So at the moment cannot tell wether it is an Einstein or a computer graphics/memory problem.
It is new cpu, mobo and RAM, but no testing with usual programs and games that run DirectX and openGL have indicated any problems.