Hashcat stuck at "Initialized device kernels and memory"

[ztilB]

Hi, I'm using hashcat in command prompt as administrator in Windows 10.

When I enter the following line in version 6.2.6:

Code:

hashcat.exe -a 3 -m 9400 -o pass.txt hash.txt ?a?a?a?a --increment

...it runs for a very short while and just stops at initiating self-test. Here's the command prompt:

Code:

hashcat.exe -a 3 -m 9400 -o pass.txt hash.txt ?a?a?a?a --increment hashcat (v6.2.6) starting OpenCL API (OpenCL 1.2 ) - Platform #1 [Intel(R) Corporation] ============================================================= * Device #1: Intel(R) UHD Graphics 600, 736/1567 MB (391 MB allocatable), 12MCU * Device #2: Intel(R) Celeron(R) N4000 CPU @ 1.10GHz, skipped Minimum password length supported by kernel: 0 Maximum password length supported by kernel: 256 Hashes: 1 digests; 1 unique digests, 1 unique salts Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates Optimizers applied: * Zero-Byte * Single-Hash * Single-Salt * Brute-Force * Slow-Hash-SIMD-LOOP Watchdog: Hardware monitoring interface not found on your system. Watchdog: Temperature abort trigger disabled. Host memory required for this attack: 141 MB Starting self-test. Please be patient...

When pressing a key, the menu

Code:

[s]tatus [p]ause [b]ypass [c]heckpoint [f]inish [q]uit =>

appears but nothing happens no matter what I do.

To counter this I added the

Code:

--self-test-disable

option, but this time it gets stuck at

Code:

Initialized device kernels and memory

! I've also tried the command in version 6.2.5, and the exact same thing happens.

Here's the command prompt for detail:

Code:

hashcat.exe -a 3 -m 9400 -o pass.txt hash.txt ?a?a?a?a --increment --self-test-disable hashcat (v6.2.5) starting OpenCL API (OpenCL 1.2 ) - Platform #1 [Intel(R) Corporation] ============================================================= * Device #1: Intel(R) UHD Graphics 600, 736/1567 MB (391 MB allocatable), 12MCU * Device #2: Intel(R) Celeron(R) N4000 CPU @ 1.10GHz, skipped Minimum password length supported by kernel: 0 Maximum password length supported by kernel: 256 Hashes: 1 digests; 1 unique digests, 1 unique salts Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates Optimizers applied: * Zero-Byte * Single-Hash * Single-Salt * Brute-Force * Slow-Hash-SIMD-LOOP Watchdog: Hardware monitoring interface not found on your system. Watchdog: Temperature abort trigger disabled. Host memory required for this attack: 141 MB Initialized device kernels and memory

Any help would be VERY appreciated, thank you!

[marc1n]

hashcat -I and paste score here

[ztilB]

Here it is:

Code:

hashcat (v6.2.6) starting in backend information mode OpenCL Info: ============ OpenCL Platform ID #1 Vendor..: Intel(R) Corporation Name....: Intel(R) OpenCL Version.: OpenCL 1.2 Backend Device ID #1 Type...........: GPU Vendor.ID......: 8 Vendor.........: Intel(R) Corporation Name...........: Intel(R) UHD Graphics 600 Version........: OpenCL 1.2 NEO Processor(s)...: 12 Clock..........: 650 Memory.Total...: 1567 MB (limited to 391 MB allocatable in one block) Memory.Free....: 736 MB Local.Memory...: 64 KB OpenCL.Version.: OpenCL C 1.2 Driver.Version.: 23.20.16.4936 Backend Device ID #2 Type...........: CPU Vendor.ID......: 8 Vendor.........: Intel(R) Corporation Name...........: Intel(R) Celeron(R) N4000 CPU @ 1.10GHz Version........: OpenCL 1.2 (Build 611) Processor(s)...: 2 Clock..........: 1100 Memory.Total...: 3919 MB (limited to 489 MB allocatable in one block) Memory.Free....: 1927 MB Local.Memory...: 32 KB OpenCL.Version.: OpenCL C 1.2 Driver.Version.: 7.6.0.611

It works when using CPU only in version 6.2.5, but is there a way to resolve this while also using GPU?

[slyexe]

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.