VanitySearch-bitcrack icon indicating copy to clipboard operation
VanitySearch-bitcrack copied to clipboard

Multiple GPU Not worked !!! Bro, Help PLEEEEAAAASEEE ??

Open Comarro753 opened this issue 5 years ago • 4 comments

` C:\Users\Admin\Desktop\zaredo2>powershell Get-Date

15 июля 2020 г. 12:47:50

C:\Users\Admin\Desktop\zaredo2>VanitySearch-1.15.4_bitcrack_th256gr.exe -t 0 -gp u -stop -g 136,256 -o result2.txt --keyspace B504F333F9DE6484:FFFFFFFFFFFFFFFF 1 ***********xXz8933232ggg VanitySearch v1.15.4, add BitCrack mode Invalid gridSize or gpuId argument, must have same size VanitySeacrh [-check] [-v] [-u] [-b] [-c] [-gpu] [-stop] [-i inputfile] [-gpuId gpuId1[,gpuId2,...]] [-g gridSize1[,gridSize2,...]] [-o outputfile] [-m maxFound] [-ps seed] [-s seed] [-t nbThread] [-nosse] [-r rekey] [-check] [-kp] [-sp startPubKey] [-rp privkey partialkeyfile] [prefix]

prefix: prefix to search (Can contains wildcard '?' or '') -v: Print version -u: Search uncompressed addresses -b: Search both uncompressed or compressed addresses -c: Case unsensitive search -gpu: Enable gpu calculation -stop: Stop when all prefixes are found -i inputfile: Get list of prefixes to search from specified file -o outputfile: Output results to the specified file -gpu gpuId1,gpuId2,...: List of GPU(s) to use, default is 0 -g gridSize1,gridSize2,...: Specify GPU(s) kernel gridsize, default is 8(MP nu mber) -m: Specify maximun number of prefixes found by each kernel call -t threadNumber: Specify number of CPU thread, default is number of core -nosse: Disable SSE hash function -l: List cuda enabled devices -check: Check CPU and GPU kernel vs CPU -kp: Generate key pair -rp privkey partialkeyfile: Reconstruct final private key(s) from partial key(s ) info. -sp startPubKey: Start the search with a pubKey (for private key splitting) -r rekey: Rekey interval in MegaKey, cpu=1000 gpu=100000

--keyspace START START:END START:+COUNT :+COUNT :END Where START, END, COUNT are in hex format --share M / N: Divide the keyspace into N equal shares, process the Mth share --continue sessfile: Save / load progress from specified file '

Buddy, how to fix this problem ?

Comarro753 avatar Jul 15 '20 12:07 Comarro753

Need "gpuId" arg for more 1 gpu. For x6 gpu: -t 0 -gpu -gpuId 0,1,2,3,4,5 For x6 gpu with custom gridsize: -t 0 -gpu -gpuId 0,1,2,3,4,5 -g 136,256,136,256,136,256,136,256,136,256,136,256

Telariust avatar Jul 15 '20 19:07 Telariust

Need "gpuId" arg for more 1 gpu. For x6 gpu: -t 0 -gpu -gpuId 0,1,2,3,4,5 For x6 gpu with custom gridsize: -t 0 -gpu -gpuId 0,1,2,3,4,5 -g 136,256,136,256,136,256,136,256,136,256,136,256

Bro, Thx for you reply. But With gpuId not worked too !!!

Please try, this exact not support multiple gpu Bro !!!! With castom gridsise, without castom gridsize - NOT worked !!!

???

For info - VanitySearch now support multiple GPU. I don know, in vanitysearch-bitcrck multyGPU from vanity or from Bitcrack

Big Txh.

Comarro753 avatar Jul 15 '20 21:07 Comarro753

D:\>VanitySearch-1.15.4_bitcrack_th256gr.exe -t 0 -gpu -gpuId 0,1,2,3,4,5  -o result2.txt --keyspace B504F333F9DE6484:FFFFFFFFFFFFFFFF 1LqJ9cHPKxPXDRia4tteTJdLXnisnfHsof
VanitySearch v1.15.4, add BitCrack mode
[keyspace] start=000000000000000000000000000000000000000000000000B504F333F9DE6484
[keyspace]   end=000000000000000000000000000000000000000000000000FFFFFFFFFFFFFFFF
Difficulty: 1461501637330902918203684832716283019655932542976
Search: 1LqJ9cHPKxPXDRia4tteTJdLXnisnfHsof [Compressed]
Start at Thu Jul 16 04:49:56 2020
Number of CPU thread: 0
GPU: GPU #0 GeForce GTX 1070 (15x128 cores) Grid(120x256)
GPU: GPU #3 GeForce GTX 1070 (15x128 cores) Grid(120x256)
GPU: GPU #5 GeForce GTX 1070 (15x128 cores) Grid(120x256)
GPU: GPU #2 GeForce GTX 1070 (15x128 cores) Grid(120x256)
GPU: GPU #1 GeForce GTX 1070 (15x128 cores) Grid(120x256)
GPU: GPU #4 GeForce GTX 1070 (15x128 cores) Grid(120x256)
1589.889 MK/s (GPU 1589.889 MK/s) (2^35.25) [00:00:24 lost_TIME_left 107.76y][0]

i dont help without msg_errors or logs

Telariust avatar Jul 16 '20 01:07 Telariust

I may be able to help you, @Comarro753. Just tag me here and tell me what you've already tried on your machine. Your screen log shows you're using v1.15. Please update to 1.19 and try again.

CasparNuel avatar Dec 25 '20 15:12 CasparNuel