What it means
A Domino process received a fatal operating system signal and crashed. Domino then runs NSD to capture diagnostics and terminates the server.
Common causes
- A bad memory access in Domino, an add-in or an API program (signal 11)
- A preceding PANIC raised by Domino itself
- Memory corruption caused by a damaged database or a product defect
Quick fixes
- Read the lines just above it on the console for a PANIC message, then open the NSD log it names
- Check the FATAL THREAD section of the NSD to find the task and function involved
- Compare several NSDs: if the same database or task appears each time, deal with that first (backup, then fixup)
- Update to a current fix pack and enable automatic restart after fault
Disclaimer
The errors, causes and fixes on this site are carefully researched, drawing on HCL documentation and 28 years of hands-on Domino and Notes experience. Every environment is different, though, and a solution that works in one may not be right for yours. Exact wording can also vary between Domino and Notes versions.
This information is general guidance only and is provided without warranty of any kind. Always back up your data and test changes on a non-production system first. To the extent permitted by law, Bruinsma Services Pty Ltd accepts no responsibility or liability for any loss, damage, downtime or other consequence arising from use of this information. For advice specific to your environment, please contact me.