New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stuck on "Initializing device kernels and memory..." when trying to crack WPA2 #1714

Open
steamp0rt opened this Issue Oct 6, 2018 · 6 comments

Comments

Projects
None yet
3 participants
@steamp0rt

steamp0rt commented Oct 6, 2018

GPU: RX 580
OS: Windows 10 1809
Drivers: Adrenalin 18.9.3
Hashcat Version: 4.2.1

D:\Programs\Hashcat> .\hashcat64.exe -m 2500 WPA-01.hccapx rockyou.txt
hashcat (v4.2.1) starting...

OpenCL Platform #1: Advanced Micro Devices, Inc.
================================================
* Device #1: Ellesmere, 3264/4096 MB allocatable, 36MCU

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

Applicable optimizers:
* Zero-Byte
* Single-Salt
* Slow-Hash-SIMD-LOOP

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

Watchdog: Temperature abort trigger set to 90c

Initializing device kernels and memory...
D:\Programs\Hashcat>

However, non-WPA2 works, such as SHA1

@steamp0rt

This comment has been minimized.

Show comment
Hide comment
@steamp0rt

steamp0rt Oct 7, 2018

Hashcat 3.6.0 works with WPA2.

steamp0rt commented Oct 7, 2018

Hashcat 3.6.0 works with WPA2.

@philsmd

This comment has been minimized.

Show comment
Hide comment
@philsmd

philsmd Oct 12, 2018

Member

it's probably a driver issue. Did you try to reinstall the driver for instance by following this guide https://hashcat.net/wiki/doku.php?id=frequently_asked_questions#i_may_have_the_wrong_driver_installed_what_should_i_do

Furthermore, did you try with different driver versions? Does it really depend only on the hashcat version or is that just a coincident (because the OpenCL kernel code changed for WPA between hashcat versions 3.6.0 and 4.2.1).

You say it is stuck... How long did you wait? Do you see any new files created within the kernels\ folder while it is initializing ?

Did you try to downloading a fresh version of hashcat (within a new folder) and try again ? Did you try using the beta version of hashcat from https://hashcat.net/beta/ ?

Member

philsmd commented Oct 12, 2018

it's probably a driver issue. Did you try to reinstall the driver for instance by following this guide https://hashcat.net/wiki/doku.php?id=frequently_asked_questions#i_may_have_the_wrong_driver_installed_what_should_i_do

Furthermore, did you try with different driver versions? Does it really depend only on the hashcat version or is that just a coincident (because the OpenCL kernel code changed for WPA between hashcat versions 3.6.0 and 4.2.1).

You say it is stuck... How long did you wait? Do you see any new files created within the kernels\ folder while it is initializing ?

Did you try to downloading a fresh version of hashcat (within a new folder) and try again ? Did you try using the beta version of hashcat from https://hashcat.net/beta/ ?

@steamp0rt

This comment has been minimized.

Show comment
Hide comment
@steamp0rt

steamp0rt Oct 12, 2018

It says "15.12 or later"... and I have 18.9.3

steamp0rt commented Oct 12, 2018

It says "15.12 or later"... and I have 18.9.3

@steamp0rt

This comment has been minimized.

Show comment
Hide comment
@steamp0rt

steamp0rt Oct 12, 2018

Also, yes, the beta works for some reason...

steamp0rt commented Oct 12, 2018

Also, yes, the beta works for some reason...

@SnakePin

This comment has been minimized.

Show comment
Hide comment
@SnakePin

SnakePin Oct 14, 2018

Can confirm, same problem happens with RX580 8GB and 18.10.1. And beta only works when --self-test-disable is present.

SnakePin commented Oct 14, 2018

Can confirm, same problem happens with RX580 8GB and 18.10.1. And beta only works when --self-test-disable is present.

@SnakePin

This comment has been minimized.

Show comment
Hide comment
@SnakePin

SnakePin Oct 14, 2018

And also it is not stuck on that text, program just quits after that text is displayed if you look closely to the console log.

SnakePin commented Oct 14, 2018

And also it is not stuck on that text, program just quits after that text is displayed if you look closely to the console log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment