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

farmgpu0914

newbie

Activity: 3

Merit: 0

Quote from: VasilyS on July 15, 2019, 04:48:34 PM

You have to increase virtual memory size to at least sum of the memory of your cards.

Well, for windows it's true but I'm running hiveos(linux). How to be here?
Some people running 13 or more cards and I've never heard that they do virtual memory tuning in linux.
Some calculations - for me problem epoch - #280 (3.19 Gb). 6 cards its 19.14Gb in sum. Why does its worked fine with epoch 279?

VasilyS

member

Activity: 618

Merit: 21

You have to increase virtual memory size to at least sum of the memory of your cards.

farmgpu0914

newbie

Activity: 3

Merit: 0

Hi
celeron3930/4GbRAM/8Gb usb Flash drive/ 6card RX580 4Gb on hiveOS, ETC mining Claymore 14.7
AMD Rx580 4Gb hangs on start and writing: not enough GPU memory to place DAG
Huh

on epoch #280 ?
Then WATCHDOG: GPU error, you need to restart miner
What I should do - expand RAM on motherboard, expand disk drive or something else?

Code:

21:45:44:309 6ac2d740 Check and remove old log files...
21:45:44:310 6ac2d740 args: -mport -3333 -r 1 -logfile /var/log/miner/claymore/lastrun_noappend.log -tt 68 -ttli 76 -tstop 82 -mode 1 -allcoins etc -allpools 0 -
21:45:44:310 6ac2d740
21:45:44:310 6ac2d740 ................................................................ͻ
21:45:44:310 6ac2d740 . Claymore's Dual GPU Miner - v14.7 .
21:45:44:310 6ac2d740 . ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK .
21:45:44:310 6ac2d740 ................................................................ͼ
21:45:44:310 6ac2d740
21:45:44:310 6ac2d740 b745
21:45:44:511 6ac2d740 no address specified - ignore
21:45:44:511 6ac2d740 ETH: 1 pool is specified
21:45:44:511 6ac2d740 Main Ethereum pool is etc.2miners.com:1010
21:45:44:560 6ac2d740 OpenCL platform: AMD Accelerated Parallel Processing
21:45:44:560 6ac2d740 OpenCL initializing...

21:45:44:560 6ac2d740 AMD Cards available: 6
21:45:44:560 6ac2d740 GPU #0: Ellesmere (Radeon RX 580 Series), 4087 MB available, 36 compute units (pci bus 1:0:0)
21:45:44:560 6ac2d740 GPU #0 recognized as Radeon RX 480/580
21:45:44:560 6ac2d740 GPU #1: Ellesmere (Radeon RX 580 Series), 4087 MB available, 36 compute units (pci bus 3:0:0)
21:45:44:560 6ac2d740 GPU #1 recognized as Radeon RX 480/580
21:45:44:560 6ac2d740 GPU #2: Ellesmere (Radeon RX 580 Series), 4087 MB available, 36 compute units (pci bus 4:0:0)
21:45:44:560 6ac2d740 GPU #2 recognized as Radeon RX 480/580
21:45:44:560 6ac2d740 GPU #3: Ellesmere (Radeon RX 580 Series), 4087 MB available, 36 compute units (pci bus 5:0:0)
21:45:44:560 6ac2d740 GPU #3 recognized as Radeon RX 480/580
21:45:44:560 6ac2d740 GPU #4: Ellesmere (Radeon RX 580 Series), 4087 MB available, 36 compute units (pci bus 8:0:0)
21:45:44:560 6ac2d740 GPU #4 recognized as Radeon RX 480/580
21:45:44:560 6ac2d740 GPU #5: Ellesmere (Radeon RX 580 Series), 4087 MB available, 36 compute units (pci bus 9:0:0)
21:45:44:560 6ac2d740 GPU #5 recognized as Radeon RX 480/580
21:45:44:560 6ac2d740 POOL/SOLO version
21:45:44:560 6ac2d740 Platform: Linux
21:45:44:623 6ac2d740 AMD ADL library not found.
21:45:44:625 6ac2d740 amdgpu cnt: 6
21:45:44:628 6ac2d740 start building OpenCL program for GPU 0...
21:45:44:728 6ac2d740 done
21:45:44:935 6ac2d740 start building OpenCL program for GPU 1...
21:45:45:036 6ac2d740 done
21:45:45:243 6ac2d740 start building OpenCL program for GPU 2...
21:45:45:343 6ac2d740 done
21:45:45:549 6ac2d740 start building OpenCL program for GPU 3...
21:45:45:650 6ac2d740 done
21:45:45:858 6ac2d740 start building OpenCL program for GPU 4...
21:45:45:958 6ac2d740 done
21:45:46:166 6ac2d740 start building OpenCL program for GPU 5...
21:45:46:266 6ac2d740 done
21:45:46:479 6ac2d740 GPU #0: algorithm ASM 1
21:45:46:486 6ac2d740 GPU #1: algorithm ASM 1
21:45:46:493 6ac2d740 GPU #2: algorithm ASM 1
21:45:46:503 6ac2d740 GPU #3: algorithm ASM 1
21:45:46:513 6ac2d740 GPU #4: algorithm ASM 1
21:45:46:522 6ac2d740 GPU #5: algorithm ASM 1
21:45:46:524 6ac2d740 cudaGetDeviceCount returned error 38
-> no CUDA-capable device is detected
21:45:46:524 6ac2d740 No NVIDIA CUDA GPUs detected.
21:45:46:524 6ac2d740 Total cards: 6
21:45:49:726 6ac2d740
You can use "+" and "-" keys to achieve best ETH speed, see "FINE TUNING" section in Readme for details.

21:45:50:727 6ac2d740 No NVIDIA cards in the list, NVML library will not be used.
21:45:50:778 227fc700 ETH: Stratum - connecting to 'etc.2miners.com' <54.36.109.160> port 1010 (unsecure)

21:45:50:864 227fc700 ETH: Stratum - Connected (etc.2miners.com:1010) (unsecure)
21:45:50:877 6ac2d740 ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)

21:45:50:877 6ac2d740 ETH: eth-proxy stratum mode
21:45:50:877 6ac2d740 "-allcoins" option is set, default pools will be used for devfee, check "Readme" file for details.
21:45:50:877 6ac2d740 Watchdog enabled
21:45:50:877 6ac2d740 Remote management (READ-ONLY MODE) is enabled on port 3333
21:45:50:877 6ac2d740

21:45:50:877 6ac2d740 You did not specify -dcri values directly, so they will be detected automatically
21:45:50:878 6ac2d740 Automatic detection of best -dcri values started, please wait...

21:45:50:945 227fc700 buf: {"id":2,"jsonrpc":"2.0","result":true}

21:45:50:945 227fc700 ETH: Authorized
21:45:50:945 227fc700 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

21:45:51:135 23fff700 Setting DAG epoch #280...
21:45:53:516 682fd700 GPU 0 temp = 34, old fan speed = 22, new fan speed = 25

21:45:53:517 682fd700 GPU 1 temp = 34, old fan speed = 22, new fan speed = 25

21:45:53:517 682fd700 GPU 2 temp = 37, old fan speed = 22, new fan speed = 25

21:45:53:517 682fd700 GPU 3 temp = 34, old fan speed = 22, new fan speed = 25

21:45:53:517 682fd700 GPU 4 temp = 36, old fan speed = 22, new fan speed = 25

21:45:53:517 682fd700 GPU 5 temp = 35, old fan speed = 22, new fan speed = 25

21:45:54:383 23fff700 Setting DAG epoch #280 for GPU4
21:45:54:383 23fff700 Create GPU buffer for GPU4
21:45:54:383 237fe700 Setting DAG epoch #280 for GPU5
21:45:54:383 237fe700 Create GPU buffer for GPU5
21:45:54:383 237fe700 GPU5 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
21:45:54:383 2b7fe700 Setting DAG epoch #280 for GPU1
21:45:54:383 2b7fe700 Create GPU buffer for GPU1
21:45:54:383 2b7fe700 GPU1 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
21:45:54:383 237fe700 GPU5 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

21:45:54:383 2b7fe700 GPU1 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

21:45:54:383 23fff700 GPU4 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
21:45:54:383 23fff700 GPU4 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

