Hashcat and R9 390

[KSK_Nico]

Hello,
this is my first post here so I'm pretty knew when it comes to hashcat.
I have a R9 390 AMD GPU and want to crack a hccapx with a WPA handshake on Windows 10. Everytime I run this command

Code:

.\hashcat64.exe -m 2500 -a 3 .\example.hccapx -1 0123456789 ?1?1?1?1?1?1?1?1?1

it shows me the following error message:

Code:

hashcat (v5.1.0-267-ga01142ef) starting...

OpenCL Platform #1: Advanced Micro Devices, Inc.
================================================
* Device #1: Hawaii, 4048/8192 MB allocatable, 40MCU

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

Applicable optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
* Brute-Force
* 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

* Device #1: ATTENTION! OpenCL kernel self-test failed.

Your device driver installation is probably broken.
See also: https://hashcat.net/faq/wrongdriver

Aborting session due to kernel self-test failure.

You can use --self-test-disable to override this, but do not report related errors.

When I try to run it with

Code:

--self-test-disable

it only runs at about 179 kH/s with little to no GPU load only taking up 3.5/8 GB GPU memory.
I have already checked my drivers (Radeon software version 19.1.1 and OpenCL 25.20.15011.1004). 


I would appreciate if someone could help in case he was in a similair situation.

[DanielG]

Your device driver installation is probably broken.
See also: https://hashcat.net/faq/wrongdriver

[KSK_Nico]

I took a look and the drivers are up to date. Also reinstalling didn't fix the issue. I'm coming to the conclusion that there's no other option for me to just wait until AMD has fixed their drivers. Thank you anyway.

[esphack]

I took a look and the drivers are up to date. Also reinstalling didn't fix the issue. I'm coming to the conclusion that there's no other option for me to just wait until AMD has fixed their drivers. Thank you anyway.

AMD driver updates routinely break things afaik, mine was working fine with --selftest-disable on 18.12.3 but updating to 19.1.1 and 19.1.2 broke the openCL runtime and i got a similar error as you did, but apparently you had it working on 19.1.2 so what gives, running an rx570 8gb here

btw the speeds seem normal to me, around 140 to 150khs is what i get at 1050 to 1160mhz core, 100% utilization

also the temp limit adjustment on afterburner is broken after december updates

[undeath]

If you need to disable the selftest something is probably broken anyway.