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

Any word about the AMD 17.7.2 released today? Working? Good? DAG?

I couldn't get it working. For the first time since i'm using 580 i needed to revert to the old drive.

See this screenshot to see how Claymore Miner contributes to Ethereum Difficulty growth.
When 9.7 was released the difficulty raised for 11% in 1 day. Impressive.
https://photos.app.goo.gl/1hOylZFdKFr3Cdj23

I have been mining on wifi since I started with no issues. I have a usb extended wifi adapter for 1 right and the other is one of the plug in wifi extenders I have hard connected to my other rig that just repeats the wireless router to a new network name. I will probably build a few more rigs and run them off a switch off the wifi extender.

If you want to use WiFi use an USB extention cable, been working happy for long time now.

It has to do with interference of the GPUs working, don't ask me how I know.
Try it an let me know

Save your ETH.

you need The Creative Update. You can't just hit update. need to download separate.

https://www.microsoft.com/en-us/software-download/windows10

Absent of evidence otherwise I think it was rational to think what I did.  Not sure I want to push that much voltage to hit 1200 MHz but I would like to learn the process.  Any suggestions on search criteria would be appreciated.

Thank You that's what I figured something is wrong going to try miningpoolhub

Very low hash rate less than 3Mh/s per card! Offering .1 eth to solve problem.

My settings:
Windows 10 with latest updates
Nvidia 1070 Hybrids with latest updates (tried many different versions as well)
Synced full blockchain with Geth
Windows tweaks for 16gb virtual memory
Claymore 9.7 (also tried 9.5)


I have 4 GPUs running and they are pulling less than 9Mh/s in total. I have spent like 20 hours trying to fix this problem i'm just about ready to part out this whole rig. I even tried reinstalling windows and trying everything from scratch without any luck. Willing to pay .1 eth to whomever can help me get this to 25Mh/s+ per card like it's supposed to be.

Never said *I* can't ;P Already have it at 1.45v and pushing 1200. Just pointing out the other guy that thinks he's changing HBM2 voltage with the slider on watt man

Can someone tell me some good advice about use of miner. example I use bat file only for start. all other stuf I do in afterburner, what can I beter do in bat or config file. thanks

Is there place to look around that method on RX4/580 ? Is ther an I2C diag tool on Linux, similar to VRMTool...
atl least to learn who to put in VoltageObjectInfo....

Both my Vega FE's are in my gaming machine running win10.  My Linux box barely had room for my GTX 970.

I have zero experience modding video card bios, and limited experience editing the bios for overclocking a CPU.  I've always been a person to leave things stock unless I have a pressing need.  OC'ed my 3770k for Arma3... playing with my Vega's for mining purposes since that's why I bought them.

DON'T MINE WITH WIFI--

It really doesn't work well.  Wifi is OK while traveling, but at home I use cable.       --scryptr

Please share!  I would love to break the 1100MHz wall!

I did notice that wattman said 1000mV when I switched it off of auto.  I did need to go from 1000 to 1050mV to get 1100MHz stable, though it's possible other factors effected my results.

Your not changing HBM2 voltage. If your changing memory voltage via wattman your probably not doing anything(if anything your changing VDDCI). Vega's HBM2 voltage is locked at 1.35v for highest state. There is not much headroom to over volt it much more, since they are already over-volting it from the HBM2 spec of 1.2v.

hey guys, new to the forums.  Been mining for about 1.5 months.

I have 2 PCs mining, 1 was my main rig (older) and the other was a somewhat dedicated miner.  Both on wifi adapters

I've been having a problem in this couple of days with my main PC where i get the "socket was closed remotely by pool error".

When it's not mining, the PC's internet connection is completely fine.  Once I open the miner, connection drops (but shows as connected at the icon), can't go nowhere with chrome and the error pops in the miner.

Once I close the miner, internet connection comes back after a while (or sometimes I need to restart, but point being that connection is ok as long as the miner isn't on)

A moment ago I experimented with a lan cable.  Wifi adaptor in, miner started, same old problem.  Unplugged wifi adaptor and plugged in cable while miner still running, error went away in like 20 seconds and it's happily mining.  This happened while the other PC is mining fine the whole time with a different wifi adaptor.

So according to above, I've seemed to pinpoint the problem to the wifi adaptor, a TP link TL-WN823N.  Anyone knows how this could happen though?  I've also experienced extremely poor performance in online gaming with this adaptor, but I mean the thing still works when I'm just surfing the web, even streaming videos in youtube so connection speed is out of the question.  

What makes the adaptor go bad when executing connection-dependant programs?  Is this adaptor trash or not?

Hi, I just started using this version of Claymore and I get an error that doesn't let me mine ETH:

ETH: Received error: {"i":4,"result":null,"error":[24,"unauthorizedworker"]} and then only DCR keeps getting it's share normally. I have registered a worker correctly for both pools (ETH and DCR), any ideas? password is right for both too. ETH start mining normally and then suddenly this happens. I also have allpools set to 1

Also, any chance in the future to allow to mine only DCR for example?

Haahaha bro i know very well how to dual mining infact i am dual decred at 3200 mh with amd rig but is low earn

Forgive me, but what is ISA?

I wish I could get the HBM2 memory clock over 1100MHz, but that seems to be the hard limit.  I can't get my vega cards to sit at a specified core clock.  It seems from my experimentation that the core clock needs to be equal to our slightly above the memory clock to achieve peak hashrate.  Any higher and it's wasted energy.  I've also noticed that GPU temp has a drastic effect on performance, so getting lower clocks, lower volts and high memory clocks seems to be the ticket.