hashcat Forum › Support › hashcat v
Hardware monitoring interface not found on your system?

Threaded Mode
Hardware monitoring interface not found on your system?
Anne1246 Offline
Junior Member
**
Posts: 5
Threads: 2
Joined: Mar 2021
#1
03-19-2021, 07:25 PM (This post was last modified: 03-19-2021, 10:27 PM by Anne1246. Edit Reason: Typo fix )
So, earlier I posted about a problem with my hash but I was able to fix that, but now I keep getting this:
Code:
hashcat (v6.1.1-116-gfb219e0a6) starting...

You have enabled --force to bypass dangerous warnings and errors!
This can hide serious problems and should only be done when debugging.
Do not report hashcat issues encountered when using --force.
OpenCL API (OpenCL 2.1 ) - Platform #1 [Intel(R) Corporation]
=============================================================
* Device #1: Intel(R) HD Graphics 615, 3180/3244 MB (1622 MB allocatable), 24MCU

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

Applicable optimizers applied:
* Zero-Byte
* Single-Hash
* Single-Salt
* Brute-Force
* Slow-Hash-SIMD-LOOP
* Uses-64-Bit

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

the code I applied is this: hashcat -m 23500 -a 3 -2 ?l?d --increment --increment-min 8 --increment-max 16 hash.txt ?2?2?2?2?2?2?2?2 --force




any idea what I'm doing wrong? thanks in advance!
Find
Reply
hblender Offline
Junior Member
**
Posts: 22
Threads: 0
Joined: Dec 2019
#2
03-20-2021, 06:17 PM
Try adding --hwmon-disable at the end of the command.
Find
Reply
Anne1246 Offline
Junior Member
**
Posts: 5
Threads: 2
Joined: Mar 2021
#3
03-20-2021, 09:09 PM
(03-20-2021, 06:17 PM)hblender Wrote: Try adding --hwmon-disable at the end of the command.


still the same thing.
Find
Reply
slyexe Offline
Senior Member
****
Posts: 353
Threads: 0
Joined: Nov 2017
#4
03-21-2021, 06:23 PM
It's just a warning stating that it will not be able to monitor the temperature of your CPU so it will not shut down the attack if it gets too hot. The problem is using --force.
Find
Reply
Anne1246 Offline
Junior Member
**
Posts: 5
Threads: 2
Joined: Mar 2021
#5
03-21-2021, 07:37 PM (This post was last modified: 03-21-2021, 07:38 PM by Anne1246.)
(03-21-2021, 06:23 PM)slyexe Wrote: It's just a warning stating that it will not be able to monitor the temperature of your CPU so it will not shut down the attack if it gets too hot. The problem is using --force.

Okay so what do you suggest doing instead? I can't run the command otherwise. I get: 

*Device #1: Unstable OpenCL driver detected! 

this OpenCL has been marked as likely to fail kernel compilation or to produce false negatives. You can use --force to override this, but do not report related errors.

No devices found/left. 

I have tried updating my OpenCL driver for CPU but no luck.
Find
Reply