06-23-2016, 01:58 PM
Has AMD fucked up something or did I fuck up?
Clean install of latest AMD drivers (Crimson 16.6.1) and this is what I get:
So after retrying a couple times I checked what the 32bit version says:
and it works just fine.
I absolutely installed 64bit drivers, file is "non-whql-64bit-radeon-software-crimson-16.6.1-win10-win8.1-win7-june2.exe" which contains a "Bin64" and several other "...64" files/folders. So I'm very sure it's not the 32bit driver in a 64bit named package by accident. Of course I'm also using Windows 7 64bit and not 32bit.
Would appreciate any input, have a nice day!
Clean install of latest AMD drivers (Crimson 16.6.1) and this is what I get:
Code:
...\oclHashcat-2.01>oclHashcat64.exe -b
oclHashcat v2.01 starting in benchmark-mode...
...\oclHashcat-2.01>So after retrying a couple times I checked what the 32bit version says:
Code:
...\oclHashcat-2.01>oclHashcat32.exe -b
oclHashcat v2.01 starting in benchmark-mode...
Device #1: Pitcairn, 1024MB, 860Mhz, 16MCU
Hashtype: MD4
Workload: 1024 loops, 256 accel
Speed.GPU.#1.: 6945.6 MH/s
Hashtype: MD5
Workload: 1024 loops, 256 accel
Speed.GPU.#1.: 3655.1 MH/s
...and it works just fine.
I absolutely installed 64bit drivers, file is "non-whql-64bit-radeon-software-crimson-16.6.1-win10-win8.1-win7-june2.exe" which contains a "Bin64" and several other "...64" files/folders. So I'm very sure it's not the 32bit driver in a 64bit named package by accident. Of course I'm also using Windows 7 64bit and not 32bit.
Would appreciate any input, have a nice day!