probably a user error
#1
I am a first time user just messing around and when I attempt to start hashcat on windows 11 then I get the following message:

hashcat (v6.2.6) starting

* Device #1: WARNING! Kernel exec timeout is not disabled.
            This may cause "CL_OUT_OF_RESOURCES" or related errors.
            To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #2: WARNING! Kernel exec timeout is not disabled.
            This may cause "CL_OUT_OF_RESOURCES" or related errors.
            To disable the timeout, see: https://hashcat.net/q/timeoutpatch

C:\Users\corym\Downloads\hashcat-6.2.6\hashcat-6.2.6>


I did the wddm_timeout_patch.reg steps and still get the same error
Reply
#2
What is your command you're entering? Also please post hashcat -I
Reply
#3
Not sure if you just wanted me to put in "hashcat -I" but when I did it only replied "starting in backend information mode"

hashcat -m 14800 -a3 -1 ?d?s P@ssWord123?1?1 test.txt
hashcat (v6.2.6) starting

* Device #1: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #2: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch

C:\Users\user\Downloads\hashcat-6.2.6\hashcat-6.2.6>hashcat -I
hashcat (v6.2.6) starting in backend information mode


C:\Users\user\Downloads\hashcat-6.2.6\hashcat-6.2.6>
Reply
#4
If it isn't starting your attack or even producing any information I'd say you have an issue with your drivers. What is your PC's hardware? I would start by installing any GPU drivers and see if hashcat -I produces any results. It is detecting 2 devices but obviously crashing by the looks of things.
Reply
#5
I just updated the NVidia drivers that were updated as of 9 May and I have this machine
MSI - Infinite RS Gaming Desktop - Intel Core i9-13900KF - 32GB Memory - NVIDIA GeForce RTX 4090 - 2TB SSD + 2TB HD
Reply
#6
You have any ideas on anything I could try?
Reply
#7
It's the stupid Windows 10/11 OpenCL runtime they are bundling into DirectX now. It causes a crash on launch that isn't resolved yet. Adding --backend-ignore-opencl to your command and just using CUDA will allow hashcat to function fine until we figure out how to avoid or perhaps uninstall the conflicting runtime.
Reply