Author

Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 220. (Read 6590565 times)

member
Activity: 135
Merit: 10
Please, no one of you is mining ethereum with nvidia through Ethermine in win 10?.
I need someone to help me, none of the versions of Claymore work.
I have 1 nvidia running on a rig with AMDs
Claymore 11.7 / Ethermine / Win 10
I have not tried yet with this version, I'll make an attempt. I find it strange that I have done everything and nothing.
Thanks bro.

I've tried again with v11.8 in my nvidia rig with win10 and
these are the data in the file log.txt:

Any help please

How much virtual memory do you have? What version of Win10 do you have?



Win 10 pro
version : 1709
OS Build: 16299.431
Virtual Memory: 16.000
Increase the paging file, it was the same, until you added
newbie
Activity: 63
Merit: 0
Ok, it is clear you are trying to help but please let this one go.

That source you posted is obviously outdated and clearly rookie targeted.

Mining is not the typical usage senario for desktop PC so please skip any article, guide whatever that is not specifically made for Cryptomining.

Anything below 20GB virtual memory will propably crash the miner. Even the OP states that VM should be 16GB or more.

I recommend he sets it to 25GB and try again.


Actually, when I decreased my RAM from 8 GB to 3 GB, I was facing some sort of application crash during mining (somewhat similar to @damba_'s), but decreasing the virtual RAM to 15000 MB worked out for me that time (it was way over this number before I decreased it). It's still running good at 15000 MB (just re-checked this number) with 3 GB RAM.

From what I can conclude, if you've over 4 GB RAM, you can set insanely huge values of virtual RAM like 40 GB or 50 GB (probably as big as your available secondary memory size), but if you've around 2-3 GB RAM, you've to set it lower and can't be that crazy.

Well that does not mean that it's because you decreased the pagefile that it ran better, rather decreasing the pagefile deletes it and recreates it. I am certain that if you went right back after to 15gb it would still work, proving my point. The amount of virtual memory has nothing to do with system stability, especially for mining where with ETH you need about 2.5gb of memory for each card.
Now on a 10 cards rig that's close to 25gb and you want to set a bit more for increase over time. I run mine with 60gb pagefile and don't have stability issues.

What you mention is what I believe you had instability issues in that pagefile and recreating it fixed your problem, the issue was not fixed by lowering it. See the difference?
jr. member
Activity: 117
Merit: 3
Anyone found a consistent fix for the Cuda Error 11?

I have 4 Nvidia rigs, 2x 1050 TI rigs and 2x 1070 TI rigs ( all 12 cards each ) and they are identical to eachother, but 1 rig just does not want to mine Eth ( one of the 1070TI's), always gives this error.

All identical Windows 10, 32GB page file, Driver 388.71 from December 20th with afterburner 4.5.0. 1070TI's both run identical OC settings.

I'm tearing my hairs out because of this one, i am an IT guy and really can't handle not being able to fix this Smiley

Are the motherboards all the exact same? Same bios versions? Also take a look at one that could be messing up. Check if using Risers you have the GPUs all firmly seated. I had an issue where once one GPU started acting weird and sure enough it was slightly tilted in riser.

GLTU
jr. member
Activity: 63
Merit: 1
Anyone found a consistent fix for the Cuda Error 11?

I have 4 Nvidia rigs, 2x 1050 TI rigs and 2x 1070 TI rigs ( all 12 cards each ) and they are identical to eachother, but 1 rig just does not want to mine Eth ( one of the 1070TI's), always gives this error.

All identical Windows 10, 32GB page file, Driver 388.71 from December 20th with afterburner 4.5.0. 1070TI's both run identical OC settings.

I'm tearing my hairs out because of this one, i am an IT guy and really can't handle not being able to fix this Smiley
jr. member
Activity: 150
Merit: 3
Since I updated to windows 1803, when my rigs restart, it needs to be connected to a monitor otherwise claymore don't start. Anyone have the same issue ? As soon as a monitor is plugged, rigs restart. Here is what I got in log.


20:19:42:833   1c28   Main Ethereum pool is us1.ethermine.org:5555
20:19:42:848   1c28   DCR: 0 pool is specified
20:19:43:527   1c28   OpenCL platform: Intel(R) OpenCL
20:19:43:527   1c28   OpenCL platform: AMD Accelerated Parallel Processing
20:19:43:543   1c28   OpenCL initializing...

20:19:43:543   1c28   AMD Cards available: 1
20:19:43:543   1c28   GPU #0: Ellesmere (Radeon RX 570 Series), 8192 MB available, 32 compute units (pci bus 1:0:0)
20:19:43:558   1c28   GPU #0 recognized as Radeon RX 470/570
20:19:43:558   1c28   POOL/SOLO version
20:19:43:558   1c28   Platform: Windows
20:19:43:839   1c28   start building OpenCL program for GPU 0...
20:20:15:721   1c50   
20:20:48:540   1c50   
20:21:21:387   1c50   
20:21:54:236   1c50   
20:22:27:096   1c50   
20:22:59:951   1c50   
20:23:32:806   1c50   
20:24:05:654   1c50   
20:24:38:511   1c50   
20:25:11:175   1c50   
20:25:11:175   1c50   Miner cannot initialize for 5 minutes, need to restart miner!
20:25:11:175   1c50   Rebooting
20:25:11:378   9fc   GPU 0 temp = 33, old fan speed = 0, new fan speed = 56




Before windows 1803, all the miners restarted like a charm...

Thank you

I had similar issue after windows updated to 1709.
Before I could run miner without monitor connected to GPU, after that update one gpu was giving 0 mh/s so I bought HDMI dummy plug and after I plugged it in, miner works fine.
newbie
Activity: 55
Merit: 0
My windows defender found a Trojan:Win32/Coinminer!bit  and Virtool:INF/Autorun.gen!AD in this 11.8 version of claymore all of them declared Severe, is any other link for clean file? I downloaded it from Mega, the link from the main page of this thread.


- Windows 10 Defender recognizes miner as a virus, some antiviruses do the same. Miner is not a virus, add it to Defender exceptions.
  I write miners since 2014. Most of them are recognized as viruses by some paranoid antiviruses, perhaps because I pack my miners to protect them from disassembling, perhaps because some people include them into their botnets, or perhaps these antiviruses are not good, I don't know. For these years, a lot of people used my miners and nobody confirmed that my miner stole anything or did something bad.
  Note that I can guarantee clean binaries only for official links in my posts on this forum (bitcointalk). If you downloaded miner from some other link - it really can be a virus.
  However, my miners are closed-source so I cannot prove that they are not viruses. If you think that I write viruses instead of good miners - do not use this miner, or at least use it on systems without any valuable data.


hero member
Activity: 2086
Merit: 562
My windows defender found a Trojan:Win32/Coinminer!bit  and Virtool:INF/Autorun.gen!AD in this 11.8 version of claymore all of them declared Severe, is any other link for clean file? I downloaded it from Mega, the link from the main page of this thread.
newbie
Activity: 8
Merit: 1
Since I updated to windows 1803, when my rigs restart, it needs to be connected to a monitor otherwise claymore don't start. Anyone have the same issue ? As soon as a monitor is plugged, rigs restart. Here is what I got in log.


20:19:42:833   1c28   Main Ethereum pool is us1.ethermine.org:5555
20:19:42:848   1c28   DCR: 0 pool is specified
20:19:43:527   1c28   OpenCL platform: Intel(R) OpenCL
20:19:43:527   1c28   OpenCL platform: AMD Accelerated Parallel Processing
20:19:43:543   1c28   OpenCL initializing...

20:19:43:543   1c28   AMD Cards available: 1
20:19:43:543   1c28   GPU #0: Ellesmere (Radeon RX 570 Series), 8192 MB available, 32 compute units (pci bus 1:0:0)
20:19:43:558   1c28   GPU #0 recognized as Radeon RX 470/570
20:19:43:558   1c28   POOL/SOLO version
20:19:43:558   1c28   Platform: Windows
20:19:43:839   1c28   start building OpenCL program for GPU 0...
20:20:15:721   1c50   
20:20:48:540   1c50   
20:21:21:387   1c50   
20:21:54:236   1c50   
20:22:27:096   1c50   
20:22:59:951   1c50   
20:23:32:806   1c50   
20:24:05:654   1c50   
20:24:38:511   1c50   
20:25:11:175   1c50   
20:25:11:175   1c50   Miner cannot initialize for 5 minutes, need to restart miner!
20:25:11:175   1c50   Rebooting
20:25:11:378   9fc   GPU 0 temp = 33, old fan speed = 0, new fan speed = 56




Before windows 1803, all the miners restarted like a charm...

Thank you
newbie
Activity: 85
Merit: 0
Please, no one of you is mining ethereum with nvidia through Ethermine in win 10?.
I need someone to help me, none of the versions of Claymore work.
I have 1 nvidia running on a rig with AMDs
Claymore 11.7 / Ethermine / Win 10
I have not tried yet with this version, I'll make an attempt. I find it strange that I have done everything and nothing.
Thanks bro.

I've tried again with v11.8 in my nvidia rig with win10 and
these are the data in the file log.txt:

Any help please

How much virtual memory do you have? What version of Win10 do you have?



Win 10 pro
version : 1709
OS Build: 16299.431
Virtual Memory: 16.000
newbie
Activity: 55
Merit: 0
Please, no one of you is mining ethereum with nvidia through Ethermine in win 10?.
I need someone to help me, none of the versions of Claymore work.
I have 1 nvidia running on a rig with AMDs
Claymore 11.7 / Ethermine / Win 10
I have not tried yet with this version, I'll make an attempt. I find it strange that I have done everything and nothing.
Thanks bro.

I've tried again with v11.8 in my nvidia rig with win10 and
these are the data in the file log.txt:

Any help please

How much virtual memory do you have? What version of Win10 do you have?
newbie
Activity: 85
Merit: 0
Please, no one of you is mining ethereum with nvidia through Ethermine in win 10?.
I need someone to help me, none of the versions of Claymore work.
I have 1 nvidia running on a rig with AMDs
Claymore 11.7 / Ethermine / Win 10
I have not tried yet with this version, I'll make an attempt. I find it strange that I have done everything and nothing.
Thanks bro.

I've tried again with v11.8 in my nvidia rig with win10 and
these are the data in the file log.txt:



19:13:11:617   1548   Check and remove old log files...
19:13:11:618   1548   args: -epool us1-etc.ethermine.org:4444 -ewal 0xfF4a2178527481420310Cd069335b472E3FE1156.MN1 -epsw x -mode 1 -platform 2 -ftime 10
19:13:11:620   1548   
19:13:11:622   1548   ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
19:13:11:623   1548   º                Claymore's Dual GPU Miner - v11.8               º
19:13:11:624   1548   º              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             º
19:13:11:625   1548   ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
19:13:11:627   1548   
19:13:11:628   1548   b591
19:13:11:889   1548   ETH: 1 pool is specified
19:13:11:890   1548   Main Ethereum pool is us1-etc.ethermine.org:4444
19:13:12:989   1548   CUDA initializing...

19:13:12:990   1548   NVIDIA Cards available: 10
19:13:12:992   1548   CUDA Driver Version/Runtime Version: 9.1/8.0
19:13:13:311   1548   GPU #0: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1  (pci bus 1:0:0)
19:13:13:320   1548   GPU #1: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1  (pci bus 3:0:0)
19:13:13:330   1548   GPU #2: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1  (pci bus 4:0:0)
19:13:13:340   1548   GPU #3: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1  (pci bus 5:0:0)
19:13:13:352   1548   GPU #4: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1  (pci bus 9:0:0)
19:13:13:367   1548   GPU #5: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1  (pci bus 10:0:0)
19:13:13:382   1548   GPU #6: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1  (pci bus 12:0:0)
19:13:13:393   1548   GPU #7: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1  (pci bus 13:0:0)
19:13:13:406   1548   GPU #8: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1  (pci bus 14:0:0)
19:13:13:420   1548   GPU #9: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1  (pci bus 15:0:0)
19:13:13:421   1548   Total cards: 10
19:13:17:027   1548   
You can use "+" and "-" keys to achieve best ETH speed, see "FINE TUNING" section in Readme for details.

19:13:18:034   1548   NVML version: 9.390.77
19:13:18:042   1548   NVML API: failed to get device handle 1, error 999.
19:13:18:100   1548   NVML API: failed to get device handle 1, error 999.
19:13:18:103   1548   NVML API: failed to get device handle 1, error 999.
19:13:18:105   1548   NVML API: failed to get device handle 1, error 999.
19:13:18:107   1548   NVML API: failed to get device handle 1, error 999.
19:13:18:109   1548   NVML API: failed to get device handle 1, error 999.
19:13:18:112   1548   NVML API: failed to get device handle 1, error 999.
19:13:18:114   1548   NVML API: failed to get device handle 1, error 999.
19:13:18:117   1548   NVML API: failed to get device handle 1, error 999.
19:13:18:119   1548   NVML API: failed to get device handle 1, error 999.
19:13:20:730   1548   SSL: Imported 41 certificates from local storage
19:13:20:740   374   ETH: Stratum - connecting to 'us1-etc.ethermine.org' <54.177.207.188> port 4444 (unsecure)
19:13:20:832   1548   ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)

19:13:20:833   1548   ETH: eth-proxy stratum mode
19:13:20:835   1548   Watchdog enabled
19:13:20:837   1548   Remote management (READ-ONLY MODE) is enabled on port 3333
19:13:20:838   1548   

19:13:20:868   374   sent: {"worker": "eth1.0", "jsonrpc": "2.0", "params": ["0xfF4a2178527481420310Cd069335b472E3FE1156.MN1", "x"], "id": 2, "method": "eth_submitLogin"}

19:13:20:870   374   ETH: Stratum - Connected (us1-etc.ethermine.org:4444) (unsecure)
19:13:20:997   374   buf: {"id":2,"jsonrpc":"2.0","result":true}

19:13:20:998   374   ETH: Authorized
19:13:20:999   374   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

19:13:21:116   374   buf: {"id":3,"jsonrpc":"2.0","result":["0x7f2def7afd3145f63f0be5165d6e79eae7cbf3f5794757a1f3f85b57ec69ee76","0x8308d376eeb469b7ff84bd59c51988d9618b208dc3b951d1dc1918fa08306723","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5be6c5"]}

19:13:21:129   2188   Setting DAG epoch #200...
19:13:23:800   116c   Setting DAG epoch #200 for GPU0
19:13:23:801   165c   Setting DAG epoch #200 for GPU3
19:13:23:804   96c   Setting DAG epoch #200 for GPU5
19:13:23:800   2c0   Setting DAG epoch #200 for GPU1
19:13:23:807   116c   Create GPU buffer for GPU0
19:13:23:802   1710   Setting DAG epoch #200 for GPU9
19:13:23:804   1540   Setting DAG epoch #200 for GPU7
19:13:23:799   2188   Setting DAG epoch #200 for GPU4
19:13:23:804   2308   Setting DAG epoch #200 for GPU8
19:13:23:806   1610   Setting DAG epoch #200 for GPU2
19:13:23:810   165c   Create GPU buffer for GPU3
19:13:23:827   1710   Create GPU buffer for GPU9
19:13:23:829   2188   Create GPU buffer for GPU4
19:13:23:816   96c   Create GPU buffer for GPU5
19:13:23:821   2c0   Create GPU buffer for GPU1
19:13:23:825   1a28   Setting DAG epoch #200 for GPU6
19:13:23:834   1610   Create GPU buffer for GPU2
19:13:23:844   1a28   Create GPU buffer for GPU6
19:13:23:846   2308   Create GPU buffer for GPU8
19:13:23:847   1540   Create GPU buffer for GPU7
19:13:24:506   2188   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

19:13:24:528   2c0   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

19:13:24:563   2308   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

19:13:24:681   1610   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

19:13:27:509   2188   Set global fail flag, failed GPU4
19:13:27:510   1080   Setting DAG epoch #200 for GPU4
19:13:27:511   2188   GPU 4 failed
19:13:27:513   1080   GPU 4, CUDA error 11 - cannot write buffer for DAG

19:13:27:531   2c0   Set global fail flag, failed GPU1
19:13:27:533   2c0   GPU 1 failed
19:13:27:534   2080   Setting DAG epoch #200 for GPU1
19:13:27:535   2080   GPU 1, CUDA error 11 - cannot write buffer for DAG

19:13:27:568   2308   Set global fail flag, failed GPU8
19:13:27:571   2308   GPU 8 failed
19:13:27:572   118c   Setting DAG epoch #200 for GPU8
19:13:27:574   118c   GPU 8, CUDA error 11 - cannot write buffer for DAG

19:13:27:684   1610   Set global fail flag, failed GPU2
19:13:27:685   fb0   Setting DAG epoch #200 for GPU2
19:13:27:687   1610   GPU 2 failed
19:13:27:688   fb0   GPU 2, CUDA error 11 - cannot write buffer for DAG

19:13:30:515   1080   Set global fail flag, failed GPU4
19:13:30:516   1080   GPU 4 failed
19:13:30:537   2080   Set global fail flag, failed GPU1
19:13:30:538   2080   GPU 1 failed
19:13:30:576   118c   Set global fail flag, failed GPU8
19:13:30:577   118c   GPU 8 failed
19:13:30:691   fb0   Set global fail flag, failed GPU2
19:13:30:692   fb0   GPU 2 failed
19:13:31:131   374   ETH: checking pool connection...
19:13:31:132   374   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

19:13:31:249   374   buf: {"id":3,"jsonrpc":"2.0","result":["0x7f2def7afd3145f63f0be5165d6e79eae7cbf3f5794757a1f3f85b57ec69ee76","0x8308d376eeb469b7ff84bd59c51988d9618b208dc3b951d1dc1918fa08306723","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5be6c5"]}

19:13:31:841   116c   GPU0 DAG creation time - 7842 ms
19:13:31:842   116c   Setting DAG epoch #200 for GPU0 done
19:13:32:183   1a28   GPU6 DAG creation time - 7860 ms
19:13:32:184   1a28   Setting DAG epoch #200 for GPU6 done
19:13:32:187   96c   GPU5 DAG creation time - 7837 ms
19:13:32:188   96c   Setting DAG epoch #200 for GPU5 done
19:13:32:238   165c   GPU3 DAG creation time - 7854 ms
19:13:32:240   165c   Setting DAG epoch #200 for GPU3 done
19:13:32:368   1710   GPU9 DAG creation time - 7898 ms
19:13:32:370   1710   Setting DAG epoch #200 for GPU9 done
19:13:32:468   1540   GPU7 DAG creation time - 7854 ms
19:13:32:470   1540   Setting DAG epoch #200 for GPU7 done
19:13:41:131   374   sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x98b37c8", "0x00000000000000000000000000000000000000000000000000000000fca64bb9"]}

19:13:41:146   374   ETH: checking pool connection...
19:13:41:147   374   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

19:13:41:250   374   buf: {"id":6,"jsonrpc":"2.0","result":true}

19:13:41:364   374   buf: {"id":3,"jsonrpc":"2.0","result":["0x7f2def7afd3145f63f0be5165d6e79eae7cbf3f5794757a1f3f85b57ec69ee76","0x8308d376eeb469b7ff84bd59c51988d9618b208dc3b951d1dc1918fa08306723","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5be6c5"]}

19:13:41:940   7a0   GPU0 t=53C fan=75%, GPU1 t=46C fan=75%, GPU2 t=47C fan=75%, GPU3 t=62C fan=75%, GPU4 t=46C fan=75%, GPU5 t=58C fan=75%, GPU6 t=55C fan=75%, GPU7 t=56C fan=75%, GPU8 t=47C fan=75%, GPU9 t=55C fan=75%
19:13:42:032   1f44   em hbt: 0, fm hbt: 94,
19:13:42:033   1f44   watchdog - thread 0 (gpu0), hb time 172
19:13:42:033   1f44   watchdog - thread 1 (gpu0), hb time 16
19:13:42:034   1f44   watchdog - thread 2 (gpu1), hb time 9563
19:13:42:035   1f44   watchdog - thread 3 (gpu1), hb time 9563
19:13:42:036   1f44   watchdog - thread 4 (gpu2), hb time 9578
19:13:42:037   1f44   watchdog - thread 5 (gpu2), hb time 9578
19:13:42:038   1f44   watchdog - thread 6 (gpu3), hb time 78
19:13:42:039   1f44   watchdog - thread 7 (gpu3), hb time 218
19:13:42:040   1f44   watchdog - thread 8 (gpu4), hb time 9578
19:13:42:041   1f44   watchdog - thread 9 (gpu4), hb time 9578
19:13:42:042   1f44   watchdog - thread 10 (gpu5), hb time 265
19:13:42:043   1f44   watchdog - thread 11 (gpu5), hb time 125
19:13:42:043   1f44   watchdog - thread 12 (gpu6), hb time 265
19:13:42:044   1f44   watchdog - thread 13 (gpu6), hb time 125
19:13:42:045   1f44   watchdog - thread 14 (gpu7), hb time 140
19:13:42:046   1f44   watchdog - thread 15 (gpu7), hb time 281
19:13:42:047   1f44   watchdog - thread 16 (gpu8), hb time 9578
19:13:42:048   1f44   watchdog - thread 17 (gpu8), hb time 9578
19:13:42:049   1f44   watchdog - thread 18 (gpu9), hb time 234
19:13:42:050   1f44   watchdog - thread 19 (gpu9), hb time 93
19:13:42:051   1f44   WATCHDOG: GPU error, you need to restart miner Sad
19:13:42:167   408   Quit, please wait...
19:13:43:609   1f44   Restarting OK, exit...


This is my bat file:

EthDcrMiner64.exe -epool us1-etc.ethermine.org:4444 -ewal 0xfF4a2178527481420310Cd069335b472E3FE1156.MN1 -epsw x -mode 1 -platform 2 -ftime 10

Any help please
newbie
Activity: 85
Merit: 0
Please, no one of you is mining ethereum with nvidia through Ethermine in win 10?.
I need someone to help me, none of the versions of Claymore work.
I have 1 nvidia running on a rig with AMDs
Claymore 11.7 / Ethermine / Win 10
I have not tried yet with this version, I'll make an attempt. I find it strange that I have done everything and nothing.
Thanks bro.
newbie
Activity: 15
Merit: 0
Please, no one of you is mining ethereum with nvidia through Ethermine in win 10?.
I need someone to help me, none of the versions of Claymore work.
I have 1 nvidia running on a rig with AMDs
Claymore 11.7 / Ethermine / Win 10
newbie
Activity: 85
Merit: 0
Please, no one of you is mining ethereum with nvidia through Ethermine in win 10?.
I need someone to help me, none of the versions of Claymore work.
full member
Activity: 202
Merit: 100
Hi guys,
Can i mine solo ETC with this miner right?
If yes, what OC you recommend for RX580 8G cards? Please help.
jr. member
Activity: 150
Merit: 3
Can this miner run on 2GB of system memory?
I had 3 gb ddr2, but one ram stick stopped working so I'm left with only 2 gb of system memory.
I tried to start miner and I get message: ethdcrminer64.exe has stopped working
I didn't have any problems so far with 3 gb of RAM.

I am running CDE v.11.8 with 2Gb Ram since the version is available, no problems. Just use Linux :-) and forget all this windows crap about pagefile, disabling updates and new drivers with performance issues. No-brainer for Linux noob - HiveOS with Web managment console and free for home mining up to 3 rigs.

I was thinking of using HiveOS but since I got replacement RAM very fast, I didn't.
But I am planning to switch to HiveOS, Win10 is starting to get on my nerves.
member
Activity: 239
Merit: 10
Can this miner run on 2GB of system memory?
I had 3 gb ddr2, but one ram stick stopped working so I'm left with only 2 gb of system memory.
I tried to start miner and I get message: ethdcrminer64.exe has stopped working
I didn't have any problems so far with 3 gb of RAM.

I am running CDE v.11.8 with 2Gb Ram since the version is available, no problems. Just use Linux :-) and forget all this windows crap about pagefile, disabling updates and new drivers with performance issues. No-brainer for Linux noob - HiveOS with Web managment console and free for home mining up to 3 rigs.
legendary
Activity: 1030
Merit: 1006
Please suggest correction of my RIG    Claymore miner error " Not initializing "   Keeps trying for 5 minutes.  Disconnects.  and tries again.  etc.

