+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Support (https://hashcat.net/forum/forum-3.html)
+--- Forum: hashcat (https://hashcat.net/forum/forum-45.html)
+--- Thread: hashcat mix temperature readings (/thread-6091.html)
hashcat mix temperature readings - martin.po21 - 12-03-2016
Hello!
Hashcat 3.1 and 3.2 mixes temperatures of my gtx980 and 980Ti.
Output of 3.2 is below:
Code:
Session..........: hashcat
Status...........: Running
Hash.Type........: WPA/WPA2
Hash.Target......: Tcell-E5172-XXXX (e8:08:8b:XX:XX:XX <-> d8:1d:72:XX:XX:XX)
Time.Started.....: Sat Dec 03 00:53:54 2016 (10 secs)
Time.Estimated...: Sat Dec 03 01:24:56 2016 (30 mins, 52 secs)
Input.Mask.......: ?d?d?d?d?d?d?d?d?d [9]
Input.Queue......: 1/1 (100.00%)
Speed.Dev.#6.....: 331.4 kH/s (259.36ms)
Speed.Dev.#7.....: 206.3 kH/s (313.18ms)
Speed.Dev.#*.....: 537.6 kH/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 3932160/1000000000 (0.39%)
Rejected.........: 0/3932160 (0.00%)
Restore.Point....: 0/100000000 (0.00%)
Candidates.#6....: 323456789 -> 318982501
Candidates.#7....: 206207201 -> 253009569
HWMon.Dev.#6.....: Temp: 84c Fan:100% Util: 95% Core:1240Mhz Mem:1900Mhz Lanes:8 *Throttled*
HWMon.Dev.#7.....: Temp: 65c Fan: 62% Util:100% Core:1528Mhz Mem:2497Mhz Lanes:8 *Throttled*
Drivers temperature threshold hit on GPU #7, expect performance to drop...As you can see, Hahscat thinks drivers temperature threshold hit on GPU #7, but actually it is hitting at GPU #6.
IF I run with only gpu 7 (-d 7) it will report its temperature as 35C- temperature on wich gpu6 idles.
I'm using nvidia drivers 376.09
Is this problem known to somebody?
I tried driver clean and reinstall, but ut stays the same.
Thanks in advance!
M
RE: hashcat mix temperature readings - atom - 12-03-2016
Can you please open an issue for this on Github. Thanks!
RE: hashcat mix temperature readings - martin.po21 - 12-03-2016
Thank you for reply. I've just opened it.
RE: hashcat mix temperature readings - atom - 12-03-2016
I need some additional information, but let's continue to talk on github about this bug. Forum should be for usage problems not bugs, therefore closing here.