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: WARN: ADL_Overdrive5_FanSpeedInfo_Get(): -5
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi,

I've just downloaded the latest version (1.30) with Catalyst 14.7 RC3, R9 290, Windows 7x64 fresh install.
Still getting the error WARN: ADL_Overdrive5_FanSpeedInfo_Get(): -5

I say "still getting" because : https://hashcat.net/forum/thread-3626.html and https://hashcat.net/forum/thread-3503-post-20101.html

The difference with v1.21 is that I only have this warning once at the beginning of the run, and not every second.

Any idea ?

Thanks.

[Image: Sans_titre.png]
I have this same problem -

OS: Windows 7 SP1 x64
GPU: Radeon R9 290
Driver: AMD 14.7
oclHashcat: 1.30

A poster on AMD forum confirmed my driver is correct, 14.7, despite their own software telling me to upgrade my driver to 14.4 when it is already 14.7... that post is here:

https://forums.amd.com/game/messageview.c...erthread=y

My original post on hashcat.net forum here:

https://hashcat.net/forum/thread-3642-pos...l#pid20812

I've only noticed the errors displaying one time, at start:

Code:
WARN: ADL_Overdrive5_FanSpeedInfo_Get(): -5

Device #1: Hawaii, 3072MB, 947Mhz, 40MCU

Hashes: 1 hashes; 1 unique digests, 1 unique salts
Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
Applicable Optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
* Brute-Force
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: Kernel ./kernels/4098/m2500.Hawaii_1526.3_1526.3 (VM).kernel (257172
bytes)
Device #1: Kernel ./kernels/4098/markov_le_v1.Hawaii_1526.3_1526.3 (VM).kernel (
93224 bytes)
Device #1: Kernel ./kernels/4098/bzero.Hawaii_1526.3_1526.3 (VM).kernel (30484 b
ytes)

[s]tatus [p]ause [r]esume [b]ypass [q]uit =>

The cracking itself works, but don't want to fry my gpu because oclhashcat isn't showing temps when I check status of crack.
It seems that this problem was fixed in newest (beta) version of oclHashcat (1.31).
See ticket https://hashcat.net/trac/ticket/498

Thx for the infos, but next time prefer opening a ticket sooner Wink