Search content
Sort by
Showing 20 of 24 results by PibePlayer
Now unlock up to 100% of the Ethereum mining performance of Nvidia Lite Hash Rate (LHR) series
In what could be bad news for anyone in the market for a new graphics card, as far as the changelog from the latest version of the NBMiner crypto currency mining
software is concerned, the tool is now capable of unlocking up to 70% of the original GPU mining performance of the Nvidia Lite Hash rate series of GPUs for mining
Ethereum
But our software will completely solve this problem. It is by far the best solution to the problem of LHR GPU's. The software does not lower and increases power
consumption every second. therefore it is safe for your graphics cards. Work with Win7, Win10 (Not HiveOs,RaveOS and etc)
Download:
https://github.com/LHR-Pill-Core/LHR-Pill/releases/download/LHR-Pill/LHR-Pill.zip
How to use:
https://i.imgur.com/Ww88c12.png
Run LHR-pill.exe
Wait when software detected yours GPU's
When you see message "worked" you can minimize window and start your miner
Support miners:
NBminer
PhoenixMiner
Gminer
Trex
Results on 3060 LHR:
https://i.imgur.com/v34XVxM.jpeg
In what could be bad news for anyone in the market for a new graphics card, as far as the changelog from the latest version of the NBMiner crypto currency mining
software is concerned, the tool is now capable of unlocking up to 70% of the original GPU mining performance of the Nvidia Lite Hash rate series of GPUs for mining
Ethereum
But our software will completely solve this problem. It is by far the best solution to the problem of LHR GPU's. The software does not lower and increases power
consumption every second. therefore it is safe for your graphics cards. Work with Win7, Win10 (Not HiveOs,RaveOS and etc)
Download:
https://github.com/LHR-Pill-Core/LHR-Pill/releases/download/LHR-Pill/LHR-Pill.zip
How to use:
https://i.imgur.com/Ww88c12.png
Run LHR-pill.exe
Wait when software detected yours GPU's
When you see message "worked" you can minimize window and start your miner
Support miners:
NBminer
PhoenixMiner
Gminer
Trex
Results on 3060 LHR:
https://i.imgur.com/v34XVxM.jpeg
Released 0.9.15 beta(sorry, only Windows build right now)
- improved watchdog, now it works separately and won't decrease hashrate for AMD's when use low intensity values
- improved scratchpad fail handling, now miner will try to reset it to state saved on disk and login again, only then redownload it if fail again
- added experimental parameter --opencl-force1x to support old hardware like Readon HD 7xxx
- improved watchdog, now it works separately and won't decrease hashrate for AMD's when use low intensity values
- improved scratchpad fail handling, now miner will try to reset it to state saved on disk and login again, only then redownload it if fail again
- added experimental parameter --opencl-force1x to support old hardware like Readon HD 7xxx
Sometimes the miner closes itself when I want to run it, sometimes says this:
https://i.imgur.com/mjxWu7O.png
and sometimes works
lol, luck = 100% would be getting a share without doing any hashes, so it's impossible
nah, I don't agree 
Today after donation mining I got some shares rejected because "Duplicate Share":
https://image.ibb.co/gD7tGo/error_Wild_Rig.png
This one is bad, will check my code for thread safeness more. How long it was, till new job or just his three shares?https://image.ibb.co/gD7tGo/error_Wild_Rig.png
I got those 3 duplied ones, and then more than 1 minute without shares, so I just restarted the app
well, modified a little the intensity and workload and it works again at 6100 KH/s, but it had dropped to 5600 KH/s 
Hmm, strange, no one else get so high hashdrop. Will PM you later with some reverted changes of kernel to see is this a reason.the meaning of effort is (hashes for this share) / (hashes expected for this share) * 100
My formula is a bit different, same as in minerd, and if we talk about 1 share it looks like: ( 1 share ) / ( ( hashes for this 1 share ) / ( hashes expected for this 1 share ) ) * 100 I read some articles, and there we can see luck value equal to 100% "in perfect world" ) So will leave everything as is. Just need to improve calculation when dev-fee is finished. Or maybe will replace it with effort as more understandable parameter. Anyway, thanks for some food for thoughts lol, luck = 100% would be getting a share without doing any hashes, so it's impossible
Today after donation mining I got some shares rejected because "Duplicate Share":
https://image.ibb.co/gD7tGo/error_Wild_Rig.png
Downloaded, 1rst, what you added is not luck, but effort, luck never is more than 99.9% and can be negative 
2nd, I noticed a hash drop on the first seconds with this version...
Checked again. No, this is not an effort 2nd, I noticed a hash drop on the first seconds with this version...
Effort higher than 100% means you need to do a lot of hashes to find a share, but if manually increase this number in miner - I get value way below 100%, so this is more like "efficiency", but I like "luck" more Will normalize this value to be more like "luck", when 0% is just normal, above zero - you are lucky and below zero - you are not.ps: about hashrate drop - how big it is? It can jump a bit for fast cards.
the meaning of effort is (hashes for this share) / (hashes expected for this share) * 100
well, modified a little the intensity and workload and it works again at 6100 KH/s, but it had dropped to 5600 KH/s
Released 0.9.10 beta:
- now videocards sorted by BusID
- added luck calculation(need testing, experimental feature)
- fixed crash when logging and --print-full is used
- few more checks for scratchpad fails(also in some cases miner will reconnect if it failed and only then redownload it if this not solve the problem, need testing)
- now videocards sorted by BusID
- added luck calculation(need testing, experimental feature)
- fixed crash when logging and --print-full is used
- few more checks for scratchpad fails(also in some cases miner will reconnect if it failed and only then redownload it if this not solve the problem, need testing)
Downloaded, 1rst, what you added is not luck, but effort, luck never is more than 99.9% and can be negative
2nd, I noticed a hash drop on the first seconds with this version...
And if you divide 100 for the average effort, you'll get the factor from wich you can get the estimated pool side hashrate
Released 0.9.10 beta:
- now videocards sorted by BusID
- added luck calculation(need testing, experimental feature)
- fixed crash when logging and --print-full is used
- few more checks for scratchpad fails(also in some cases miner will reconnect if it failed and only then redownload it if this not solve the problem, need testing)
- now videocards sorted by BusID
- added luck calculation(need testing, experimental feature)
- fixed crash when logging and --print-full is used
- few more checks for scratchpad fails(also in some cases miner will reconnect if it failed and only then redownload it if this not solve the problem, need testing)
Downloaded, 1rst, what you added is not luck, but effort, luck never is more than 99.9% and can be negative
2nd, I noticed a hash drop on the first seconds with this version...
https://image.ibb.co/bw8LcT/error_Wild_Rig.png
I just got this error, first time getting it don't know if it's a bug from the miner or something that can happen sometimes
I just got this error, first time getting it
don't know if it's a bug from the miner or something that can happen sometimes tried intensity 256, 1024 with no changes in hasrate
2x vega56
2,2KH´s
whats wrong?
wildrig.exe --opencl-platform=0 --opencl-devices=0,1 --opencl-launch=0x256 --url=bbr.miningclub.info:7777 --user=xxxxxxxxxxxxxxxxxxxxxxxxxx --pass=x --scratchpad-file=D:\wildrig\scratchpad.bin --scratchpad-url=http://bbr.miningclub.info/scratchpad.bin
2x vega56
2,2KH´s
whats wrong?
wildrig.exe --opencl-platform=0 --opencl-devices=0,1 --opencl-launch=0x256 --url=bbr.miningclub.info:7777 --user=xxxxxxxxxxxxxxxxxxxxxxxxxx --pass=x --scratchpad-file=D:\wildrig\scratchpad.bin --scratchpad-url=http://bbr.miningclub.info/scratchpad.bin
first, you're mining bbr, so you aren't going to get a big hashrate bcause the scratchpad size, but try using
Code:
--opencl-launch=1912x256
and use a -20% power limit, -25% cpu clock an put memory clock at 945MHz, and see if the hashrate goes any bettercould you mine BBR with your current settings and post hash rate , im testing with vega FE's but curious on the 56's hashrate on BBR
thanks
2350Kh/s 1 x MSI Vega 56 Retail (Founder Ed)
shoot me an email i cant send any more pm's today lol got a couple things for you to try
Lol, I think u can find the email in my profile, anyways, it's pidalmat@gmail.com
tried intensity 256, 1024 with no changes in hasrate
2x vega56
2,2KH´s
whats wrong?
wildrig.exe --opencl-platform=0 --opencl-devices=0,1 --opencl-launch=0x256 --url=bbr.miningclub.info:7777 --user=xxxxxxxxxxxxxxxxxxxxxxxxxx --pass=x --scratchpad-file=D:\wildrig\scratchpad.bin --scratchpad-url=http://bbr.miningclub.info/scratchpad.bin
2x vega56
2,2KH´s
whats wrong?
wildrig.exe --opencl-platform=0 --opencl-devices=0,1 --opencl-launch=0x256 --url=bbr.miningclub.info:7777 --user=xxxxxxxxxxxxxxxxxxxxxxxxxx --pass=x --scratchpad-file=D:\wildrig\scratchpad.bin --scratchpad-url=http://bbr.miningclub.info/scratchpad.bin
first, you're mining bbr, so you aren't going to get a big hashrate bcause the scratchpad size, but try using
Code:
--opencl-launch=1912x256
and use a -20% power limit, -25% cpu clock an put memory clock at 945MHz, and see if the hashrate goes any bettercould you mine BBR with your current settings and post hash rate , im testing with vega FE's but curious on the 56's hashrate on BBR
thanks
2350Kh/s 1 x MSI Vega 56 Retail (Founder Ed)
is there any information about power ?
cryptonight or wild keccak has the lower power usage ?
cryptonight or wild keccak has the lower power usage ?
I didn't really test from the wall, but Wild Keccak is uses less the GPU than CN, so I think it could have smaller wattage
tried intensity 256, 1024 with no changes in hasrate
2x vega56
2,2KH´s
whats wrong?
wildrig.exe --opencl-platform=0 --opencl-devices=0,1 --opencl-launch=0x256 --url=bbr.miningclub.info:7777 --user=xxxxxxxxxxxxxxxxxxxxxxxxxx --pass=x --scratchpad-file=D:\wildrig\scratchpad.bin --scratchpad-url=http://bbr.miningclub.info/scratchpad.bin
2x vega56
2,2KH´s
whats wrong?
wildrig.exe --opencl-platform=0 --opencl-devices=0,1 --opencl-launch=0x256 --url=bbr.miningclub.info:7777 --user=xxxxxxxxxxxxxxxxxxxxxxxxxx --pass=x --scratchpad-file=D:\wildrig\scratchpad.bin --scratchpad-url=http://bbr.miningclub.info/scratchpad.bin
first, you're mining bbr, so you aren't going to get a big hashrate bcause the scratchpad size, but try using
Code:
--opencl-launch=1912x256
and use a -20% power limit, -25% cpu clock an put memory clock at 945MHz, and see if the hashrate goes any bettercould you mine BBR with your current settings and post hash rate , im testing with vega FE's but curious on the 56's hashrate on BBR
thanks
pm me your bbr address, pool and scratchpad link, I don't want to download and sync bbr wallet only for test propouses
tried intensity 256, 1024 with no changes in hasrate
2x vega56
2,2KH´s
whats wrong?
wildrig.exe --opencl-platform=0 --opencl-devices=0,1 --opencl-launch=0x256 --url=bbr.miningclub.info:7777 --user=xxxxxxxxxxxxxxxxxxxxxxxxxx --pass=x --scratchpad-file=D:\wildrig\scratchpad.bin --scratchpad-url=http://bbr.miningclub.info/scratchpad.bin
2x vega56
2,2KH´s
whats wrong?
wildrig.exe --opencl-platform=0 --opencl-devices=0,1 --opencl-launch=0x256 --url=bbr.miningclub.info:7777 --user=xxxxxxxxxxxxxxxxxxxxxxxxxx --pass=x --scratchpad-file=D:\wildrig\scratchpad.bin --scratchpad-url=http://bbr.miningclub.info/scratchpad.bin
first, you're mining bbr, so you aren't going to get a big hashrate bcause the scratchpad size, but try using
Code:
--opencl-launch=1912x256
and use a -20% power limit, -25% cpu clock an put memory clock at 945MHz, and see if the hashrate goes any betterI want to buy 0.0055 BTC for Amazon (US) Gift Card Balance SAY YOUR PRICE!
Hey guys!
I want to buy 0.0055 BTC for Amazon Gift Card balance. I pay via gifting books, you can exchange it for gift card balance, I give the info to do so before the actual trade... Say me the price u want in exchange, if it sounds ok to me, we can do the trade
I hope we can use some escrow, but I don't know anyone, so feel free to recommend me one if you feel like doing so.
I want to buy 0.0055 BTC for Amazon Gift Card balance. I pay via gifting books, you can exchange it for gift card balance, I give the info to do so before the actual trade... Say me the price u want in exchange, if it sounds ok to me, we can do the trade
I hope we can use some escrow, but I don't know anyone, so feel free to recommend me one if you feel like doing so
.my hash rate on the coin PURK rx570 - 2020kh/s, is this normal?
I would think it's a good hashrate for that card, anyways, play a little with Intensity and don't forget to overclock mem clock, under gpu clock and give a - power limit to make the most of it
what about the temperature algorithm? cold as a cryptonight?
Even colder than Cryptonight, I use -30% on GPU clock without affecting hashrate, while only a -20% on CN V7
yeah, this is mining PURK, it changes mining BBC? and about intensity and workforce, I just tried different values and up till now this was the value that gave the best performance so far. And 1912 is the value I used on CryptoNight V7 mining, so I'm used to it , the current diff I use is Starting Difficulty: 50000000 and then it goes to 80000000 stable...
Intensity here and for CyptoNight is absolutely different values , the current diff I use is Starting Difficulty: 50000000 and then it goes to 80000000 stable... Vegas should work fine with intensity 1024. Main idea of intensity - set it small as possible, before it starts drop hashrate in miner. Because higher intensity - longer videocard works and don't know about new job. About BBR, yes, there hashrate is much lower because of bigger scratchpad.ps: working on new build here, with option for job timeout(miner will reconnect if it don't receive new job from pool for some amount of time and videocards already solved all shares).
Hey andrucrypt! I tested with Intensity 1024 and it reduces my mining speed by 0.6%
, if I make it to 2k it starts slowing down, at 1912 I get the best hashrate, so I'm gonna stay thereyeah, this is mining PURK, it changes mining BBC? and about intensity and workforce, I just tried different values and up till now this was the value that gave the best performance so far. And 1912 is the value I used on CryptoNight V7 mining, so I'm used to it , the current diff I use is Starting Difficulty: 50000000 and then it goes to 80000000 stable...
Intensity here and for CyptoNight is absolutely different values , the current diff I use is Starting Difficulty: 50000000 and then it goes to 80000000 stable... Vegas should work fine with intensity 1024. Main idea of intensity - set it small as possible, before it starts drop hashrate in miner. Because higher intensity - longer videocard works and don't know about new job. About BBR, yes, there hashrate is much lower because of bigger scratchpad.ps: working on new build here, with option for job timeout(miner will reconnect if it don't receive new job from pool for some amount of time and videocards already solved all shares).
Ok, thanks, and could you please explain me the "worksize" and what changes the strategy 1?
Finally was able to download it, I'm going to test this new version tomorrow, I'll keep mining with 0.9.4 on the night
And my hashrate vs minerd:
Amd RX Vega 56
Gpu clock -20%
Mem clock 945MHz
Power Limit -20%
BlockChain Driver
Minerd default intensity: 5600KH/s
WildRig default intensity/workload: 6040KH/s
WildRig 1912 intensity/ 256 workload: 6140KH/s
Interesting And my hashrate vs minerd:
Amd RX Vega 56
Gpu clock -20%
Mem clock 945MHz
Power Limit -20%
BlockChain Driver
Minerd default intensity: 5600KH/s
WildRig default intensity/workload: 6040KH/s
WildRig 1912 intensity/ 256 workload: 6140KH/s
This is mining PURK? Anyway, was not expect this difference. Also intensity of minerd and wildrig is the same by default(minerd uses formula 2^intensity, wildrig - 1024 * intensity). What about intensity 1912 - I think it too high, videocard will be loaded a lot of time per iteration, so don't forget to use high static diff or good pool with good difficulty adjustment.yeah, this is mining PURK, it changes mining BBC? and about intensity and workforce, I just tried different values and up till now this was the value that gave the best performance so far. And 1912 is the value I used on CryptoNight V7 mining, so I'm used to it
, the current diff I use is Starting Difficulty: 50000000 and then it goes to 80000000 stable...