Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 36.

7anonminer7

newbie

Activity: 15

Merit: 0

Quote from: azza_ on July 30, 2020, 04:55:19 AM

update: First test shows that lowering memory speed and getting back to very old crimson beta driver helps for now, at the cost of 3-5% lower performance. Memory usage around 3,895 MB

HWinfo shows that old driver is using around 27-29 MB of dynamic D3D memory while new driver is using more then 130 MB, at least for me.

Can you please tell me which version of old Crimson beta driver are you using now? Will 17.11.4 do?

I too face 0MH/s with my RX570/470 4G since today on Windows 10, Adrenaline driver v19.20. Only monitor is connected to integrated mobo graphics (HDMI port), yet Windows still not allowing to allocate more than 3737 MB of VRAM (according to HWInfo). -eres 1 or 0 doesn't help, lowering GPUs' memory timings to 1700 (instead of ~2000) gives no change.

Metroid

sr. member

Activity: 2142

Merit: 353

Xtreme Monster

Quote from: dislorth on July 30, 2020, 04:53:26 PM

Quote from: Metroid on July 30, 2020, 03:49:23 PM

It seems claymore is done for if you have 4gb gpus at moment, PhoenixMiner still working with 4gb gpus but you need to know how to, lot of work, you will need to flash a new rom to make worthwhile.

I try to make it work Phoenixminer but you have to connect monitor to mobo video port so in case your mobo video port is a DVI port and you dont have a DVI monitor you can't do anything Undecided

GPU1 stops Phoenixminer and it just restarts mining over and over again... do you know if there is a command line to stop minig a selected GPU to fix this issue with Phoenixminer? Huh

