Quote from: Frippster on March 11, 2018, 05:10:00 PM

11.3 crashed all three rigs within 5 minutes. 11.2 has been perfectly stable between my 72 hour reboots.

Quote from: Teress on March 11, 2018, 04:55:57 PM

@Claymore
I switched to linux version of Claymore some time ago. But am I blind or why is linux version storing in log files less info then win version? For example one of my rigs is rebooting. I want to analyze problem reading logs. On windows version I saw in that case for example "Gpu0 failed..". On linux I can see only "NVML: cannot get fan speed, error 999" but NO info about which gpu crashed the driver. Can anybody point me right direction?
Thanks a lot...

BTW: v11.2 & v11.3 is crashing after a while all my Nvidia rigs, previous version was absolutelly stable.

I have 2 rigs, each with 6 NVIDIA GTX 1070 8GB cards, and my MSI laptop has 1. A few months ago, I decided to add Windows 10 OS, as I was having problems with Linux on the x6 card rigs (I had large capacity drives, so partitioned them in order to keep Linux in case I ever want to test anything and compare results). Sounds like we likely experienced the same and/or similar problem, as all 3 of my machines were running fine with previous versions. After an hour of testing, adjusting, and tweaking some things, everything has been stable on v11.3 for almost 24 hours now.

For me, I believe the majority of the crashing was caused by the auto fan control feature in MSI Afterburner (which I prefer for overclocking, and read a few posts elsewhere in this thread from others about that program causing conflicts). Anyway, the fix was to disable fan control in MSI Afterburner, and let Claymore miner control the fans. I have x3 powerful fans controlled by the motherboard on each rig anyway, as I like to keep my cards cool. Obviously, use caution, keep a close eye on temps, and make sure the fans on your cards are working correctly if you attempt this fix on your NVIDIA cards!

I was also running the latest Windows 10 x64 391 official NVIDIA drivers, but rolled them back to the 388.71, although I don't believe this was any cause of the problem. I will reinstall the latest drivers later today and report back after running stably for at least 24 hours.

On a different subject, I did download a virus from the latest zip file found in Claymore's link to the Google Drive download. After extracting the download, there were x3 folders within the main one named "cuda6.5", "cuda7.5", and "cuda9.1". Inside each of those folders were x1 .dll file and a separate "EthDcrMiner64.exe". I always scan compressed files downloaded from the internet after extraction, and thankfully it paid off! The "EthDcrMiner64.exe" file in the "cuda6.5" folder was flagged as a backdoor trojan virus - NOT the usual false positive "bitcoin/coin miner" virus. Not sure how or why that file got in there, but it was definitely a very real threat that still has me on edge and VERY uneasy! I just attempted to download the same file found in the Google link in the OP, and now it gets flagged as a virus and won't allow me to download.

I have used Claymore's miners for quite a while and never had any problems with his programs, so I do NOT believe Claymore would purposely and knowingly include a virus which allows remote access to your pc (ultimately for the purposes of stealing your coins, digital assets, credit card numbers, personal details, etc...). The infected file was downloaded via the Google link in the OP approximately 3 hours after its release. If the people who create and use these viruses spent half the time it would take to create such a thing, they could make plenty of money on their own (legally, and without having to steal). The thieving scums who do this continue giving Bitcoin/digital assets a bad rep and seriously impact this emerging sector in a very negative way which hurts all of us (not to mention the lack of words that describe all lowlife bottom feeding thieves).

Anyway, USE EXTREME CAUTION & ALWAYS SCAN DOWNLOADED FILES BEFORE USING!

Here is a screenshot of Claymore's Miner showing as a false positive "Trojan.BitcoinMiner". Although correctly flagged (as a miner could be negligently installed on a persons computer to mine for the attacker), it is a false positive in this case, as we want the file to mine for ourselves. The screenshot shows what your antivirus program should falsely flag. In my case, the antivirus program found two separate threats - the one seen in screenshot, and another which was a very real and dangerous threat that would have unwillingly allowed the attacker remote access to my computer (sorry, but I do not have a screenshot of the real virus. as I immediately removed it). Screenshot of false positive on imgur.com via

or https://imgur.com/a/XH75d