|
Error cuCtxPopCurrent (cudaHashcat+64.exe)
|
|
02-02-2011, 09:11 AM
Post: #1
|
|||
|
|||
|
Error cuCtxPopCurrent (cudaHashcat+64.exe)
Hi,
I don't know if it's a bug.. When I run this command line : Code: cudaHashcat+64.exe -r rules\d3ad0ne_1.5K.rule -n 512 --gpu-loops 512 -m 1000 hash.txt "dics\full.txt"And program exits. Why ? Then I put -n 256 instead of 512 and it works fine. When I use a smaller rule (like leetspeak.rule) I am able to run the program with -n 512, without any error. Does the rule file length acts on the -n parameter ? Thank you. |
|||
|
02-02-2011, 09:36 AM
(This post was last modified: 02-02-2011 09:42 AM by Rolf.)
Post: #2
|
|||
|
|||
|
RE: Error cuCtxPopCurrent (cudaHashcat+64.exe)
What's your GPU ?
I cant test cudahc+ due to driver incompability, but I have an idea that your gpu is just overloaded, that's why -n 512 doesnt work. |
|||
|
02-02-2011, 10:21 AM
Post: #3
|
|||
|
|||
|
RE: Error cuCtxPopCurrent (cudaHashcat+64.exe)
play with it but dont oversize it
|
|||
|
02-02-2011, 10:04 PM
Post: #4
|
|||
|
|||
|
RE: Error cuCtxPopCurrent (cudaHashcat+64.exe)
My GPU is GeForce 8400 GS, 239MB, 1400Mhz, 1MCU.
Not so good but works ![]() I will stay on "-n 256 --gpu-loops 512" it's fine for me. |
|||
|
02-02-2011, 11:33 PM
Post: #5
|
|||
|
|||
|
RE: Error cuCtxPopCurrent (cudaHashcat+64.exe)
I was able to reproduce the same problem by also putting extreme values:
-n 216 --gpu-loops 512 got the error cuCtxPopCurrent() 999 My cards in this case were a GTX260 and a GTS250. Now another side effect and/or bug. If I put only --gpu-loops 1024. It works fine but end up missing passwords. Definitely don't want that. Maybe it already affects people without knowing... |
|||
|
02-03-2011, 12:08 AM
Post: #6
|
|||
|
|||
|
RE: Error cuCtxPopCurrent (cudaHashcat+64.exe)
hm, because of the status display it may look like it does not find all passes, but it does. look here:
Quote:root@erebus:~/oclHashcat+-0.02# /root/maskprocessor-0.63/mp64.bin ?d?d?d?d?d?d | ./cudaHashcat+64.bin x -o y but its just a display problem. if you check the output file they are all found. its just missing a final display. Quote:root@erebus:~/oclHashcat+-0.02# wc -l y |
|||
|
02-12-2011, 10:51 AM
Post: #7
|
|||
|
|||
|
RE: Error cuCtxPopCurrent (cudaHashcat+64.exe)
I put a lower number for -n and --gpu-loops parameter, and it works better.
|
|||
|
02-13-2011, 08:38 AM
Post: #8
|
|||
|
|||
|
RE: Error cuCtxPopCurrent (cudaHashcat+64.exe)
maybe i should limit this to like 800 or so in next release
|
|||
|
02-20-2011, 08:08 AM
(This post was last modified: 02-20-2011 08:10 AM by tatgdi.)
Post: #9
|
|||
|
|||
|
RE: Error cuCtxPopCurrent (cudaHashcat+64.exe)
Hello Atom,
Please do look at providing some form of automation for the following -n value and --gpuloops-value options discussed above. I find as well depending on the digest length and type it can increase/decrease your attack. When in doubt I have left off the folloiwing 2 parameters and the speed has been descent. I posted additonal information at the following thread: http://hashcat.net/forum/thread-293.html |
|||
|
02-20-2011, 09:55 AM
Post: #10
|
|||
|
|||
|
RE: Error cuCtxPopCurrent (cudaHashcat+64.exe)
no, they are there for a reason. for example if i want to play games or watch movies on the same card while i am cracking i need to lower these number to make room for additional calculations by 3rd applications.
|
|||
|
« Next Oldest | Next Newest »
|
Search
Member List
Calendar
Help





