hashcat-3.00 - Printable Version +- 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-3.00 (/thread-5547.html) |
hashcat-3.00 - ScAnMaG - 06-25-2016 hashcat-3.00-rc3 error immediately after launch: Code: hashcat (v3.00-beta-215-g1550b9d) starting... hashcat-3.00-rc2 and earlier versions strange fan operation: Code: hashcat (v3.00-beta-213-g268b1e3) starting... Windows 8.1 x64 GIGABYTE AMD Radeon HD7770 [GV-R777OC-1GD V2.0] non-whql-64bit-radeon-software-crimson-16.6.1-win10-win8.1-win7-june2.exe RE: hashcat-3.00 - atom - 06-25-2016 There's rc4 now which should fix the path problematic on windows, the "catastrophic error". The fanspeed changes is a new feature, you can turn it off by using --gpu-temp-retain 0. RE: hashcat-3.00 - ScAnMaG - 06-25-2016 Fan speed control function is clearly useful. I'm just stating a fact that it works strange. Temp: 42c - 47c | Fan: 40% Temp: 57c - 66c | Fan: 15% Temp: 67c - 70c | Fan: 100% Thanks for your work RE: hashcat-3.00 - philsmd - 06-25-2016 Wow, actually this looks like a perfect temperature handling for me. At the beginning for both safety reasons and maybe because your card was already a little bit warm/hot, the fan speed was set to a reasonable high value. After that it recognizes that the temperature is still a little bit below the --gpu-temp-retain value and acts accordingly. Since the temperature raised again (now because of the cracking), fan speed was increases from 15 to 30, than 45, 51, 88 and finally 100% because the retain value was reached... At some point in time the temperature will almost exactly hit the --gpu-temp-retain value and keep that value, while the fan speed might lower a little bit again (but in some cases - depending on GPU, cooling setup etc - it also could need to keep the fan at 100%.... in most cases, in my experience, it won't keep a constant 100% fan speed, at least for NVidia GPUs) RE: hashcat-3.00 - ScAnMaG - 06-25-2016 If it helps, hashcat-3.00-rc5: AfterBurner Screen | https://drive.google.com/open?id=0B_SHSv8ZeqFCVGhpd0M0TVhPUk0 AfterBurner Log | https://drive.google.com/open?id=0B_SHSv8ZeqFCMy1pTkEzOWppMXc RE: hashcat-3.00 - atom - 06-26-2016 Thanks for the screenshots. As philsmd already pointed out, that's the ideal handling. RE: hashcat-3.00 - ScAnMaG - 06-28-2016 Fan control error in hashcat-3.00-rc19: https://drive.google.com/open?id=0B_SHSv8ZeqFCYkFTTjV1OFVCMms Sorry, it's my fault. Accidentally turn the fan control in Afterburner to manual mode. In hashcat-3.00 versions before rc16 (one of those that I have), default temperature retain trigger set to 65c, in later versions default temperature retain trigger set to 75c, so almost immediately activated temperature abort trigger, which is set by default on to 80c |