Similar issue with me.
Couple of weeks ago I started overclocking with overdriventool, with very little success. When I overclock, I can see the values are applied through GPUz, but no hash increase. Very strange. It worked once actually but only once. I had to restart the rig, and never managed to get those speeds again. BTW I worked with both HDMI dummy and screen connected (not at the same time of course).
Now I’m not getting even that far. As soon as I overclock, and run the claymore, the system crashes. With Adrenalin drivers I would get TDR BSOD error, and with block chain drivers I would get thread-stuck-in-device-driver BSOD error.
My overclock is a very modest one, not pushing the evnelope here.
The rig has Polaris one click modded BIOS and is rock solid running stock.
Any advice would be appreciated.
win 10, all the latest updates, .net 3.5 installed, claymore 10.6, 5x rx570 4gb Elpida mem, PSU not an issue.
Topic: Weird glitch (AMD + OverdriveNTool + Claymore's) (Read 294 times)
For me, this problem developed suddenly and was not present when I first built the rig.
This.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? But I don't see how the two could be related
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?
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
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.
No one?
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?
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?
Jump to: