Table of Contents

Timeout Fix

Note: You see some warning like “WARNING! Kernel exec timeout is not disabled, it might cause you errors of code 702” , then you should try to apply the registry patch on windows or changes to xorg.conf on linux.

Note: Since hashcat v3.20 (actually since hashcat v3.00) this warning is no longer required since the autotune engine will make sure the kernel runtime will stay below 1 second.


While running oclHashcat at extreme settings users may experience crashes, followed by automatic recoveries of the GPU(s) through driver resets. This is a useful feature to prevent freezes, but not for hashcracking. It is caused by kernel runtimes exceeding 2 seconds.


Timeout Registry Patch

Note: this should work starting with windows vista (also with all server variants).

To disable WDDM recovery, create a file called patch.reg, paste the contents of the code there, run as admin, reboot and enjoy!

Windows Registry Editor Version 5.00


WDDM explainedRolf 2011/09/24 14:33


Add a line “Interactive” in /etc/X11/xorg.conf:

Section "Device"
    Identifier     "Device0"
    Option         "Interactive"        "False"

You might need to restart X11 or reboot your system entirely before this change works and the warning in oclHashcat disappears.

Newer versions of Ubuntu (and maybe other distributions as well) do not use xorg.conf any longer. Alternatively they use the folder /usr/share/x11/xorg.conf.d/ where you can put in snippets of the config. Create a new file, call it “20-nvidia.conf” and put in the following content:

Section "Device"
Identifier "MyGPU"
Driver "nvidia"
Option "Interactive" "0"

You may need to restart the system afterwards.