Hashcat hangs at Initializing backend runtime for device #X... "forever"

Hashcat hangs at Initializing backend runtime for device #X... "forever" - Printable Version

+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Support (https://hashcat.net/forum/forum-3.html)
+--- Forum: hashcat (https://hashcat.net/forum/forum-45.html)
+--- Thread: Hashcat hangs at Initializing backend runtime for device #X... "forever" (/thread-9662.html)

Pages: 1 2

Hashcat hangs at Initializing backend runtime for device #X... "forever" - dydx - 11-24-2020

Hello,

I am using hashcat on Win10 (I tried in on my linux machine but I have no GPU there and no CPU device if found either). (The Win machine, being an older laptop I know it's not the optimal machine for hashcat but I just need to iterate over a few thousand passwords)

Unfortunately hashcat hangs "forever" at

Code:
Hashcat hangs at Initializing backend runtime for device #X...

"Forever" means 10-15 minutes which feels like an eternity (I have to loop over a bunch of hash modes and --truecrypt-keyfiles so 10 min startup is somewhat problematic). I have two devices (GPU and CPU) and it does not matter which one I pick with "-D".

Is this normal or is something wrong here?

These are my devices:

Code:
hashcat -I

hashcat (v6.1.1) starting...

OpenCL Info:

============

OpenCL Platform ID #1

  Vendor..: Intel(R) Corporation

  Name....: Intel(R) OpenCL

  Version.: OpenCL 1.2

  Backend Device ID #1

    Type...........: CPU

    Vendor.ID......: 8

    Vendor.........: Intel(R) Corporation

    Name...........: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz

    Version........: OpenCL 1.2 (Build 76427)

    Processor(s)...: 4

    Clock..........: 2600

    Memory.Total...: 16075 MB (limited to 4018 MB allocatable in one block)

    Memory.Free....: 16011 MB

    OpenCL.Version.: OpenCL C 1.2

    Driver.Version.: 3.0.1.10891

  Backend Device ID #2

    Type...........: GPU

    Vendor.ID......: 8

    Vendor.........: Intel(R) Corporation

    Name...........: Intel(R) HD Graphics 4000

    Version........: OpenCL 1.2

    Processor(s)...: 16

    Clock..........: 1200

    Memory.Total...: 1400 MB (limited to 350 MB allocatable in one block)

    Memory.Free....: 1336 MB

    OpenCL.Version.: OpenCL C 1.2

    Driver.Version.: 10.18.10.4358

Thanks!

RE: Hashcat hangs at Initializing backend runtime for device #X... "forever" - bumbaras - 04-12-2021

I have the same problem. CPU i5-3230M on ivy bridge and OpenCL 1.2. I tried with 6.1.1 and 6.1.1+200.
Gpu is HD4000 and is not compatibile with hashcat. System Windows 7x64 SP1.
Didn't pass Initializing backend runtime for device #X ...
CPU is hogged at 25% (one thread busy) all time.

I tried on other machine with i7 of newer generation and AMD GPU and setting -D 1 -d 1 took this machine to start computing on CPU from "Initializing backend runtime for device #X" in less than minute.

RE: Hashcat hangs at Initializing backend runtime for device #X... "forever" - oleedee - 04-15-2021

I have similar issue, any help please?

Code:
* Device #1: CUDA SDK Toolkit installation NOT detected.

            CUDA SDK Toolkit installation required for proper device support and utilization

            Falling back to OpenCL Runtime

* Device #1: WARNING! Kernel exec timeout is not disabled.

            This may cause "CL_OUT_OF_RESOURCES" or related errors.

            To disable the timeout, see: https://hashcat.net/q/timeoutpatch

OpenCL API (OpenCL 3.0 CUDA 11.3.70) - Platform #1 [NVIDIA Corporation]

=======================================================================

* Device #1: NVIDIA GeForce RTX 2070, 7104/8192 MB (2048 MB allocatable), 36MCU

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

Rules: 1

Applicable optimizers applied:

* Zero-Byte

* Single-Hash

* Single-Salt

Watchdog: Temperature abort trigger set to 90c

Initializing backend runtime for device #1...

RE: Hashcat hangs at Initializing backend runtime for device #X... "forever" - oleedee - 04-15-2021

(04-15-2021, 12:39 PM)oleedee Wrote: I have similar issue, any help please?

Code:
* Device #1: CUDA SDK Toolkit installation NOT detected. CUDA SDK Toolkit installation required for proper device support and utilization Falling back to OpenCL Runtime * Device #1: WARNING! Kernel exec timeout is not disabled. This may cause "CL_OUT_OF_RESOURCES" or related errors. To disable the timeout, see: https://hashcat.net/q/timeoutpatch OpenCL API (OpenCL 3.0 CUDA 11.3.70) - Platform #1 [NVIDIA Corporation] ======================================================================= * Device #1: NVIDIA GeForce RTX 2070, 7104/8192 MB (2048 MB allocatable), 36MCU 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 Rules: 1 Applicable optimizers applied: * Zero-Byte * Single-Hash * Single-Salt Watchdog: Temperature abort trigger set to 90c Initializing backend runtime for device #1...

getting visual studio from here: https://visualstudio.microsoft.com/downloads/
apparently Cuda requires this..
and Nvidea Cuda from here: https://developer.nvidia.com/cuda-downloads
will try run after

RE: Hashcat hangs at Initializing backend runtime for device #X... "forever" - storax80 - 04-17-2021

Same problem. Work fine 10 days ago, suddenly stop working, no hardware changes. Win10, ryzen 5, 16gb ram, GeForce RTX 2070

Another machine Win10, Amd FX, 8gb ram, gforce 1030, same problem.

Another, Laptop, Win10, Pentium Gold, 8gb ram, HD610, same problem.

Another, Win10, AMD APU A10, 8gb ram, RX550 same problem

in all the machines it worked before....

RE: Hashcat hangs at Initializing backend runtime for device #X... "forever" - csrx - 04-20-2021

(04-17-2021, 12:50 AM)storax80 Wrote: Same problem. Work fine 10 days ago, suddenly stop working, no hardware changes. Win10, ryzen 5, 16gb ram, GeForce RTX 2070

Another machine Win10, Amd FX, 8gb ram, gforce 1030, same problem.

Another, Laptop, Win10, Pentium Gold, 8gb ram, HD610, same problem.

Another, Win10, AMD APU A10, 8gb ram, RX550 same problem

in all the machines it worked before....

i had the same problem, i did a downgrade from my driver video and works again...

RE: Hashcat hangs at Initializing backend runtime for device #X... "forever" - HelmanFrow - 03-19-2022

Same here. Stuck on 'Initializing backend for device #1".
ThinkPad P50 with Quadro M1000M.

RE: Hashcat hangs at Initializing backend runtime for device #X... "forever" - slavikfoxy - 03-20-2022

hashcat (v6.2.5) starting

Successfully initialized NVIDIA CUDA library.

Failed to initialize NVIDIA RTC library.

* Device #1: CUDA SDK Toolkit not installed or incorrectly installed.
CUDA SDK Toolkit required for proper device support and utilization.
Falling back to OpenCL runtime.

* Device #1: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
OpenCL API (OpenCL 3.0 CUDA 11.6.110) - Platform #1 [NVIDIA Corporation]
========================================================================
* Device #1: NVIDIA GeForce 940MX, 1728/2047 MB (511 MB allocatable), 3MCU

OpenCL API (OpenCL 3.0 ) - Platform #2 [Intel(R) Corporation]
=============================================================
* Device #2: Intel(R) HD Graphics 620, 1568/3240 MB (810 MB allocatable), 23MCU

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

Hashes: 19 digests; 19 unique digests, 19 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 1

Optimizers applied:
* Zero-Byte
* Slow-Hash-SIMD-LOOP

Watchdog: Hardware monitoring interface not found on your system.
Watchdog: Temperature abort trigger disabled.

Initializing backend runtime for device #1. Please be patient...

Lenovo ideapad 320-15ikb - 940mx, 8gb ram, i3-7130u, windows 10 pro
updated the video driver, it did not start with version 6.0.0, tested on several versions.

RE: Hashcat hangs at Initializing backend runtime for device #X... "forever" - Snoopy - 03-21-2022

(03-20-2022, 05:39 PM)slavikfoxy Wrote: hashcat (v6.2.5) starting

Successfully initialized NVIDIA CUDA library.

Failed to initialize NVIDIA RTC library.

* Device #1: CUDA SDK Toolkit not installed or incorrectly installed.
CUDA SDK Toolkit required for proper device support and utilization.
Falling back to OpenCL runtime.

Install Cuda SDK and it should work

RE: Hashcat hangs at Initializing backend runtime for device #X... "forever" - Snoopy - 03-21-2022

(11-24-2020, 09:43 PM)dydx Wrote:
Code:
hashcat -I hashcat (v6.1.1) starting... OpenCL Info: ============ OpenCL Platform ID #1 Vendor..: Intel(R) Corporation Name....: Intel(R) OpenCL Version.: OpenCL 1.2 Backend Device ID #1 Type...........: CPU Vendor.ID......: 8 Vendor.........: Intel(R) Corporation Name...........: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz Version........: OpenCL 1.2 (Build 76427) Processor(s)...: 4 Clock..........: 2600 Memory.Total...: 16075 MB (limited to 4018 MB allocatable in one block) Memory.Free....: 16011 MB OpenCL.Version.: OpenCL C 1.2 Driver.Version.: 3.0.1.10891 Backend Device ID #2 Type...........: GPU Vendor.ID......: 8 Vendor.........: Intel(R) Corporation Name...........: Intel(R) HD Graphics 4000 Version........: OpenCL 1.2 Processor(s)...: 16 Clock..........: 1200 Memory.Total...: 1400 MB (limited to 350 MB allocatable in one block) Memory.Free....: 1336 MB OpenCL.Version.: OpenCL C 1.2 Driver.Version.: 10.18.10.4358

Thanks!

6.1.1 is old, update to 6.2.5

next, OpenCL 1.2 tells me you didnt install

Intel CPUs require "OpenCL Runtime for Intel Core and Intel Xeon Processors" (16.1.1 or later)

as statet on the hashcat landingpage

install this, this will get you to opencl 2.1 at least and the problem will be gone

see

https://hashcat.net/forum/thread-10548.html

*ttp://registrationcenter-download.intel.com/akdlm/irc_nas/vcp/13794/opencl_runtime_18.1_x64_setup.msi

EDIT: you have to stick to CPU because the openCL Intel integrated GPU runtime is broken (maybe you need to uninstall UHD graphicdrivers from windows, before you can install this opencl cpu driver)