Pages:
Author

Topic: VanitySearch (Yet another address prefix finder) - page 25. (Read 33086 times)

newbie
Activity: 12
Merit: 0
Why is there no answer? Jean Luc ask for an answer on this question. All data I have provided.

I'm sorry but I didn't manage to reproduce the issue.
It is the same if you try to reduce the grid size ?

When reducing the grid, the error -GPUEngine: Launch: unspecified launch failure. And when enlarging the grid, the error -GPUEngine: Kernel: too many resources requested for launch. https://fex.net/ru/s/sfypzfa  link to check
sr. member
Activity: 462
Merit: 701
Why is there no answer? Jean Luc ask for an answer on this question. All data I have provided.

I'm sorry but I didn't manage to reproduce the issue.
It is the same if you try to reduce the grid size ?
newbie
Activity: 12
Merit: 0
Why don't VanitySearch1.18 and VanitySearch1.19 versions work for me, reports the error GPUEngine: Launch: an illegal memory access was encountered, and VanitySearch1.17 version works correctly? Help me to understand.

Why is there no answer? Jean Luc ask for an answer on this question. All data I have provided.
sr. member
Activity: 462
Merit: 701
@Jean_Luc

What exactly is the base key and why we can't manually change it?

The base key is the key used for starting calculation from. This key is transformed (translation,symmetry and endomorphism) until the target prefix is reached. This base key is generated randomly or from a pass phrase.
There is no way to set it manually to a specific value.
full member
Activity: 706
Merit: 111
In fact a parallel kangaroo program that look for a single key creates several pubkeys from this key (by simply translating it). So this is a multi key search but this does not decrease the probability to solve this single key. It just allows a simple parallelization.

Usually, for a multi target attack, the first key has no benefit but the following keys can gain from the previous calculation.
If you want to search a pubkey with a x starting with 32 leading F (between n and p), you will have to perform ~2^128 group operations.


@Jean_Luc

What exactly is the base key and why we can't manually change it?
sr. member
Activity: 462
Merit: 701
In fact a parallel kangaroo program that look for a single key creates several pubkeys from this key (by simply translating it). So this is a multi key search but this does not decrease the probability to solve this single key. It just allows a simple parallelization.

Usually, for a multi target attack, the first key has no benefit but the following keys can gain from the previous calculation.
If you want to search a pubkey with a x starting with 32 leading F (between n and p), you will have to perform ~2^128 group operations.
full member
Activity: 206
Merit: 450

Do you have any references for the work required for the best multi-target discrete log attacks?


AFAIK there are no multi-target ECDLP algorithms.

Since the private key is not restricted, only the usual Pollard Rho is applicable. Selecting a single public key from the desired range, and doing 2^128 group operations (more or less).


[I'm posting in this thread because it's obviously most related to vanity search, in particular, it's a vanitysearch for an address prefix "BC1QLLLLLLLLLLLLLLLLLLLLLLLLL"


Taproot addresses should start with "BC1P".

staff
Activity: 4326
Merit: 8951
JeanLuc (and others),

Do you have any references for the work required for the best multi-target discrete log attacks?

For the test vectors for BIP340 it would be extremely useful if there was a test vectors where the signature R or Pubkey's x value had an usually large value in the range the scalar order [0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364141, 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEFFFFFC2F) (between the scalar order and the field order).  Test vectors using points with a value inside this range would test if an implementation isn't erroneously reducing these inputs mod Fn or considering them as too large (e.g. by mistakenly using the Fn overflow test that they use for deserializing the S value in signatures).

To construct tests like this we would need a point with an x in this range where we know the discrete log.

One way to perform this test is to just mock the choice of G in the cryptosystem, if you can pick G you can make any single chosen point have a known DL. ... but having test vectors which require the implementation to use a different G means that the test can't be just applied to an unmodified system, so it's less useful.

Because this range is pretty large-- about 129 bits-- there are ~2^129 acceptable keys...  It sounds to me like it might be feasible for a multi-target discrete log search to find a solution. If so, it would be a record breaking computation that would be practically useful in addition to offering bragging rights.

But it's not clear to me if this actually feasible or what the concrete computational cost would be of the best known multi-target attack.

[I'm posting in this thread because it's obviously most related to vanity search, in particular, it's a vanitysearch for an address prefix "BC1QLLLLLLLLLLLLLLLLLLLLLLLLL"
jr. member
Activity: 41
Merit: 1
Could you try to run cuda-memcheck with your input address file ?
Code:
"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\cuda-memcheck.exe" VanitySearch119.exe -gpu -r 1000000 -t 0 -g 320,256 -o found.txt -i 50.txt -stop


After about 3 minutes, there is an error, this is with 100 addresses (-i inputfile). There was no error with 50 addresses. With 500 addresses, an error occurs after a few seconds. We are talking about full bitcoin addresses (example: 152hx7Sp822qqWSPHRbK7b8cKdAaPzALqd)



What you do makes no sense at all.

The point is for the program to work correctly.

just to chime in here since i have the same error since 2 month ago... and yep it also craches from 50--100 addresses and upwards



>"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\cuda-memcheck.exe" VanitySearch.exe -b -t 0 -gpu -gpuId 0 -g 540,512 -m 1520000 -r 44400 -o found_0.txt -i 20.txt
========= CUDA-MEMCHECK
[Loading input file 100.0%]
VanitySearch v1.19
[Building lookup16  98.9%]
[Building lookup32 100.0%]
Search: 67714 addresses (Lookup size 42081,[1,11]) [Compressed or Uncompressed]
Start Tue Sep  1 11:49:36 2020
Base Key: Randomly changed every 44400 Mkeys
Number of CPU thread: 0
GPU: GPU #0 GeForce RTX 2080 Ti (68x64 cores) Grid(540x512)
GPUEngine: Kernel: too many resources requested for launch
========= Program hit cudaErrorLaunchOutOfResources (error 701) due to "too many resources requested for launch" on CUDA API call to cudaLaunchKernel.
=========     Saved host backtrace up to driver entry point at error
=========     Host Frame:C:\Windows\system32\DriverStore\FileRepository\nv_dispui.inf_amd64_ae0a6307e8a28cc4\nvcuda64.dll (cuProfilerStop + 0x8ff3e) [0x2ad53e]
=========     Host Frame:C:\Windows\system32\DriverStore\FileRepository\nv_dispui.inf_amd64_ae0a6307e8a28cc4\nvcuda64.dll (cuProfilerStop + 0x928e3) [0x2afee3]
=========     Host Frame:C:\Windows\system32\DriverStore\FileRepository\nv_dispui.inf_amd64_ae0a6307e8a28cc4\nvcuda64.dll [0x86ebe]
=========     Host Frame:C:\Windows\system32\DriverStore\FileRepository\nv_dispui.inf_amd64_ae0a6307e8a28cc4\nvcuda64.dll (cuProfilerStop + 0x113e8a) [0x33148a]
=========     Host Frame:C:\Windows\system32\DriverStore\FileRepository\nv_dispui.inf_amd64_ae0a6307e8a28cc4\nvcuda64.dll (cuProfilerStop + 0x12c212) [0x349812]
=========     Host Frame:C:\Users\x\Desktop\VS\VanitySearch.exe [0x2199]
=========     Host Frame:C:\Users\x\Desktop\VS\VanitySearch.exe [0x4f214]
=========     Host Frame:C:\Users\x\Desktop\VS\VanitySearch.exe [0x4f0ca]
=========     Host Frame:C:\Users\x\Desktop\VS\VanitySearch.exe [0x4a922]
=========     Host Frame:C:\Users\x\Desktop\VS\VanitySearch.exe [0x4643f]
=========     Host Frame:C:\Windows\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x17bd4]
=========     Host Frame:C:\Windows\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x6ce51]
=========
========= Program hit cudaErrorLaunchOutOfResources (error 701) due to "too many resources requested for launch" on CUDA API call to cudaGetLastError.
=========     Saved host backtrace up to driver entry point at error
=========     Host Frame:C:\Windows\system32\DriverStore\FileRepository\nv_dispui.inf_amd64_ae0a6307e8a28cc4\nvcuda64.dll (cuProfilerStop + 0x8ff3e) [0x2ad53e]
=========     Host Frame:C:\Windows\system32\DriverStore\FileRepository\nv_dispui.inf_amd64_ae0a6307e8a28cc4\nvcuda64.dll (cuProfilerStop + 0x928e3) [0x2afee3]
=========     Host Frame:C:\Windows\system32\DriverStore\FileRepository\nv_dispui.inf_amd64_ae0a6307e8a28cc4\nvcuda64.dll [0x86ebe]
=========     Host Frame:C:\Windows\system32\DriverStore\FileRepository\nv_dispui.inf_amd64_ae0a6307e8a28cc4\nvcuda64.dll (cuProfilerStop + 0x113e8a) [0x33148a]
=========     Host Frame:C:\Windows\system32\DriverStore\FileRepository\nv_dispui.inf_amd64_ae0a6307e8a28cc4\nvcuda64.dll (cuProfilerStop + 0x12c212) [0x349812]
=========     Host Frame:C:\Users\x\Desktop\VS\VanitySearch.exe [0x1e31]
=========     Host Frame:C:\Users\x\Desktop\VS\VanitySearch.exe [0x4f0cf]
=========     Host Frame:C:\Users\x\Desktop\VS\VanitySearch.exe [0x4a922]
=========     Host Frame:C:\Users\x\Desktop\VS\VanitySearch.exe [0x4643f]
=========     Host Frame:C:\Windows\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x17bd4]
=========     Host Frame:C:\Windows\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x6ce51]
=========
========= ERROR SUMMARY: 2 errors
newbie
Activity: 12
Merit: 0
Could you try to run cuda-memcheck with your input address file ?
Code:
"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\cuda-memcheck.exe" VanitySearch119.exe -gpu -r 1000000 -t 0 -g 320,256 -o found.txt -i 50.txt -stop


