I slammed the ignore button before I could think.  I guess if you're going to suck, you might as well put a little effort into it.

MANY THANKS, Claymore!!!

Don't forget to pull each GPU card out by the riser and light them on fire one at a time to insure proper eradication.

Then go back and read page 1 - only after you complete the above steps.  Be careful, you don't want to get these out of order.  

Pretty much right on.  The best way to describe it is that many "anti-virus" programs don't even use scheduled downloads of "pattern" files for matching any more.  These days usually it's all kept in "the cloud" for easy (and instant) update.

The problem is that many no longer differentiate between a malicious (AKA "virus") code and a "PUP" or Potentially Unwanted Program in a commercial environment.  For businesses, you likely don't want employees running a mining application on your company servers, right?  Speaking as a former network security officer for the U S Department of Justice, you don't really care exactly what it is, but rather whether or not it is allowed by your "Terms of Service" (PUP) or whatever - or if it is actually harmful or what we use the term "virus".

"VirusTotal.com" doesn't care why (or how) any of the "anti-virus" applications determine it is unwanted, they just report the total detects.

There is no malicious code here, but it is a P2P app, and most - if not all - companies don't want Peer to Peer software on their servers.

5 hours, maybe??  Actually 4:59 - I use "-r 200" = 3:19

Truly odd one:

As of about two hours ago, 100% of my shares are being reported as stale..I am using 11.5 and had at most 40% ever, with fewer since 11.4/11.5 updates until then.

Niw I am actually seeing more reported stale than submitted, like the 9 or 10 sales with 8 total for a single card? Weird, but consistent for nearly 2 1/2 hours now.

I am single mining on ethermine.org

PS: (Post Mortem)

As always, I should have done a bit more research on things. I just got my first cup of coffee and didn't look at basic things like the reported share acceptance times. Watching more closely for a few minutes showed numbers like 5000ms or more than 5 full seconds.

I still have not pinned down exactly why it was, but since the rig had been running Windoze 10 for 18 days, I used the reboot method of fixing the problem and the times went back to being consistently under a second.

For me out in the middle of the national forest 20 miles from the closest true high speed internet, I'm on a satellite link, so the fact that I don't get under 50ms is normal. In fact 500ms is low for me and 750ms not unusual due to the propagation delay inherent to satellite up links and downlinks.

Regardless of how or why (I don't think it was a recent Windows 10 update, either), you should turn "QuickEditMode" off.  It does cause the problem described where the window appears to be "frozen".

My GTX 1060 6GB card from Gigabyte also has Hynix memory.  It's usually around 21.2MH/sec.  I got 23.8MH/sec from a 3GB generic "HP" card with Samsung VRAM, but it is in the shop.

It seems we're hearing a good bit of "things didn't work right" for about two days, mostly ending a couple of days ago.

I have been sick so not keeping up, and missed the 11.4 version, and went directly to 11.5.  I haven't really noticed anything major except that my standard deviation (amount of change in the average hash rate) has been a bit tighter, and the stales seem to have dropped a bit.

Draw your own conclusion. (?)

Ahahahahaha. Well? It's almost funny.

Yes, Mr Moderator - please run this non issue to ground (especially for ppl who can't read but figured out how to type). 

Actually, depending on who made the GDDR5 memory, recently built 6GB 1060's all run at +800 memory clock or more.  My new one has been running at +1000 (effectively 2000) since the day I got it and hashes about 15-20% better there than with the default setting.  I have Hynix memory, and since about August GTX 1060 cards made have all had RAM intended to run at 11M instead of 8, so it probably can take more but +1000 is the software limitation of the drivers.  (per the author of "nVidia Inspector" and "Profile Inspector")

Yep, G4560 or 4600/4620 are hyperthreaded, therefore essentially twice as fast from a logical point of view.  You should be fine!

Seriously?   It varies widely especially for rigs that have inexpensive CPUs like Celerons and some of the slower Pentium models.  Even the i3-7100 takes longer than 60 seconds to complete the boot process and load the purposefully delayed start items.

Any i5, i7 or faster or Ryzen 1500+ should get there in under a minute, true.  It also depends a lot on exactly what is installed on each rig, although if it is a true bare bones system without anything other than mining software added, it's probably fine unless it's a Celeron under 3.0GHz.

I haven't looked at the new iGPU type Ryzens yet, but - likely just not as easy and plugging them in and finding support for everything.  I know that a lot of people are finding that even recently made motherboards don't support them without a BIOS upgrade, which isn't possible if you don't have another CPU that works on it.

Exactly, but only for AMD cards, it's not supported for nVidia GPU cards.  The range is -50 to (+)50.

How do you figure that?  I get nearly double from my GTX1080 ROG/Strix OC than I can from my 1060.  A 1070ti should get just about the same, and a 1080ti gets more.

Some 1060 cards work better than others: my Gigabyte 6GB GTX1060 gets 21MH/sec but my 3GB Asus card gets close to 23MH/s.

Both my GTX1060 6GB and RX480 4GB Sappire Nitro+ cards get best ETH hashrate at 70% of their power (-30) - by 15 to 20%.

WTH is it with people posting the entire README!!!.txt file (and then quoting it?) lately? 

People just seem to think that open air rigs aren't susceptible to collecting dust, but a can of compressed air always does wonders for things - especially if you are not using a typical external rack rig setup.  It's especially true for enclosed rigs that have been running more than a full year, although in some situations I have found 'dusting' is needed every six months.

Another thing people seem to miss is that even though a card can hold a specific overclock for graphics work, that doesn't mean that running in almost 100% compute mode it is the best setting.  Typically we stress the cards much more than even the best graphics-based benchmarking tools by running the compute intensive miner 24x7 on our GPU cards.

Just using my single-card rig as an example: it's a GTX1060/6GB Gigabyte card that will easily hold +230 core clock offset, but I have backed it down to +220 and later +210 because Claymore is much more stable and tends to get better quantity of shares at that setting.  It would run with +225 forever, but it would get those messages about invalid shares, and regardless of what many people think - 99% of the problems we're having trace back to one of two problems: either OC is set too high or there is a problem with a riser card(s).  Some of them are better than others, and if you run into a batch with problems it is likely going to affect the whole group, not just one riser.  That other 1% can be elusive, but almost every problem can be cured by backing off overclock by 5% or swapping out the riser for the "problem card".

On a PC or smartphone? I had that problem on my Pixel XL phone and it was because I didn't have TOR resolution (Verge is a "dark" coin). I installed Orbot and configured it (using defaults) and then it connected. IHNI what the PC equivalent is, but you likely need .onion addresses to be resolved.

That is a quirk of how the Linux resolves name mapping to IP addresses. For example, if you look under Windows, there is no reply from the server for inquiries on us1.ethermine.org because it doesn't respond to them and Windows uses port 80 for NSLOOKUP & ping queries. The server is intentionally not reachable using port 80. Port 4444 (and 5555 for SSL in this case) respond to connection requests of course - or we would not be able to get and submit work.

Try " PING us1.ethermine.org ", it doesn't respond on my machine. Now, us1.ethermine.com does - but we use the .org address to work.

Just like any other protocol, you can not pass normal and SSL (for all practical purposes encrypted) traffic on the same port. Think about hypertext for the browser - normally port 80 but 443 for SSL.

I knew it couldn't work on the same port, but the README!!!.txt doesn't really make much note about it, just the example shows port 5555 vice 4444.

It works very well and isolates you from man in the middle attacks that might capture your traffic amongst other things.

In the context of pool mining, a 'stale' share means that someone else beat you to it (i.e. it was reported already).