![]() ![]()
To start it in mining mode, you use the -mine command-line flag. As gpu2 and gpu3 are not even heating up at 100% utilization, and the hashrate the pool shows reflects that, but the miner for some strange reason shows each card is hashing at 233-235 h/s. When you start up your ethereum node with geth it is not mining by default. via Windows key r, and entering regedit) Create a new DWORD with the Name being the path from step 2 with amdocl64. it seems as if either these cards are defective or something is really flawed with them. Open regedit, aka the Registry Editor, (e.g. Which seems to = perfectly to the temperature of the cards. The mining pools accepted shares/hashrate is Im mining bytecoin and litecoin with ccminer, but only getting around 2. Finally up and running with cuda 8.0 and 375.66 drivers. Thread stuck in device driver ethereum drivers#| 72% 64C P0 39W / 53W | 1005MiB / 4042MiB | 100% Default | New to mining and quite frankly it was a big headache installing the Nvidia drivers on my machine, got the dreaded login loop and a million other issues. | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. ![]() | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. But, here are ways that can probably fix this error. %NVIDIA_DEV.13BD.110A.10DE% = Section112, PCI\VEN_10DE
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |