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: run hashcat on winserver 2019
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
i have windows server 2019 with 2 x Xeon E5-2680v2
i try install opencl runtime 18.1, but i get an error "CL_PLATFORM_NOT_FOUND_KHR"
then i try install opencl runtime 16.1.2 and hashcat started and just closed without any errors.

Can i really run it ot on this OS?
Maybe Xeon CPUs have a special OpenCL runtime? I don't know. But hashcat should work just fine if you have a correctly installed OpenCL runtime.
(02-15-2020, 06:36 PM)undeath Wrote: [ -> ]Maybe Xeon CPUs have a special OpenCL runtime? I don't know. But hashcat should work just fine if you have a correctly installed OpenCL runtime.

Also i have another machine with Windows Server 2012 and Intel Xeon Gold 6154, and it's have same troubles.
if anyone can start hashcat with Windows Server system and Xeon - tell me how.
(02-15-2020, 05:38 PM)Hudrolax Wrote: [ -> ]i have windows server 2019 with 2 x Xeon E5-2680v2
i try install opencl runtime 18.1, but i get an error "CL_PLATFORM_NOT_FOUND_KHR"
then i try install opencl runtime 16.1.2 and hashcat started and just closed without any errors.

Can i really run it ot on this OS?

Read the Intel version(s) Release Notes very carefully here:

https://software.intel.com/en-us/article...ase-notes/

Be mindful that Intel is not above leaving 'legacy' CPUs in The Purgatory of Deprecation!

Additionally search for "Intel OpenCL upgrade problems"- some have had glitches when 
upgrading from 16.0,01, and 02 to 18.1. Remedies may include deleting a couple registry
keys and routing-out remnant dll files manually. Good Luck!
(02-15-2020, 08:58 PM)evets97 Wrote: [ -> ]
(02-15-2020, 05:38 PM)Hudrolax Wrote: [ -> ]i have windows server 2019 with 2 x Xeon E5-2680v2
i try install opencl runtime 18.1, but i get an error "CL_PLATFORM_NOT_FOUND_KHR"
then i try install opencl runtime 16.1.2 and hashcat started and just closed without any errors.

Can i really run it ot on this OS?

Read the Intel version(s) Release Notes very carefully here:

https://software.intel.com/en-us/article...ase-notes/

Be mindful that Intel is not above leaving 'legacy' CPUs in The Purgatory of Deprecation!

Additionally search for "Intel OpenCL upgrade problems"- some have had glitches when 
upgrading from 16.0,01, and 02 to 18.1. Remedies may include deleting a couple registry
keys and routing-out remnant dll files manually. Good Luck!

I don't know how, but i do it. I reboot the server in 2 times and reinstall opencl runtimes 18.1, and it's work. But machine have 2 processors, then hashcat see 3 processors. Device 3 named same other two, but get error. if i start hashcat with "-d 1,2" parameter - it's work and give 80 h/s on -m 15700. Sorry for my english...
p.s. Xeon Gold 6154 give 84 h/s on Scrypt (-m 15700)
maybe it's from a different OpenCL Platform ?

please post the output of:
hashcat -I
(02-15-2020, 10:31 PM)philsmd Wrote: [ -> ]maybe it's from a different OpenCL Platform ?

please post the output of:
hashcat -I

You right.
  • hashcat (v5.1.0) starting...

  • OpenCL Info:

  • Platform ID #1
  •   Vendor  : Intel(R) Corporation
  •   Name    : Intel(R) OpenCL
  •   Version : OpenCL 2.1

  •   Device ID #1
  •     Type          : CPU
  •     Vendor ID      : 8
  •     Vendor        : Intel(R) Corporation
  •     Name          : Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
  •     Version        : OpenCL 2.1 (Build 0)
  •     Processor(s)  : 40
  •     Clock          : 2800
  •     Memory        : 32759/131038 MB allocatable
  •     OpenCL Version : OpenCL C 2.0
  •     Driver Version : 18.1.0.0920

  • Platform ID #2
  •   Vendor  : Advanced Micro Devices, Inc.
  •   Name    : AMD Accelerated Parallel Processing
  •   Version : OpenCL 2.0 AMD-APP (1800.8)

  •   Device ID #2
  •     Type          : CPU
  •     Vendor ID      : 128
  •     Vendor        : GenuineIntel
  •     Name          : Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
  •     Version        : OpenCL 1.2 AMD-APP (1800.8)
  •     Processor(s)  : 40
  •     Clock          : 2800
  •     Memory        : 32759/131038 MB allocatable
  •     OpenCL Version : OpenCL C 1.2
  •     Driver Version : 1800.8 (sse2,avx)

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

  •   Device ID #3
  •     Type          : CPU
  •     Vendor ID      : 8
  •     Vendor        : Intel(R) Corporation
  •     Name          : Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
  •     Version        : OpenCL 2.1 (Build 0)
  •     Processor(s)  : 40
  •     Clock          : 2800
  •     Memory        : 32759/131038 MB allocatable
  •     OpenCL Version : OpenCL C 2.0
  •     Driver Version : 18.1.0.0920
it's strange, but server have 2 same Xeon, and it's work only, if i start it with "-d 1,2", else i get error "CL_INVALID_PLATFORM". 
Anyway two Xeons hashrate was enough for crack my Ethereum wallet hash with my password-candidate generate method, and it's cracked in 3 hours. I was try crack it with GTX1080 ti, and rigs with 8*AMD RX580 and rig with 14*GTX1070 before, GPU give maximum 1 hash per second from card.
Thank you for help.
From Intel's OpenCL Troubleshooting Notes, FWIW....

"OpenCL™ programs are said to observe an extra, non-existant CPU platform and/or device. Uninstallation of 16.1.2 may leave assets on disk... the following system alterations should help complete uninstallation procedure for 16.1.2:

1) Remove following registry keys:
On 64-bit OS:

HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenCL\Vendors\intelopencl64.dll
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Khronos\OpenCL\Vendors\intelopencl32.dll

2) (optional) Remove following files if they exist:
On 64-bit
C:\Windows\System32\intelopencl64.dll
C:\Windows\SysWOW64\intelopencl32.dll

*End update 20181025*"

For more information on manual installation of runtimes, users should refer to the guidance in section 5.1 of the release notes.

See full 18.1 release notes