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

TFW you get busted using claymore on company computers to mine a crappy alt coin... They can't fire me though because I quit

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.

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.

I had a problem when I started with only 2gb of RAM, but when I did 4gb it ran. So I believe it won't work on 2gb of RAM. I am pretty sure I had the virtual memory set correctly and that it was just a physical ram problem.

I remember I fixed that very same issue after I removed some RAM from my miner by decreasing the virtual memory. With 2 GB RAM, there should be a maximum of 6 GB virtual memory set according to Microsoft. In my opinion, up-to 8 GB virtual RAM should be fine as well for 2 GB RAM systems.

I'm pretty sure you've 4-8 GB RAM installed in your systems where you've set that much virtual memory.

EDIT: Here's what I'm talking about: https://www.ultraedit.com/support/tutorials-power-tips/ultracompare/increase-virtual-memory.html ... Read the last paragraph.

Just what the heck are you talking about? Virtual memory (pagefile) can be anything you want, there are no min or max, in fact the more cards you have the more Virtual ram you need, I have plenty or rigs running 50GB pagefiles.

You are confusing what Windows automatically sets with your 1.5x...

Please don't spread misinformation.

I have a question regarding the voltage options in a mixed rig.

I have a rig with nvidia and amd cards.

"-cvddc   set target GPU core voltage, multiplied by 1000. For example, "-cvddc 1050" means 1.05V. You can also specify values for every card, for example "-cvddc 900,950,1000,970". Supports latest AMD 4xx cards only in Windows.
   Note: for NVIDIA cards this option is not supported.

-mvddc   set target GPU memory voltage, multiplied by 1000. For example, "-mvddc 1050" means 1.05V. You can also specify values for every card, for example "-mvddc 900,950,1000,970". Supports latest AMD 4xx cards only in Windows.
   Note: for NVIDIA cards this option is not supported."

So, I understand I cannot use -cvddc and -mvddc for voltage control on the nvidia cards, but is there a way to use them on my AMD cards without running 2 instances of the miner?  (I use MSI Afterburner to control the power on the Nvidia cards)

Thanks in advance

Miner should run just fine on 2 GB of RAM. "Virtual memory" could be the issue here. It should be no less than 1.5x and no more than 3x the amount of system memory (RAM).

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.

Hi there i have only being mining for 3 weeks , i have created a very nice automated email alert system thanks to https://www.howtogeek.com/120011/stupid-geek-tricks-how-to-send-email-from-the-command-line-in-windows-without-extra-software/

and HWINFO64 , we create this

$EmailFrom = “[email protected]”

$EmailTo = “[email protected]”

$Subject = “The subject of your email”

$Body = “What do you want your email to say”

$SMTPServer = “smtp.gmail.com”

$SMTPClient = New-Object Net.Mail.SmtpClient($SmtpServer, 587)

$SMTPClient.EnableSsl = $true

$SMTPClient.Credentials = New-Object System.Net.NetworkCredential(“usr”, “pass”);

$SMTPClient.Send($EmailFrom, $EmailTo, $Subject, $Body)

on notepad

You will need to change the following:

$EmailFrom = Your GMail address.
$EmailTo = The recipient’s email address.
$Subject = What you want the subject of the mail to say.
$Body = What you want the main part of the mail to say.
usr = You will need to replace this with your GMail username.
pass = You will need to replace this with your GMail password.
, we change the extension to .ps1 then we apply this on powershell Set-ExecutionPolicy RemoteSigned

then we create a .bat file with these "powershell -noexit .\email.ps1" we create a shorcut to the bat and put in on shell:startup , by doing that if the computer restarts by lets say a windows update or a power failure it will automatically send an email to your phone an if you have an apple watch you will get the alert , but its better if you also use HWINFO64

to monitor the watts on gpu chip power in my case i put the low on 100 the max on 200 you choose alert settings to run a program to the name of the .bat so it will automatically send a continuous email alert if one of the cards goes below 100 watts or up of 200 watts (i use a vega 56 with 852 mhz on gpu and 935 mhz on memory , it uses 172 watts claymore dual miner 41,3 mhs ) but if something goes wrong and the computer restarts wattman will go default and it will go to 230 watts 34 mhs the i will get the constant alert and remotely connect and put then to 41,3 mhs 172 watts , i hope you like it and if you feel to tip on ETH thank you

0xebceb44fb2af75acc4a834774eee6d1330d333d7

Hello, i have a big problem with Claymore Miner Manager. I have about 150 rigs in my network. Most of them works with Ethos - some of them with miner version 11.6 some with 11.7 or 11.8. A lot of miners after about 20h stops sending stats on port 3333. I get information on Claymore Manager that rig is not working (same in Awesome miner - i use both solutions), but rig works normally. I found that was a problem with version 11.6 on Linux and there is some fix for them, but i hav this problem also with 11.7. Do you have any solution for that?

Nice

My bro , why the 11.8 work great on AMD and on Nvidia on etherminer does not work for nothing, please any help

How does this affects certificate checking when using ssl/tls? Where/how does claymore verify certificate now?

Sorry, noob question: My rigs doesn't restart even with the "-r 1" and reboot.bat file in the same folder. Anyone manage to get this option working?

The power management did not cross my mind , i will check that out right now but wow this issue is seriously driving me crazy lol. I love fine tuning my machines to work like clocks. the other 5 rigs haven't turned off, dropped hash rate or anything else in months(unless of course when i swap to another coin)

An excellent calculator, I use it myself .. With a lot of functions and the second time is simple for a beginner

If it happens exactly at the same time each day right after the rig starts mining then its most likely your power management settings.

Basically if there was a Win 10 forced update it might of reset some of your power management settings and after a certain while it turns off certain devices which can cause this.

Go to your power settings and make sure everything is on Always ON and 100% power.

Temporary Solution until you found a fix

try to create a batch file that will restart the system ... let say every 3 to 12 hours it will auto start

Weird issue with 1 rig.
I have 6 rigs 8 cards each. everything has been fine for about 1 year.
now my rig 5 drops hash rate from stead 235MH/s down to like 100
EXACTLY after 24hrs, i mean as soon as it hits the 24hr marker bam hash rate drops to shit and only a system reboot brings it back to normal for 24hrs again.
system configuration applies to all 6 rigs
windows 10
claymore 11.8
4gb of ram

**
if the issue happened at random times after some random interval i would think its drivers or some other issue but i cant wrap my head around what could cause
the hash rate to drop and not get fixed unless system is rebooted after exactly 24hrs later.
any help would be greatly appreciated