Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux)

[SummersideGuy]

having an issue where the miner just crashes immediately upon start.

using:
win 10 (creators update)
latest nvidia driver
gigabyte geforce 1080
20 gb ram

batch:
GPU_FORCE_64BIT_PTR 0
GPU_MAX_HEAP_SIZE 100
GPU_USE_SYNC_OBJECTS 1
GPU_MAX_ALLOC_PERCENT 100
GPU_SINGLE_ALLOC_PERCENT 100

EthDcrMiner64.exe -epool us1.ethermine.org:4444 -ewal 0x34B1dbA2F6A60FFc643EBC438e60Fe9bE9Aba437 -epsw x -eworker stratum

any ideas?

What happens when you run the default start.bat?

same thing.

I am having this issue also, first I was getting black screen and then I just did a fresh install of windows 7 now no black screen but the miner crashes upon start up 9.7 and 9.8 both crash upon start up

[1714887693]

1714887693

[1714887693]

1714887693

[1714887693]

1714887693

[Trimegistus]

ok and what about a .bat file and is supernova reputable? oih and theres also a epools wich i have with nanno, but then a dpool file do i need to make a new dpool file?

A config file is more versatile, an epool and dpool files are only required if you want to have failovers. As you should...  

Suprnova's reputation?



You can be the judge of that, ok?

[speedyb]

ok, do i neede a pool worker? noticed u had a number sign by it is it neccisary to name a worker? should i name it as name of wallet?

[speedyb]

actually how about how do i make a .bat file as i dont really use my config file. also another thing when i was doing sia coin i had some stratum in there not sure if ima need that for decred or not am tryin to learn slowly.
i tried to make a new .bat file and it says failed to get nonce1 handshake and times out i used same parameters can you help with a .bat file would be very thanksfull

added dpool dcr.suprnova.cc:3252 -dwal suprnova.1 -dpsw x -allpools 1 as a dpool.txt

now i get a stratum error?

[MigratingCoconuts]

Upgraded to the latest beta driver with mining fix while coming from 17.5.2. Like others, I'm having some issues with voltages returning to default. Running Windows 10, mix 470/480/580.

I've read various posts relating to voltages not staying set, and I figured I'd add my own experiences in hopes of finding a workaround/solution.

What I see happening is that AMD drivers are not correctly storing voltage settings. The drivers seem to re-apply the default voltages when switching between power states, when primary display is turned off, resolution is changed, and potentially going in and out of exclusive fullscreen.

Once the voltages are reset, all tools (wattman, overdriventool) still display the voltages as the user defined settings. To get the voltages back down, I must either increase, or decrease mV slightly, then return back to preferred setting.


A possible solution could be to have claymore dual miner check every minute or so, and if needed automatically re-apply cvddc and mvddc with a +/- 1 mV. My past experience using cvddc is that it sets only once when the miner is first launched and never tries to re-apply if settings have changed.

[speedyb]

question is the dual miner just a gpu and cpu miner combined?
when doing ether to get lower fees would i be better off doing ether with claymores then downloading a cpu miner and mining with the cpu somthin different?

[xmonkx]

hello
i have a big problem with the last version and all over miners. works with 3 cards and when i want to put 4 gpu cards on my rig, it crashes...
all the same cards, Under win10 fresh installed, AMD driver 17.4.4, stock cards, psu 1200w seasonic prime on asrock H81 rev2

risers are ok because:
- gpu 1+2+3 => ok
- gpu 1+2+4 => ok
- gpu 1+2+3+4 => ko...

claymore start well and detect the 4 gpu's but crashed before to start mining, just after GPU detect.

please help me !!

- Make sure the card is not sharing power with another card
- Make sure each riser not sharing its power with another riser
- Run all cards on stock BIOS and stock seetings
- Uninstall MSI AB or similar software
- Run DDU in safe mode
- Reinstall AMD driver, the latest
- Run Claymore with minimal settings -cvdcc 1000 -mvdcc 1500

Share results and screenshots from GPU-Z

hello,
i did everything and its still the same problem... im running now Under 4 cards and it's crashing.
Under GPUZ i don't see any problem and all the cards are detected. no time to post screenshots for the moment.
any idea ?

i put under 2 cards, i've got another problem about drivers, perhaps it's my problem, with 2 cards, on pciexpress 1 and 2,
one cards is Under Crimson 17.7.2 / whql /win10 64 drivers (opencl ticked)
and the second one is only whql / win10 64 drivers (opencl not ticked)

Did you run DDU? be honest...

of course i did it !
i had to go to my job this morning, not enought time sorry.
here is the screenshot with one card, it seem that there an exclamation behind my card. Conflict between windows drivers and AMD driver ??
do i have to use DDU each time i add a card and re install crimson AMD drivers 17.7.2 ?
https://www.noelshack.com/2017-33-3-1502867786-capture.png

i tried to use simplemining and it does not work well at all... only 10mhs with 3 cards and gpu core often low at 300 instead of 1236, really strange.

You installed the wrong driver. It has to be CRIMSON BETA, not 17.7.2.
This is the latest AMD driver, optimised for mining
http://support.amd.com/en-us/kb-articles/Pages/Radeon-Software-Crimson-ReLive-Edition-Beta-for-[Suspicious link removed]pute-Release-Notes.aspx

I have the same problem. I mean 3-cards problem.
I have 8 amd rx cards.
I run 3 claymore miners with 3 cards per miner as workaround. It works fine.

I still don't know the what the root cause is.

[biggee]

Mixed RX480 / 470 6 Card rig (all cards modded) / Clay v9.8 / Win 10

- Wiped the old drivers, installed the new AMD dag fix drivers
- Patched the drivers
- Installed AB beta

Mining again and hashrate almost back to what it was before.

But....

Afterburner is pretty much useless now other than as a fan controller. No control over anything else whatsoever, gpu / mem / voltage - nothing...

Trixx looks like it's working but does either fuck all or drops the hashrate (on settings that have been perfect for nearly a year now).

Wattool doesn't work anymore either - showing no readings for anything.

Claymore crashes on DAG creation as soon as you try to use any -cclock settings in the batch file.

Wattman is the only thing that seems to work, allowing everything to be set as it should be with the desired results, but this new driver is so fucking unstable that the rig crashes every hour and every time it does wattman resets itself.

Props to AMD for trying to sort the problem for us, but this is just a fucking shambles.

The latest thing I'm trying is using AB as fan control and setting the mclock in Clay, so far it's working but will have to wait to see how stable it is.

**EDIT** Claymore crashed after 5 minutes - GPU's hung.

[biggee]

Hi Claymore,

I believe the voltage issues with 9.8 and the beta driver, are specific to the RX580 cards, from what I've read the RX480s are just fine with the beta driver.

Not true, 480s here, voltage control doesn't work at all on the new driver.

[SummersideGuy]

Ok so I need some help here:

Rig
Windows 7 64 bit
3x RX 560 1x RX 570
Rig was working fine then I decided to installed the Beta Drivers that fix the dag issue
I ran  DDU then rebooted then ran the driver installation
Rebooted
My card Bois's are all modified
When I install PixelPatcher and reboot the windows boot logo comes up then black screen
If I undo the Pixel patcher everything is fine but I cannot mine as the cards are altered so I need the patcher but if I install the patcher I get a black screen

So a fresh install of Windows fixed the black screen with the beta drivers but I have another issue when i go to run 9.8 or even 9.7 it starts gets to the point where just before it creates the DAG file then it crashes
I reverted back to older AMD drivers for now as the current frustration and inability to control the voltage for 3-4Mh is not worth it. Hopefully this will get more refined over the coming weeks

[tperalta82]

Hi Claymore,

I believe the voltage issues with 9.8 and the beta driver, are specific to the RX580 cards, from what I've read the RX480s are just fine with the beta driver.

Not true, 480s here, voltage control doesn't work at all on the new driver.

on Afterburner, latest beta, try to set the voltage control in settings to thirdparty

[esrodrig]

updated to 17.7.2 and 9.8 and I cannot keep memory clock at 2045 where I usually keep it.. it keeps bouncing 2045 to 1000 and back to 2045 as a result my hash rate is saw tooth even on my pool page. evn in wattman, the slider is not able to be set to a static value.. seems greyed out.

I installed with DDU to clear old drivers, I also tried upgrading to the new beta drivers and no fix.

it was fine prior to upgrading to 17.7.2

Has anyone else come across this issue?

ASUS ROG Strix Radeon RX 580

https://i.imgur.com/OZ0Zs3C.png

-Not 17.7.2 but CRIMSON BETA

Had the same issue when using 17.7.2 drivers. Went back to 17.4.4 where it was running before with no issues mining ETH.

[TechPark]

Upgraded to the latest beta driver with mining fix while coming from 17.5.2. Like others, I'm having some issues with voltages returning to default. Running Windows 10, mix 470/480/580.

I've read various posts relating to voltages not staying set, and I figured I'd add my own experiences in hopes of finding a workaround/solution.

