Why is there any allocated memory difference between 6.2 2 versions with 6.2.5?

[Helfrigg]

Code:

OpenCL API (OpenCL 1.2 )

this is really old and you will run into some troubles using these old opencl api with hahscat

next thing opencl on intel iGPU is broken by default

you have to! (plz just believe me)

deinstall intel hd graficsdriver with windows programs (it is there) and install 
*ttp://registrationcenter-download.intel.com/akdlm/irc_nas/vcp/13794/opencl_runtime_18.1_x64_setup.msi

this will install opencl runtime 2.1 for cpu only (the speed will be the same) due to the combined cpu/gpu architecture

see whole thread here for more informations
https://hashcat.net/forum/thread-10548.html

the only thing to be aware of, you have to add at least

Code:

-D1

to your command line to tell hashcat to stick to your cpu

after de- and installing see output of

Code:

hashcat -I 

telling your cpu with opencl 2.1

I downloaded and installed the Runtime from the link you gave. I uninstalled the graphics driver before installing. I restarted. Version 6.2.5 still allocates less memory than 6.2.2. I wrote the hashcat -I command without installing the graphics driver.

Code:

hashcat (v6.2.5) starting in backend information mode

OpenCL Info:
============

OpenCL Platform ID #1
  Vendor..: Intel(R) Corporation
  Name....: Intel(R) CPU Runtime for OpenCL(TM) Applications
  Version.: OpenCL 2.1 WINDOWS

  Backend Device ID #1
    Type...........: CPU
    Vendor.ID......: 8
    Vendor.........: Intel(R) Corporation
    Name...........: Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz
    Version........: OpenCL 2.1 (Build 0)
    Processor(s)...: 4
    Clock..........: 3600
    Memory.Total...: 8064 MB (limited to 1008 MB allocatable in one block)
    Memory.Free....: 4000 MB
    OpenCL.Version.: OpenCL C 2.0
    Driver.Version.: 18.1.0.0920

Code:

hashcat (v6.2.2) starting in backend information mode...

OpenCL Info:
============

OpenCL Platform ID #1
  Vendor..: Intel(R) Corporation
  Name....: Intel(R) CPU Runtime for OpenCL(TM) Applications
  Version.: OpenCL 2.1 WINDOWS

  Backend Device ID #1
    Type...........: CPU
    Vendor.ID......: 8
    Vendor.........: Intel(R) Corporation
    Name...........: Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz
    Version........: OpenCL 2.1 (Build 0)
    Processor(s)...: 4
    Clock..........: 3600
    Memory.Total...: 8064 MB (limited to 2016 MB allocatable in one block)
    Memory.Free....: 8000 MB
    OpenCL.Version.: OpenCL C 2.0
    Driver.Version.: 18.1.0.0920

I downloaded and reinstalled the graphics driver. I couldn't use the cpu again. I can't use runtime with graphics driver. Maybe that's how it should be.

Code:

D:\hashcat>hashcat -m 0 -b -D 1
hashcat (v6.2.3) starting in benchmark mode

Benchmarking uses hand-optimized kernel code by default.
You can use it in your cracking session by setting the -O option.
Note: Using optimized kernel code limits the maximum supported password length.
To disable the optimized kernel code in benchmark mode, use the -w option.

OpenCL API (OpenCL 2.1 WINDOWS) - Platform #1 [Intel(R) Corporation]
====================================================================
* Device #1: Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz, 8000/8064 MB (2016 MB allocatable), 4MCU

OpenCL API (OpenCL 1.2 ) - Platform #2 [Intel(R) Corporation]
=============================================================
* Device #2: Intel(R) HD Graphics 4400, skipped
* Device #3: Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz, 8000/8064 MB (2016 MB allocatable), 4MCU

Benchmark relevant options:
===========================
* --opencl-device-types=1
* --optimized-kernel-enable

Hashmode: 0 - MD5

It's always worked for me when it comes to cpu usage. Even if the OpenCL driver is outdated. But I don't want to use the cpu for a long time.


Regarding the graphics driver; It's clear I have a problem. I tested my own created md5s. Dictionary attack works fine. Mask attack if the 'password' consists of 5 digits, mask attack cracks the password. But if it's longer than 5, it mostly can't find the password, sometimes it can find the password if I give a hint. I also tried --markov-disable command for this, same result.