21:45:54:383 54900700 Setting DAG epoch #280 for GPU0
21:45:54:383 54900700 Create GPU buffer for GPU0
21:45:54:383 54900700 GPU0 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
21:45:54:383 54900700 GPU0 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

21:45:54:383 297fa700 Setting DAG epoch #280 for GPU3
21:45:54:383 2a7fc700 Setting DAG epoch #280 for GPU2
21:45:54:383 2a7fc700 Create GPU buffer for GPU2
21:45:54:383 2a7fc700 GPU2 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
21:45:54:383 2a7fc700 GPU2 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

21:45:54:383 297fa700 Create GPU buffer for GPU3
21:45:54:383 297fa700 GPU3 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
21:45:54:383 297fa700 GPU3 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

21:45:56:517 682fd700 GPU 0 temp = 34, old fan speed = 22, new fan speed = 25

21:45:56:517 682fd700 GPU 1 temp = 34, old fan speed = 22, new fan speed = 25

21:45:56:517 682fd700 GPU 2 temp = 37, old fan speed = 22, new fan speed = 25

21:45:56:518 682fd700 GPU 3 temp = 34, old fan speed = 22, new fan speed = 25

21:45:56:518 682fd700 GPU 4 temp = 36, old fan speed = 22, new fan speed = 25

21:45:56:518 682fd700 GPU 5 temp = 35, old fan speed = 22, new fan speed = 25

21:45:57:383 237fe700 Set global fail flag, failed GPU5
21:45:57:383 237fe700 GPU 5 failed
21:45:57:383 54900700 Set global fail flag, failed GPU0
21:45:57:384 54900700 GPU 0 failed
21:45:57:384 22ffd700 Setting DAG epoch #280 for GPU5
21:45:57:384 22ffd700 GPU5, OpenCL error -38 - cannot write buffer for DAG

21:45:57:383 2a7fc700 Set global fail flag, failed GPU2
21:45:57:384 2a7fc700 GPU 2 failed
21:45:57:383 23fff700 Set global fail flag, failed GPU4
21:45:57:384 23fff700 GPU 4 failed
21:45:57:384 2affd700 Setting DAG epoch #280 for GPU2
21:45:57:383 2b7fe700 Set global fail flag, failed GPU1
21:45:57:385 2b7fe700 GPU 1 failed
21:45:57:383 297fa700 Set global fail flag, failed GPU3
21:45:57:385 297fa700 GPU 3 failed
21:45:57:385 29ffb700 Setting DAG epoch #280 for GPU3
21:45:57:385 29ffb700 GPU3, OpenCL error -38 - cannot write buffer for DAG

21:45:57:385 2affd700 GPU2, OpenCL error -38 - cannot write buffer for DAG

21:45:57:385 2bfff700 Setting DAG epoch #280 for GPU1
21:45:57:385 2bfff700 GPU1, OpenCL error -38 - cannot write buffer for DAG

21:45:57:385 55101700 Setting DAG epoch #280 for GPU0
21:45:57:385 55101700 GPU0, OpenCL error -38 - cannot write buffer for DAG

21:45:57:385 28ff9700 Setting DAG epoch #280 for GPU4
21:45:57:385 28ff9700 GPU4, OpenCL error -38 - cannot write buffer for DAG

21:45:58:346 227fc700 ETH: 07/15/19-21:45:58 - New job from etc.2miners.com:1010
21:45:58:346 227fc700 target: 0x000000007fd9a601 (diff: 8600MH), epoch 280(3.19GB)
21:45:58:347 227fc700 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
21:45:58:347 227fc700 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
21:45:59:518 682fd700 GPU 0 temp = 34, old fan speed = 22, new fan speed = 25

21:45:59:518 682fd700 GPU 1 temp = 34, old fan speed = 22, new fan speed = 25

21:45:59:518 682fd700 GPU 2 temp = 37, old fan speed = 22, new fan speed = 25

21:45:59:518 682fd700 GPU 3 temp = 34, old fan speed = 22, new fan speed = 25

21:45:59:518 682fd700 GPU 4 temp = 36, old fan speed = 22, new fan speed = 25

21:45:59:518 682fd700 GPU 5 temp = 35, old fan speed = 22, new fan speed = 25

21:46:00:037 297fa700 srv_thr cnt: 1, IP: 127.0.0.1
21:46:00:037 297fa700 recv: 51
21:46:00:037 297fa700 srv pck: 50
21:46:00:037 297fa700 srv bs: 0
21:46:00:037 297fa700 sent: 308
21:46:00:384 22ffd700 Set global fail flag, failed GPU5
21:46:00:384 22ffd700 GPU 5 failed
21:46:00:385 2affd700 Set global fail flag, failed GPU2
21:46:00:385 29ffb700 Set global fail flag, failed GPU3
21:46:00:385 29ffb700 GPU 3 failed
21:46:00:385 55101700 Set global fail flag, failed GPU0
21:46:00:385 55101700 GPU 0 failed
21:46:00:385 2bfff700 Set global fail flag, failed GPU1
21:46:00:385 2bfff700 GPU 1 failed
21:46:00:385 28ff9700 Set global fail flag, failed GPU4
21:46:00:386 28ff9700 GPU 4 failed
21:46:00:386 2affd700 GPU 2 failed
21:46:01:038 227fc700 ETH: checking pool connection...
21:46:01:038 227fc700 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

21:46:02:306 227fc700 ETH: 07/15/19-21:46:02 - New job from etc.2miners.com:1010
21:46:02:306 227fc700 target: 0x000000007fd9a601 (diff: 8600MH), epoch 280(3.19GB)
21:46:02:306 227fc700 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
21:46:02:306 227fc700 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
21:46:02:519 682fd700 GPU 0 temp = 34, old fan speed = 22, new fan speed = 25

21:46:06:666 227fc700 ETH: 07/15/19-21:46:06 - New job from etc.2miners.com:1010
21:46:06:666 227fc700 target: 0x000000007fd9a601 (diff: 8600MH), epoch 280(3.19GB)
21:46:06:666 227fc700 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
21:46:06:666 227fc700 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
21:46:08:521 682fd700 GPU 0 temp = 34, old fan speed = 22, new fan speed = 25

Luke83

newbie

Activity: 7

Merit: 0

Quote from: simpleCZAR on July 15, 2019, 07:37:09 AM

Vega 64 speed drop--
you already have much better speed than most. It could be due to temp as summer kicks in..Memory downclocks if hot at about 70C for mine ..mine does that but does not come up..so I increased the fan speed

My Vegas are running between 48 to 55°C with 90% fan speed, I have a private room with aircon, so the temp is not the issue I guess

simpleCZAR

newbie

Activity: 3

Merit: 0

Vega 64 speed drop--
you already have much better speed than most. It could be due to temp as summer kicks in..Memory downclocks if hot at about 70C for mine ..mine does that but does not come up..so I increased the fan speed

Luke83

newbie

Activity: 7

Merit: 0

Hello,

I have a 6 nitro+ Vega 64 Limited Edition mining rig, each card is doing 51+ Mhs, but it happens time to time, that randomly, 1 card, (or more) from the 6, drops its hashrate for like 30 to 60 seconds and then goes back to 51mhs.

I am using Claymore 14.7 with -strap 4 option.

My overclock settings are :

GPU : 1408 Mhz 905 Mv;
Memory : 1100 Mhz 900Mv

Fans are set at 90% and the power draw is around 155W.

I think my overclocking is not stable. Or maybe some settings are wrong in the Bios? (motherboard : MSI Z270 A PRO)

The drop can be down to 49 or 44 or even 42 Mhs. And when the drop happens the power draw is reduced to like 140W.

Any one can assist? Your help would be very appreciated.

sharmanov

newbie

Activity: 54

Merit: 0

getting GPU #0 strap "1" failed, error 1002 how do I fix that and what does that error mean? all straps get that error

Junkey

full member

Activity: 164

Merit: 100

When I set -mclock and cclock in the miner and close it Windows 10 freezes for a bit and then resets the config to default. Is there a more graceful way to do it that I am missing? Thanks,

gianb

newbie

Activity: 5

Merit: 0

Quote from: WhackOBill on July 12, 2019, 02:45:22 PM

Quote from: gianb on July 12, 2019, 01:10:33 PM

Quote from: UnclWish on July 12, 2019, 12:47:02 PM

Quote from: gianb on July 12, 2019, 11:31:37 AM

My claymore its working fine but, when I start claymore a message appears in red that says Unknown option 1

It's simple - you must remove option "1" from command line to launch miner.

%~dp0
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
:ini
timeout /t 20

EthDcrMiner64.exe -epool eth-us-east1.nanopool.org:9999 -ewal 0x3f8c701099e6748bc44938467121d8ff2c165.RGCCS01ETH -epsw x -tstop 75 -ftime 10 -allpools 1 -allcoins -1 -asm 1 -cclock 1090,1090,1090,1090,1090,1090 -mclock 2070,2070,2070,2060,2070,2070 -mvddc 900,900,900,910,900,900 -cvddc 900,900,900,910,900,900 -r 3600 -estale 1 -gser 2 -mode 1 -etha 0 -erate 1 -ttli 75 -y -platform 1 -tstart 60 -retrydelay 5 -mport 3333 -strap 1 -rxboost 1 -mpsw 748
end

Could you help me with what I should remove?

You're missing the ' 1' after the -y it seems.

Yes thanks!

WhackOBill

jr. member

Activity: 73

Merit: 3

Quote from: gianb on July 12, 2019, 01:10:33 PM

Quote from: UnclWish on July 12, 2019, 12:47:02 PM

Quote from: gianb on July 12, 2019, 11:31:37 AM

My claymore its working fine but, when I start claymore a message appears in red that says Unknown option 1

It's simple - you must remove option "1" from command line to launch miner.

%~dp0
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
:ini
timeout /t 20

EthDcrMiner64.exe -epool eth-us-east1.nanopool.org:9999 -ewal 0x3f8c701099e6748bc44938467121d8ff2c165.RGCCS01ETH -epsw x -tstop 75 -ftime 10 -allpools 1 -allcoins -1 -asm 1 -cclock 1090,1090,1090,1090,1090,1090 -mclock 2070,2070,2070,2060,2070,2070 -mvddc 900,900,900,910,900,900 -cvddc 900,900,900,910,900,900 -r 3600 -estale 1 -gser 2 -mode 1 -etha 0 -erate 1 -ttli 75 -y -platform 1 -tstart 60 -retrydelay 5 -mport 3333 -strap 1 -rxboost 1 -mpsw 748
end

Could you help me with what I should remove?

You're missing the ' 1' after the -y it seems.

gianb

newbie

Activity: 5

Merit: 0

Quote from: UnclWish on July 12, 2019, 12:47:02 PM

Quote from: gianb on July 12, 2019, 11:31:37 AM

My claymore its working fine but, when I start claymore a message appears in red that says Unknown option 1

It's simple - you must remove option "1" from command line to launch miner.

%~dp0
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
:ini
timeout /t 20

EthDcrMiner64.exe -epool eth-us-east1.nanopool.org:9999 -ewal 0x3f8c701099e6748bc44938467121d8ff2c165.RGCCS01ETH -epsw x -tstop 75 -ftime 10 -allpools 1 -allcoins -1 -asm 1 -cclock 1090,1090,1090,1090,1090,1090 -mclock 2070,2070,2070,2060,2070,2070 -mvddc 900,900,900,910,900,900 -cvddc 900,900,900,910,900,900 -r 3600 -estale 1 -gser 2 -mode 1 -etha 0 -erate 1 -ttli 75 -y -platform 1 -tstart 60 -retrydelay 5 -mport 3333 -strap 1 -rxboost 1 -mpsw 748
end

Could you help me with what I should remove?

UnclWish

sr. member

Activity: 1484

Merit: 253

Quote from: gianb on July 12, 2019, 11:31:37 AM

My claymore its working fine but, when I start claymore a message appears in red that says Unknown option 1

It's simple - you must remove option "1" from command line to launch miner.

gianb

newbie

Activity: 5

Merit: 0

My claymore its working fine but, when I start claymore a message appears in red that says Unknown option 1

4ward

member

Activity: 473

