I see huge influx of people here and some are way more clueless then the others...
so here some tips for you there, mining with Polarises on Win10:

1. make sure you have sufficient power on your PSU(10-20% spare from the peaks)
Note: properly configured polaris should be just below 150W on dual ETH
2. molex power to raisers is probably the most common point of failure (bad/unstable hash, card disconnects, crashes, and such)
Note: it seems there's no such thing as bad raiser, only bad contacts in power connectors
3. disable all you can via Group Policy, especially windows update and drivers update
4. use latest DDU and install 17.11.1 driver, pointing manually from Device Manager to the dir with unzipped driver
Note: Do not use blockchain beta driver as it has some issues with latest API and also doesn't support more than 8 AMD GPUs
5. set compute mode for all GPUs. here's the example for dev0 (special thanks to @ober for that):
6. Flash bios mods with tighter straps. Look for PolarisEditor v164 with "one click modify" bios timings and use atiflash without gui
7. Use overdriven tool (RX5* Polarises normally do well on 1180 & 1950-2150 @ 850mv, RX4* may need lower core freq)
Note: do not use AB.
Note: do not use claymore for core&mem&fans control
8. Use sysinternals autologon and built-in MS task scheduler
9. make reboot.bat and set "-r 1", as restarting miner most likely will NOT work

Bonus:
* I'm using RealVNC for remote access - flawless
* you may find useful: display dummy dongles and usb watchdogs
* and as always openVPN is your friend

If I just made your life easier and increased your profits PM me and I'll give you my ETH address:)
...or you can just find it in my profile yourself

hi guys,

still experiencing the same issue. claymore refuses to set clock, core and voltage settings on my gigabyte aorus 580 xtr cards. i have to use afterburner which isnt reliable. every now and then my cards default to normal clock settings which affects the hashrate and power use.

Any ideas why this might be the case?

running win 10 pro, and claymore 10.2.

Thanks

Thanks mate,

Have just tried radeon adrenaline 17.12.1 with compute setting on. without afterburner installed, claymore's doesnt change any settings now. including mem/core clock speeds? i tried 17.11.1 initially, however i was getting about 6mh lower than with the blockchain drivers.

Thanks

Hi,

Im running 2 x gigabyte rx 580 xtr 8gb oc cards, and have noticed the variables passed to claymore dont take effect on the second card. Is this common?

For example, ive tried this line (assuming same values should be applied to all cards?)
 
-cclock 1200 -mclock 2200 -cvddc 900 -mvddc 900

then tried this

-cclock 1200,1200 -mclock 2200,2200 -cvddc 900,900 -mvddc 900,900 (to assign each card specifically) and same thing happens both times.

My primary card gets the values set, but secondary just uses the default or the afterburner settings

Im mining dual eth + decred, tried claymore 10.1 and 10.2, win10 machine, and radeon driver - Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23

Any ideas on what it might be?

Hey mate,

Since you are reading for such a long time you must have read my post - chain, where (in my final post) I concluded that the blockchain drivers can cause power spikes that cause great instability.

Mr. Claymore said on this:


So there you have it.

Reducing voltage indeed does the trick on system freezes.
I myself had to lower my clocks as well with the voltage, sacrificing some hashrate in order to have stability

Since building my first rig last June, i've always had this rock-stable settings for six of my Asus Dual OC 580s 8GB Samsung memory

-cclock 1260
-mclock 2050
-cvddc 925mV
-mvddc 925mV

This yields me a constant 29.1 to 29.3 across all cards (175 total) and pulls about 1175 up to 1200w. High, I know but they go for weeks until needing a restart.

Earlier this week, I played with them again to squeeze in few more Mh. These are my settings:
-cclock 1140
-mclock 2075
-cvddc 875
-mvddc 875

They average a total of 177.5 now and cards hashes from 29.5 up to 30.0. But the best thing is they now only pull 1035w dual-mining with DCR.