06-01-2013, 02:36 PM
Hey Kuci,
did you try also w/ catalyst 13.1 (http://support.amd.com/us/gpudownload/wi...6&rev=13.1 ) as suggested in GPU Driver and SDK Requirements here: https://hashcat.net/oclhashcat-lite/ ?
I think this is the only (officially) supported driver for oclHashcat-lite (for now!).
Furthermore, you should tell us if this behaviour is "new" or if you experienc(ed) it also w/ other/older oclHashcat versions.
It would be also interesting if oclHashcat-lite was/is able to recover hashes before crashing and if it happens only w/ specific commands, e.g. if it depends on hash type, attack mode, dict size etc etc.
Did this problem appear after you installed a new driver? New oclHashcat-lite? Are you on a 32/64 bit system? For example, try to run 32bit on 64 system etc. What about oclHashcat-plus ? Same problem here?
We need to pinpoint this further...
Ps. also see this thread: https://hashcat.net/forum/thread-2325-post-13969.html . We first tought this has definitely to do w/ oclhashcat-plus, but the problem was resolved just by (manually) installing a *clean* version of catalyst 13.1 (therefore the problem was not oclhashcat ;-) )
did you try also w/ catalyst 13.1 (http://support.amd.com/us/gpudownload/wi...6&rev=13.1 ) as suggested in GPU Driver and SDK Requirements here: https://hashcat.net/oclhashcat-lite/ ?
I think this is the only (officially) supported driver for oclHashcat-lite (for now!).
Furthermore, you should tell us if this behaviour is "new" or if you experienc(ed) it also w/ other/older oclHashcat versions.
It would be also interesting if oclHashcat-lite was/is able to recover hashes before crashing and if it happens only w/ specific commands, e.g. if it depends on hash type, attack mode, dict size etc etc.
Did this problem appear after you installed a new driver? New oclHashcat-lite? Are you on a 32/64 bit system? For example, try to run 32bit on 64 system etc. What about oclHashcat-plus ? Same problem here?
We need to pinpoint this further...
Ps. also see this thread: https://hashcat.net/forum/thread-2325-post-13969.html . We first tought this has definitely to do w/ oclhashcat-plus, but the problem was resolved just by (manually) installing a *clean* version of catalyst 13.1 (therefore the problem was not oclhashcat ;-) )