of the last 19 WUs crunched 5 have exited with --
exit code 1073741819***Unhandled exception***
Reason: Access Violation.
these are
l1 1387 5 1387 9 0 1 T 01 S 41 B 0 0
l1 1387 5 1387 8 0 1 T 01 S 41 B 0 0
l1 0361 0 0361 0 0 1 T 00 S 41 B 0 0
w1 1299 5 1229 5 0 1 T 16 S 4 h a 2 0
l1 1387 5 1387 5 0 1 T 01 S 41 B 0 0 --
Running Windows SP2 256 RAM 2.8 IBM Think Centre.
Is this a normal percentage of failed batches or do I need to do something??
Running BOINC 4.45
Copyright © 2024 Einstein@Home. All rights reserved.
Unrecoverable Error
)
I lost everything! My computer updated and had to boot. I've booted without incident before. I rarely have to even suspend the projects.
I had to find my login key, and figure out what my username was. Good thing my default email address hasn't changed!
Boinc says disconnected at the bottom, and I was about 89% done on one project and 3.3% done on another. No messages, no files in the disk tab, nothing. All gone. Was anything saved on this end? My deadlines are 9/5 and 9/3 for the smaller project.
I can't make the system work - even the comm fields are blank. I added english to the language, but I don't know what the other stuff was.
RE: Is this a normal
)
Depends on what you define as "normal". We have no WUs that seem to be broken (i.e. give a client error on every machine they run on), and usually have about 5% of all Results (on Windows) that fail with a client error, by far the most of them with a General Access Violation.
There are quite a lot possible reasone for this error - hardware, system, drivers and of course bugs in our software. Walt Gribben recently found a nasty one in the BOINC library, but it will take some time to get this fixed and until it makes its way into our App.
This particular one and quite some other bugs may be avoided when running without using the graphics, so this might be worth a try.
BM
BM