teltek

Your system is experiencing corrupted memory faults which in turn will force the system to reboot (reload). The trace back is due to a corrupted memory location. This can be caused by a bad disk read or defective memory itself. Three areas to check. The diskettes are my first inclination, the memory on the MCC is my second and thirdly (less likely of the three) is the MCC itself.

Fatal exceptions are caused from one of two issues;

1. your disk set (one of the two but usually not both) has begun "thinning" that diskettes eventually fall pray to. The system is constantly reading/writing to this diskette pair whenever a change in feature or service is made. This means each checkin/checkout, dnd, msg lamp, wake up call, etc. is captured to diskette so the system remains current during a reboot. You may find a replacement drive pair is in your cards as well.

* force a backup to a "CLEAN" diskette set.

OR,
2. your memory daughter board is not 100% seated (unlikely) or this module has lived the good life and requires replacement. It may be the MCC but this is least likely.



SUMMARY - these are staged options and unless the previous proves ineffective, do not continue on.
1. replace your disk set with a "very clean ... like new" pair.
2. replace the MEM module on the MCC.
3. replace the MCC { ouch$ }



hopin' this helps,

jsaad

4 meg memory mod replaced, no problems since.