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.

Search Results
Post Author [desc] Forum Replies Views Posted
    Thread: hashcat v3.00 + older nvidia
Post: RE: hashcat v3.00

rico Wrote: (06-29-2016, 11:02 PM) -- > Note that with older NVidia GPUs, and by old I mean before maxwell chipsets, there is a drop in performance. You weren't kidding, WPA hashrate down 43% on m...
atom hashcat 4 7,432 06-29-2016, 11:27 PM
    Thread: What means "1024/4096 MB allocatable"
Post: RE: What means "1024/4096 MB allocatable"

OpenCL has a bit a strange policy on memory allocation: Quote: -- Max size of memory object allocation in bytes. The minimum value is max (1/4th of CL_DEVICE_GLOBAL_MEM_SIZE, 128*1024*1024) --...
atom hashcat 1 4,416 06-30-2016, 08:53 AM
    Thread: hashcat v3.00 error
Post: RE: hashcat v3.00 error

Please try again and add --gpu-temp-disable
atom hashcat 3 4,694 06-30-2016, 08:54 AM
    Thread: hashcat v3.00 + older nvidia
Post: RE: hashcat v3.00 + older nvidia

Did you use -w 3 ?
atom hashcat 4 7,432 06-30-2016, 08:57 AM
    Thread: hashcat v3.00 + The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali)
Post: RE: hashcat v3.00 + The-Distribution-Which-Does-No...

Try with --gpu-temp-disable if this does any change
atom hashcat 4 6,451 06-30-2016, 08:58 AM
    Thread: hashcat v3.00 + bcrypt
Post: RE: hashcat v3.00 + bcrypt

It's unknown yet, happend after the move from CUDA to OpenCL. I will look into it when I have some time
atom hashcat 2 4,334 06-30-2016, 09:01 AM
    Thread: Hashcat 3.0 inc_vendor.cl missing
Post: RE: Hashcat 3.0 inc_vendor.cl missing

Look like AMDs OpenCL runtime (on windows only) silently ignores the -I parameter. It's configured correctly, as you can see in the debug output: Quote: -- -I "C:/Users/tv/Desktop/HTPHashcat3/ha...
atom hashcat 23 39,240 06-30-2016, 09:05 AM
    Thread: hashcat v3.00 + ntlm performance
Post: RE: hashcat v3.00 + ntlm performance

It was always that fast (in oclHashcat), I just didn't backport the optimizations to hashcat-legacy. If you want to know more about the partial reversal used read this: https://hashcat.net/events/p13/...
atom hashcat 1 3,354 06-30-2016, 09:07 AM
    Thread: Hashcat 3.0 inc_vendor.cl missing
Post: RE: Hashcat 3.0 inc_vendor.cl missing

Maybe a general AMD + windows problem?
atom hashcat 23 39,240 06-30-2016, 09:46 AM
    Thread: Hashcat 3.0 inc_vendor.cl missing
Post: RE: Hashcat 3.0 inc_vendor.cl missing

l30n Wrote: (06-30-2016, 09:51 AM) -- Well, I don't have AMD Quote: -- OpenCL Platform #1: Intel(R) Corporation ======================================== - Device #1:        Intel(R) Core(...
atom hashcat 23 39,240 06-30-2016, 09:53 AM
    Thread: Hashcat 3.0 inc_vendor.cl missing
Post: RE: Hashcat 3.0 inc_vendor.cl missing

Good because I tested the CPU version of Intel myself and it worked. However I did not test the GPU version. So that means both AMD and Intel (at least the GPU part) have a different JIT than NVidia f...
atom hashcat 23 39,240 06-30-2016, 10:14 AM
    Thread: Hashcat 3.0 inc_vendor.cl missing
Post: RE: Hashcat 3.0 inc_vendor.cl missing

winxp5421 Wrote: (06-30-2016, 11:59 AM) -- i have 5 machines total 3 are windows 10 and 2 are windows 7. windows 10 machine one (nvidia) no issues windows 10 machine two (amd) catalyst 15.12 missin...
atom hashcat 23 39,240 06-30-2016, 12:27 PM
    Thread: Cannot execute hashcat v3.00
Post: RE: Cannot execute hashcat v3.00

Both errors go back to some broken OpenCL installation
atom hashcat 4 6,943 06-30-2016, 12:33 PM
    Thread: Cannot execute hashcat v3.00
Post: RE: Cannot execute hashcat v3.00

Cool, thanks for reporting back
atom hashcat 4 6,943 06-30-2016, 05:08 PM
    Thread: Hashcat 3.0 inc_vendor.cl missing
Post: RE: Hashcat 3.0 inc_vendor.cl missing

That could explain it. Can you completely uninstall in one of the windows 7 machines the drivers. Also make sure the OpenCL.dll is removed (I think it will be not uninstalled). Then remove it by hand,...
atom hashcat 23 39,240 06-30-2016, 05:11 PM
    Thread: MBP not enough allocatable device-memory
Post: RE: MBP not enough allocatable device-memory

Quote: -- - Device #2: Device does not provide enough allocatable device-memory to handle this attack -- This kind of error is actually that you do not have enough (device) memory to handle scr...
atom hashcat 1 5,089 07-01-2016, 09:05 AM
    Thread: hashcat v3.00 + The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali)
Post: RE: hashcat v3.00 + The-Distribution-Which-Does-No...

OK I think we need to go more deep into debugging here. It's important hashcat works fine on The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali). However this should be done on GitHub. Can you p...
atom hashcat 4 6,451 07-01-2016, 09:07 AM
    Thread: ERROR: clCreateContext() : -2 : CL_UNKNOWN_ERROR
Post: RE: ERROR: clCreateContext() : -2 : CL_UNKNOWN_ERR...

It's a pure OpenCL runtime error. Not Hashcat fault, 100%. Sorry. All I can think of is to true a different OpenCL runtime. For example POCL, but that requires you to install Linux.
atom hashcat 5 7,908 07-01-2016, 09:09 AM
    Thread: AMD RX480 performance?
Post: RE: AMD RX480 performance?

Thanks for benchmark, good to have a reference.
atom Hardware 18 38,801 07-01-2016, 09:11 AM
    Thread: hashcat v3.00 - Is this the reasonable speed on Mac?
Post: RE: hashcat v3.00 - Is this the reasonable speed o...

This is wrong, for sure, and for sure it's an OpenCL runtime error. We have no influence on this, you need to report to NVidia. Until they release an updated version you can use -D 1 to use your CPU.
atom hashcat 3 5,108 07-01-2016, 09:29 AM