No need water cooling for 3900x. I used one Thermalright 140 with two fans, and one with stock cooler but with a $10 fan pointing at the rig. Both of them are around 12k at around 70c. I set the cpus running at 4G around 1.2v.
|
|
|
Well my 3900x can't reach 12k h/s. Does it have to use 3600 ram? my 3900x @.38 g with 3200 ram gets only 11400 on a vii hero, another @4.0g with 2400 ram get the same but on a cheap gigabyte ab350. really strange.
|
|
|
my 3900x can't reach 12k h/s. Does it have to use 3600 ram? my 3900x @.38 g with 3200 ram gets only 11400 on a vii hero, another @4.0g with 2400 ram get the same but on a cheap gigabyte ab350. really strange.
|
|
|
Interesting. I am using xmrig to mine Loki now with a 3900x amd chip. It seemed i can't make it run in full steam. It is running at 3.8G while when mining XMR it is 4G. And the speed is only 9000h.
Anyone has idea how to config it?
|
|
|
Oh man. I did not really calculate before seeing your question. Now after I did that, it is 42 cents NEGATIVE... I need to find a better way to mine. Any idea? And thanks for the question! So I bought a 3900x from bestbuy as well and got it yesterday. I then installed it on my gigabyte ab350 gaming 3 mobo with its own AMD cooler. LOL. Very excited that it can run on such an old board.
So it is mining AEON now with 70c temp. What is the best way to utilize its power in mining now? Any ideas?
what does aeon earn for you?
|
|
|
So I bought a 3900x from bestbuy as well and got it yesterday. I then installed it on my gigabyte ab350 gaming 3 mobo with its own AMD cooler. LOL. Very excited that it can run on such an old board.
So it is mining AEON now with 70c temp. What is the best way to utilize its power in mining now? Any ideas?
|
|
|
I am now mining Monero using a vega 56 rig. With new xmr algo planning to roll out in coming Oct., GPU mining for Monero is inefficient so I am going to stop mining it using GPU. But the problem is, what can I mine now with the vega rig?
|
|
|
No windows update in my case. Weird.  Thanks Doc. The first thing I did is ddu and reinstalled the driver. No go. Thanks Doc. It has been working for weeks. Yesterday it stopped working and I rebooted the box. The miner started to be like that. My other miners are using the same software and same config. All are just fine. SRBMiner-CN.exe --enablecoinforking --config Config\config-litev7.txt --pools pools.txt --logfile %LOGTIME%
Try without the --enablecoinforking parameter, maybe that's causing the issue. Interesting, then i guess it isn't that parameter that causes the issue, but maybe windows pulled some driver update. To be sure that's not the case you could do a quick DDU and driver reinstall. Got the same issue. Noone cn miner works. Seems like its windows update related, but even uninstall last updates wont help :/
|
|
|
Thanks Doc. The first thing I did is ddu and reinstalled the driver. No go. Thanks Doc. It has been working for weeks. Yesterday it stopped working and I rebooted the box. The miner started to be like that. My other miners are using the same software and same config. All are just fine. SRBMiner-CN.exe --enablecoinforking --config Config\config-litev7.txt --pools pools.txt --logfile %LOGTIME%
Try without the --enablecoinforking parameter, maybe that's causing the issue. Interesting, then i guess it isn't that parameter that causes the issue, but maybe windows pulled some driver update. To be sure that's not the case you could do a quick DDU and driver reinstall.
|
|
|
Thanks Doc. It has been working for weeks. Yesterday it stopped working and I rebooted the box. The miner started to be like that. My other miners are using the same software and same config. All are just fine. SRBMiner-CN.exe --enablecoinforking --config Config\config-litev7.txt --pools pools.txt --logfile %LOGTIME%
Try without the --enablecoinforking parameter, maybe that's causing the issue.
|
|
|
Hi Doc, here is the start.bat file. setx GPU_MAX_HEAP_SIZE 100 setx GPU_MAX_USE_SYNC_OBJECTS 1 setx GPU_SINGLE_ALLOC_PERCENT 100 setx GPU_MAX_ALLOC_PERCENT 100 setx GPU_MAX_SINGLE_ALLOC_PERCENT 100 @echo off cd %~dp0 cls for /f "tokens=2 delims==" %%a in ('wmic OS Get localdatetime /value') do set "dt=%%a" set LOGTIME=%dt:~0,4%_%dt:~4,2%_%dt:~6,2%_%dt:~8,2%_%dt:~10,2%_%dt:~12,2% set LOGTIME=%LOGTIME: =% set LOGTIME=%LOGTIME:,=.%.txt SRBMiner-CN.exe --enablecoinforking --config Config\config-litev7.txt --pools pools.txt --logfile %LOGTIME% I have the same issue. Tried to reinstall the driver and the same result. The mb looks ok and everything runs and recognized. Any idea what is going on? Hello,
I'm knew to SRB miner and I'm having some difficulty. I followed instructions in the guide and can only manage to get.
Enumerating OpenCL devices, please wait...
Restarting miner...
Enumerating OpenCL devices, please wait...
Restarting miner...
Enumerating OpenCL devices, please wait...
Restarting miner...
Times infinity. I'm using the generic guided set up with V1.8.9 and 8.6.1 for my vegas. I'm not sure what else to add, any advice?
Try reinstalling the drivers using DDU. Otherwise, it might be an indication of a faulty motherboard. Show me your start.bat file
|
|
|
I have the same issue. Tried to reinstall the driver and the same result. The mb looks ok and everything runs and recognized. Any idea what is going on? Hello,
I'm knew to SRB miner and I'm having some difficulty. I followed instructions in the guide and can only manage to get.
Enumerating OpenCL devices, please wait...
Restarting miner...
Enumerating OpenCL devices, please wait...
Restarting miner...
Enumerating OpenCL devices, please wait...
Restarting miner...
Times infinity. I'm using the generic guided set up with V1.8.9 and 8.6.1 for my vegas. I'm not sure what else to add, any advice?
Try reinstalling the drivers using DDU. Otherwise, it might be an indication of a faulty motherboard.
|
|
|
Hi Doc. Any idea what is the problem for the above message? I am using the right algo as you can see. Normal v4
|
|
|
some weird result on 1.8.8
GPU0: Radeon RX 570 Series [ellesmere] [4096 MB][I: 59.0][W: 16][T: 2][F: 8][BUS: 1] GPU1: Radeon RX 570 Series [ellesmere] [4096 MB][I: 59.0][W: 16][T: 2][F: 8][BUS: 30] GPU2: Radeon RX 570 Series [ellesmere] [4096 MB][I: 59.0][W: 16][T: 2][F: 8][BUS: 31] GPU3: Radeon RX 570 Series [ellesmere] [4096 MB][I: 59.0][W: 16][T: 2][F: 8][BUS: 34] GPU4: Radeon RX 570 Series [ellesmere] [4096 MB][I: 59.0][W: 16][T: 2][F: 8][BUS: 35] GPU5: Radeon RX 570 Series [ellesmere] [4096 MB][I: 59.0][W: 16][T: 2][F: 8][BUS: 38]
-------------------------------------------------------------------------------------- SRBMiner Cryptonight AMD GPU miner 1.8.8 DevFee ~0.85%
Press 's' to display stats Press 'h' to display hashrate Press 'r' to reload pools Press 'p' to switch to the next pool Press 'o' to switch to the previous pool Press 0-9 to disable/enable GPU 0-9, shift+0-9 for GPU 10-19 --------------------------------------------------------------------------------------
Recommended drivers : Adrenalin 18.6.1 or Adrenalin 2019 Algorithm : Cryptonight V4 (R) Algo switching : enabled Coin forking : enabled Gpu watchdog : enabled [normal mode] Startup monitor : enabled Tweaking : disabled
[2019-05-27 19:43:41] Pools defined -> 2 [2019-05-27 19:43:41] Please run miner as administrator to enable tweaking [2019-05-27 19:43:42] Compiling [normalv4] kernel for DEVICE BUS_ID[1] [2019-05-27 19:43:46] Loading [normalv4] kernel for DEVICE BUS_ID[1] [2019-05-27 19:43:46] Loading [normalv4] kernel for DEVICE BUS_ID[30] [2019-05-27 19:43:46] Loading [normalv4] kernel for DEVICE BUS_ID[30] [2019-05-27 19:43:47] Loading [normalv4] kernel for DEVICE BUS_ID[31] [2019-05-27 19:43:47] Loading [normalv4] kernel for DEVICE BUS_ID[31] [2019-05-27 19:43:48] Loading [normalv4] kernel for DEVICE BUS_ID[34] [2019-05-27 19:43:48] Loading [normalv4] kernel for DEVICE BUS_ID[34] [2019-05-27 19:43:49] Loading [normalv4] kernel for DEVICE BUS_ID[35] [2019-05-27 19:43:49] Loading [normalv4] kernel for DEVICE BUS_ID[35] [2019-05-27 19:43:50] Loading [normalv4] kernel for DEVICE BUS_ID[38] [2019-05-27 19:43:50] Loading [normalv4] kernel for DEVICE BUS_ID[38] [2019-05-27 19:43:50] ADL initialised successfully [2019-05-27 19:43:51] Connected to pool.supportxmr.com:7777 [2019-05-27 19:43:51] Pool difficulty: 40000 [2019-05-27 19:43:51] Pool sent a new job, block height 1844209 [ID: Qmj+TM6O22XoHgb5LSYc1TqLJrQm] [normalv4] [2019-05-27 19:43:51] Precompiling program [BUS:1] [2019-05-27 19:44:04] Pool sent a new job, block height 1844210 [ID: PLArP+CMDHmAblPA0AoEGE9AGIu0] [normalv4] [2019-05-27 19:44:05] Finished program precompilation [BUS:1] [2019-05-27 19:44:05] Precompiling program [BUS:30] [2019-05-27 19:44:20] Finished program precompilation [BUS:30] [2019-05-27 19:44:20] Precompiling program [BUS:34] [2019-05-27 19:44:29] Pool difficulty: 40001 [2019-05-27 19:44:29] GPU1[BUS:30] result rejected for job[2] [low difficulty share] [2019-05-27 19:44:35] Finished program precompilation [BUS:34] [2019-05-27 19:44:35] Precompiling program [BUS:31] [2019-05-27 19:44:50] Finished program precompilation [BUS:31] [2019-05-27 19:44:50] Precompiling program [BUS:38] [2019-05-27 19:44:55] GPU0[BUS:1] result rejected for job[2] [low difficulty share] [2019-05-27 19:45:01] GPU3[BUS:34] result rejected for job[2] [low difficulty share] [2019-05-27 19:45:04] Finished program precompilation [BUS:38] [2019-05-27 19:45:04] Precompiling program [BUS:35] [2019-05-27 19:45:08] GPU3[BUS:34] result rejected for job[2] [invalid job id] [2019-05-27 19:45:14] GPU0[BUS:1] result rejected for job[2] [invalid job id] [2019-05-27 19:45:16] GPU1[BUS:30] result rejected for job[2] [invalid job id] [2019-05-27 19:45:19] Finished program precompilation [BUS:35] [2019-05-27 19:45:19] Pool sent a new job, block height 1844210 [ID: uSxHgoDQ+6OTzv8/aSVByu4u+Ek/] [normalv4] [2019-05-27 19:45:19] Pool difficulty: 21622 [2019-05-27 19:46:06] Pool difficulty: 21621 [2019-05-27 19:46:06] Pool sent a new job, block height 1844212 [ID: geRjmtGOjG9dU+3htvcv68e88nvQ] [normalv4] [2019-05-27 19:46:06] GPU4[BUS:35] result rejected for job[11] [low difficulty share] [2019-05-27 19:46:11] Pool difficulty: 21622 [2019-05-27 19:46:11] Pool sent a new job, block height 1844212 [ID: OP1sZcF7d35n33QkX7XBrBke8tC8] [normalv4] [2019-05-27 19:46:12] GPU2[BUS:31] result rejected for job[12] [low difficulty share] [2019-05-27 19:46:12] Pool difficulty: 14415 [2019-05-27 19:46:14] GPU1[BUS:30] result rejected for job[12] [low difficulty share] [2019-05-27 19:46:16] GPU0[BUS:1] result rejected for job[12] [low difficulty share] [2019-05-27 19:46:18] Pool sent a new job, block height 1844212 [ID: WcNRYrKmgUF15IT9/zk6QuhPQiyS] [normalv4] [2019-05-27 19:46:18] GPU1[BUS:30] result rejected for job[13] [low difficulty share] [2019-05-27 19:46:18] Pool difficulty: 14414 [2019-05-27 19:46:22] Pool sent a new job, block height 1844212 [ID: 1JeUETe3pNhJeBG0tCPMF6QKPbel] [normalv4] [2019-05-27 19:46:25] Pool sent a new job, block height 1844212 [ID: oTPhwy4OxZveAUZqJ/LRkO6YHDhp] [normalv4] [2019-05-27 19:46:29] Pool sent a new job, block height 1844212 [ID: G3cF+wAg6lmPK3WFjYEe+xPhS3wG] [normalv4] [2019-05-27 19:46:32] Pool difficulty: 14415 [2019-05-27 19:46:32] GPU2[BUS:31] result rejected for job[16] [low difficulty share] [2019-05-27 19:46:32] GPU4[BUS:35] result rejected for job[16] [low difficulty share]
|
|
|
Hi there,
I have a rig with mixed 480 and 580. I used command like:
teamredminer.exe -a cnr -o stratum+tcp://pool.supportxmr.com:7777 -u 84PDXS6PngdBh2XUd28jbN3Sb69RXPq7gdCNVukcrFCj1v6jgb13uEpHrzf6DF9cDjKCToaS842gLx8 sgF1jNCNGfuFgi -p amd:cryptocoins@outlook.com -d 0,1,2,3,4,5 --cn_config 8+8,8+8,8+8,8+8,8+8,8+8
Here is what I got:
Team Red Miner version 0.4.2 [2019-03-17 16:37:13] Auto-detected AMD OpenCL platform 0 [2019-03-17 16:37:20] Initializing GPU 0. [2019-03-17 16:37:20] Watchdog thread starting. ... [2019-03-17 16:39:20] GPU 5: detected DEAD (35:00.0), no restart script configured, will continue mining. [2019-03-17 16:39:20] Please use command line argument --watchdog_script to handle dead GPUs.
Have you read any other posts?? If you had you would realise 8+8 is to high for those cards. Also it always pays to try a few different settings yourself some times. Try 8+7 or 7+7 or 6+6 ........... Yes, init is failing. Another potential issue (that we should document better) is concurrent cpu mining. If you're cpu mining while starting the miner, please stop cpu mining and start the miner. Once the miner is running, you can safely start parallel cpu mining again, it's just very sensitive during startup. This is an unfortunate side-effect of having a different initialization process than other miners. Indeed that is the issue. I stopped the cpu mining and run the start again and everything works fine now. Thanks for the information and please document this.
|
|
|
Hi there,
I have a rig with mixed 480 and 580. I used command like:
teamredminer.exe -a cnr -o stratum+tcp://pool.supportxmr.com:7777 -u 84PDXS6PngdBh2XUd28jbN3Sb69RXPq7gdCNVukcrFCj1v6jgb13uEpHrzf6DF9cDjKCToaS842gLx8 sgF1jNCNGfuFgi -p amd:cryptocoins@outlook.com -d 0,1,2,3,4,5 --cn_config 8+8,8+8,8+8,8+8,8+8,8+8
Here is what I got:
Team Red Miner version 0.4.2 [2019-03-17 16:37:13] Auto-detected AMD OpenCL platform 0 [2019-03-17 16:37:20] Initializing GPU 0. [2019-03-17 16:37:20] Watchdog thread starting. [2019-03-17 16:37:20] Pool pool.supportxmr.com connecting to address 104.140.201.62. [2019-03-17 16:37:20] Pool pool.supportxmr.com successfully connected to address 104.140.201.62. [2019-03-17 16:37:20] Pool pool.supportxmr.com login succeeded.(76 ms) [2019-03-17 16:37:20] Pool pool.supportxmr.com received new job. (job_id: cnLOlcrewGdcVf1XzQRbdhjwp1Vb) [2019-03-17 16:37:20] Pool pool.supportxmr.com set difficulty to 40000 [2019-03-17 16:37:21] Dev pool connected and ready. [2019-03-17 16:37:25] Pool pool.supportxmr.com received new job. (job_id: XIB96CLjgQdVKYBbNUaRktOh8rcO) [2019-03-17 16:37:25] Pool pool.supportxmr.com set difficulty to 68571 [2019-03-17 16:37:50] Stats Uptime: 0 days, 00:00:32 [2019-03-17 16:37:50] GPU 0 [30C, fan 55%] cnr: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0 [2019-03-17 16:37:50] GPU 1 [28C, fan 55%] cnr: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0 [2019-03-17 16:37:50] GPU 2 [29C, fan 55%] cnr: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0 [2019-03-17 16:37:50] GPU 3 [29C, fan 55%] cnr: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0 [2019-03-17 16:37:50] GPU 4 [28C, fan 55%] cnr: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0 [2019-03-17 16:37:50] GPU 5 [23C, fan 55%] cnr: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0 [2019-03-17 16:37:50] Total cnr: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0 [2019-03-17 16:38:20] Stats Uptime: 0 days, 00:01:02 [2019-03-17 16:38:20] GPU 0 [29C, fan 55%] cnr: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0 [2019-03-17 16:38:20] GPU 1 [27C, fan 55%] cnr: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0 [2019-03-17 16:38:20] GPU 2 [29C, fan 55%] cnr: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0 [2019-03-17 16:38:20] GPU 3 [28C, fan 55%] cnr: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0 [2019-03-17 16:38:20] GPU 4 [28C, fan 55%] cnr: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0 [2019-03-17 16:38:20] GPU 5 [23C, fan 55%] cnr: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0 [2019-03-17 16:38:20] Total cnr: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0 [2019-03-17 16:38:25] Pool pool.supportxmr.com received new job. (job_id: i5dMQvSKsNVfeMp9FbvfyScUpeu5) [2019-03-17 16:38:25] Pool pool.supportxmr.com set difficulty to 45714 [2019-03-17 16:38:50] Stats Uptime: 0 days, 00:01:32 [2019-03-17 16:38:50] GPU 0 [29C, fan 55%] cnr: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0 [2019-03-17 16:38:50] GPU 1 [27C, fan 55%] cnr: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0 [2019-03-17 16:38:50] GPU 2 [29C, fan 55%] cnr: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0 [2019-03-17 16:38:50] GPU 3 [28C, fan 55%] cnr: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0 [2019-03-17 16:38:50] GPU 4 [27C, fan 55%] cnr: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0 [2019-03-17 16:38:50] GPU 5 [23C, fan 55%] cnr: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0 [2019-03-17 16:38:50] Total cnr: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0 [2019-03-17 16:39:10] GPU 0: detected DEAD (34:00.0), no restart script configured, will continue mining. [2019-03-17 16:39:10] Please use command line argument --watchdog_script to handle dead GPUs. [2019-03-17 16:39:10] GPU 1: detected DEAD (30:00.0), no restart script configured, will continue mining. [2019-03-17 16:39:10] Please use command line argument --watchdog_script to handle dead GPUs. [2019-03-17 16:39:10] GPU 2: detected DEAD (31:00.0), no restart script configured, will continue mining. [2019-03-17 16:39:10] Please use command line argument --watchdog_script to handle dead GPUs. [2019-03-17 16:39:10] GPU 3: detected DEAD (38:00.0), no restart script configured, will continue mining. [2019-03-17 16:39:10] Please use command line argument --watchdog_script to handle dead GPUs. [2019-03-17 16:39:10] GPU 4: detected DEAD (01:00.0), no restart script configured, will continue mining. [2019-03-17 16:39:10] Please use command line argument --watchdog_script to handle dead GPUs. [2019-03-17 16:39:10] GPU 5: detected DEAD (35:00.0), no restart script configured, will continue mining. [2019-03-17 16:39:10] Please use command line argument --watchdog_script to handle dead GPUs. [2019-03-17 16:39:20] Stats Uptime: 0 days, 00:02:02 [2019-03-17 16:39:20] GPU 0 [29C, fan 55%] cnr: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0 [2019-03-17 16:39:20] GPU 1 [27C, fan 55%] cnr: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0 [2019-03-17 16:39:20] GPU 0: detected DEAD (34:00.0), no restart script configured, will continue mining. [2019-03-17 16:39:20] Please use command line argument --watchdog_script to handle dead GPUs. [2019-03-17 16:39:20] GPU 1: detected DEAD (30:00.0), no restart script configured, will continue mining. [2019-03-17 16:39:20] Please use command line argument --watchdog_script to handle dead GPUs. [2019-03-17 16:39:20] GPU 2: detected DEAD (31:00.0), no restart script configured, will continue mining. [2019-03-17 16:39:20] Please use command line argument --watchdog_script to handle dead GPUs. [2019-03-17 16:39:20] GPU 3: detected DEAD (38:00.0), no restart script configured, will continue mining. [2019-03-17 16:39:20] Please use command line argument --watchdog_script to handle dead GPUs. [2019-03-17 16:39:20] GPU 4: detected DEAD (01:00.0), no restart script configured, will continue mining. [2019-03-17 16:39:20] Please use command line argument --watchdog_script to handle dead GPUs. [2019-03-17 16:39:20] GPU 5: detected DEAD (35:00.0), no restart script configured, will continue mining. [2019-03-17 16:39:20] Please use command line argument --watchdog_script to handle dead GPUs.
|
|
|
I woke up this morning found all my rigs has 0 hash rate and miners keep restarting. I changed the commands from normalv8 to normalv4 and everything back to normal. Anyone has similar issues please try this.
SRBMiner-CN.exe --enablecoinforking --config Config\config-normalv4.txt --pools pools.txt --logfile %LOGTIME%
|
|
|
ok so I tried again with default setting and no overclock. Still no go. Same errors. I used 1.7.0 before. So I just copied pool.txt and start.bat to new 1.7.9 folder. Is there anything else I need to do? Seemed I missed something. Come on. They have been working for years now with new algo we have to clock down? Did anyone have similar issue?
reduce memory clock or add power to memory yes. before i fck my wife 2-3 time on day but now i dont  mybe your GPU dirty. - new card have beter hr. old card have lower and have high temperature. new CAR work fine but old CAR dont work fine and you must old CAR drive litle slowly or machine die. comput eror = so high memory clock and to low power. reduce clock and try. example my card have many compute error- 30 in hour on 1100mhz 900mv but on 1098mhz 900mv dont have any compute error in 1 day
|
|
|
Come on. They have been working for years now with new algo we have to clock down? Did anyone have similar issue?
reduce memory clock or add power to memory
|
|
|
|