+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Support (https://hashcat.net/forum/forum-3.html)
+--- Forum: hashcat (https://hashcat.net/forum/forum-45.html)
+--- Thread: hashcat ends without error message (/thread-8417.html)
hashcat ends without error message - HashTaeg03 - 06-10-2019
Hello
i try to run hashcat64.exe on a Windows 10 OS.
But hashcat ends after the "Initializing OpenCL runtime for device #1..." to command line without any error message.
I went twice trough "I may have the wrong driver installed, what should I do?" I try it with the Crimson 16.11.5 and 17.11.4 without success.
What else am I still trying to do
Thx
RE: hashcat ends without error message - philsmd - 06-12-2019
in general these are problems with drivers. maybe you have some further drivers installed e.g. for your OpenCL CPU etc.
I think driver fusion and/or ddu (Display Driver Uninstaller) might help you after removing the driver by uninstalling them all (Control Panel). sometimes some OpenCL related .dll are still available after uninstalling so you might manually delete them as mentioned in the FAQ https://hashcat.net/wiki/doku.php?id=frequently_asked_questions#i_may_have_the_wrong_driver_installed_what_should_i_do
RE: hashcat ends without error message - HashTaeg03 - 06-12-2019
I have done everything as described in your link.
I found out that it works with version 4.2.1 without any problems. With version 5.0.0 and 5.1.0 it doesn't work.
RE: hashcat ends without error message - philsmd - 06-12-2019
would be actually quite interesting to debug this to find out who the culprit is here.
Did you try to test it with all the GPUs (physically) removed ? does it also crash with only the CPU within your system.
I think under windows you can see which dll are loaded with process monitor . could be interesting to see what is loaded (most importantly of course the OpenCL related drivers).
It could maybe work if you re-install windows etc... but I guess that's not an option for you. Furthermore, it would be also quite interesting to troubleshoot this system just to make sure which driver problem is able to stop the process entirely from running (which on its own is very strange/rare)