hashcat Forum
ERROR: cuLaunchKernel() 999 - Printable Version

+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Deprecated; Ancient Versions (https://hashcat.net/forum/forum-46.html)
+--- Forum: Very old oclHashcat-plus Support (https://hashcat.net/forum/forum-23.html)
+--- Thread: ERROR: cuLaunchKernel() 999 (/thread-2040.html)

Pages: 1 2 3


ERROR: cuLaunchKernel() 999 - coneboy - 02-05-2013

Hey guys,
I get this error in 0.13 and with the previous version too.
I hope you can help me out!

Thx in advance!



Code:
cudaHashcat-plus v0.13 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, 8 accel
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: GeForce GTX 660 Ti, 2048MB, 1110Mhz, 7MCU
Device #1: Kernel ./kernels/4318/m2500.sm_30.ptx

Cache-hit dictionary stats rockyou.txt: 139921497 bytes, 14100049 words, 1410004
9 keyspace

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

.bat-file:
cudaHashcat-plus32.exe -m 2500 capture.hccap rockyou.txt
pause

OS:
Win7 Home Premium SP1 32bit

nVidia-Driver Version:
310.90


RE: ERROR: cuLaunchKernel() 999 - Hash-IT - 02-05-2013

There is a similar problem here.


However your command line could probably do with an attack mode. -a 0 and an output -o although probably not essential.


RE: ERROR: cuLaunchKernel() 999 - coneboy - 02-06-2013

Added an attack mode and output, but nothing changes.
Can't open your link. Can you specify please?


RE: ERROR: cuLaunchKernel() 999 - Hash-IT - 02-06-2013

(02-06-2013, 02:33 PM)coneboy Wrote: Added an attack mode and output, but nothing changes.
Can't open your link. Can you specify please?

You might need to install a reg fix and reboot.

Read about it here.


RE: ERROR: cuLaunchKernel() 999 - coneboy - 02-08-2013

Added that to the reg. But still the same error. Thx for that hint though.
Any other ideas what could cause this?


RE: ERROR: cuLaunchKernel() 999 - Hash-IT - 02-08-2013

(02-08-2013, 02:50 AM)coneboy Wrote: Added that to the reg. But still the same error. Thx for that hint though.
Any other ideas what could cause this?

I was rather hoping someone else here may have known the answer as I am only a novice at this.

I think only atom can answer your question, he will almost instantly know whats wrong but he is working away from home at the moment I believe.

Until he is back you might want to try the link I posted above again, the Trac seems to be back online now so it should work for you.

Its mainly to do with making sure you have "fully" uninstalled properly.

I use ATI so I can't really help much more than I have. If you are really stuck and no one else knows what to do, let me know and I will ask atom to look at this thread when he is back, but I cannot guarantee he will.


RE: ERROR: cuLaunchKernel() 999 - corex - 02-10-2013

Same problem here...
Dont know where to start to fix this problem.
Still stuck to this error
Please help!


RE: ERROR: cuLaunchKernel() 999 - Rolf - 02-10-2013

Downgrade to 306.97 using this link and see if that changes anything.


RE: ERROR: cuLaunchKernel() 999 - corex - 02-11-2013

(02-10-2013, 08:22 AM)Rolf Wrote: Downgrade to 306.97 using this link and see if that changes anything.

Still no success mate...Update / downgrade drivers , disable WDDM...
Any ideas to fix this error...

Running smooth but super slow with my old gpu 8400gs...
How come i cant run this on my gt630?


RE: ERROR: cuLaunchKernel() 999 - Rolf - 02-11-2013

Nah, it has nothing to do with the OS.

I suggested downgrading just because I'm using those drivers.

One last thing.
A fellow coder had some issues with sm_21 lately(that's your card's architecture), so my last suggestion will be a wee bit weird: go to pluscat\kernels\4318 and rename ALL the sm_20 kernels to sm_21.
Actually, I've done this for ya, so just download this archive and extract the contents to the folder I mentioned above, overwriting current kernels.
It'll be a Frankenstein, but it'll should still work(if the 999 error is gone) with minimal speed loss.
Try that and let me know if that changes anything.