hashcat keeps ending with "killed"

[xkcd3301]

Hello!

Firstly, I saw the thread: https://hashcat.net/forum/thread-4642.html , where the conclusion was that OP ran out of memory. Hope it's not a duplicate, if it is, I'm sorry in forward!
I use hashcat v3.60 on a GTX 980 rig, with newest nvidia driver, on a Ubuntu machine. It worked flawlessly for years, with different hashes and modes.
Now I tried a RAR3 type hash (-m 12500), which I got with rar2john from the rar file, edited a little, so it won't cause line length exception.
Now I tried it with different modes, but always ends with "Killed" error.
Previous thread concluded it was because of insufficient memory, but he tried loading thousands of hashes, while I only worked with one (also he used much older version of hashcat).
I have 2 gigs of memory (I know it is not much), and it always was sufficient for my cracking rig.
Is it possible, that there is another cause for the error?
I know upgrading RAM isn't a big deal nowadays, but our rig is stored remotely, so reaching it and upgrading takes quite some effort, that's why I wanted to ask here before!

Thanks in forward!

[undeath]

what happens when you try to run the example rar hash? https://hashcat.net/wiki/doku.php?id=example_hashes

[xkcd3301]

what happens when you try to run the example rar hash? https://hashcat.net/wiki/doku.php?id=example_hashes

Good idea, I checked it, runs with around 20000H/s (which is something I would expect from GTX 980, according to benchmarks).
Makes me wonder if the hash is the actual problem, although it didn't fail the line length exception, so I presume it is a valid hash!
I'll try formatting it, and also try hashcat with different RAR3 hashes as well!
Thanks for the help!