The same as claymore, the command line is -di, if you write -di 01 that means gpu 0 and gpu 1, -di 18 (that means gpu 1 and gpu Cool

.

dislorth

jr. member

Activity: 48

Merit: 1

Quote from: Metroid on July 30, 2020, 03:49:23 PM

It seems claymore is done for if you have 4gb gpus at moment, PhoenixMiner still working with 4gb gpus but you need to know how to, lot of work, you will need to flash a new rom to make worthwhile.

I try to make it work Phoenixminer but you have to connect monitor to mobo video port so in case your mobo video port is a DVI port and you dont have a DVI monitor you can't do anything Undecided

GPU1 stops Phoenixminer and it just restarts mining over and over again... do you know if there is a command line to stop minig a selected GPU to fix this issue with Phoenixminer? Huh

Metroid

sr. member

Activity: 2142

Merit: 353

Xtreme Monster

It seems claymore is done for if you have 4gb gpus at moment, PhoenixMiner still working with 4gb gpus but you need to know how to, lot of work, you will need to flash a new rom to make worthwhile.

JFoxOne

member

Activity: 640

Merit: 56

minerstat

If you have 4GB GPUs and you are facing errors then read this guide - what to mine with 4GB GPUs.

- OpenCL error -38 - cannot write buffer for DAG
- Creating DAG buffer failed: clCreateBuffer: CL_INVALID_BUFFER_SIZE (-61)
- CUDA error in CudaProgram.cu:373 : out of memory (2)
- initMiner error: out of memory
- or any other similar error related to “DAG” and “memory”.

Hopefully Claymore miner gets updated soon.

tytanick

legendary

Activity: 2660

Merit: 1096

Simplemining.net Admin

Quote from: Prom_ZA on July 30, 2020, 11:17:10 AM

I keep getting "not enough GPU memory to place DAG, you cannot mine this coin with this GPU". This started with epoch 351. I reinstalled Linux and it disappeared until epoch 352 today. I thought it might be a bad disk as it's not functioning so well but it's still the same on a new one.

I don't have this problem on windows 10. The whole reason I switched to Linux was it has less problems and is supposed to mine for longer. This can't be a memory problem as it's still mineable with over 250MB free. Also if the DAG size was the issue it would have stopped on card #1 ages ago as this has about 80MB less memory available but it's with all cards.

This miner is buggy and it's been like this even 2 years ago with 8GB cards. I see it's no longer being maintained as well and is 10 months old.

Yes. claymore should upgrade his miner to fix those 4GB problem.
But there are other miners on which 4GB cards are still working under SimpleMining OS.

Regarding windows, the main problem is that windows has graphical interface which allocates some memory in gpu.
Linux can be hadless and does not have this problem so putting 8GB makes sense only in windows.
Yet you can try in claymore using some options that load dag slower or uses different kernel.

fatmeto

newbie

Activity: 5

Merit: 0

Quote from: dislorth on July 29, 2020, 07:42:32 PM

Quote from: fatmeto on July 21, 2020, 08:28:38 AM

I HAVE 3 RIG THE mainboards is same Gigabyte 970a-DS3p
3x5=15 Rx470 Asus Mining edition have
Today I see no hashrate all rig. I restarted Same Problem. I edit my miner config And added -eres 1 rigs start to work. But I see 3 rig Same Problem GPU0 is not start to work hashrate Still 0 mh. But in device manager No problem.
I think this problem Claymore's script problem. I try reinstall driver and patch same Problem Still.
Any Solution ?

I fixed this too with command line -eres 1 and GPU0 is not mining the hasrate for GPU0 is 0.000 MH/s why is this issue?

Without command line -eres 1 all my rig GPUs hashrate drops between 0.000 MH/s and 1.200 MH/s.

With command line -eres 1 GPU0 hasrate is 0.000 MH/s and the rest of GPUs hashrate are between 23.086 and 23.386 MH/s

Can Claymore team fix this issue please?

Today if onboard vga with mining not mining. Dag error or another opencl errors...

I found the solution. TAke one 8gb cards in Gpu 0 slot. Other cards can do 4gb. And use -eres 1 continue to mining.

enjoy

Prom_ZA

newbie

Activity: 18

Merit: 3

I keep getting "not enough GPU memory to place DAG, you cannot mine this coin with this GPU". This started with epoch 351. I reinstalled Linux and it disappeared until epoch 352 today. I thought it might be a bad disk as it's not functioning so well but it's still the same on a new one.

I don't have this problem on windows 10. The whole reason I switched to Linux was it has less problems and is supposed to mine for longer. This can't be a memory problem as it's still mineable with over 250MB free. Also if the DAG size was the issue it would have stopped on card #1 ages ago as this has about 80MB less memory available but it's with all cards.

This miner is buggy and it's been like this even 2 years ago with 8GB cards. I see it's no longer being maintained as well and is 10 months old.

dislorth

jr. member

Activity: 48

Merit: 1

Quote from: safar1980 on July 30, 2020, 08:44:14 AM

In the past, the integrated graphics card was on the motherboard (built into the chipset), now the graphics card is integrated into the processor. If your rig has an integrated graphics video card, then connect the monitor to it. Windows uses 100-400 MB of RAM from the built-in video card, and the memory of other video cards will not be used, so you can mine as long as the DAG file does not exceed 4 GB.

-eres 1 command line is not working now:

Code:

14:43:17:319 1138 Check and remove old log files...
14:43:17:327 1138 args: -epool eu1.ethermine.org:4444 -eres 1 -ewal 0x499a93e483e997fa4f1b3c9ebf975f466eca791a -epsw x -rxboost 1
14:43:17:329 1138
14:43:17:335 1138 ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
14:43:17:336 1138 º Claymore's Dual GPU Miner - v15.0 º
14:43:17:341 1138 º ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK º
14:43:17:344 1138 º Supercharged Edition º
14:43:17:347 1138 ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ¼
14:43:17:349 1138
14:43:17:350 1138 b755
14:43:17:553 1138 ETH: 1 pool is specified
14:43:17:556 1138 Main Ethereum pool is eu1.ethermine.org:4444
14:43:17:558 1138 DCR: 0 pool is specified
14:43:18:251 1138 OpenCL platform: AMD Accelerated Parallel Processing
14:43:18:255 1138 OpenCL initializing...

14:43:18:255 1138 AMD Cards available: 5
14:43:18:256 1138 GPU #0: Ellesmere (Radeon (TM) RX 470 Graphics), 4096 MB available, 32 compute units (pci bus 1:0:0)
14:43:18:257 1138 gpu 0 max alloc size is 3840 MB
14:43:18:258 1138 GPU #0 recognized as Radeon RX 470/570
14:43:18:259 1138 GPU #1: Ellesmere (Radeon (TM) RX 470 Graphics), 4096 MB available, 32 compute units (pci bus 3:0:0)
14:43:18:259 1138 gpu 1 max alloc size is 3840 MB
14:43:18:260 1138 GPU #1 recognized as Radeon RX 470/570
14:43:18:262 1138 GPU #2: Ellesmere (Radeon (TM) RX 470 Graphics), 4096 MB available, 32 compute units (pci bus 4:0:0)
14:43:18:263 1138 gpu 2 max alloc size is 3840 MB
14:43:18:263 1138 GPU #2 recognized as Radeon RX 470/570
14:43:18:264 1138 GPU #3: Ellesmere (Radeon (TM) RX 470 Graphics), 4096 MB available, 32 compute units (pci bus 12:0:0)
14:43:18:265 1138 gpu 3 max alloc size is 3840 MB
14:43:18:265 1138 GPU #3 recognized as Radeon RX 470/570
14:43:18:267 1138 GPU #4: Ellesmere (Radeon (TM) RX 470 Graphics), 4096 MB available, 32 compute units (pci bus 13:0:0)
14:43:18:268 1138 gpu 4 max alloc size is 3840 MB
14:43:18:268 1138 GPU #4 recognized as Radeon RX 470/570
14:43:18:269 1138 POOL/SOLO version
14:43:18:270 1138 Platform: Windows
14:43:18:376 1138 start building OpenCL program for GPU 0...
14:43:18:684 1138 done
14:43:18:909 1138 start building OpenCL program for GPU 1...
14:43:19:220 1138 done
14:43:19:426 1138 start building OpenCL program for GPU 2...
14:43:19:756 1138 done
14:43:19:971 1138 start building OpenCL program for GPU 3...
14:43:20:296 1138 done
14:43:20:510 1138 start building OpenCL program for GPU 4...
14:43:20:889 1138 done
14:43:21:174 1138 GPU #0: algorithm ASM 1
14:43:21:217 1138 GPU #1: algorithm ASM 1
14:43:21:258 1138 GPU #2: algorithm ASM 1
14:43:21:299 1138 GPU #3: algorithm ASM 1
14:43:21:343 1138 GPU #4: algorithm ASM 1
14:43:21:344 1138 cudaGetDeviceCount failed (35, CUDA driver version is insufficient for CUDA runtime version), probably no CUDA devices
14:43:21:345 1138 No NVIDIA CUDA GPUs detected.
14:43:21:347 1138 Total cards: 5
14:43:21:348 1138
Please consider using "-strap" option to increase mining speed, check Readme for details.

14:43:22:951 1138 No NVIDIA cards in the list, NVML library will not be used.
14:43:22:954 1138 Driver is not installed! Trying to install it...
14:43:22:970 1138 Driver is in use, try to start miner with "-driver uninstall" parameter.
14:43:24:043 1138 SSL: Imported 29 certificates from local storage
14:43:24:054 cd4 ETH: Stratum - connecting to 'eu1.ethermine.org' <172.65.207.106> port 4444 (unsecure)
14:43:24:144 1138 No pool specified for Decred! Ethereum-only mining mode is enabled

14:43:24:148 1138 ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)

