11-10-2022, 03:54 AM
I've seen this quite frequently in the past few months. I believe its due to the low amount of memory allocated for your integrated graphics built into the CPU. Hashcat requires RAM as well as VRAM to processes its attacks and many situations where either the self-test fails or seems to never process is either due to improper OpenCL drivers being installed or that there is never enough VRAM for the attack.
As you mentioned, running the attack strictly on CPU side seems to function just dandy, but as soon as you're enabling the graphics processor included within your CPU hashcat does not seem to work. There should be a few threads here regarding this issue in the previous months which I am to occupied to look for at the moment but I'm pretty sure there is a resolution included in several of these post.
As you mentioned, running the attack strictly on CPU side seems to function just dandy, but as soon as you're enabling the graphics processor included within your CPU hashcat does not seem to work. There should be a few threads here regarding this issue in the previous months which I am to occupied to look for at the moment but I'm pretty sure there is a resolution included in several of these post.