 Show Posts
|
|
Pages: « 1 2 [3] 4 5 6 »
|
I know we can no longer mine Ethereum with 2gb cards
If you updated your windows 10 version then you can't with 3gb too cause the new updated windows 10 version takes 666mb and the dag file is right now at 2.33gb + 666mb = 3gb, nobody can mine eth with 3gb on windows 10 anymore. i am mining with 3gb card  Do not update, if you do then gameover. I know we can no longer mine Ethereum with 2gb cards
If you updated your windows 10 version then you can't with 3gb too cause the new updated windows 10 version takes 666mb and the dag file is right now at 2.33gb + 666mb = 3gb, nobody can mine eth with 3gb on windows 10 anymore. Is this a recent update? Yes. Has anyone tried moving the 3gb 1060 to any other than the primary GPU (pci 0:0:0)? It seems like Windows would only mess up the primary card. My 3gb 1060 is off for repairs / replacement, so unable to try myself. |
|
|
|
-wd 1 -r 1 -epool stratum+tcp://eth-eu.dwarfpool.com:8008 -ewal MYWALLETADDRESS/Rig2 -esm 0 -epsw x -allpools 1 -mport 127.0.0.1:3333 -asm 1 -epool stratum+tcp://exp-us.dwarfpool.com:8018 -ewal MYWALLETADDRESS/Rig2 -epsw x -allpools 1
replace the -epool with -dpool command before the second coin to mine configuration, see below EthDcrMiner64.exe -epool stratum+tcp://eth-eu.dwarfpool.com:8008 -ewal MYWALLETADDRESS/Rig2 -esm 0 -epsw x -dpool stratum+tcp://exp-us.dwarfpool.com:8018 -ewal MYWALLETADDRESS/Rig2 -epsw x -allpools 1 -wd 1 -r 1 I didn't even notice: that, the second "-ewal" and second "-epsw" all should be "-dxxx" instead. Still getting the same error. You don't have a "-dcoin" and DCR is the default: is that what you intended? |
|
|
|
Been trying everything the last few days. I can't stop my 2gb video card from trying to mine Ethereum and causing the DAG error. These are just a couple bat file I have tried, set GPU_FORCE_64BIT_PTR 0
set GPU_MAX_HEAP_SIZE 100
set GPU_USE_SYNC_OBJECTS 1
set GPU_MAX_ALLOC_PERCENT 100
set GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe -epool us1.ethermine.org:4444 -ewal **** -epsw **** >>> -mode 1-123 <<< -tt 68 -allpools 1 -dpool stratum+tcp://dcr-us.coinmine.pl:2222 -dwal ***** -dpsw **** -mode 0 -dcri 15 -dcoin dcr
pause
set GPU_FORCE_64BIT_PTR 0
set GPU_MAX_HEAP_SIZE 100
set GPU_USE_SYNC_OBJECTS 1
set GPU_MAX_ALLOC_PERCENT 100
set GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe -epool us1.ethermine.org:4444 -ewal **** -epsw **** -di 123 -tt 68 -allpools 1 -dpool stratum+tcp://dcr-us.coinmine.pl:2222 -dwal ***** -dpsw **** -di 0123 -dcri 15 -dcoin dcr
pause
Assuming it is a cut and paste - maybe the "-mode 1-123" is confusing it? You don't want "mode 1" anyway, you have "-mode 0" later on the command-line. |
|
|
|
hello, any chance of support for overclocking with nvidia cards? the 1060's in particular can mine at 23 mhs with 70% or even less power limit, afterburner only support 8 gpus max, kinda of a bummer with 13+ pcie slots motherboards.
Find the nVidiaInspector by "Orbmu2k" (not "nVidia Profile Inspector" - by the same guy) and use it. Works really well, and supports everything you need and then some. I renamed a copy "NVI.EXE" for my use and call it from my miner batch file. Don't forget to set the "Administrator" rights flag so you don't get the ACP prompt. |
|
|
|
-wd 1 -r 1 -epool stratum+tcp://eth-eu.dwarfpool.com:8008 -ewal MYWALLETADDRESS/Rig2 -esm 0 -epsw x -allpools 1 -mport 127.0.0.1:3333 -asm 1 -epool stratum+tcp://exp-us.dwarfpool.com:8018 -ewal MYWALLETADDRESS/Rig2 -epsw x -allpools 1
replace the -epool with -dpool command before the second coin to mine configuration, see below EthDcrMiner64.exe -epool stratum+tcp://eth-eu.dwarfpool.com:8008 -ewal MYWALLETADDRESS/Rig2 -esm 0 -epsw x -dpool stratum+tcp://exp-us.dwarfpool.com:8018 -ewal MYWALLETADDRESS/Rig2 -epsw x -allpools 1 -wd 1 -r 1 I didn't even notice: that, the second "-ewal" and second "-epsw" all should be "-dxxx" instead. |
|
|
|
-wd 1 -r 1 -epool stratum+tcp://eth-eu.dwarfpool.com:8008 -ewal MYWALLETADDRESS/Rig2 -esm 0 -epsw x -allpools 1 -mport 127.0.0.1:3333 -asm 1 -epool stratum+tcp://exp-us.dwarfpool.com:8018 -ewal MYWALLETADDRESS/Rig2 -epsw x -allpools 1
You are replacing the slash between WALLET and WORKER with a dot (period / decimal point)? It should not be a slash, pretty certain. |
|
|
|
NO IT IS NOT TRUE! You CAN run mix of AMD and NVIDIA cards within one miner.
Thanks for clarifying, as I was mining with 6x amd and 6 x nvidia cards with the one miner. Just need to figure out what the problem is with my claymore!!! and why its crashing my pc and not detecting my CUDA devices and only mining with 3 amd devices disabled. Back to basics: I hate to make any assumptions, but you say it was working? I was thinking maybe you don't have the Cuda software installed? ("nSight") |
|
|
|
Someone recently asked about a program to find "Shares" in the output log. I don't know of any simple answer, but depending on the detail you need, something like findstr /n nonce 1519244225_log.txt will find the shares in the logfile, only because the word "nonce" only appears when a share is uploaded. I didn't even try to generalize for anything beyond ETH shares, but something relatively simple should work out if you look to figure out what is unique about those particular lines in the logfile. I do know that it works for "B2S" (blake2s) as well, but I don't have logfiles to test for other coins. The word "nonce" appears in the header for some pools because it's also a parameter (i.e. "extranonce") but beyond that it's accurate for both coins I have mined recently. If you add redirection like: findstr /n nonce 1519244225_log.txt > nonce_count.log it will write them to a file named "nonce_count.log" instead of simply displaying them onscreen. You can manipulate them easily, and the "/n" param adds the line numbers in front of the extract like this: 365:15:19:44:510 3d1c ETH: put share nonce a8b3147c03a7e455
412:15:20:05:510 15ec ETH: put share nonce 486eac900c27e164
607:15:21:16:593 15ec ETH: put share nonce d76c08f80207fa48
1211:15:25:12:302 3d1c ETH: put share nonce 413392400d2dd6dc
2421:15:33:27:153 15ec ETH: put share nonce 5e58f04005f173ea
2781:15:35:36:813 3d1c ETH: put share nonce dd179ba809d65310
2869:15:36:28:895 15ec ETH: put share nonce 6ca93f181375d86b
3689:15:42:44:060 3d1c ETH: put share nonce 330430240c9085e4
3839:15:44:01:403 3d1c ETH: put share nonce 3932b92c0b06a2ab
4679:15:50:12:059 15ec ETH: put share nonce 1aa0f12803cc0c42
4872:15:51:32:595 3d1c ETH: put share nonce 7f7178a414011feb
4985:15:52:15:581 3d1c ETH: put share nonce 6e76965400460ebd
5478:15:56:09:181 15ec ETH: put share nonce 2db26928019f2453
5919:15:59:10:735 15ec ETH: put share nonce 5a20bdd004576d96
5996:15:59:40:128 15ec ETH: put share nonce ed94e408057c2f4b
6673:16:04:41:959 3d1c ETH: put share nonce 8cb7d900403bf0d
6792:16:05:21:687 15ec ETH: put share nonce dd9cb6e803b53095
7212:16:08:37:562 15ec ETH: put share nonce 97d0a0d80c01366e
7896:16:13:41:546 15ec ETH: put share nonce e5cc78900adf3c0b
8403:16:17:17:089 3d1c ETH: put share nonce 4a8d61b806a5a4d0
9326:16:23:50:756 15ec ETH: put share nonce 2adb5eb0003a8460
9397:16:24:10:092 15ec ETH: put share nonce f0ee99f803932d40
9977:16:28:20:265 3d1c ETH: put share nonce d596c4300b47176b
10199:16:30:05:228 3d1c ETH: put share nonce a50e335814b7ef7f
10321:16:31:17:717 3d1c ETH: put share nonce 16ccd2e018389517
10449:16:32:15:480 3d1c ETH: put share nonce 565c6f5c00af4e82
11016:16:35:52:043 3d1c ETH: put share nonce d04698bc018776ea
11340:16:38:17:727 3d1c ETH: put share nonce a23866a805b76f3f
11661:16:40:07:617 3d1c ETH: put share nonce 5defeea40305f088
12250:16:44:45:733 15ec ETH: put share nonce 1a64e7300d376b88
12423:16:46:12:838 3d1c ETH: put share nonce cd1f839c0e1f5399
12880:16:49:40:091 3d1c ETH: put share nonce 51f18f5003850517
13359:16:52:52:962 15ec ETH: put share nonce 6aa96f48015cd05b
13560:16:54:03:206 15ec ETH: put share nonce 645c35d000c90048
Blake2s ("B2S") shares look like this: 32:07:58:26:137 934 send: {"id": 5, "method": "mining.extranonce.subscribe", "params": []}
174:07:59:27:067 3644 B2S: put share nonce 117f4069 enonce aa
227:07:59:51:581 3644 B2S: put share nonce 13d5015 enonce 12a
241:07:59:55:377 3644 B2S: put share nonce 72cd3bc enonce 13e
268:08:00:00:525 226c B2S: put share nonce af17c enonce d
505:08:01:29:753 3644 B2S: put share nonce b085330 enonce 3a
1455:08:08:20:412 226c B2S: put share nonce 8ba725a enonce 85
1919:08:11:04:943 226c B2S: put share nonce 9ea43da enonce 5
The first one is not a share, it's setting the parameter for nlpool.nl's extranonce values. |
|
|
|
Offtopic: did you know that stock Vega64 can do >2MH/s neoscrypt? "Hint, hint, hint?" Everybody go get your GoByte, FeatherCoin &c wallets ready for next week. ahahahahahah... Ppl should rly drop WTM and learn to make calculations themself It's a crutch. You KNOW people love crutches. |
|
|
|
"Change VM to > 32768"
My VM was already 16384MB Just to be sure I went ahead and changed it to 65536MB and its still crashing. So it seems like an issue with Claymore v11 on my computer. I can mine ETH on version 10 no problem, but when I try to use v11 it crash if it's dual mining and even if it's ETH only And you rebooted? Not the VM, then. Interesting. It is complaining about the memory. I don't see that message. |
|
|
|
I'm about to give up, I can't seems to setup dual mining for ETH + XVG (Blake2s). The miner keep restart saying "WATCHDOG: GPU error, you need to restart miner  " I googled it for hours and couldn't find anyone with the same issue as me. If someone here can help that would be amazing! I have only 1 card - RX 580 8GB, no OC and running AMD mining beta driver on Windows 10 Here is how my .bat file looks like: ... It's right up there at the top of the console window when you start the miner: "At least 16 GB of Virtual Memory is required for multi-GPU systems". Right, wrong or indifferent (the text displayed), you need more virtual memory. Use Control Panel to expand your VM to at least 32768MB - or more. |
|
|
|
Doktor83, since you obviously have a vested interest in oxo, do you really think we're all going to take what you post as gospel? That's a valid assumption - in the post you refer us to - but it hardly justifies things we have seen from other posters. You can cherry pick posts to "prove" just about anything you want - if you disregard everything else, of course. |
|
|
|
|
Thinking about the latest Windows 10 problem with the OS eating 666MB of the VRAM and specifically with the issue on GTX1060 3MB cards -vs- Ethereum DAG stored in RAM, has anyone tried moving the card to something other than the primary? (PCI 0,0,0)
It seems like Windoze would only chew up the VRAM on the first card found, not every GPU it sees. I don't have my 3GB 1060 online right now, so I can't test my theory. I know that it's not helpful if you have multiple 3GB 1060s and nothing with 4GB or more.
|
|
|
|
FAILOVER
Use "epools.txt" and "dpools.txt" files to specify additional pools. These files have text format, one pool per line. Every pool has 3 connection attempts.
Miner disconnects automatically if pool does not send new jobs for a long time or if pool rejects too many shares.
If the first character of a line is ";" or "#", this line will be ignored.
Do not change spacing, spaces between parameters and values are required for parsing.
If you need to specify "," character in parameter value, use two commas - ,, will be treated as one comma.
You can reload "epools.txt" and "dpools.txt" files in runtime by pressing "r" key.
Pool specified in the command line is "main" pool, miner will try to return to it every 30 minutes if it has to use some different pool from the list.
If no pool was specified in the command line then first pool in the failover pools list is main pool.
You can change 30 minutes time period to some different value with "-ftime" option, or use "-ftime 0" to disable switching to main pool.
You can also use environment variables in "epools.txt", "dpools.txt" and "config.txt" files. For example, define "WORKER" environment variable and use it as "%WORKER%" in config.txt or in epools.txt.
You can also select current pool in runtime by pressing "e" or "d" key. ...but it will try to return to the main pool after 30 minutes (or whatever you've configured it). When manually selecting the pool with "e" or "d", would it be possible to consider it is the main pool? MUCH easier for you to do the adjustments to "dpools.txt" or "epools.txt" and use the "r" key to reload both pool tables when it's running than it is to convolute the logic from Claymore's perspective. I used to code for a living, so I usually notice when "you can do that" without the coder having a headache. Now someone is bound to point out that what I said isn't 100% because it doesn't change the parameters passed on the command-line, but you can do that, too. |
|
|
|
I can add some info for all uneducated lads complaining in the last 30 or more pages:
- whattomine blake2s estimates are for solo mining. So your expectations are wrong from the start...
Hopefully that is obvious, but most people zero out the equipment part of the equation anyway because. For dual mining you need to - at a minimum - at least adjust the power spent, also. For my example I assumed zero costs except for 10% more power because the equipment costs basically nothing more than single mining and my wattage goes from 83-85 to around 92-94. Certainly far from perfect, but better than not adjusting. |
|
|
|
|
The code is easily available as people have pointed out, but someone without a good understanding of network security is going to either suck at it or be sucked into a mess.
Beefy server would help, but something like AWS (Amazon distributed Web Services) with built-in resiliency and redundancy would be much better, but of course requires more hardware.
The other side of the coin here (see what I did there?) is that security, redundancy and distributed points of presence are already built into AWS. Unfortunately I only have used it for domestic / US needs, and don't have a good handle on how it works (or not) overseas. You need US, European and Asian connectivity to be useful worldwide.
They would probably balk on trying to support mining, unfortunately. Great idea, but implementing it may well be impossible.
|
|
|
|
I'm not having any problems with random restarts and my GPU isn't warmer than dual-mining the previous coins - however I'm Dual-Mining ETH+SMART anyway... first of all SMART is more profitable for my GPU and there are stable (official) pools without fee. But even when I was mining XVG there were no crashes or overheating - just unstable pools.
Most people are not - at least I hope. As always your mileage WILL vary, that is a given. When I take the second coin out, I just crunch endlessly. |
|
|
|
there are pools which do not steal There may be, but when WTM gives you a negative income, it is time to punt.  (charts from the beta side with a single card pulled to show trends) I put my observations in the Claymore thread this time - because I was directly addressing dual mining with his miner. I dropped back to ETH only after I got up three times to fix my rig overnight. It ran for days at a time with "-mode 0" but was overheating and sucking more power by 30% Edit: "JEEZ!" that image handler auto-resizes to the max it can display. I started out with a little tiny graphic from my phone. Negative income is not the result I need, anyway. My effective hashrate used to be slightly higher than actual, but it was 10-15% less for the last week or so. I see my rig finding shares three or four times a minute again, and I suppose that the shear amount of time spent reloading and building the DAG was the culprit. |
|
|
|
|
Observations - I wanted to give my rig a little more time to settle down before I posted, but it is obvious that XVG / "Verge" is not the answer to what we can mine for the second coin.
My second go at what to mine this morning confirmed that I was paying to mine XVG, so I put my rig back into "-mode 0" because it had been awfully squirrelly for the past week. Normally it runs for days without intervention but Claymore kept restarting every 15 minutes and sometimes in only two. Max I have seen is like 50 minutes, and I was motoring for days without the second connection.
I was also burning more power and my cards were lit up to 80° at times. Of course the ambient temp is up 20° over the past two weeks, but when you hit 80° it's time to start asking questions and figuring out how to get lower temps.
I left the rig running while I was on vacation two weekends ago and it was still crunching away when I got home five days later.
The last straw was when it woke me up the second time overnight and I found the machine hung.
I removed the extra part of the command line about 6am and it hasn't restarted yet.
Claymore picked logical algos that were ASIC resistant to implement in v 11. Unfortunately all of us piling on the limited coins available with them made them unminable as well.
|
|
|
|
Iirc you can't run AMD and NVIDIA at the same time. You need to run the Claymore miner 2x.
1x with all AMD cards
1x with all NVIDIA cards
You can use -di for GPU selection (example):
NVIDIA: -di 034
AMD: -di 125
Will try it out, but i did have them running all at the same time with the one instance of claymores?  Before??? Whatt's changed? Seriously? That is your advice to this poor guy? Please tell my GTX 1060 & 1080 to quit playing fair with the two RX 580 cards in my rig. Obviously, they are not supposed to get along? I am seeing an average of 120Mh/sec from the four cards. Is it easier to manage with just AMD or nVidia? I suppose, but it is far too lazy to say that it will not work. Of course you can mix the red and the green GPU cards together in one rig. The very nature of the Claymore Miner is that it works with them all. |
|
|
|
|