After about 3 minutes, there is an error, this is with 100 addresses (-i inputfile). There was no error with 50 addresses. With 500 addresses, an error occurs after a few seconds. We are talking about full bitcoin addresses (example: 152hx7Sp822qqWSPHRbK7b8cKdAaPzALqd)



What you do makes no sense at all.

The point is for the program to work correctly.
member
Activity: 170
Merit: 58
Could you try to run cuda-memcheck with your input address file ?
Code:
"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\cuda-memcheck.exe" VanitySearch119.exe -gpu -r 1000000 -t 0 -g 320,256 -o found.txt -i 50.txt -stop


After about 3 minutes, there is an error, this is with 100 addresses (-i inputfile). There was no error with 50 addresses. With 500 addresses, an error occurs after a few seconds. We are talking about full bitcoin addresses (example: 152hx7Sp822qqWSPHRbK7b8cKdAaPzALqd)



What you do makes no sense at all.
newbie
Activity: 12
Merit: 0
Could you try to run cuda-memcheck with your input address file ?
Code:
"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\cuda-memcheck.exe" VanitySearch119.exe -gpu -r 1000000 -t 0 -g 320,256 -o found.txt -i 50.txt -stop


After about 3 minutes, there is an error, this is with 100 addresses (-i inputfile). There was no error with 50 addresses. With 500 addresses, an error occurs after a few seconds. We are talking about full bitcoin addresses (example: 152hx7Sp822qqWSPHRbK7b8cKdAaPzALqd)
C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin>cuda-memcheck.exe VanitySearch119.exe -gpu -r 1000000 -t 0 -g 320,256 -o found.txt -i 100.txt -stop
========= CUDA-MEMCHECK
VanitySearch v1.19
Search: 101 addresses (Lookup size 101,[1,1]) [Compressed]
Start Wed Aug 26 21:57:03 2020
Base Key: Randomly changed every 1000000 Mkeys
Number of CPU thread: 0
GPU: GPU #0 GeForce RTX 2070 SUPER (40x64 cores) Grid(320x256)
[0.00 Mkey/s][GPU 0.00 Mkey/s][Total 2^28.91][Prob 0.0%][50% in infy][Found 0]  GPUEngine: Launch: unspecified launch failure
========= Invalid __local__ read of size 2
=========     at 0x000158a0 in comp_keys_comp(unsigned short*, unsigned int*, __int64*, unsigned int, unsigned int*)
=========     by thread (57,0,0) in block (210,0,0)
=========     Address 0xb1c420bd is misaligned
=========     Device Frame:comp_keys_comp(unsigned short*, unsigned int*, __int64*, unsigned int, unsigned int*) ($_Z14comp_keys_compPtPjPyjS0_$_Z10CheckPointPjiiiPtS_jS_i : 0xb0)
=========     Saved host backtrace up to driver entry point at kernel launch time
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x81ded]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x82187]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x86889]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x11479a) [0x332d5a]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x1777b9]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0xe9822) [0x307de2]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x361dd]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x36601]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x368e4]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuLaunchKernel + 0x234) [0x20e394]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x3096]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x2164]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4f337]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4f09b]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4a98a]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4643f]
=========     Host Frame:C:\WINDOWS\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x16fd4]
=========     Host Frame:C:\WINDOWS\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x4cec1]
=========
========= Program hit cudaErrorLaunchFailure (error 719) due to "unspecified launch failure" on CUDA API call to cudaEventQuery.
=========     Saved host backtrace up to driver entry point at error
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x9050e) [0x2aeace]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x92eb3) [0x2b1473]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x86f17]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x11479a) [0x332d5a]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x12cd32) [0x34b2f2]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x15e3]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4deaa]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4a98a]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4643f]
=========     Host Frame:C:\WINDOWS\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x16fd4]
=========     Host Frame:C:\WINDOWS\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x4cec1]
=========
========= Program hit cudaErrorLaunchFailure (error 719) due to "unspecified launch failure" on CUDA API call to cudaEventDestroy.
=========     Saved host backtrace up to driver entry point at error
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x9050e) [0x2aeace]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x92eb3) [0x2b1473]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x86f17]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x11479a) [0x332d5a]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x12cd32) [0x34b2f2]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x14b3]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4debb]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4a98a]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4643f]
=========     Host Frame:C:\WINDOWS\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x16fd4]
=========     Host Frame:C:\WINDOWS\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x4cec1]
=========
========= Program hit cudaErrorLaunchFailure (error 719) due to "unspecified launch failure" on CUDA API call to cudaGetLastError.
=========     Saved host backtrace up to driver entry point at error
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x9050e) [0x2aeace]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x92eb3) [0x2b1473]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x86f17]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x11479a) [0x332d5a]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x12cd32) [0x34b2f2]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x1e31]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4dec0]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4a98a]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4643f]
=========     Host Frame:C:\WINDOWS\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x16fd4]
=========     Host Frame:C:\WINDOWS\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x4cec1]
=========
========= Program hit cudaErrorLaunchFailure (error 719) due to "unspecified launch failure" on CUDA API call to cudaFree.
=========     Saved host backtrace up to driver entry point at error
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x9050e) [0x2aeace]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x92eb3) [0x2b1473]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x86f17]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x11479a) [0x332d5a]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x12cd32) [0x34b2f2]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x186c]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4ce72]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4aba8]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4643f]
=========     Host Frame:C:\WINDOWS\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x16fd4]
=========     Host Frame:C:\WINDOWS\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x4cec1]
=========
========= Program hit cudaErrorLaunchFailure (error 719) due to "unspecified launch failure" on CUDA API call to cudaFree.
=========     Saved host backtrace up to driver entry point at error
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x9050e) [0x2aeace]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x92eb3) [0x2b1473]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x86f17]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x11479a) [0x332d5a]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x12cd32) [0x34b2f2]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x186c]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4ce7b]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4aba8]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4643f]
=========     Host Frame:C:\WINDOWS\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x16fd4]
=========     Host Frame:C:\WINDOWS\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x4cec1]
=========
========= Program hit cudaErrorLaunchFailure (error 719) due to "unspecified launch failure" on CUDA API call to cudaFree.
=========     Saved host backtrace up to driver entry point at error
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x9050e) [0x2aeace]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x92eb3) [0x2b1473]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x86f17]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x11479a) [0x332d5a]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x12cd32) [0x34b2f2]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x186c]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4ce89]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4aba8]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4643f]
=========     Host Frame:C:\WINDOWS\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x16fd4]
=========     Host Frame:C:\WINDOWS\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x4cec1]
=========
========= Program hit cudaErrorLaunchFailure (error 719) due to "unspecified launch failure" on CUDA API call to cudaFreeHost.
=========     Saved host backtrace up to driver entry point at error
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x9050e) [0x2aeace]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x92eb3) [0x2b1473]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x86f17]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x11479a) [0x332d5a]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x12cd32) [0x34b2f2]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x198c]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4ce92]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4aba8]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4643f]
=========     Host Frame:C:\WINDOWS\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x16fd4]
=========     Host Frame:C:\WINDOWS\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x4cec1]
=========
========= Program hit cudaErrorLaunchFailure (error 719) due to "unspecified launch failure" on CUDA API call to cudaFree.
=========     Saved host backtrace up to driver entry point at error
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x9050e) [0x2aeace]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x92eb3) [0x2b1473]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x86f17]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x11479a) [0x332d5a]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x12cd32) [0x34b2f2]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x186c]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4ce9b]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4aba8]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4643f]
=========     Host Frame:C:\WINDOWS\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x16fd4]
=========     Host Frame:C:\WINDOWS\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x4cec1]
=========
========= Program hit CUDA_ERROR_LAUNCH_FAILED (error 719) due to "unspecified launch failure" on CUDA API call to cuModuleUnload.
=========     Saved host backtrace up to driver entry point at error
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x9050e) [0x2aeace]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x92eb3) [0x2b1473]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x84cd7]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x86e13]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x11479a) [0x332d5a]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuModuleUnload + 0x1d6) [0x1d6766]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0xb775]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0xbd76]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0xc3a8]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x3c1d]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x9206]
=========     Host Frame:C:\WINDOWS\System32\ucrtbase.dll (execute_onexit_table + 0x156) [0x13c86]
=========     Host Frame:C:\WINDOWS\System32\ucrtbase.dll (execute_onexit_table + 0x7b) [0x13bab]
=========     Host Frame:C:\WINDOWS\System32\ucrtbase.dll (execute_onexit_table + 0x34) [0x13b64]
=========     Host Frame:C:\WINDOWS\System32\ucrtbase.dll (exit + 0x142) [0x1ff42]
=========     Host Frame:C:\WINDOWS\System32\ucrtbase.dll (exit + 0xcb) [0x1fecb]
=========     Host Frame:C:\WINDOWS\System32\ucrtbase.dll (exit + 0x6e) [0x1fe6e]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x50153]
=========     Host Frame:C:\WINDOWS\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x16fd4]
=========     Host Frame:C:\WINDOWS\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x4cec1]
=========
========= ERROR SUMMARY: 10 errors

