Topic: Vanitygen: Vanity bitcoin address generator/miner [v0.22] - page 74. (Read 1153383 times)

Looking for some advice if anyone has an answer.

I can run the miner (oclvanityminer64.exe) on my GTX860M without any issues, but when I try to use the miner (oclvanitygen.exe) to mine a address locally I get the following error.

Difficulty: 15318045009
clWaitForEvents(NDRange,0): Unknown code -9999
Device: GeForce GTX 860M
Vendor: NVIDIA Corporation (10de)
Driver: 350.12
Profile: FULL_PROFILE
Version: OpenCL 1.2 CUDA
Max compute units: 5
Max workgroup size: 1024
clEnqueueMapBuffer(4): CL_INVALID_COMMAND_QUEUE
Global memory: -2147483648
Max allocation: 536870912
Device: GeForce GTX 860M
Vendor: NVIDIA Corporation (10de)
Driver: 350.12
Profile: FULL_PROFILE
Version: OpenCL 1.2 CUDA
Max compute units: 5
Max workgroup size: 1024
Global memory: -2147483648
Max allocation: 536870912
ERROR: Could not map row buffer for slot 1
ERROR: allocation failure?

Anyone know how to get around this? Possible that its because its not x64?

If that is the case, does anyone know if there is a build for x64?

Thanks for the Program, I'm lucky to have a 4 letter name
Only takes a couple minutes to create 100 vanity's
Cheers

 You are partially correct.  The program searches for all prefixes in your file and shows the probability of matching not the easiest but any prefix (it's basically showing the sum of all of the individual probabilities).  Prefixes with a higher probability will likely be matched first but not necessarily.  

it will search for all prefixes contained in your input file.  the program just displays probability information for the easiest prefix, ie based on probability it expects to find the easiest one first, then the next easiest... it will keep displaying the next easiest prefix probability stats. as it finds each one it "removes" it from its list in memory.

I have two AMD Radeon R9 200 HD 7900 Series Graphics cards in a Win 7 box. 

Reading through the earlier posts of this thread, I went off and updated the drivers to the latest Ver 15xxx I would get ~ 25 - 27 MKey/s per card but then would get stalked night and day by Delta and Co.

Some more reading and using the -S safe mode, the speed is throttled back to ~ 9 or 10 MKeys/s per card

So, more reading and I used the uninstall program mentioned here and uninstalled the AMD drivers, then installed the ver 12.10 drivers as suggested.

I would again get ~ 25MKeys/s per card, but then Delta... she came knocking again.

So I again used -S safe-mode and got ~ 6Mkeys/s per card.

So I rolled back to the previous install (15xxx) and am back to either ~25Mkeys/s with Delta lurking behind every rose bush, or -S safe mode ~10Mkeys/s

However... after about 48 - 60 hours the program freezes, so I have to Control-C to exit and start afresh.

Any suggestions would be appreciated.

I also have a 2 - 3 yo laptop with an nVidia graphics card and get ~2 Mkeys/s (in all of these examples using oclvanitygen ) without having done anything to the drivers and haven't had Delta come a knocking, so am thinking of taking one of the AMD cards out of the Win 7 box, dropping a GTX 780 Ti card in to search for vanity wallets and the remaining AMD I can use for incidental script mining or Vanity mining for other Alt coin wallets from time to time.

Just one final question:

I have a work.txt with about 200 wallet prefixes to search for; I'm a little unclear, does the program search for all work examples, or focuses on one particularly easy one?  Why I ask when I've had to restart due to the program freezing (or last night's suburb wide black out for 20mins) the same results occur in the same order and at about the same time duration.

Thanks for looking.

You don't have to uninstall all of AMD drivers to use a Tahiti GPU.

Search for Lifeboats vanitygen, it works very well.

 You are getting rather confused I think. You have switched the devices on us??
-d 1 should not be the GPU

Earlier you told us this:


 Which indicates that the device 0:0 is the Tahiti (or the GPU) and the device 0:1 is the i7-4770

 So the option -d 0 should use the GPU but it doesn't work properly because you have the wrong driver version for AMD which will not work with oclvanitygen.  It is evident by the output you have shown us.
 Using the option -d 1 will use the CPU but it doesn't make sense to use oclvanitygen on a CPU when in fact vanitygen would probably be faster.

You have to completely uninstall the AMD drivers and reinstall with an older version.  I will try to find this information - I believe it was already posted here with a batch file to assist in removal.

It won't exist until a result is found

Might want to run them a little longer than 20 seconds, but I'd also double-check what (ocl)vanitygen is putting on the screen.  It could be that your GPU is generating addresses that are invalid when checked by the CPU, and thus rejected and not written out to the output file.  Edit: Oh, and just in case it's not clear, the keys/s only means the number of keys it can check per second - you'll find far fewer vanity addresses per second than that

so

CPU: oclvanitygen -d 1 -S -k -o D:\Text.txt 1 -- 20sec = 1131 count of addresses
GPU: oclvanitygen -d 0 -S -k -o D:\Text.txt 1 -- 20sec = 13 count of addresses

why is my CPU so fast ? and my GPU soo bad

i7 4770K = 1MKey's
AMD R9 280x = 29 - 30 MKey's

where are the 30 MKey's ??

CPU 1 - 1,5 MKey's
GPU 29 - 30 MKey's

So, i will use the GPU, but the output is ....

 In the first instance you are using OCL version but your drivers do not work so you get weird output.
In the second instance you are using the CPU and not the GPU so the drivers causing the problem in the first instance are not used.

with this cmd: oclvanitygen -d 1 -k -i -o D:\Text.txt 1Abc
what is your hashrate?  I am guessing sub 1mKeys/s because you are using the CPU.

so look my, only hash - what i do wrong

with cmd: oclvanitygen -d 0 -k -i -o D:\Text.txt 1Abc

Match idx: 9
CPU hash: 34af76e7417a64b21822982115c0a38b263be
GPU hash: 64bb46b9f30ea67bb08f26f76e71455d7b1f8
Found delta: 8376487 Start delta: 1
[10.86 Mkey/s][total 8388608]

Text.txt file is not there


with cmd: oclvanitygen -d 1 -k -i -o D:\Text.txt 1Abc

Pattern: 1Abc
Address: 1ABCcNwi2ZiVsc7rhAihAUq1nRRnRJSYLo
Privkey: 5KBLRMEJdUHjJHboBzXHK6w2fQsZ8ch19ZKjsC8AED29HxzSbzS

Text.txt file is there

Available OpenCL platforms:
0: [Advanced Micro Devices, Inc.] AMD Accelerated Parallel Processing
  0: [Advanced Micro Devices, Inc.] Tahiti
  1: [GenuineIntel] Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz

Just ran another quick test as per the image below. Worked fine and created the text file as you can see

do you create the file self or do it the program ? ( program i think )

how you finish the process ( STRG + C )

Not sure what the problem is then, maybe somebody else can assist. I just tested on my pc and it works fine. The text file is there with all the relevant details inside.

I test it, but

C:\Users\XX\Test.txt
C:\Users\XX\Desktop\t\Test.txt
C:\Windows\Temp\Test.txt
D:\test\Test.txt

oclvanitygen.exe -d 0 -o C:\Users\XX\Desktop\t\Test.txt 1ABE

no file ....

It should be there but if not try changing your line to

C:\Users\XX\Desktop\t\>oclvanitygen.exe -d 0 -o C:\Users\XX\Desktop\t\Test.txt 1ABE

Include the path

Just thinking now, is not maybe a problem with not having administrator right to save in that folder?

If that does not work try and save it somewhere else like -0 C:\Temp\Test.txt

Hey,

where is the file with the addresses ?

C:\>cd C:\Users\XX\Desktop\t\
C:\Users\XX\Desktop\t\>oclvanitygen.exe -d 0 -o Test.txt 1ABE


C:\Users\XX\Desktop\t\Test.txt - - does not exist

Where are you running the command from?  If it's from another directory, a shortcut, or batch file, or anything like that, there's a chance that the working directory is not "C:\Users\XX\Desktop\t\".  "C:\Users\XX\Desktop\t\" has to be the working directory for oclvanitygen to find that file.

Easiest way to make sure is by opening a command prompt, navigating to that directory, and then running it;
( Note that you can't use the lowercase letter L - unrelated to this error, but just in case )