14:43:24:150 1138 ETH: eth-proxy stratum mode
14:43:24:155 1138 Watchdog enabled
14:43:24:158 1138 Remote management (READ-ONLY MODE) is enabled on port 3333
14:43:24:160 1138

14:43:24:162 cd4 sent: {"worker": "eth1.0", "jsonrpc": "2.0", "params": ["0x499a93e483e997fa4f1b3c9ebf975f466eca791a", "x"], "id": 2, "method": "eth_submitLogin"}

14:43:24:168 cd4 ETH: Stratum - Connected (eu1.ethermine.org:4444) (unsecure)
14:43:24:165 1138 You did not specify -dcri values directly, so they will be detected automatically
14:43:24:174 1138 Automatic detection of best -dcri values started, please wait...

14:43:24:270 cd4 buf: {"id":2,"jsonrpc":"2.0","result":true}

14:43:24:272 cd4 ETH: Authorized
14:43:24:276 cd4 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

14:43:24:394 cd4 buf: {"id":0,"jsonrpc":"2.0","result":["0xcc0e3c98eee16c6fad85dacfe409659ff2d3e8373d7aa74654fccdbf362e19f8","0xe616e609ef9e132578cfed43964a986465f46c8f00641c0f9d72c962b666ecce","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xa1276a"]}

14:43:24:450 1ee8 Setting DAG epoch #352(3.75GB)...
14:43:27:603 cd4 buf: {"id":0,"jsonrpc":"2.0","result":["0x55e0d54071a8b1d2dee7956f8f5bd9651bd6fd27e551456221f2b4b5a68ac29a","0xe616e609ef9e132578cfed43964a986465f46c8f00641c0f9d72c962b666ecce","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xa1276a"]}

14:43:27:605 cd4 ETH: 07/30/20-14:43:27 - New job from eu1.ethermine.org:4444
14:43:27:605 cd4 target: 0x0000000112e0be82 (diff: 4000MH), epoch 352(3.75GB)
14:43:27:606 cd4 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
14:43:27:606 cd4 ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s
14:43:27:850 225c Setting DAG epoch #352 for GPU3
14:43:27:849 1ee8 Setting DAG epoch #352 for GPU1
14:43:27:852 20d4 Setting DAG epoch #352 for GPU4
14:43:27:850 1114 Setting DAG epoch #352 for GPU0
14:43:27:854 740 Setting DAG epoch #352 for GPU2
14:43:27:852 1ee8 Create GPU buffer for GPU1
14:43:27:856 1ee8 GPU1 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
14:43:27:852 225c Create GPU buffer for GPU3
14:43:27:857 225c GPU3 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
14:43:27:855 740 Create GPU buffer for GPU2
14:43:27:858 740 GPU2 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
14:43:27:860 1ee8 GPU1 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

14:43:27:853 20d4 Create GPU buffer for GPU4
14:43:27:861 20d4 GPU4 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
14:43:27:854 1114 Create GPU buffer for GPU0
14:43:27:862 1114 GPU0 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
14:43:27:863 225c GPU3 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

14:43:27:865 20d4 GPU4 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

14:43:27:866 740 GPU2 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

14:43:27:867 1114 GPU0 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

14:43:28:514 cd4 buf: {"id":0,"jsonrpc":"2.0","result":["0x0c025df2828d9d2f250f218c27f1f3bf5c2cef371f8191db346721671fd96be3","0xe616e609ef9e132578cfed43964a986465f46c8f00641c0f9d72c962b666ecce","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xa1276a"]}

14:43:28:519 cd4 ETH: 07/30/20-14:43:28 - New job from eu1.ethermine.org:4444
14:43:28:521 cd4 target: 0x0000000112e0be82 (diff: 4000MH), epoch 352(3.75GB)
14:43:28:522 cd4 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
14:43:28:525 cd4 ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s
14:43:30:862 1ee8 Set global fail flag, failed GPU1
14:43:30:868 1ee8 GPU 1 failed
14:43:30:865 764 Setting DAG epoch #352 for GPU1
14:43:30:872 764 GPU1, OpenCL error -38 - cannot write buffer for DAG

14:43:30:867 20d4 Set global fail flag, failed GPU4
14:43:30:877 20d4 GPU 4 failed
14:43:30:869 1114 Set global fail flag, failed GPU0
14:43:30:882 1114 GPU 0 failed
14:43:30:868 740 Set global fail flag, failed GPU2
14:43:30:888 740 GPU 2 failed
14:43:30:865 225c Set global fail flag, failed GPU3
14:43:30:894 225c GPU 3 failed
14:43:30:899 1fa8 Setting DAG epoch #352 for GPU2
14:43:30:904 87c Setting DAG epoch #352 for GPU3
14:43:30:907 87c GPU3, OpenCL error -38 - cannot write buffer for DAG

