Or run it with SRBMiner-CN.exe --benchmarkalgos --disablestartupmonitor

Thank you for the reply.

The missing gpu is a RX580.
GPU0 is intel HD and if I set --auto without using the -g option, it will try to mine with gpu 0,1,2,3,4 (that is intel graphics + 4 RX580) and gives a known opencl error because you can't mine on an intel HD graphics. GPU5 is listed but it doesn't start any thread for it. Using -c config.txt and specifying the 5 gpu's works as intended.
This is on a Asus z270-p with intel G4560 cpu and windows 10 ltsb (version 1607), jce_cn_gpu_miner.033b6
I have the intel graphics enabled so that the windows dwm.exe process doesn't allocate video memory on any rx580. Without it, I have to reduce intensity on the main gpu or the system lags and BSOD's

Hello

I found a bug with the new startup monitor option
If you run benchmark-algos.bat, the startup monitor will kick in and restart the miner every 120seconds and the benchmark never finishes
The .bat file needs "--disablestartupmonitor" OR make sure that "--benchmarkalgos" always disables all watchdogs
edit: one more! benchmark-algos doesn't benchmark "dark" nor "festival"

Well, I've had some spare time today and I'm testing this again.
Seems like the information you gave me is only valid for CPU mining. I'm using GPU mining and there is no information on the wiki
The wiki tells me to use --variation 16 for moneroocean, but it's an invalid value for the GPU miner so I just omit the value, and _cpu_threads_conf is not meant to be used on a gpu mining rig so I'm using --auto
Couldn't you just merge both versions in a gpu+cpu mining with the same features and maintain only one miner? Because the gpu miner also does cpu mining, but the wiki is missing information. Also you have so many .bat files and .txt, just keep it simple and put examples and all documentation inside the readme.txt for a clean and easy way to upgrade and access the documentation.
I've also experienced some bugs: For example, on the gpu miner, there's no information on how to use the gpu temperature monitoring. It always reports 0ºC (driver 18.6.1, windows 10 ltsb, no display connected to amd gpus). For some reason, --auto only runs on 4 of my 5 gpus, one is idle unless I configure it on config.txt (I have 5 RX580 4GB and 1 IGP, i've set -g 1,2,3,4,5 and it mines on 1,2,3,4)
Don't get me wrong, I've tested many miners and I would like to start using yours, but it needs some improvements before I can join. I'll keep on checking the changelogs

Hmm, I was reading the cn_gpu_miner github page and that info is missing from there. My bad, didn't noticed that there are 2 projects
Thank you for your fast and kind reply. I'll look into it

Hello

I'm testing your miner on 5 rx580 4gb on moneroocean.
Since 0.33c you support "pool managed autoswitching" but it doesn't seems to work like the other miners
For example, I would like to set each algo performance so that the pool always mines the most profitable coin. Also, if I use the same config for the different algorithms, the miner will run out of memory (for example, cn8 intensity cant be used on a cn-heavy algo). It needs to support multiple configuration files or multiple algos on config.txt
Is this going to be implemented?

Just to let you guys know

I've enabled my onboard intel graphics and use it at the primary display and all my other discrete gpu's don't have any display connected to them
This reduced the VRAM usage from 200mb to 8mb on every AMD gpu. Only side effect is that you will need to uninstall all your AMD cards before installing the intel driver or you might not be able to boot to windows.
Lower vram usage means that you can increase the mining intensity and have slightly better hashing performance. It also increased stability and system responsiveness because windows doesn't use those gpu's for nothing more than mining and the display is now handled by the IGP. If any or all AMD gpus crash, you will still be able to reset the gpu clocks with overdriventool or reboot the system safely

Hope this helps someone

To the people with 0 kh or slowdowns/crashes.
Default intensity is too high. Windows dmw.exe uses almost 200mb of vram on the primary gpu and this miner tries to allocate the full 4GB / 8gb. For example you have 4.2gb of vram usage on a 4gb gpu and the system crashes or the miner fails at 0kh/s.
Solution: rollback to windows 7 and disable aero OR reduce default mining intensity by 2 or 3 points on the gpu that is using more vram (use GPU-Z or hwinfo32 to find out).
Please OP, tweak this miner so that it never tries to allocate more vram than that you have on your system. It should be possible to predict the mining intensity based on the available vram. I've spent hours tweaking the intensity settings and still can't get more than 3-4 hours uptime on a multi-algo pool.

I'm having severe stability issues with this miner on my rx580 4gb cards
Some algos select an intensity that is too high by default that uses more than 4gb of vram and causes the system to stall and reboot (lightv7 for example, defaults to 130? but 110 is the maxium, but on normalv7 it defaults to 55 and can be increased to 58 without issues).
But even after tweaking all config files, I can't never get a uptime of 6 hours, it always reboots without no log. I've reduced the ram from 2100 to 1960mhz, increased vcore, nothing helps. It just restarts the machine.
Sometimes I notice that 1 thread is randomly not running. I have 5 GPUs and you see 330 620 620 620 620 H/s on the logs (random example).
I used to have 1 month uptime with ETH mining (rebooted just to install security updates). Running on 10 LTSB with 18.6.1 drivers. I'm trying to debug this as best as I can because the profit is near 0€ per day, every second of downtime is bad.

Suggestion: the configuration needs improvements because multiple files are a mess (if you need an API to monitor, you have to write that on every config file for every algo), default intensity needs tweaking, gpu watchdog could be reworked to search for failed threads instead of a failed gpu, on pools with multiple algos, the miner should first check the pool for the current algo being mined and then load the kernels (right now it loads normalv7 kernels, connects to pool, loads "correct" kernels).

Hello

I've been testing this on my 5x rx580 4gb (elpida) and so far so good
I'm having minor instability issues at 1230/2020mhz @ 915mv producing 930H/s for each card. I have some random restarts but i'll try to lower more the clock speed if this repeats. Mining eth was stable with much faster speeds, but it's a different algorithm so this is expected.
If you just started mining, make sure that you tweak the intensity setting. Using "58" instead of "55" for normalv7 algorithm improved my hashrate a bit.


Question @ admin
Is it possible to add the "api" configuration to the command line options instead of config.txt files? Because if you use multialgo switch, you have to configure the API settings on every config file.
Also, since you have ADL api enabled, can you provide a way to change the gpu/mem clock/voltage in your miner?

0.19$ portugal, mining is not profitable at the moment

You can only manage the miner. Like disabling gpus, increase fan speed, change pool, etc

Almost all questions that everyone is asking here could be avoided if they read the README file on claymore's miner folder. I find outstanding how is it possible that this people are mining and have not one single clue what they are doing

GT210 only has CUDA 6.5 support and not enough vram. It's not supported nor profitable.

With RX580, adrenaline is faster than the blockchain drivers (<1%, minimal gains on ETH). No idea about the vega's

Don't use the "blockchain beta" driver. It is already included on the latest AMD adrenaline drivers from amd.com/drivers. Please stop spreading old news!
-> go to amd.com/drivers and download the latest WHQL driver
-> open the adrenaline control panel and change the settings from GRAPHICS to COMPUTE mode for EACH AMD CARD that you have. Reboot and recheck if compute mode is still enabled
You should have more speed than using old blockchain driver that was created for testing purposes. Also it's the only driver that is fully compatible with windows 1803

If you are having problems with AMD and ULPS, install windows 10 LTSB 2016. It has a 10 year support without installing a new build every 6 months and absolutely 0 windows apps that use your system's resources while mining.
Because it's based on windows 1607, you won't have any issues that windows 1803 is causing. Just install and forget, forever

The etht parameter only works in solo mode. You are mining on a pool so that option does absolutely nothing!

False. That was a beta driver to test the compute mode functionality on amd drivers. It's now part of every newer driver.

I recommend that you use the latest WHQL driver (adrenaline 18.5.1) and make sure that you enable compute mode on the radeon settings and also use windows 10 LTSB for mining. If you are using windows 10 1803, make sure that you disable ULPS (check 3 or 4 posts before this one) or else you will have severe delays if you are running multiple amd gpu's.

Just to let you guys know, I'm testing AMD Adrenalin Drivers version 18.4.1 on my 5x rx580 rig and it's randomly doing 0mh/s and recovering to 31mh/s, even with increased voltage. Also I haven't noticed any performance improvement so, I recommend that everyone use the latest WHQL drivers with version 18.2.1. Those still provide the best performance and stability. Avoid upgrading to windows 1803 for now

I have my temperature target at 52ºC now that I'm mining eth only on rx580 (35% is the minimum fan speed possible) 1200mhz @ 875mv

GPU0 t=52C fan=35%, GPU1 t=51C fan=42%, GPU2 t=51C fan=35%, GPU3 t=51C fan=40%, GPU4 t=50C fan=34%

For 24/7, I would avoid having anything above 70ºC because of the known failure rates of amd gpu's