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

Thx, I was going to ask the same question. Crossfire disabled. About RDP, this question must be another one asked million times, which is the problem with it?.

Thx

Carlos

Hi:

So far I have reduced Voltage -96 mV, increased GPU Clock Speed to 1400MHz and Memory Clock Speeds to 2200MHz, I keep reading about that 1750=>2000 "thing", I understand it can be done flashing the bios, so if I understand it ok, there is nothing else I can do to improve my MH/s but to flash the bios, 27.5MH/s is the Top I can get with AfterBurner?.

Thx very much,

Carlos

I already asked about 20 pages ago, but here it goes again, cause i did not get an answer:
can pool job timeout be changed? Now it's 15 minutes, can it be set to less?

Hello,

newbie here. I am facing the following problem with the installation.

The OpenCl seems not working. I am using MSI GTX980ti. Anyone to my rescue???

The message:
SYSTEM32\OpenCL.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0xc000012f.

Is anyone mining with both AMD and NVIDIA cards in a single rig? I'm having trouble getting Afterburner to work with the AMD cards when I mix.. Anyone got a solution to this?

Well, little example. I had 2 identical cards, Nitro+ RX480 4GB Samsung. Same settings, same core, mem, voltages etc... Simply exact same confirmed settings. But one card simply was running 13-15 degC hotter then second one. Yes, far away from each other to make the cooling factor, airflow etc. irrelevant. And guess what? The hotter card even with the same mem straps was hashing a lot lower. And now why was that? Both cards had the same cooling solution from factory, backplate, not sure about Nitro+ VRM heatsink etc. My guess - one card simply was "a bit screwed" or something, my first idea previous owner run it with mem errors and the memory is since that time "more likely to produce another mem errors"...
So what is the conclusion? Should I change settings on all my card to run faster (more Mhs) but with mem errors, or just have all cards running slower but clean with zero mem errors? Where is the border where mem errors will start affecting accepted shares due to incorrect shares?

Does anyone know when Claymore will exceed the 3GB GPU's? There are some reasonable prices for 3GB CUDA cards on the market now and in times of GPU scarcity these are pretty tempting. Looking at GPU-Z right now it shows 2953MB dedicated memory on my RX 470s and I don't know if that means we are getting close to the 3GB limit. I developed a sheet that shows the DAG may not exceed 3GB until Nov 2018. Any thoughts on how much GPU memory above and beyond the DAG size is required to run? If anyone else is interested in my DAG size sheet it is https://goo.gl/YHM7HY. I couldn't find such a table anywhere so I decided to create one myself. If see any errors please let me know.

It will require some changes in Stratum implementation (in all supported versions) because I will have to use several IDs in share submit requests to identify GPU in server response. I would not like to change that code because it can break compatibility with some pools, I will do it but I need to do a lot of tests to check compatibility with all pools. No ETA for now though.

I removed it because latest drivers solved issues for Pascal cards. Well, may be I should return these notes back, though need to find them somewhere to do it...


In fact you don't understand mining details. Some people think like you and tried to check fee rate in my miners technically, for example:
https://bitcointalksearch.org/topic/edit-confirmed-fee-is-accurate-1681108
About number of shares: I explained it several times, then added to FAQ here:
https://bitcointalksearch.org/topic/claymores-zcashbtg-amd-gpu-miner-v126-windowslinux-1670733

Here it is again:
.....
Q: Why do I see more shares for devfee than in my mining for the same time?
A: Most pools support variable diff, they change "target share" after some time after connection. For example, you have very powerful rig, after connection you will send shares very often. It takes some CPU time to check your shares so after some time pool will send higher share target and miner will send less shares (but they will have more value). When pool updates share target you will see "Pool sets new share target" line in the miner. This way pool can adjust the number of shares that miner sends and balance its load.
So check the log or console text to see current target for main mining thread and for devfee thread. For example:
DevFee: Pool sets new share target: 0x0083126e (diff: 500H) - this is for devfee mining connection
Pool sets new share target: 0x0024fa4f (diff: 1772H) - this is for main mining connection
As you can see, target share for main mining is higher in about 3.5 times, so for main mining miner sends in 3 times less shares (but they have 3x more value) than for devfee mining.
.....

For ETH most popular pools don't use vardiff, but if you see many shares in devfee it means that you use such pool.
So if you see that devfee mining gets more shares - check in the log what share target is used for devfee, it will be much lower than for main mining, so these shares are much cheaper.
Of course you can forget about all these complex technical details and continue think that I fool entire community and take 3% or 5% or 7%...
I write miners for a long time and a lot of people use them, such thing would be discovered quickly because there are ways to check real devfee mining rate.

I just wanted to mention that the Mega.nz link on the OP of this thread is infected with a few viruses (as of 24hrs ago). Can someone please look into this?
I would hate to see anyone get burned...

Claymore - thanks for adding the new API to enable and disable individual GPU's. I've added support for that in Awesome Miner.
Would it also be possible to extend the API to include accepted / rejected shares per GPU? Thanks!

Wolf, maybe it would sound strange, but - are you 100% sure that running cards 24/7 for a year with millions of memory errors will have NO impact to possible degradation or damage of that cards? I saw a lot of cards for example RX 480 8GB with Samsung memories, which in normal condition can do easilly 30+ Mhs, but they were hardly hitting just 27 Mhs! Something had to degrade them and memory errors is got an idea no. 1.

Claymore claim that he take 1%, but in fact he took more. You can watch the status of mining, every devfee mining, he is always get the share. He is cheating on 1%. I think he takes at least 3%.

Claymore, I noticed the front page of the thread with the new release links no longer mentions the issues with Nvidia 9xx and new drivers on Windows 10.  Has that been resolved and Maxwell cards can mine at full hashrate with latest drivers in windows 10?

Dear,

I use ethos (linux), how can I set email in your config file?
-ewal
-eworker

How long does the devfee usually take? I just saw that "Devfee: Stop mining and disconnect"

Is the claymore chargning anything us, or the nanopool that I'm using, how much is the fee and how often does this happen (if more than once)

At the other side I'm very statisfied with claymore, I had an issue today as the windows defender is counting it as a threat/virus and deleted the files, but I got it solved by excluding the folder so the antivirus won't scan it.

Ur Windows Defender deleting some files from Claymore folder

Top tip there! Knew about the reasons behind it, but excluding the folder is an excellent shout. Thanks.

There be a Microsloth error! Windows Defender probably deleted it for you, all that dangerous money could harm a little feller like you! In any case your miner executable is missing.

The same thing is happening here.