14:43:30:909 1fa8 GPU2, OpenCL error -38 - cannot write buffer for DAG

14:43:30:903 cdc Setting DAG epoch #352 for GPU4
14:43:30:892 15dc Setting DAG epoch #352 for GPU0
14:43:30:912 cdc GPU4, OpenCL error -38 - cannot write buffer for DAG

14:43:30:913 15dc GPU0, OpenCL error -38 - cannot write buffer for DAG

14:43:32:590 cd4 buf: {"id":0,"jsonrpc":"2.0","result":["0x947a082768357384a32fef5e3bc004d5f9576377b9655fa23a4c0a95bdc7a689","0xe616e609ef9e132578cfed43964a986465f46c8f00641c0f9d72c962b666ecce","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xa1276a"]}

14:43:32:594 cd4 ETH: 07/30/20-14:43:32 - New job from eu1.ethermine.org:4444
14:43:32:596 cd4 target: 0x0000000112e0be82 (diff: 4000MH), epoch 352(3.75GB)
14:43:32:598 cd4 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
14:43:32:601 cd4 ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s
14:43:33:875 764 Set global fail flag, failed GPU1
14:43:33:877 764 GPU 1 failed
14:43:33:909 87c Set global fail flag, failed GPU3
14:43:33:912 1fa8 Set global fail flag, failed GPU2
14:43:33:915 87c GPU 3 failed
14:43:33:914 cdc Set global fail flag, failed GPU4
14:43:33:922 cdc GPU 4 failed
14:43:33:915 15dc Set global fail flag, failed GPU0
14:43:33:926 15dc GPU 0 failed
14:43:33:929 1fa8 GPU 2 failed
14:43:34:408 cd4 ETH: checking pool connection...
14:43:34:408 cd4 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

14:43:34:520 cd4 buf: {"id":0,"jsonrpc":"2.0","result":["0x947a082768357384a32fef5e3bc004d5f9576377b9655fa23a4c0a95bdc7a689","0xe616e609ef9e132578cfed43964a986465f46c8f00641c0f9d72c962b666ecce","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xa1276a"]}

14:43:36:452 cd4 buf: {"id":0,"jsonrpc":"2.0","result":["0x49b86464607a111867b0a3d51186da0d5d04054a8ce7c8041cca73b3c3f33f9e","0xe616e609ef9e132578cfed43964a986465f46c8f00641c0f9d72c962b666ecce","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xa1276a"]}

14:43:36:458 cd4 ETH: 07/30/20-14:43:36 - New job from eu1.ethermine.org:4444
14:43:36:459 cd4 target: 0x0000000112e0be82 (diff: 4000MH), epoch 352(3.75GB)
14:43:36:461 cd4 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
14:43:36:465 cd4 ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s

Why this?

safar1980

legendary

Activity: 1708

Merit: 1615

Payment Gateway Allows Recurring Payments

Quote from: dislorth on July 30, 2020, 08:08:46 AM

Quote from: patthara74 on July 29, 2020, 11:34:22 PM

connect monitor with onboard gpu

What do you mean? I didn't understand Huh

In the past, the integrated graphics card was on the motherboard (built into the chipset), now the graphics card is integrated into the processor. If your rig has an integrated graphics video card, then connect the monitor to it. Windows uses 100-400 MB of RAM from the built-in video card, and the memory of other video cards will not be used, so you can mine as long as the DAG file does not exceed 4 GB.

dislorth

jr. member

Activity: 48

Merit: 1

Quote from: patthara74 on July 29, 2020, 11:34:22 PM

connect monitor with onboard gpu

What do you mean? I didn't understand Huh

safar1980

legendary

Activity: 1708

Merit: 1615

Payment Gateway Allows Recurring Payments

I use
PhoenixMiner_5.0e_Windows
Windows 10 Pro
RX 470 4 GB
Gigabyte 970A-D3SP
Everything works fine

JFoxOne

member

Activity: 640

Merit: 56

minerstat

Current ETH DAG size is 3.75GB.
Some "4GB" cards are (or soon will be) out of use for ETH/ETC.