What I see happening is that AMD drivers are not correctly storing voltage settings. The drivers seem to re-apply the default voltages when switching between power states, when primary display is turned off, resolution is changed, and potentially going in and out of exclusive fullscreen.

Once the voltages are reset, all tools (wattman, overdriventool) still display the voltages as the user defined settings. To get the voltages back down, I must either increase, or decrease mV slightly, then return back to preferred setting.


A possible solution could be to have claymore dual miner check every minute or so, and if needed automatically re-apply cvddc and mvddc with a +/- 1 mV. My past experience using cvddc is that it sets only once when the miner is first launched and never tries to re-apply if settings have changed.

Something crucial is missing in your explanation...
How do you know that voltage resets when the same voltage is displayed?

[mamedesign]

Anyone use R9 290/290x/390/390x have tasted new driver from AMD ? Please show the hashrate with this new driver ?

[cdrx]

Upgraded to the latest beta driver with mining fix while coming from 17.5.2. Like others, I'm having some issues with voltages returning to default. Running Windows 10, mix 470/480/580.

I've read various posts relating to voltages not staying set, and I figured I'd add my own experiences in hopes of finding a workaround/solution.

What I see happening is that AMD drivers are not correctly storing voltage settings. The drivers seem to re-apply the default voltages when switching between power states, when primary display is turned off, resolution is changed, and potentially going in and out of exclusive fullscreen.

Once the voltages are reset, all tools (wattman, overdriventool) still display the voltages as the user defined settings. To get the voltages back down, I must either increase, or decrease mV slightly, then return back to preferred setting.


A possible solution could be to have claymore dual miner check every minute or so, and if needed automatically re-apply cvddc and mvddc with a +/- 1 mV. My past experience using cvddc is that it sets only once when the miner is first launched and never tries to re-apply if settings have changed.

Something crucial is missing in your explanation...
How do you know that voltage resets when the same voltage is displayed?

you can see it in HWiNFO64 or on the wall.

[marimach77]

-cvddc   set target GPU core voltage, multiplied by 1000. For example, "-cvddc 1050" means 1.05V. You can also specify values for every card, for example "-cvddc 900,950,1000,970". Supports latest AMD 4xx cards only in Windows.
   Note: for NVIDIA cards this option is not supported.

-mvddc   set target GPU memory voltage, multiplied by 1000. For example, "-mvddc 1050" means 1.05V. You can also specify values for every card, for example "-mvddc 900,950,1000,970". Supports latest AMD 4xx cards only in Windows.
   Note: for NVIDIA cards this option is not supported.

Hi Claymore, is there any chance to have both parameters working for AMD RX 5xx cards in the next miner release?

[chup]

I've checked Win10 + RX480, it seems it works, I see voltage changes in WattMan if I restart it. ADL does not report any errors.

Just to be clear:

Claymore 9.8, running on Win10 + AMD Blockchain drivers can overclock and underclock all parameters for the RX480?

my 480 refs and various 470 are doing fine.

Why You're setting voltages through config-file beside Your claim that You have already set them in BIOS? You know that You are making confusion, is it with intention?

[TechPark]

I've checked Win10 + RX480, it seems it works, I see voltage changes in WattMan if I restart it. ADL does not report any errors.

Just to be clear:

Claymore 9.8, running on Win10 + AMD Blockchain drivers can overclock and underclock all parameters for the RX480?

my 480 refs and various 470 are doing fine.

Why You're setting voltages through config-file beside Your claim that You have already set them in BIOS? You know that You are making confusion, is it with intention?

You can do both.
EG: configure some base line in BIOS and do fine tuning later via config file.
The result only matters, is not it?  Whatever works for you...

[chup]

I've checked Win10 + RX480, it seems it works, I see voltage changes in WattMan if I restart it. ADL does not report any errors.

Just to be clear:

Claymore 9.8, running on Win10 + AMD Blockchain drivers can overclock and underclock all parameters for the RX480?

my 480 refs and various 470 are doing fine.

Why You're setting voltages through config-file beside Your claim that You have already set them in BIOS? You know that You are making confusion, is it with intention?

You can do both.
EG: configure some base line in BIOS and do fine tuning later via config file.
The result only matters, is not it?  Whatever works for you...

I'm talking about confusion between readers of the post. Obviously voltage setting through Claymore miner is not working with beta mining drivers, Ursul0 is posting screenshot claiming that it works for him. Truth is that he had voltages set in GPU BIOS...

[kkourmousis]

I am not very comfortable with the idea of messing with the voltages in GPU BIOS.

So much that I would rather wait for a new miner version that can twist those voltages