Any idea how to find out which driver is used on Win 10?
I definitely have the latest Cuda toolkit installed, but not sure how to find, if the driver is 410.66.
Also, not sure how to reinstall the specific driver if needed and not touch the latest toolkit.
Thanks.
To check the driver, right click the desktop and go to NVIDIA panel…
To Uninstall just the Driver, go to Control Panel and Uninstall a Program, and select only the Display Adapter Driver…
PS - not a good Idea to uninstall and reinstall a different driver then what cammes with the toolkit, but it might work…
1 Like
FYI 15.5.2 is about .4 - .5 G/s slower on a GTX 1080 TI vs 15.4.0 using Nvidia’s 425.31 drivers using stock settings.
Bminer 15.5.3 is released!
- Fix invalid shares ETH + VBK when using multiple cards.
Please see https://bminer.me/releases/ for more information.
Happy Mining.
【Sample Usage of dual mining ETH/ VBK】
bminer -uri ethash://0xb76d43eAaB2e905028a7f0F3aF13C7A84c477B9f.worker@eth-us-west1.nanopool.org:9999 -uri2 vbk://VAR5uzCpFNfmTDZQQmfHUgbpY7NS93.worker:pwd@vbk.f2pool.com:3500 -dual-intensity 10 -dual-subsolver 3
-dual-intensity is for adjust the performance manually, so you can adjust the intensity by adding it at the end.
-dual-intensity 0 means mining eth only.
-dual-intensity 3~10 is recommended.
【TCP 50% Dual mining performance】
2080TI
Ethereum(MH/s ) 50.194
VBK (MH/s ) 501.928
2070
Ethereum(MH/s ) 35.39
VBK (MH/s ) 354.02
1080TI
Ethereum(MH/s ) 43
VBK (MH/s ) 430
1070
Ethereum(MH/s ) 25.5
VBK (MH/s ) 255.43
P106
Ethereum(MH/s ) 17.4
VBK (MH/s ) 171.4
15.5.3 is still .4GH/s per card slower than 15.4.0 when using GTX 1070s.
Just getting back into mining, using c31 algo with my 2080ti. Had some issues initially on Windows 10 as the miner couldn’t find nvml.dll but managed to get that sorted. Now it only says that there is ~9105mb of RAM available and selects the 8gb solver.
Just wanted to ask if that’s normal or not? If it’s not what can I do?
edit: nvm pretty sure it’s just windows 10 being garbage gonna try linux tomorrow
hey, I am getting this error when trying to mine on Windows 10 with an ASUS Arez Strix Vega 56 8GB
OpenCL Error '-11' in func 'bminer::cuckoo::CuckooStyleSolverCLBase::InitializeCLEnvironment' line 78
I am on bminer 15.5.3 latest version, that otherwise works flawlessly on another rig with only GTX 1070.
I have seen other users reporting it here in this thread and on Reddit as well, but I found no solution.
Can you please help me solve this realbminer?
Thanks for the great work.
We are working on the fix.
What’s the cuda version please?
Bminer will support Grin hard-fork. Please stay tuned.
I am not using a NVIDIA card, as you can see I am using a Vega 56 8GB
I uninstalled all previous drivers, including CUDA.
Hi,
I get a CUDA 500 error with the latest Bminer 15.7. I also installed the latest nVidia drivers and still the same. 
We’re pleased to release Bminer 15.7.0.
The release provides:
*Support the cuckaroo29d algorithm.
Please see https://www.bminer.me/releases/ for more details.
Happy mining.
1 Like
Hey,
I’m getting a CUDA 500 error on the latest Bminer 15.7
Updated to the latest Geforce drivers, restarted machines and its still happening.
Happening on different GPUs.
RTX 2080s,
RTX 2070s,
GTX 1080 ti’s
Please help.
Same! The miner does not work.
We are working on the fix! thanks for your feedback.
Hi，andro，it would be great if you can give me more description about what error pop up and your rig’s information including the operating system, driver version and your command lines.
thank you very much!
Hi realbminer,
I am using windows 10 with the very latest Nvidia drivers, older drivers also didn’t work.
I have two rigs GTX 1080 and GTX 1080ti
This is the error I am getting…
https://gyazo.com/908f0539b3665166dfcc3505a48ce3a0
We’re pleased to release Bminer 15.7.1.
The release provides:
- Improve the performance of the Cuckaroo29d algorithm.
- Fix the issue that the Cuckaroo29d failed to start for Turing-based cards.
Please see https://www.bminer.me/releases/ for more details.
Happy mining.
Please try Bminer 15.7.1 and check if your problem has been fixed.