02-06-2022, 01:10 AM
(02-03-2022, 04:07 PM)Snoopy Wrote: well im really sorry, but i cannot help you any further with this
maybe it is driver related or hardware , its hard to test from "far away"
the only thing you maybe could test is the following, hashcat will use the cuda backend by default, but you could try to force hahscat to use the opencl instead, given your example from above you have to add options
Code:-D2 -d2
to your command line, if this also results in instant blackscreen i dont have any clue other than, yeah well thats personal computers, dont know what they are goood for and what they are doing
Thanks, seems like I didn't got any crash with OpenCL. However I still have some errors, I'll try to make a clean install of my drivers (again). This is the errors I got on some benchmarks:
Code:
-------------------------------------------------------------
* Hash-Mode 22000 (WPA-PBKDF2-PMKID+EAPOL) [Iterations: 4095]
-------------------------------------------------------------
clCreateKernel(): CL_INVALID_KERNEL_NAME
* Device #2: Kernel amp create failed.
-----------------------
* Hash-Mode 1000 (NTLM)
-----------------------
Speed.#2.........: 23435.4 MH/s (8.47ms) @ Accel:64 Loops:256 Thr:256 Vec:1
---------------------
* Hash-Mode 3000 (LM)
---------------------
* Device #2: ATTENTION! OpenCL kernel self-test failed.
Your device driver installation is probably broken.
See also: https://hashcat.net/faq/wrongdriver