foucss

newbie

Activity: 10

Merit: 2

Quote from: zakachi on July 30, 2020, 05:07:55 AM

How fix? : "not enough GPU memory to place DAG, you cannot mine this coin with this GPU , cannot allocate big buffer for DAG" Huh

Same for me :
ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s
GPU 0 failed
Setting DAG epoch #352 for GPU0
GPU0, OpenCL error -38 - cannot write buffer for DAG
Setting DAG epoch #352 for GPU4
GPU4, OpenCL error -38 - cannot write buffer for DAG

RX570 4G under linux (ethos)

zakachi

newbie

Activity: 4

Merit: 0

How fix? : "not enough GPU memory to place DAG, you cannot mine this coin with this GPU , cannot allocate big buffer for DAG" Huh

azza_

newbie

Activity: 7

Merit: 0

I would like to report an issue:

rx570 4GB cards with tuned bios, win10, latest AMD driver (adrenalin 20.7.2) - no mining after changing epoch to #352

Only first card shows 10 mh/s, the others fixed at 0 mh/s.

Normally around 30mh/s.

update: First test shows that lowering memory speed and getting back to very old crimson beta driver helps for now, at the cost of 3-5% lower performance. Memory usage around 3,895 MB

HWinfo shows that old driver is using around 27-29 MB of dynamic D3D memory while new driver is using more then 130 MB, at least for me.

bategojko74

member

Activity: 220

Merit: 12

Claymore haven't withdrawn money from his devfee accounts since 11.28.2019, 17 days after his last post. He have withdrawn about 500 ETH from each of his 8 ethermine accounts. Now he has heaped about 450 ETH per account. If his threshold is 500 ETH we will soon find if he is OK.

iamsooraj

newbie

Activity: 15

Merit: 0

Hi,

Is there any way to mine ETH on different address, i mean like defee is mining can i mine 1 minute of each hour to a different address

patthara74

newbie

Activity: 14

Merit: 0

Quote from: dislorth on July 29, 2020, 07:42:32 PM

Quote from: fatmeto on July 21, 2020, 08:28:38 AM

I HAVE 3 RIG THE mainboards is same Gigabyte 970a-DS3p
3x5=15 Rx470 Asus Mining edition have
Today I see no hashrate all rig. I restarted Same Problem. I edit my miner config And added -eres 1 rigs start to work. But I see 3 rig Same Problem GPU0 is not start to work hashrate Still 0 mh. But in device manager No problem.
I think this problem Claymore's script problem. I try reinstall driver and patch same Problem Still.
Any Solution ?

I fixed this too with command line -eres 1 and GPU0 is not mining the hasrate for GPU0 is 0.000 MH/s why is this issue?

Without command line -eres 1 all my rig GPUs hashrate drops between 0.000 MH/s and 1.200 MH/s.

With command line -eres 1 GPU0 hasrate is 0.000 MH/s and the rest of GPUs hashrate are between 23.086 and 23.386 MH/s

Can Claymore team fix this issue please?

connect monitor with onboard gpu

dislorth

jr. member

Activity: 48

Merit: 1

Quote from: fatmeto on July 21, 2020, 08:28:38 AM

I HAVE 3 RIG THE mainboards is same Gigabyte 970a-DS3p
3x5=15 Rx470 Asus Mining edition have
Today I see no hashrate all rig. I restarted Same Problem. I edit my miner config And added -eres 1 rigs start to work. But I see 3 rig Same Problem GPU0 is not start to work hashrate Still 0 mh. But in device manager No problem.
I think this problem Claymore's script problem. I try reinstall driver and patch same Problem Still.
Any Solution ?

I fixed this too with command line -eres 1 and GPU0 is not mining the hasrate for GPU0 is 0.000 MH/s why is this issue?

Without command line -eres 1 all my rig GPUs hashrate drops between 0.000 MH/s and 1.200 MH/s.

With command line -eres 1 GPU0 hasrate is 0.000 MH/s and the rest of GPUs hashrate are between 23.086 and 23.386 MH/s

Can Claymore team fix this issue please?

Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 36. (Read 6590757 times)