Instead of launching a brute force attack on the video card, the processor is launche

[Chick3nman]

This is likely due to measuring "usage" in Windows Task Manager, which only shows "3D Usage" by default, which hashcat is not. Switching the task manager view to report "Compute" usage will show the true usage of the GPU. I have no idea why microsoft chose to do this instead in a world full of GPU compute workloads...

[kitkat]

Oh.... I see what you mean. I agree.

Continued... Decided to try from scratch. Installed a new OS window 11. At first, the usual drivers were installed + installed only Nvidia drivers without CUDA. Two video cards were displayed, respectively nvidea and integrated intel. Launched hashcat result 200 hashes per second, in short, as it was, but the first difference is visible load on the video card. Ok, decided to install the full CUDA package, rebooted, now 3 cards are displayed. Launched a test check for hash from 7zip with password 1234. and success, 11 seconds and speed 16k hashes per second, I think success. as usual there is one but)) it worked only once. when restarted again 200 hashes. that is, something breaks in the process. and the processor starts to work actively at 100%

[slyexe]

If you're still trying to convince us there is something "wrong" in hashcat in using your graphics card, the information your providing is very vague and misleading. Again, simply pressing s on your keyboard will show you an output of the attack information and its handling.

Cutting off your command prompt to only show half the information doesn't allow us to help. Literally you've shown us in Post 1 that your GPU was being used using OpenCL runtimes.

Code:

OpenCL API (OpenCL 3.0 CUDA 12.8.97) - Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #2: NVIDIA GeForce RTX 3060, 12160/12287 MB (3071 MB allocatable), 28MCU

Then Later you have CUDA being used and show your GPU and Intel Integrated graphics were being used.

Code:

CUDA API (CUDA 12.8)
====================
* Device #1: NVIDIA GeForce RTX 3060, 11242/12287 MB, 28MCU

OpenCL API (OpenCL 3.0 CUDA 12.8.97) - Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #2: NVIDIA GeForce RTX 3060, skipped

OpenCL API (OpenCL 3.0 ) - Platform #2 [Intel(R) Corporation]
=============================================================
* Device #3: Intel(R) UHD Graphics 770, 7360/14839 MB (2047 MB allocatable), 32MCU

Theres not much else you've provided us to further assist other than you making post that there is a problem with your hashrate and GPU usage disclosed from an unknown app.

[kitkat]

Thank you for your reply. I want to emphasize. I did not write that the problem is in the hashcat program. I realized that at some point hardware acceleration is connected with the processor. I found information in the part of the questions asked about the need to remove OpenCL. Disabling and enabling hardware acceleration in the Windows OS itself did not help. Of course, I will try to remove these libraries while saving copies, I will see what changes, but I have already decided to install the Linux OS, I think there is less chance of spontaneous driver installation.

[kitkat]

Thank you for your reply. I want to emphasize. I did not write that the problem is in the hashcat program. I realized that at some point hardware acceleration is connected with the processor. I found information in the part of the questions asked about the need to remove OpenCL. Disabling and enabling hardware acceleration in the Windows OS itself did not help. Of course, I will try to remove these libraries while saving copies, I will see what changes, but I have already decided to install the Linux OS, I think there is less chance of spontaneous driver installation.

Everything with Linux worked without problems. Only if I take my hash from 7z, which weighs 13 MB, the problem repeats, but here it is probably connected with the fact that the file is archived a large volume of 3 GB. What does the hash size depend on? Shouldn't it be plus, minus approximately the same, how can it be that the hash weighs 13 MB? I can't even just copy it, I can only get it by redirecting the output to the file.