C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin>pause
Для пpoдoлжeния нaжмитe любyю клaвишy . . .
sr. member
Activity: 462
Merit: 701
Could you try to run cuda-memcheck with your input address file ?
Code:
"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\cuda-memcheck.exe" VanitySearch119.exe -gpu -r 1000000 -t 0 -g 320,256 -o found.txt -i 50.txt -stop
newbie
Activity: 12
Merit: 0
The Cuda version is the most recent and the graphics card drivers are the same. The bug is present on versions VanitySearch1.18 and VanitySearch1.19. What to do help. Videocard 2070super. Sorry for google translate

Hello,

Could you try to run cuda-memcheck.exe. I didn't manage to reproduce this issue. It may end with "Error: process didn't terminate successfully" but this does not prevent the program to run, this error happens in the exit function...

Code:
C:\C++\VanitySearch>"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\cuda-memcheck.exe" --tool memcheck x64\Release\VanitySearch.exe -t 0 -gpu -stop 1Tst
========= CUDA-MEMCHECK
VanitySearch v1.19
Difficulty: 4553521
Search: 1Tst [Compressed]
Start Wed Aug 26 10:26:21 2020
Base Key: 83F4E602C7131AFCED71A0BD26861B5EED0402F945D3BE944D7E4148FCCA31CB
Number of CPU thread: 0
GPU: GPU #0 GeForce GTX 1050 Ti (6x128 cores) Grid(48x128)
[0.00 Mkey/s][GPU 0.00 Mkey/s][Total 2^-inf][Prob 0.0%][50% in infy][Found 0]
PubAddress: 1TstZdrmCC2HqcacyiteMUxkHTFsoLGxq
Priv (WIF): p2pkh:L3n1tjjp5VBMncFo3PUWBV8fgYPov7JDeQe5SXNXWqrfH17E1ksu
Priv (HEX): 0xC3A4B99A401854FCDF9E276F831E807DDB92031B47843371E503FD1447F0784D
========= Error: process didn't terminate successfully
========= No CUDA-MEMCHECK results found

It just happened like this:
C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\cuda-memcheck.exe --tool memcheck VanitySearch119.exe -t 0 -gpu -stop 1Tst
========= CUDA-MEMCHECK
VanitySearch v1.19
Difficulty: 4553521
Search: 1Tst [Compressed]
Start Wed Aug 26 12:59:31 2020
Base Key: 55178A21BDB7163ED5182EAA9D89D164A7D8D5ED1270E5627EF8EEAAAA8366C0
Number of CPU thread: 0
GPU: GPU #0 GeForce RTX 2070 SUPER (40x64 cores) Grid(320x128)
[0.00 Mkey/s][GPU 0.00 Mkey/s][Total 2^-inf][Prob 0.0%][50% in infy][Found 0]
PubAddress: 1TstGtwj3gcEnGWoU5qf9RrkYy3HcHht4
Priv (WIF): p2pkh:L2ww7Y8jJg1K47pY5hReciMTwWaKj8kvx8A9crG2qGTY8Wcp9T7a
Priv (HEX): 0xAAE875DE4248E9C12AE7D15562762E9A125606F96CEFBAD940D96FE225B2D873
newbie
Activity: 12
Merit: 0
The Cuda version is the most recent and the graphics card drivers are the same. The bug is present on versions VanitySearch1.18 and VanitySearch1.19. What to do help. Videocard 2070super. Sorry for google translate

