+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Deprecated; Previous versions (https://hashcat.net/forum/forum-29.html)
+--- Forum: Old oclHashcat Support (https://hashcat.net/forum/forum-38.html)
+--- Thread: impropper overclovk symptoms ? (/thread-4100.html)
Pages:
1
2
impropper overclovk symptoms ? - martin.po21 - 02-19-2015
Hy
I was just wondering if there can be any sideeffect of impropper gpu over/underclocking.
For example hashcat not recognising correct hash decryption key or something like that
I am asking because of my underclock... OclHashcat seems to run ok at this settings, but if i try to play a game for example computer crashes.
My current clocks for hd5970 with msi afterburner are 800 MHz core and 500 MHz memory at stock voltages
Thabk you
RE: impropper overclovk symptoms ? - r9290xocl - 02-19-2015
Run a video card benchmark like RealBench v2.4, set it to "Stress test" and run it for 1 hour. If it passes that, you are good to go.
RE: impropper overclovk symptoms ? - martin.po21 - 02-19-2015
Thank you!
Till now i tried only with hashcat- 30h without a problem, then i turned it off.
I am not planing to use this rig for anything else, thats why I wanted to know if any other stability test is needed
RE: impropper overclovk symptoms ? - r9290xocl - 02-19-2015
Realbench will test memory, CPU and video card, but if you wanted a pure video card benchmark, I would suggest Valey Benchmark, run it, and see if the FPS drops to below 20 FPS lets say, and adjust your core voltage / frequency as needed.
RE: impropper overclovk symptoms ? - martin.po21 - 02-19-2015
Thanks for your help
RE: impropper overclovk symptoms ? - epixoip - 02-20-2015
Sorry, but none of those programs suggested will stress the GPU in a way that hash cracking will. Graphics stress testing mostly hammers the FPU, doesn't really touch the ALU.
For stress testing GPUs for hash cracking, you can either use md5stress, or run oclHashcat with -w 3 -m 900 for a few hours.
RE: impropper overclovk symptoms ? - r9290xocl - 02-20-2015
^^ True, but you also want to ensure the entire system stability vs just the ALU alone. A more complete test would be all of the above combined
RE: impropper overclovk symptoms ? - martin.po21 - 02-20-2015
(02-20-2015, 02:04 AM)epixoip Wrote: Sorry, but none of those programs suggested will stress the GPU in a way that hash cracking will. Graphics stress testing mostly hammers the FPU, doesn't really touch the ALU.
For stress testing GPUs for hash cracking, you can either use md5stress, or run oclHashcat with -w 3 -m 900 for a few hours.
This is exactly what i was looking for!
No other tool mannaged to stress gpu like hashcat does, at least temperatures were much lower.
Thank you!!
RE: impropper overclovk symptoms ? - Kgx Pnqvhm - 02-21-2015
How do I get md5stress to run?
>md5stress64 100
initializing random seed...
initializing opencl...
Error 0 in line 132
>md5stress32 100
initializing random seed...
initializing opencl...
Error 0 in line 132
RE: impropper overclovk symptoms ? - epixoip - 02-21-2015
Works fine here (Ubuntu 14.04 + Catalyst 14.9):
Code:
epixoip@token:~/md5stress-0.2$ ./md5stress64.bin 500
initializing random seed...
initializing opencl...
generating 1351680 new random passwords + hashes...
generating 1351680 new random passwords + hashes...
generating 1351680 new random passwords + hashes...
generating 1351680 new random passwords + hashes...
generating 1351680 new random passwords + hashes...
generating 1351680 new random passwords + hashes...
Iteration: 0 / 500 on GPU #1...
Iteration: 0 / 500 on GPU #2...
Iteration: 0 / 500 on GPU #3...
Iteration: 0 / 500 on GPU #4...
Iteration: 0 / 500 on GPU #5...
Iteration: 0 / 500 on GPU #6...
Iteration: 1 / 500 on GPU #1...
Iteration: 1 / 500 on GPU #2...
Iteration: 1 / 500 on GPU #3...
Iteration: 1 / 500 on GPU #4...
Iteration: 1 / 500 on GPU #5...
Iteration: 1 / 500 on GPU #6...
Iteration: 2 / 500 on GPU #1...
Iteration: 2 / 500 on GPU #2...
Iteration: 2 / 500 on GPU #3...
Iteration: 2 / 500 on GPU #4...
Iteration: 2 / 500 on GPU #5...
Iteration: 2 / 500 on GPU #6...
Iteration: 3 / 500 on GPU #1...
Iteration: 3 / 500 on GPU #2...
Iteration: 3 / 500 on GPU #3...
Iteration: 3 / 500 on GPU #4...
Iteration: 3 / 500 on GPU #5...
Iteration: 3 / 500 on GPU #6...
Iteration: 4 / 500 on GPU #1...
Iteration: 4 / 500 on GPU #2...
Iteration: 4 / 500 on GPU #3...
Iteration: 4 / 500 on GPU #4...
Iteration: 4 / 500 on GPU #5...
Iteration: 4 / 500 on GPU #6...
Iteration: 5 / 500 on GPU #1...
Iteration: 5 / 500 on GPU #2...
Iteration: 5 / 500 on GPU #3...
Iteration: 5 / 500 on GPU #4...
Iteration: 5 / 500 on GPU #5...
Iteration: 5 / 500 on GPU #6...
Iteration: 6 / 500 on GPU #1...
Iteration: 6 / 500 on GPU #2...
Iteration: 6 / 500 on GPU #3...
Iteration: 6 / 500 on GPU #4...
Iteration: 6 / 500 on GPU #5...
Iteration: 6 / 500 on GPU #6...
Iteration: 7 / 500 on GPU #1...
Iteration: 7 / 500 on GPU #2...
Iteration: 7 / 500 on GPU #3...
Iteration: 7 / 500 on GPU #4...
Iteration: 7 / 500 on GPU #5...
Iteration: 7 / 500 on GPU #6...