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: HELP, oclHashcat-plus 0.12 ERROR: cuMemcpyDtoH() 700
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3
I changed the OS to win7(32bit), and installed the newest driver, but ... ERROR: cuLaunchKernel() 999

D:\oclHashcat-plus-0.12>cudaHashcat-plus32.exe -m 500 example500.hash example.dict
cudaHashcat-plus, advanced password recovery

cudaHashcat-plus v0.12 by atom starting...

Hashes: 1 total, 1 unique salts, 1 unique digests
Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
Rules: 1
Workload: 16 loops, 80 accel
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: GeForce GTX 550 Ti, 1023MB, 1800Mhz, 4MCU
Device #1: Kernel ./kernels/4318/m0500.sm_21.ptx

Generating dictionary stats for example.dict: 1047587 bytes (86.56%), 112372 word
Generated dictionary stats for example.dict: 1210228 bytes, 129988 words, 129988 keyspace

[s]tatus [p]ause [r]esume [b]ypass [q]uit => ERROR: cuLaunchKernel() 999


...Emmmm, bad result
Maybe we need new .def files for cuda 32 bit. The 700 error should be fixed, the 999 one is a different.
Hey there, I also am having the 999 error
Latest drivers for nVidia, and hash V 0.12
What can be possibly causing this issue?
(of course, the 32 bit win version)

omg, i found the cpp

999 = error unknown?

atom, please any suggestions?
Please switch to 64 bit and try again with the same setup. Maybe a workaround.
Will try that. Perhaps you could suggest the best platform for HashCat because I think its worth buying.
Regards.
... worth buying?
Worth buying best graphic card for hashcat.
AMD 7970 is currently the fastest card i think.
Is it a 32bit issue?

Getting the same thing on an update to date ubuntu 12.04 32bit

cudaHashcat-plus v0.12 by atom starting...

Hashes: 1 total, 1 unique salts, 1 unique digests
Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
Rules: 1
Workload: 16 loops, 80 accel
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: GeForce GT 520, 1023MB, 1620Mhz, 1MCU
Device #1: Kernel ./kernels/4318/m0400.sm_21.ptx

Starting attack in stdin mode...

ERROR: cuMemcpyDtoH() 700

Also found this in dmesg

NVRM: Your system is not currently configured to drive a VGA console
[ 11.704048] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[ 11.704050] NVRM: requires the use of a text-mode VGA console. Use of other console
[ 11.704051] NVRM: drivers including, but not limited to, vesafb, may result in
[ 11.704053] NVRM: corruption and stability problems, and is not supported.

I don't know if it's related
Not related to the dmes warning, but its a good chance its because its 32 bit. If you can, try again with a 64 bit version.
Pages: 1 2 3