Hello,

Could you try to run cuda-memcheck.exe. I didn't manage to reproduce this issue. It may end with "Error: process didn't terminate successfully" but this does not prevent the program to run, this error happens in the exit function...

Code:
C:\C++\VanitySearch>"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\cuda-memcheck.exe" --tool memcheck x64\Release\VanitySearch.exe -t 0 -gpu -stop 1Tst
========= CUDA-MEMCHECK
VanitySearch v1.19
Difficulty: 4553521
Search: 1Tst [Compressed]
Start Wed Aug 26 10:26:21 2020
Base Key: 83F4E602C7131AFCED71A0BD26861B5EED0402F945D3BE944D7E4148FCCA31CB
Number of CPU thread: 0
GPU: GPU #0 GeForce GTX 1050 Ti (6x128 cores) Grid(48x128)
[0.00 Mkey/s][GPU 0.00 Mkey/s][Total 2^-inf][Prob 0.0%][50% in infy][Found 0]
PubAddress: 1TstZdrmCC2HqcacyiteMUxkHTFsoLGxq
Priv (WIF): p2pkh:L3n1tjjp5VBMncFo3PUWBV8fgYPov7JDeQe5SXNXWqrfH17E1ksu
Priv (HEX): 0xC3A4B99A401854FCDF9E276F831E807DDB92031B47843371E503FD1447F0784D
========= Error: process didn't terminate successfully
========= No CUDA-MEMCHECK results found

Found something, the error appears if there are more than 50 addresses in the file (-i inputfile). My settings- VanitySearch119.exe -gpu -r 1000000 -t 0 -g 320,256 -o found.txt -i 50.txt -stop . Version VanitySearch 1.17 works with any number of addresses in the file (-i inputfile)     https://ibb.co/17p2X58
sr. member
Activity: 462
Merit: 701
The Cuda version is the most recent and the graphics card drivers are the same. The bug is present on versions VanitySearch1.18 and VanitySearch1.19. What to do help. Videocard 2070super. Sorry for google translate

Hello,

Could you try to run cuda-memcheck.exe. I didn't manage to reproduce this issue. It may end with "Error: process didn't terminate successfully" but this does not prevent the program to run, this error happens in the exit function...

