A decade ago "capacitor plague" was common and caused by a batch of fraudulent capacitors that got into the supply chain.
Another possibility for your sick system is that possibly the power supply is dying and can't handle a full load.
But to get this back on the original thread topic, I know of three reasons why calibre doesn't work well on a network filesystem:
- Calibre doesn't expect to share its files. If you run two copies of calibre on the shared disk, they will step on each others toes and corrupt things.
- Many network filesystems (Onedrive, Dropbox, Google drive) do not preserve filenames, and like to mangle them for you. This corrupts things badly.
- Some network filesystems are not stable, and if they disconnect while calibre is running, this corrupts things. Samba can disconnect in the middle of a file operation. sshfs is worse, as it requires a manual restart. NFS is designed to handle this, and will hang the client until the server comes back.
I can't say for sure, but I suspect calibre would be fine on NFS as long as you didn't run it twice on the same library. But if your desktop is unstable, it could still crash with calibre running, and this still could mess things up.