My RIg.   Windows 10 fresh install fully updated.  16gb Ram.  Asus B250 Mining expert MOBO, Intel I3, 120GB Sd card.  4- RX-570 - 8gb AND 4- RX 580 - 8gb.

Did a AMD delete of all drivers and a fresh install. 

On Boot up cards are recognized, AMD latest drivers are installed, all cards are set to compute.  AMD and system shows no errors.

The system was working fine.  I was getting 220 MHz on average. Can not exactly pinpoint when it stopped. 

Been reading the forums and can not see anyone with the same issue.  I do not get any error codes other than " Miner fails initialing Restart miner "

Any help would be appreciated.

Thanks

Chip
1803. rollback.  Lot of posts here you can find.
newbie
Activity: 1
Merit: 0
Please suggest correction of my RIG    Claymore miner error " Not initializing "   Keeps trying for 5 minutes.  Disconnects.  and tries again.  etc.

My RIg.   Windows 10 fresh install fully updated.  16gb Ram.  Asus B250 Mining expert MOBO, Intel I3, 120GB Sd card.  4- RX-570 - 8gb AND 4- RX 580 - 8gb.

Did a AMD delete of all drivers and a fresh install. 

On Boot up cards are recognized, AMD latest drivers are installed, all cards are set to compute.  AMD and system shows no errors.

