Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ERROR: cuMemsetD8() 1 #1

Closed
Xanadrel opened this issue Dec 4, 2015 · 6 comments
Closed

ERROR: cuMemsetD8() 1 #1

Xanadrel opened this issue Dec 4, 2015 · 6 comments

Comments

@Xanadrel
Copy link
Member

Xanadrel commented Dec 4, 2015

Multiple users reported getting this error (both on windows/linux), with driver versions higher than the required one.

OS: Windows 7 64b
GPU : GTX Titan X
CPU : i5 2500k
Driver : 353.62
oclHashcat : 2.00

Command :
./cudaHashcat64.exe -m 100 ../hashcat-0.50/examples/A0.M100.hash example.dict

Output :

cudaHashcat v2.00 starting...

Device #1: GeForce GTX TITAN X, 12288MB, 1076Mhz, 24MCU

Hashes: 100 hashes; 100 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 1
Applicable Optimizers:
* Zero-Byte
* Precompute-Init
* Precompute-Merkle-Demgard
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Salt
* Scalar-Mode
* Raw-Hash
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: Kernel z:\Hashcat\cudaHashcat-2.00/kernels/4318/m00100_a0.sm_52.64.cubin

Generated dictionary stats for example.dict: 1210228 bytes, 129988 words, 129988 keyspace
[...]
[s]tatus [p]ause [r]esume [b]ypass [q]uit =>

ERROR: cuMemsetD8() 1
@Xanadrel
Copy link
Member Author

Xanadrel commented Dec 4, 2015

The error seems to happen only with wordlist based attacks, so all but -a 3.

@Wohn
Copy link

Wohn commented Dec 5, 2015

I got the same error :(

@philsmd
Copy link
Member

philsmd commented Dec 5, 2015

The pull request above fixes the problem.
The problem doesn't seem to be specific to any particular nvidia driver. However, it seems to be a very recently introduced code and this problem somehow did remain undetected.

@Wohn
Copy link

Wohn commented Dec 5, 2015

ok, with -a 3 i got GPU speed 0 H/s but its running 10 digits

jsteube added a commit that referenced this issue Dec 5, 2015
@jsteube
Merge pull request #2 from philsmd/master
a1b373a 
for issue #1: cuMemsetD8() 1 error
@jsteube
Copy link
Member

jsteube commented Dec 5, 2015

Problem solved with PR #2

@jsteube jsteube closed this as completed Dec 5, 2015
jsteube added a commit that referenced this issue Dec 5, 2015
@jsteube
It's important to release a fixed version of v2.00 because of the issue
490ff03 
#1 even if AMD is not affected
@Wohn
Copy link

Wohn commented Dec 5, 2015

oclhashcat 2.0.1 released!!! :)

@epixoip epixoip mentioned this issue Dec 20, 2015
Closed
@me-scotty me-scotty mentioned this issue Jan 13, 2016
Closed
@Zyntax3rror Zyntax3rror mentioned this issue Jan 24, 2016
Closed
This was referenced Jan 27, 2016
Closed
Closed
@Zyntax3rror Zyntax3rror mentioned this issue Feb 4, 2016
Closed
@ZerBea ZerBea mentioned this issue Mar 9, 2016
Closed
@ghost ghost mentioned this issue Mar 20, 2016
Closed
@ubuntutest ubuntutest mentioned this issue Mar 21, 2016
Closed
@lalaithion lalaithion mentioned this issue Apr 21, 2016
Closed
@BeetleChunks BeetleChunks mentioned this issue May 15, 2016
Closed
@ZerBea ZerBea mentioned this issue May 17, 2016
Closed
@neheb neheb mentioned this issue May 17, 2016
Closed
@L1nkus L1nkus mentioned this issue Jun 2, 2016
Closed
@CthUlhUzzz CthUlhUzzz mentioned this issue Jun 2, 2016
Closed
This was referenced Jun 3, 2016
Closed
Closed
@gituser gituser mentioned this issue Jun 3, 2016
Closed
@Zyntax3rror Zyntax3rror mentioned this issue Jun 8, 2016
Closed
@derhornspieler derhornspieler mentioned this issue Jun 20, 2016
Closed
@fmarquez fmarquez mentioned this issue Jun 23, 2016
Closed
@alanjfora alanjfora mentioned this issue Jan 5, 2023
Closed
PenguinKeeper7 referenced this issue in PenguinKeeper7/hashcat Jan 7, 2023
@PenguinKeeper7
QoL status hex fix
b6c24a9 
Current behaviour $HEXes both `Candidate` plains in the `[s]tatus` prompt, even when one plain doesn't require it, this change will only $HEX the plains that require it

Previous:
Candidates.#1....: $HEX[313537393434] -> $HEX[042a0337c2a1]

Current:
Candidates.#1....: 157944 -> $HEX[042a0337c2a1]
@OmegaCap OmegaCap mentioned this issue Jan 26, 2023
Closed
@tabularasa007 tabularasa007 mentioned this issue Mar 2, 2023
Closed
@Wingman4l7 Wingman4l7 mentioned this issue Mar 8, 2023
Open
@boulevard-h boulevard-h mentioned this issue Mar 22, 2023
Closed
@miguelacaro miguelacaro mentioned this issue Apr 6, 2023
Closed
@NordmanPro NordmanPro mentioned this issue Jun 20, 2023
Open
@deloam deloam mentioned this issue Jul 6, 2023
Open
@ovcrash ovcrash mentioned this issue Jul 18, 2023
Open
@efic1 efic1 mentioned this issue Aug 15, 2023
Open
@IamHuskar IamHuskar mentioned this issue Aug 16, 2023
Closed
@MiChaelinzo MiChaelinzo mentioned this issue Aug 22, 2023
Closed
@BHack007 BHack007 mentioned this issue Aug 25, 2023
Closed
@YetAnotherRussian YetAnotherRussian mentioned this issue Sep 4, 2023
Closed
@s0uvenir2566 s0uvenir2566 mentioned this issue Sep 5, 2023
Open
@HarukaMa HarukaMa mentioned this issue Sep 22, 2023
Closed
jsteube pushed a commit that referenced this issue Sep 23, 2023
@ViperelB
Merge pull request #1 from ViperelB/ViperelB-patch-1
300a208 
Optimized T0XlCv2.rule with ruleprocessorY
@niroop893 niroop893 mentioned this issue Oct 12, 2023
Closed
@PenguinKeeper7 PenguinKeeper7 mentioned this issue Oct 27, 2023
Open
@CustosClarus CustosClarus mentioned this issue Nov 27, 2023
Closed
@nicolas2k nicolas2k mentioned this issue Dec 24, 2023
Closed
@md1440 md1440 mentioned this issue Dec 27, 2023
Closed
@T3chC0wb0y T3chC0wb0y mentioned this issue Feb 22, 2024
Open
@scotch123 scotch123 mentioned this issue Feb 23, 2024
Closed
PenguinKeeper7 referenced this issue in PenguinKeeper7/hashcat Feb 29, 2024
@PenguinKeeper7
Make skipped device warning respect --quiet
16b249c 
The other usual device information does not show when using --quiet, only the skipped warning does, making it a little out of place. Old:
```
> ./hashcat -m 99999 abcdef -a 3 abcdef --quiet
The device hashcat#2 specifically listed was skipped because it is an alias of device #1

abcdef:abcdef
>
```
New:
```
> ./hashcat -m 99999 abcdef -a 3 abcdef --quiet
abcdef:abcdef
```
@phillipsjk phillipsjk mentioned this issue Mar 16, 2024
Closed
@roycewilliams roycewilliams mentioned this issue Apr 14, 2024
Open
@EricFromCanada EricFromCanada mentioned this issue Apr 17, 2024
Closed
@Aggelos11 Aggelos11 mentioned this issue Apr 23, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@philsmd @Wohn @Xanadrel @jsteube