08-25-2013, 08:34 PM
(This post was last modified: 08-25-2013, 11:50 PM by Kgx Pnqvhm.)
(08-25-2013, 03:03 AM)Kgx Pnqvhm Wrote: The readme.txt says:
oclHashcat-plus v0.15
=====================
NV users require ForceWare 319.37 or later
As I reported last month, I had trouble determining whether the problems I was having were due to hashcat or Windows. Following the advice in the NVIDIA forums, I dropped down to ForceWare 314.22, and my system problems stopped.
If any Windows 7 users can report which ForceWare drivers they use succesfully for this new oclHashcat-plus v0.15, I'd be grateful.
So yesterday, I updated to the 326.80 beta drivers, and ran a mode 0 attack overnight successfully, then started another one this morning, set the monitor to sleep mode like I usually do, then went away for a while.
When I returned, I could not get the monitor to wake up, or the system to resond in any way, so had to power cycle to regain control.
Should I blame 'hashcat-plus v0.15 or buggy drivers from NVIDIA?
So now I have to downgrade again, but to something 319.37 or above.
But it is well know that the 320 driver series and 500 series cards don't work together.
Unless, is there some way to obtain just what 'hashcat-plus v0.15 needs without installing a whole new driver?