The system was working fine.  I was getting 220 MHz on average. Can not exactly pinpoint when it stopped. 

Been reading the forums and can not see anyone with the same issue.  I do not get any error codes other than " Miner fails initialing Restart miner "

Any help would be appreciated.

Thanks

Chip
jr. member
Activity: 150
Merit: 3
Ok, it is clear you are trying to help but please let this one go.

That source you posted is obviously outdated and clearly rookie targeted.

Mining is not the typical usage senario for desktop PC so please skip any article, guide whatever that is not specifically made for Cryptomining.

Anything below 20GB virtual memory will propably crash the miner. Even the OP states that VM should be 16GB or more.

I recommend he sets it to 25GB and try again.


Actually, when I decreased my RAM from 8 GB to 3 GB, I was facing some sort of application crash during mining (somewhat similar to @damba_'s), but decreasing the virtual RAM to 15000 MB worked out for me that time (it was way over this number before I decreased it). It's still running good at 15000 MB (just re-checked this number) with 3 GB RAM.

From what I can conclude, if you've over 4 GB RAM, you can set insanely huge values of virtual RAM like 40 GB or 50 GB (probably as big as your available secondary memory size), but if you've around 2-3 GB RAM, you've to set it lower and can't be that crazy.

I tried lowering and increasing Virtual memory but it didn't help.
I borrowed 1GB of RAM from a friend and now the miner runs ok.
Total memory consumption in Win 10 while mining is ~1,8GB so that's the reason why 2GB of RAM is not enough.
Jump to: