Bitcoin Forum

Alternate cryptocurrencies => Mining (Altcoins) => Topic started by: Amstellodamois on February 05, 2018, 07:34:44 PM



Title: Weird glitch (AMD + OverdriveNTool + Claymore's)
Post by: Amstellodamois on February 05, 2018, 07:34:44 PM
Weirdly, when I make setting changes in OverdriveNTool, they do not improve my hashrate (Claymore) until I restart the whole rig.
If I just restart the miner, I doesn't work.

Same when something happens and the driver reverts back to default settings on one card, that card will only do 28 MH/s until I restart windows, no matter what settings change or profile loading I do with OverdriveNTool).
Same thing happens if I relauch a Calymore's instance with the clock & vcc in the command line: I can see on GPUz or OverdriveNTool that the settings are applied but the card is stuck at 28 MH/s.


That's a bit time consuming. Anyone has a workaround?


Title: Re: Weird glitch (AMD + OverdriveNTool + Claymore's)
Post by: Amstellodamois on February 06, 2018, 01:11:31 PM
No one?


Title: Re: Weird glitch (AMD + OverdriveNTool + Claymore's)
Post by: Rho_Hotel_Yankee on February 07, 2018, 02:43:46 PM
I have had the same issue with OverdriveNToll and Claymore.  I can even watch the cclocks and mclocks in HiWinFo64 change, but there is no change in hashrate until I restart the rig.  For me, this problem developed suddenly and was not present when I first built the rig.  Indeed, this does make optimizing a card a real pain.  What kind of cards are you running?  It happens to me with RX580s with Elpida memory (blockchain drivers) on Windows 10 using Claymore 10.3. 


Title: Re: Weird glitch (AMD + OverdriveNTool + Claymore's)
Post by: dohfish on February 07, 2018, 03:10:21 PM
This is because there's no monitor attached - There's no way around that without plugging a monitor into each one after the rig has been started up :)


Title: Re: Weird glitch (AMD + OverdriveNTool + Claymore's)
Post by: mshordja on February 07, 2018, 03:16:15 PM
This is because there's no monitor attached - There's no way around that without plugging a monitor into each one after the rig has been started up :)
Exist any type of software that make windows believe that is a monitor attached, i make some search but nothing, or the best solution is to get dummy hdmi? 


Title: Re: Weird glitch (AMD + OverdriveNTool + Claymore's)
Post by: Amstellodamois on February 07, 2018, 03:54:42 PM
For me, this problem developed suddenly and was not present when I first built the rig.
This.

Quote
What kind of cards are you running?  It happens to me with RX580s with Elpida memory (blockchain drivers) on Windows 10 using Claymore 10.3. 
RX 580, Hynix. There: https://bitcointalk.org/index.php?topic=2896991.msg29792631;topicseen#new

This is because there's no monitor attached - There's no way around that without plugging a monitor into each one after the rig has been started up :)
Exist any type of software that make windows believe that is a monitor attached, i make some search but nothing, or the best solution is to get dummy hdmi? 
I've looked for days and couldn't find a software solution. I have an HDMI dummy plugged into the onboard graphics.

But I don't see how the two could be related ???