cuModuleLoad 301 error GTX 750 ti only on some hash types - Printable Version +- hashcat Forum (https://hashcat.net/forum) +-- Forum: Deprecated; Previous versions (https://hashcat.net/forum/forum-29.html) +--- Forum: Old oclHashcat Support (https://hashcat.net/forum/forum-38.html) +--- Thread: cuModuleLoad 301 error GTX 750 ti only on some hash types (/thread-3328.html) |
cuModuleLoad 301 error GTX 750 ti only on some hash types - RainingStars - 04-28-2014 Getting the GTX 750 Ti to work is not really the issue, I can run through most of the benchmarks, it's just certain hash types that cause this failure. Primarily the unix based ones. Like: 500 = md5crypt, MD5(Unix), FreeBSD MD5, Cisco-IOS MD5 1800 = sha512crypt, SHA512(Unix) However 1500 = descrypt, DES(Unix), Traditional DES Does work, but seems really slow for being so old Speed.GPU.#1.: 14306.9 kH/s This is my result with just MD5 Speed.GPU.#1.: 596.5 MH/s Anyway here is my output on trying to do a sha512crypt (unix) Code: cudaHashcat v1.20 starting... RE: cuModuleLoad 301 error GTX 750 ti only on some hash types - 3kings - 04-29-2014 What is your driver version? RE: cuModuleLoad 301 error GTX 750 ti only on some hash types - RainingStars - 04-29-2014 Driver version : 334.21 RE: cuModuleLoad 301 error GTX 750 ti only on some hash types - atom - 04-29-2014 descrypt is slower than md5, around 90 times. RE: cuModuleLoad 301 error GTX 750 ti only on some hash types - atom - 04-29-2014 on nv RE: cuModuleLoad 301 error GTX 750 ti only on some hash types - RainingStars - 04-29-2014 Any thoughts on the failure to load module on only certain hash types? RE: cuModuleLoad 301 error GTX 750 ti only on some hash types - atom - 04-29-2014 I'd say it's missing the bzero or markov kernels. Did you remove some of the kernels in the kernels/4318/ directory? It's part of the archieve so it must be something like this. If unsure, just unpack it again RE: cuModuleLoad 301 error GTX 750 ti only on some hash types - atom - 04-29-2014 we've worked on that issue on irc and found out a bug related to sm_50. If you have the same problem, come to IRC and tell me or wait for v1.21 release. |