Every answer below was written for one of these:

• fglrx, AMD's proprietary Linux driver, replaced by ROCm and the open kernel driver
• AMD Catalyst and its amdconfig and aticonfig tools
• ADL, the AMD Display Library, which is where the FanSpeed_Get and ADL_Overdrive5 errors come from. hashcat still loads ADL for the old Overdrive 5 and 6 cards on Windows, but the device-matching failures below belonged to multi-GPU rigs of that era
• ForceWare, the old name for the NVIDIA driver
• precompiled .ptx kernel containers, from before hashcat compiled its kernels while it runs

If you hit an error on a current machine, start at How does one install the correct driver for the GPU(s)? in the live FAQ instead. The short version is that a GPU needs two things and not one: the driver, and the compiler that goes with it.

Official SDK ErrorCode: CUDA_ERROR_NO_BINARY_FOR_GPU = 209

This error can simply mean that the version of the driver that you have installed is too old:

• Solution: How does one install the correct driver for the GPU(s)?

However, it can also be worse than just that. The 209 error means that there was no precompiled kernel found in an existing precompiled kernel container file (the ones that end with .ptx). This sometimes happens with new GPUs that are not yet supported by hashcat.

• Solution: Please update your ForceWare driver to the latest one (not the recommended one)

If the problem still exist:

• Solution: Open an issue on github. We will add support for your GPU with the next release.

Official SDK ErrorCode: CUDA_ERROR_FILE_NOT_FOUND = 301

You've unpacked the hashcat.7z archive using the command “7z e”. This destroys the directory structure.

• Solution: Please use the x flag to decompress 7z archives. For example: “7z x”

NVidia added a completely new ShaderModel which is not yet support by hashcat.

• Solution: Please update your ForceWare driver to the latest one (not the recommended one)

If the problem still exist:

• Solution: Open an issue on github. We will add your GPU with the next release.

This is the typical error message you get when you're AMD driver installation is faulty. You need to reinstall the recommended driver (while making sure that there is no older driver libs conflicting with it).

• Solution: I may have the wrong driver installed, what should I do?

This is the typical error message you get when your AMD driver installation is faulty. You need to reinstall the recommended driver.

• Solution: I may have the wrong driver installed, what should I do?

Receiving this error means that hashcat could not detect any capable GPUs in your system. If you are positive that you have capable GPUs you can try the following suggestions to fix your system:

• #define CL_DEVICE_NOT_FOUND -1
• Are you logged in as the user who has opened the X session?
• Did you use “export DISPLAY=:0”?
• Do you have X Authority and/or disable X11 ACLs with “xhost +”?
• Is your display manager configured correctly? (gdm example config: http://www.sch0.org/gdm.conf )
• Did you use the recommended driver (for the hashcat version you use) mentioned on the download page? I may have the wrong driver installed, what should I do?

Official SDK ErrorCode: CL_BUILD_PROGRAM_FAILURE -11

This means you are using an incompatible driver version. Sometimes the structure inside the .llvmir archive changes. This is something the developers of hashcat have no influence on. This structure is dictated by the driver.

• Solution: Make sure you have the latest hashcat version
• Solution: I may have the wrong driver installed, what should I do?

Official ADL SDK ErrorCode: ADL_ERR_INVALID_ADL_IDX -5

The most likely reason of this problem is that hashcat could not perfectly map the found and supported OpenCL devices to the devices that the ADL (AMD Display Library) did find. The main problem here is that ADL and OpenCL do use some different means to describe/priorize/sort/name/identify the different devices.

hashcat does some fuzzy matching to try matching those devices with the best accuracy possible, but still sometimes this fails. It could, for instance, fail when you have a multi-GPU setup where some devices are identical (same model/make etc), and you specify -d 1/-d 2.

There is little hashcat can do to avoid this problem since the bus id and device id are sometimes the same (reported by OpenCL), even if we are dealing with 2 “different” (but similar) GPUs.

A possible workaround is to set the fan manually to 100% and use --hwmon-disable flag in hashcat.

Official ADL SDK ErrorCode: ADL_ERR -1

The most likely reason for this problem is that hashcat could not perfectly map the found and supported OpenCL devices to the devices that the ADL (AMD Display Library) did find. ADL and OpenCL do use some different means to describe/priorize/sort/name/identify the different devices, which can contribute to this problem.

hashcat does some fuzzy matching, due to the lack of a unique and consistent way to identify the devices, to try to match those devices with the best accuracy possible, but still sometimes this fails. It could, for instance, fail when you have a multi-GPU setup where some devices are identical (same model/make etc), and you specify -d 1/-d 2.

There is little hashcat can do to avoid this problem since the bus id and device id are sometimes the same (reported by OpenCL), even if we are dealing with 2 “different” (but similar) GPUs.

In this particular case, hashcat fails to get the temperature of the GPU which uses overdrive 5. This could be because the mapping somehow failed and the device is an overdrive 6 GPU instead or something similar.

A possible workaround is to set the fan manually to 100% and use the --hwmon-disable flag in hashcat.

This is simple. You are using a version of the Nvidia ForceWare driver that is way too old. It is time to update!

• Solution: How does one install the correct driver for the GPU(s)?

This is a typical error with AMD GPUs when using the packaged driver (*.deb package) as “/usr/lib/libOpenCL.so.1” is exchanged by the package.

Solution:

• completely purge fglrx
• apt-get install --reinstall ocl-icd-libopencl1
• service xdm stop
• install driver (not package version: e.g. radeon-crimson-15.12-15.302-151217a-297685e.zip)
• reboot
• service xdm stop
• amdconfig --initial -f --adapter=all
• reboot