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

Is this 15.0 good for gpu 1060 nvidia?

Are the 1050ti still giving "cannot write dag" errors on windows? And has anyone found a new fix for it?

I've seen that some of you guys have problem with allocating DAG on 4GB cards. What mobos and configs do you use?

Never once i had encounter that problem and some of you have even switched to Linux because of this. I have a really hyge virtual memory config and the HDMI to monitor is on the motherboard iGPU-port (and of course activated in BIOS). Maybe that is the reason that some experience an issue and some not. Windows doesnt allocate any memory to my gpus at all what i can see.
It is even possible to mine ETC at DAG #308 with total GPU memory usage at 3,56GB per GPU.

Can you who have problems with allocating DAG size please share your configs?

I have a rig with:

Windows 10 pro
Newest AMD drivers (19.11.3)
64GB virtual memory
Asus B250 Mining Expert
Intel core i5 6500

GPUs:
6x Sapphire Nitro RX470 4GB Mining Edition
2x Sapphire Nitro+ RX580 4GB
1x Sapphire Nitro+ RX580 8GB
1x MSI Radeon Vii 16gb

//Trehjulingsleffe

my geforce 1050ti  dont have any problem in ubuntu 18.04 and work correctly but i have problem to use ubuntu with amd rx560 card
i do install driver in ubuntu 18.04 but claymore not detect my card to start mining.
what i must to do ?
pls help
thanks

We will shortly release a Ethash miner testing tool, it's just a simple open source node.js project. You will be able to run controlled long-running tests on all miners. The reason this is important is that the displayed hashrates of Claymore and Phoenix are just bullshit. They both add +1.5% or more of fake hashrate. I don't ask anyone to buy these claims without being able to verify it themselves though, which is why we'll release the tool (which acts as a low diff fake pool with a static epoch and controlled job update mechanism) and everyone can see for themselves if they are willing to mine air for ~24h. To verify that we're not insane, we've also reverse engineered both miners, analysed their kernels, traced their OpenCL enqueue calls, and the evidence is clear.

Plenty of people have already pointed this out just by logging all shares over time, but it's really hard to prove anything. You need controlled runs of (preferably) 1 million shares, which is more or less impossible without controlling the environment properly. Another simple way is just to find a big farm from e.g. the frontpage of ethermine.org (found blocks) and check the difference between their reported and accepted hashrate.

Here is one example: https://ethermine.org/miners/6F714AaAAF72977267601cC1cADC49fb3966Ff89/dashboard

Reported: 3.206 TH/s, Accepted: 3.111 TH/s, difference -2.97%. I'm fairly certain this is Phoenix miner. Why do we have a diff of -3%? The dev fee is 0.65%, and there are 1% stale shares, and this is a HUGE sample set that should converge nicely. Contrary to what people seem to believe, the additional -1.35% just should _not_ disappear. For comparison, here is a run using our soon-to-be-released testing tool for 247k shares on Phoenix 4.7c:

Code:

Hashrates for 1 active connections:
    Global hashrate: 228.51 MH/s vs 235.43 MH/s avg reported [diff -2.94%] (A247366:S1575:R0 shares, 93582 secs)
    Global stats: 99.37% acc, 0.63% stale, 0% rej.
    [1] hashrate:  228.51 MH/s vs 235.43 MH/s avg reported [diff -2.94%] (A247366:S1575:R0 shares, 93582 secs)


Look at that, a diff of -2.94% between the reported and accepted hashrate, what a coincidence? To be fair though, 247k shares is only good for a +-0.5% estimate at 99% confidence, so we must treat the value accordingly. The point is that neither CM nor PM can never ever produce a poolside hashrate over time that matches their displayed hashrates.

Sorry for a long rant to your simple question, the bigger point I'm trying to make is this: unless miners start accepting that CM and PM are bullshitting their displayed hashrates, "comparing" CM/PM/TRM/Ethminer is pointless, you'll just be stating that CM and PM are much better than what they really are.

Under the circumstances that's not possible since gpu will return old strap and memory clock when miner is closed.

Have similar issue,

Updated my miners to Claymore 15 and now they just keep crashing...

8 x Asus RX 580 OC 8GB edition per mining rig
Windows 10 with Latest Update
8GB DDR4 Ram on Motherboard
Additional 24GB Virtual Memory.
120GB SSD drive.

Using older AMD ASUS Drivers that were working fine before update

Everything was working fine until new Claymore 15 released...hoping it is a bug and will be fixed soon.

Some of the GPUs start up fine but then the miner crashes and restarts

I am using latest version of Awesome Miner to run my mining farm. Anyone else having similar issues?

Any help would be much much appreciated.

Cheers

Are the 1050ti still giving "cannot write dag" errors on windows? And has anyone found a new fix for it?

its there a way to use just the straps and disable the miner ?

Sounds like you are using Graphics Mode instead of Compute Mode.

Hey guys, i used to read last 50 pages before but i didnt find the solve. I have 5 rigs with 8x470/480/580 and all of them worked perfectly utill couple days ago... with claymore v10.. i was getting about 30hs from all of them and now when i tryied clayomor v15 only about 9hs.. im running it on win10, and used to overclock them with .bat file... Please can anyone help me, or show me the post where i can find the answers...

Thank you, I going to try video steps.

I have another old rig with 6 GPU EVGA Geforce GTX 1060 3GB video cards and I was wondering if it's possible to use Claymore 15.0 to mine on it.

Is there a way to mine with Claymore 15.0 with this rig?