Please note, this is a STATIC archive of website hashcat.net from 08 Oct 2020, cach3.com does not collect or store any user information, there is no "phishing" involved.

hashcat Forum

Full Version: error cuStreamsynchronize() 700
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
hi everyone i need some help please. i try to crack sl3 with this :
Code:
cudaHashcat-lite32 6A1F74847CC6A7FFCA6E181A1926748DE6448AA4:003526960415284100 -1 00010203040506070809 -m 101 ?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1 --pw-min=15 --pw-max=15 -n 160 --hex-charset --hex-salt --outfile-format=1 --outfile=352696041528414.txt
but i have an error "error cuStreamsynchronize() 700"
can you explain me please waht it seems.
Thank's and sorry for my english.

What kind of video card is it?
(08-13-2011, 07:19 PM)radix Wrote: [ -> ]What kind of video card is it?
Hi thank's for your help i have a geforce 8500GT. before it works and now i have this error.
You are mad!
Also, crappy budget GPUs do not support high -n modes, so should you decide to continue your craziness, just lower it, and it should work.

ATM, my best guess that it's related to either GPU memory or host memory. Cant say for sure.
Maybe it's a Linux issue.
Hi!

OS:
Linux P5W-DH-Deluxe 3.0.0-23-generic #39-Ubuntu SMP Thu Jul 19 19:18:53 UTC 2012 i686 i686 i386 GNU/Linux

CPU0: Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz stepping 07

Version:
cudaHashcat-lite v0.10 by atom starting...

Run shell:
./cudaHashcat-lite32.bin --gpu-accel=60 --gpu-async --hash-type=1400 --outfile=pass.out --pw-min=15 --pw-max=16 XXdXX0XXf66a02838234XX5f25f221c9XX7c3195e107a2fb95e02dXX84b3eeXX ?d?d?d?d?d?d?d?d?d?d?d?d?d?d?d?d

Error:
Password lengths range: 15 - 16
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: GeForce GT 520, 1023MB, 1620Mhz, 1MCU

[s]tatus [p]ause [r]esume [q]uit => ERROR: cuStreamSynchronize() 700

What to do?

Thx.
Buy a new card !
yeah the card sucks for sure. however you can try -n 1 --gpu-loops 1 and see if it work. if yes, slowly increase them to find the maximum possible for your 1 MCU card
(08-05-2012, 08:45 AM)atom Wrote: [ -> ]yeah the card sucks for sure. however you can try -n 1 --gpu-loops 1 and see if it work. if yes, slowly increase them to find the maximum possible for your 1 MCU card

--hash-type=1400 --pw-min=15 --pw-max=16 -n 1 --gpu-loops 1

Not help, but in use previous version 0.09 all working normally. Very thx Mem5 for hint.

In strace log, last lines:
Code:
gettimeofday({1344158286, 193701}, NULL) = 0
mmap2(NULL, 8392704, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0xb0d82000
mprotect(0xb0d82000, 4096, PROT_NONE)   = 0
clone(child_stack=0xb1582484, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0xb1582bd8, {entry_number:6, base_addr:0xb1582b70, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}, child_tidptr=0xb1582bd8) = 2738
futex(0xb1582bd8, FUTEX_WAIT, 2738, NULL <unfinished ... exit status 255>


I can send full "strace" log file.