Please try `dmesg | grep oom-killer`. If you see cp2k there, this is it. Other running process might have also been affected. Alternatively, if you investigate "killed 9" crash right after it happened, you can just look at the end of `dmesg | less` (press End key, or type "G" (shift and 'g' key) to scroll "less" to the end). Other info you may find there is details of memory consumption before process was killed, but this may be overwhelming to read if you aren't used to such things. What is the most important, if there are no other memory hungry processes running in the system in parallel with cp2k and you still get oom, you'll probably have to reduce your system, basis set, or find another way to reduce memory consumption. Adding some swap on NVMe SSD might be helpful, but performance should be monitored carefully to ensure that it does not cause "thrashing" (constant swapping memory in and out) which would cause catastrophic slowdown of calculations. -- You received this message because you are subscribed to the Google Groups "cp2k" group. To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:cp2k+unsubscribe@googlegroups.com">cp2k+unsubscribe@googlegroups.com</a>. To view this discussion visit <a href="https://groups.google.com/d/msgid/cp2k/3c278a37-8c85-41f1-9210-e4b7afb56d2cn%40googlegroups.com?utm_medium=email&utm_source=footer">https://groups.google.com/d/msgid/cp2k/3c278a37-8c85-41f1-9210-e4b7afb56d2cn%40googlegroups.com</a>.