09-09-2015, 10:11 PM
(09-09-2015, 09:49 PM)epixoip Wrote: You're not answering the most important question: 32GB total, or 32GB free? Are you observing the memory utilization while running hashcat?
It's not "normal," but it all depends on what else is running on the system and what exactly you're doing. If you have other RAM-hungry processes running, or built the system without swap space, or are working on a large hash list with lots of salts, then yeah, that can certainly happen.
Also remember that the Titan X is a 12GB card, and while 32GB should be fine for four Titan X in a dedicated cracking rig, it could in fact want to allocate 48GB of host memory for some attack. Just depends on what you're doing.
Once my current burn-in test is done, I can observe the memory consumption, but this system is running nothing else. Clean & default install of W10. Totally dedicated for hashcat and please note, that the error only appears when trying the "hashcat -b/--benchmark" option - within a few seconds.
I don't know what the benchmark option does "behind the scenes", but I'm not specifying any hash lists with/without salts etc.