09-21-2012, 04:28 PM
Hi guys,
First of all, thanks atom for the wonderful software, really appreciate your work on hashcat!
I have a GTX690 that I've been trying to use with hashcat for auditing "-m 1800" (sha512crypt) hashes. While the card peaks about 21,000 c/s, it constantly crashes with cuStreamSynchronize() 700 / 999 error messages, after 5-50 mins of running.
I've tried several settings down to "-n 1 --gpu-loops 1", but the crash still happens.
Interestingly, the crash does NOT take place with "-m 500" (md5crypt) hashes, only with "-m 1800". With "-m 500" I can do "-n 256 --gpu-loops 1000" and it works for days without problems at 2100K c/s.
I wonder, is this because my card if buggy, or is something else?
I tried it under Linux (NVIDIA 304.x drivers) and Windows 7 (306.x drivers), exactly same behavior. In Linux it crashes with cuStreamSynchronize() 700, in Windows it alternates between 700 and 999.
Thanks
P
First of all, thanks atom for the wonderful software, really appreciate your work on hashcat!
I have a GTX690 that I've been trying to use with hashcat for auditing "-m 1800" (sha512crypt) hashes. While the card peaks about 21,000 c/s, it constantly crashes with cuStreamSynchronize() 700 / 999 error messages, after 5-50 mins of running.
I've tried several settings down to "-n 1 --gpu-loops 1", but the crash still happens.
Interestingly, the crash does NOT take place with "-m 500" (md5crypt) hashes, only with "-m 1800". With "-m 500" I can do "-n 256 --gpu-loops 1000" and it works for days without problems at 2100K c/s.
I wonder, is this because my card if buggy, or is something else?
I tried it under Linux (NVIDIA 304.x drivers) and Windows 7 (306.x drivers), exactly same behavior. In Linux it crashes with cuStreamSynchronize() 700, in Windows it alternates between 700 and 999.
Thanks
P