Code:
C:\C++\VanitySearch>"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\cuda-memcheck.exe" --tool memcheck x64\Release\VanitySearch.exe -t 0 -gpu -stop 1Tst
========= CUDA-MEMCHECK
VanitySearch v1.19
Difficulty: 4553521
Search: 1Tst [Compressed]
Start Wed Aug 26 10:26:21 2020
Base Key: 83F4E602C7131AFCED71A0BD26861B5EED0402F945D3BE944D7E4148FCCA31CB
Number of CPU thread: 0
GPU: GPU #0 GeForce GTX 1050 Ti (6x128 cores) Grid(48x128)
[0.00 Mkey/s][GPU 0.00 Mkey/s][Total 2^-inf][Prob 0.0%][50% in infy][Found 0]
PubAddress: 1TstZdrmCC2HqcacyiteMUxkHTFsoLGxq
Priv (WIF): p2pkh:L3n1tjjp5VBMncFo3PUWBV8fgYPov7JDeQe5SXNXWqrfH17E1ksu
Priv (HEX): 0xC3A4B99A401854FCDF9E276F831E807DDB92031B47843371E503FD1447F0784D
========= Error: process didn't terminate successfully
========= No CUDA-MEMCHECK results found
newbie
Activity: 12
Merit: 0
Why don't VanitySearch1.18 and VanitySearch1.19 versions work for me, reports the error GPUEngine: Launch: an illegal memory access was encountered, and VanitySearch1.17 version works correctly? Help me to understand.

GPUEngine: Launch: an illegal memory access was encountered

PS C:\WINDOWS\system32> nvcc -V
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2020 NVIDIA Corporation
Built on Wed_Jul_22_19:09:35_Pacific_Daylight_Time_2020
Cuda compilation tools, release 11.0, V11.0.221
Build cuda_11.0_bu.relgpu_drvr445TC445_37.28845127_0
PS C:\WINDOWS\system32>

The Cuda version is the most recent and the graphics card drivers are the same. The bug is present on versions VanitySearch1.18 and VanitySearch1.19. What to do help. Videocard 2070super. Sorry for google translate
legendary
Activity: 2646
Merit: 6681
Self-proclaimed Genius
I don't run an antivirus though. I'm pretty sure there's an issue with cpu thread selections on some CPUs and that's what I'm encountering atm.
Run it using a different command, like vanitysearch -o output.txt 1a.
If it consumes all of your CPU resource, then it's not "that issue".

I think the problem is the way you want to use vanitysearch, it's not meant for creating bulk random addresses IMO.
I'm pretty sure that there are other tools that can do that bulk address generation better (I don't have one however).

Why don't VanitySearch1.18 and VanitySearch1.19 versions work for me, reports the error GPUEngine: Launch: an illegal memory access was encountered, and VanitySearch1.17 version works correctly?
You have the same issue as this guy: Issue #70
And one of v1.18's release note was "Updated to CUDAv11", maybe it has something to do with your drivers.
newbie
Activity: 12
Merit: 0
Why don't VanitySearch1.18 and VanitySearch1.19 versions work for me, reports the error GPUEngine: Launch: an illegal memory access was encountered, and VanitySearch1.17 version works correctly? Help me to understand.
newbie
Activity: 7
Merit: 0
Okay, I've ran some tests and noticed that:
My antivirus is acting up whenever I'm using vanitysearch, it's not detecting anything but consuming a lot of resources.
Much higher than what Vanitysearch is using; so I've included it to my AV's "exceptions list".
And it worked!

What's the best way of maximizing the generation speed ? Is there any good config out there?
Somehow, vanitysearch isn't using all of the cores or even processing power when using that command, there should be something wrong.

Whatever the reason is, I've tried to use 1 thread and it resulted with a slightly slower rate (just about -10%).
So, try to run 3-4 instances of Vanitysearch running with the same command but pointing to different output files.

Creating batch files is a good shortcut to do this, eg.:
instance1.bat
Code:
vanitysearch -t 1 -o output1.txt 1*
instance2.bat
Code:
vanitysearch -t 1 -o output2.txt 1*
instance3.bat
Code:
vanitysearch -t 1 -o output3.txt 1*
...And so forth

Each instance will be slower than a solo instance but overall number of generated addresses and keys could be higher.

Yeah, I already thought about that, to use different instances of Vanity

I don't run an antivirus though. I'm pretty sure there's an issue with cpu thread selections on some CPUs and that's what I'm encountering atm.

I also don't run an AV because I don't need one, I tried with Defender off aswell and same result. Nothing is using my processor except vanity.
Pages:
Jump to: