I recommend running a database repair now that the program has crashed. What's probably occuring now is something got corrupted and that's causing more program crashes.
If you continue to suffer from program closures, you need to look beyond the program its self as it can be a symptom of a lot of things including faulty hardware, bad or corrupted files, drivers, heat, and including insufficient disk and RAM.
If you are unable to increase the amount of physical RAM, meaning DIMMs, and not hard drives as many people get the two mixed up, you can increase your virtual memory.
There are hundreds of articles on how to do this and this is one of the many based on a quick Google search.
https://blogs.systweak.com/2016/09/how-to-increase-virtual-memory-in-windows-10-a-quick-guide/
The general rule is first try system defaults. If you have out-of-memory issues or crashes, try increasing the size. The old general rule used to be 1-1/2 the size of installed memory so in your case a 20GB swap file is a good one to try. If that doesn't work well double that, but I wouldn't go bigger because that can cause overall poor system performance - it's a bit too much to explain here as to why.