Merit: 18

Quote from: Furious_scorpion on July 09, 2019, 01:49:20 PM

Hello!
With dual mining ETH+Pascal, the number of rejected shares for Pascal is about 50%. Can this be fixed someway?
Thanks!

Its a surprise that there are accepted shares, since Pascal coin changed their algo completely

jeremyismer

newbie

Activity: 55

Merit: 0

Quote from: Wcrypto on July 10, 2019, 08:45:18 PM

Can we use the -strap command with a bios modified card?

Yeah, you can. I ran it on mine, but I didn't get any better performance than the straps I had myself. Others have suggested to reflash back to stock and run strap and rxboost, but at the moment I'm not fixing what ain't broken.

destinys

newbie

Activity: 2

Merit: 0

Hi Claymore,

i think alot of us got the RX5700 graphics card waiting for the software to be updated the community alot of us is waiting. Is there any updates or any finding which able for us to mine. Thanks

Regards
Melvin

STT

legendary

Activity: 4004

Merit: 1428

☠ ☠ ☠ メメ

Quote from: blastbob on April 11, 2016, 11:39:25 AM

My antivirus removed the file as soon as it was available.

So ill keep off until some more comments are available

All these years later and yep, my ethdcrminer64 is kidnapped by some ever so friendly stupid software. It does at least force me to update to the latest version since I've completely lost track of whatever dungeon the old .exe has been placed in

Is there any preference between 14.6 and 14.7 at the moment, using vega

[Chrome also says its a dangerous download, but at least lets me decide in finality for myself. just fyi for my fellow noobs

]

Wcrypto

newbie

Activity: 5

Merit: 0

Can we use the -strap command with a bios modified card?

Wcrypto

newbie

Activity: 5

Merit: 0

Quote from: Geniusvzla on July 10, 2019, 05:53:13 PM

Quote from: Wcrypto on July 10, 2019, 03:00:40 PM

Hi,

I tried to bring back my RX580 (Red devil 8gb Samsung) to the original bios in order to use claymore 14.7 with rxboost and the strap function. (I use windows 10)

My problem is that every time I try to set-up the core voltage in claymore (I use -mvdcc 850) , the system crash almost immediately. (blank screen).

If I don't use the -mvdcc command, it is working and I get 10% more mh/s but I use 25% more watt than before so it is not very good.

I have tried to change the core voltage in MS afterburner (Core voltage -100) but it doesn't have any effect on my power consumption….(like if it was not working).

Anyone can help me please?

Thank you!

Regards,
here you need more data: If you use afterbuner it indicates what values you have there and in your belt configuration what values you put on! if you use -mvdcc 850 and -cvddc 850 you should increase it or 900 or 950 each! On the contrary, if you want to keep the 850 you should lower the memory clock until it is stable; Afterwards if your Mh / s are very low you may have to try another belt or return to the one you had previously. Sorry my bad english

Thanks for your answer but the miner is already stable with my bios modded card, I have a problem when I get back to original bios and I try to use "-strap" and "-rxboost" command with exactly the same command line...

Geniusvzla

newbie

Activity: 36

Merit: 0

Quote from: Wcrypto on July 10, 2019, 03:00:40 PM

Hi,

I tried to bring back my RX580 (Red devil 8gb Samsung) to the original bios in order to use claymore 14.7 with rxboost and the strap function. (I use windows 10)

My problem is that every time I try to set-up the core voltage in claymore (I use -mvdcc 850) , the system crash almost immediately. (blank screen).

If I don't use the -mvdcc command, it is working and I get 10% more mh/s but I use 25% more watt than before so it is not very good.

I have tried to change the core voltage in MS afterburner (Core voltage -100) but it doesn't have any effect on my power consumption….(like if it was not working).

Anyone can help me please?

Thank you!

Regards,
here you need more data: If you use afterbuner it indicates what values you have there and in your belt configuration what values you put on! if you use -mvdcc 850 and -cvddc 850 you should increase it or 900 or 950 each! On the contrary, if you want to keep the 850 you should lower the memory clock until it is stable; Afterwards if your Mh / s are very low you may have to try another belt or return to the one you had previously. Sorry my bad english

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