Please note, this is a STATIC archive of website hashcat.net from October 2020, cach3.com does not collect or store any user information, there is no "phishing" involved.

hashcat Forum

Full Version: Win10 x64 crashes on multiple hash types
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I have a GTX970 with the newest drivers and I installed the CUDA SDK. When using -m 500 or -m 1800 I get the following output and then it exits. Am I missing something with the setup? The token length is ok as I have two different hashes in the same file so its skipping the one of the opposite mode.

Thanks in advance.

Code:
>hashcat -D1 -m1800 hashes rockyou.txt
hashcat (v6.0.0) starting...

CUDA API (CUDA 11.0)
====================
* Device #1: GeForce GTX 970, skipped

OpenCL API (OpenCL 1.2 CUDA 11.0.197) - Platform #1 [NVIDIA Corporation]
========================================================================
* Device #2: GeForce GTX 970, skipped

OpenCL API (OpenCL 1.2 ) - Platform #2 [Intel(R) Corporation]
=============================================================
* Device #3: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz, 24394/24458 MB (6114 MB allocatable), 8MCU
* Device #4: Intel(R) HD Graphics 4000, skipped

Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 256

Hashfile 'hashes' on line 2 (xxxxx...xxxxxxxxx:18120:0:99999:7:::): Token length exception
Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 1

Applicable optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
* Uses-64-Bit

ATTENTION! Pure (unoptimized) backend kernels selected.
Using pure kernels enables cracking longer passwords but for the price of drastically reduced performance.
If you want to switch to optimized backend kernels, append -O to your commandline.
See the above message to find out about the exact limits.

Watchdog: Temperature abort trigger set to 90c

clBuildProgram(): CL_BUILD_PROGRAM_FAILURE

Compilation started
In file included from :10:
OpenCL\inc_common.cl:1333:24: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1334:24: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1335:24: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1336:24: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1337:24: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1338:24: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1339:24: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1340:24: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1387:19: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1388:19: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1389:19: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1390:19: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1391:19: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1392:19: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1393:19: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1394:19: error: 'long long' type is invalid in OpenCL
Compilation failed

* Device #3: Kernel ./OpenCL/shared.cl build failed.

Started: Thu Jul 16 18:19:01 2020
Stopped: Thu Jul 16 18:19:03 2020
It would probably help if you were using the 970, but you aren't in that paste, you are specifying that it try and use your CPU instead. Remove -D1 and try again.
Without the -D it seems to try to use device 4. Is that possibly due to running something else using the GPU? I see #4 during the initializing backend runtime step. It also seems to hang there for awhile.

edit: using -d 1 chose the GPU and seemed to work ok.