Please note, this is a STATIC archive of website hashcat.net from 08 Oct 2020, cach3.com does not collect or store any user information, there is no "phishing" involved.

hashcat Forum

Full Version: Trouble with hashes.
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hey guys, I'm at my wits end here. (TRY HARDER!) I have a LM hash that i pulled from cain after dumping the remote registry of a MSSQL server. I'm trying to crack it now and I'm not making any progress. I've been fiddling with this for over an hour now trying to get my 660 Ti to brute force this hash. The password policy of the network i pulled this from is fairly complex, and the ophcrack tables have not left me with many results.

I've been using oclHashcat-lite-0.10:

C:\Users\Osprey\Desktop\hashcat gui\oclHashcat-lite-0.10>cudaHashcat-lite32.exe
A223B1233BB50F3XYTRFDS97DBC7AF7C
cudaHashcat-lite v0.10 by atom starting...

Password lengths range: 1 - 55
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: GeForce GTX 660 Ti, 3072MB, 980Mhz, 7MCU

[s]tatus [p]ause [r]esume [q]uit => ERROR: cuStreamSynchronize() 999


Oh yea: thats not the actual hash...
c:\Users\Osprey\Desktop\hashcat gui\oclHashcat-lite-0.10>oclhashcat-lite32.exe -m 3000 --pw-min=8 A223B1233BB50F3XYTRFDS97DBC7AF7C ?1?1?1?1?1?1?1?1
ERROR: No AMD compatible platform found

What's going on here? Video drivers are a brand new install. My old card was an ATI, is the system screwed or is it hashcat?
(11-26-2012, 04:50 AM)kryptosec Wrote: [ -> ]c:\Users\Osprey\Desktop\hashcat gui\oclHashcat-lite-0.10>oclhashcat-lite32.exe -m 3000 --pw-min=8 A223B1233BB50F3XYTRFDS97DBC7AF7C ?1?1?1?1?1?1?1?1
ERROR: No AMD compatible platform found

What's going on here? Video drivers are a brand new install. My old card was an ATI, is the system screwed or is it hashcat?
For this last command line it's easy, you have used oclhashcat-lite instead of cudahashcat-lite.
this question has been covered several times, if you search for "cuStreamSynchronize() 999"

you need to disable wddm recovery: https://hashcat.net/wiki/doku.php?id=timeout_patch