LHC@home

I've been getting the following message come up when sixtrack tries to execute on a particular work unit:

jwe0019i-u [...] EXCEPTION_ACCESS_VIOLATION

v64lhc1000proten-48s12_14522.32_1_sixvf_20229_0
sixtrack version 4.46

I'm running Windows 2000 on an Athlon XP 2600+

I guess I'll just delete that work unit by hand, since it's preventing any others from workin.. I just wanted to report the error.

There are a number of currently unexplained Fortran errors. There's a note about it in Known Bugs. The CERN team are investigating.


Giskard - the first telepathic robot.

I've had a lot of Fortran errors here since my first participation in LHC@home.
One thing I noticed is the fact that nearly all errors seem to be caused by an access violation.

Under normal conditions something like this shall never happen, even if there are errors in the mathematics inside the sixtrack code.

Errors like this can only happen if you read/write to variables or arrays using pointer and accidently do a read/write attempt outside the reserved memory areas.

So from my point of view it is VERY certain that some bad pointer offsets are leading to such failures. Maybe someone should have a deeper look on the source again.

I get also this error with sixtrack 4.47 and package: v64lhc1000proeleven-54s10_12512.69_1_sixvf_19125_2_0

Fortran error v 4.47

jwe0019i-u [...] EXCEPTION_ACCESS_VIOLATION


I am getting also stack error on my win 98 machine.

Even though it's known already I'd like to post my similar error, too:

LHC@home - 2004-10-31 07:43:30 - Unrecoverable error for result v64lhc1000protwelve-59s16_18549.95_1_sixvf_28529_3 (Session aborted. (0xf0) - exit code 240 (0xf0))

Graphics to this error are as follows:



Kind regards

Mike

> Even though it's known already I'd like to post my similar error, too:
>

No matter,point it out anyway. I hate to see my machines sitting there with an error box waiting for me to press OK twice, I am paying for the power to run it.

jwe0019i-u [...] EXCEPTION_ACCESS_VIOLATION

I am getting this again on my two computers. The worst is on the win 98 it simply freezes with a window message "the program ( 6t) making illegal op" or fortran error.
(can't find anything wrong with my old box ran memtest86 v 3.1 for 15 hours no errors and CPU Stability Test 6.0
Test Results:
Tested: 6 Hours, 54 Minutes, 23 Seconds
Errors: 0
Stability: Rock Solid))))

No graphics


Does not look good for 4.47.

My systems run 24/7, configured as a service, and with the app left in memory when suspended. I have only seen the Fortran errors twice, and on both occasions after I had to stop and start the BOINC system for some reason. My machines never need to use the checkpoint system. I suspect there may be a fault there.

So, two questions:

Are your BOINC systems configured to leave the app in memory when suspended?

Do your systems ever get rebooted, or have the BOINC software restarted?

If the answer is YES then it might point to a checkpoint error. If the answer to both is NO then the fault must be elsewhere.


Giskard - the first telepathic robot.

> Are your BOINC systems configured to leave the app in memory when suspended?

I never suspend my systems.

> Do your systems ever get rebooted, or have the BOINC software restarted?

The systems are getting rebooted at least once a day because they're only running when the computers are in use.

Kind regards

Mike

I've got now first time this Fortran error. It is the same as StieflerDuo. It happened on first WU with 4.47 when it was at 100%. The Boinc screensaver was active this time but I am not sure if it was on blank screen or not.

I have Windows 2000 with Service pack 4 and Boinc 4.13

I just got the same fortran error after lots of 4.47 work units. First error in ages...

System is Windows XP SP3 Intel Mobile Pentium.

Running the Boinc 4.53 alpha quite happly here...