cudahashcat is hanging
#1
Hey guys, when I run cudaHashcat it sometimes hangs during initialization of kernel:

Code:
cudaHashcat v2.01 starting...

Device #1: GeForce GTX 970, 4096MB, 1316Mhz, 13MCU
Device #2: GeForce GTX 970, 4096MB, 1316Mhz, 13MCU
Device #3: GeForce GTX 970, 4096MB, 1316Mhz, 13MCU
Device #4: GeForce GTX 970, 4096MB, 1316Mhz, 13MCU
Device #5: GeForce GTX 970, 4096MB, 1316Mhz, 13MCU

Hashes: 1116984 hashes; 1116984 unique digests, 1 unique salts
Bitmaps: 17 bits, 131072 entries, 0x0001ffff mask, 524288 bytes, 5/13 rotates
Rules: 32
Applicable Optimizers:
* Zero-Byte
* Precompute-Init
* Precompute-Merkle-Demgard
* Meet-In-The-Middle
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Salt
* Scalar-Mode
* Raw-Hash
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: Kernel c:\Password\tools\cudaHashcat/kernels/4318/m00000_a0.sm_52.64.cubin


There is one process cudaHashcat64.exe sitting in background, eating up to 1GB of memory and doing something in the background as I see CPU utilisation at ~32%. The process itself is unkillable. I have to restart whole system (actually power it off and on again) to be able to use it again.

Usually I am using RDP to access this system. I've also read some posts here suggesting to use other method so I switched to VNC and then to KVM (connected to Intel gfx, see below) - same result.

This happens on random occasions. I can't find any pattern. Do you have any idea what could it be? A bug? Faulty nVidia card?

My setup is:
  • Procesor Intel Core i3-3220
  • Windows 2008 R2 64bit (fully patched)
  • Intel HD 2500 (integrated)
  • 5x EVGA GeForce GTX970 4096MB 256bit SC GAMING ACX 2.0 (running with latest nvidia drivers, updated today)
  • mobo: ASRock H61-PRO BTC
#2
Ugh, H61-PRO. The issue is almost certainly with your risers. Figure out which riser is bad and swap it out.

You've built your rig like a bitcoin miner, not a password cracker, which means you've done the exact opposite of nearly every piece of advice we've ever provided on these forums. So this will just be the first of many, many issues for you.