hashcat exits without any message or error

[forky]

hello, newbie question.. I am running hashcat as:

Code:

hashcat.exe -m 22000 -a 3 scan.hc22000

or

Code:

hashcat.exe -m 22000 -a 3 scan.hc22000 -1 ?u?d ?1?1?1?1?1?1?1?1

where the content of scan.hc22000 is like:

Code:

WPA*01*701f3dbcbb75ff1bfa1bb22f55972ff1*b4305268925c*92810c252c59*54414c4b54314c4b363839323536***

and I get:

Code:

hashcat (v6.2.5) starting

Unsupported AMD HIP runtime version '0.0.3276' detected! Falling back to OpenCL...

ADL2_Overdrive_Caps(): -8

ADL2_Overdrive_Caps(): -8

ADL2_Overdrive_Caps(): -8

ADL2_Overdrive_Caps(): -8

ADL2_Overdrive_Caps(): -8

ADL2_Overdrive_Caps(): -8

ADL2_Overdrive_Caps(): -8

OpenCL API (OpenCL 2.1 AMD-APP (2841.5)) - Platform #1 [Advanced Micro Devices, Inc.]
=====================================================================================
* Device #1: AMD Radeon Pro WX 3100, 3968/4096 MB (3264 MB allocatable), 8MCU

Minimum password length supported by kernel: 8
Maximum password length supported by kernel: 63

Hashes: 2 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: Temperature abort trigger set to 90c

Initializing backend runtime for device #1. Please be patient...
C:\Users\forky\Downloads\hashcat-6.2.5>

In other words, it exits without any error. I suspect it is something related to the input file, but without any message I am having hard time figuring it out.

Benchmark and example scripts run OK.

Thanks

[forky]

Reading the forum, it looks like this issue is similar.

Sharing my findings, using a macbook pro, compiling from source, I was able to have it running, with the same command and the same input.

By exclusion, there is a problem with the hardware/driver/OS combination. I originally ran it on Windows and an AMD WX3100. Interesting enough, when trying different types of attacks, it works.

Is it possible that this is due to the type of algorithm used? -m 22000?

[forky]

... and in fact, it was a driver issue!!

Re-installing the drivers fixed the issue. The culprit, my guess, was Windows automatic updates.

Hope it helps someone else