not enough GPU memory to place DAG, you cannot mine this coin with this GPU
12.0 miner, -Eres 0 dont help, more that 32 GB of virtual mem dont help...
Win 10 1803
Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 169. (Read 6590718 times)
January 01, 2019, 08:00:51 AM
All mine 4GB AMD rigs stop working last night.
not enough GPU memory to place DAG, you cannot mine this coin with this GPU
12.0 miner, -Eres 0 dont help, more that 32 GB of virtual mem dont help...
Win 10 1803
not enough GPU memory to place DAG, you cannot mine this coin with this GPU
12.0 miner, -Eres 0 dont help, more that 32 GB of virtual mem dont help...
Win 10 1803
January 01, 2019, 05:39:39 AM
https://github.com/ethereum-mining/ethminer work perfect now, no fee.
You gave some of your coins to claymore and got a headache for several months.
Think about switching to open source
You gave some of your coins to claymore and got a headache for several months.
Think about switching to open source
January 01, 2019, 03:30:28 AM
@Claymore are you going to release a new version for Constantinople or that is not needed?
January 01, 2019, 12:21:41 AM
Hi there!
All my rigs are still on Windows 10 build 1709. Has there been any development regarding mining on Win10 build 1803 and later? Is it known what is/was causing the problem?
All my rigs are still on Windows 10 build 1709. Has there been any development regarding mining on Win10 build 1803 and later? Is it known what is/was causing the problem?
I've had no issues with Windows 10 builds 1803 and 1809.
vcn and many other network features are broken on windows 1803, for now only 1709.
This is wrong, windows 10 builds 1809 and 1803 works like 1709, no issues.
December 31, 2018, 10:13:32 PM
Hi there!
All my rigs are still on Windows 10 build 1709. Has there been any development regarding mining on Win10 build 1803 and later? Is it known what is/was causing the problem?
All my rigs are still on Windows 10 build 1709. Has there been any development regarding mining on Win10 build 1803 and later? Is it known what is/was causing the problem?
I've had no issues with Windows 10 builds 1803 and 1809.
vcn and many other network features are broken on windows 1803, for now only 1709.
December 31, 2018, 06:59:12 PM
hey guys, got a weird one today.
We built a new mining rig with rx 470 4GB (MSI Gaming X, Samsung memory and yeah, we're lucky enough to have free electricity), we copied the 1500 memory straps from 1500 to 2000 (like we always do), but for some odd reason we can't OC our cards memory above 1850Mhz without having the good old GPU#X got incorrect share etc... which means our cards are stuck around 27.2Mh/s.
You guys got any idea what the problem might be ? We have downvolted anything yet so our cards are definitely not power starved, I'm just a bit confused.
We built a new mining rig with rx 470 4GB (MSI Gaming X, Samsung memory and yeah, we're lucky enough to have free electricity), we copied the 1500 memory straps from 1500 to 2000 (like we always do), but for some odd reason we can't OC our cards memory above 1850Mhz without having the good old GPU#X got incorrect share etc... which means our cards are stuck around 27.2Mh/s.
You guys got any idea what the problem might be ? We have downvolted anything yet so our cards are definitely not power starved, I'm just a bit confused.
First of all, you have free elec
Even if those cards are doing 15Mh/s youll have good profit...
But ok
What is your config? Win ver., driver ver., etc
Yeah, I'm definitely not complaining about our situation (the rig belongs to me and my brother), I just thought I could squeeze a lil bit more out of our cards since I saw a lot of people having around 30mh/s with the same cards.
So we're using Windows 10 (with the latest update), the latest Claymore version as well and the latest stable AMD drivers (18.12.2). In terms of hardware we are using :
ASrock H81 Pro BTC 2.0
4GB of DDR3
a 1000W Aerocool Gold+ PSU
a Celeron G1840 CPU
and of course 6* MSI Gaming X RX 470@4GB
I managed to slightly increase the memory clock to 1860Mhz but I can't go beyond that.
those cards are bios modded or you are using an afterburner to set the clocks?
Hey and sorry for the late reply (Xmas and stuff!). We tried to things:
1. No bios mod, we simply increased the clocks and we ended up with ~25Mh/s with the clocks around 2050Mhz but with a shit ton of GPU#x got incorrect shares
2. We then bios mod the card ourselves (using Polaris Bios Editor), copying the 1500 strap values from 1500 to 2000. (we also tried with the 1750 values from 1750 to 2000 as well), and this is the situation where we are at at the moment, with 27.2Mh/s and a few GPU errors here and there on our GPU2.
This is our rig stats btw: https://ethermine.org/miners/f6c10F2CB2A2161efb43e4e0eabee60629329d5a/dashboard
Any advices would be much appreciated !
try the driver versions 18.xxxx
and with the compute patcher turn all the gpus in one shot to the compute mode and share if you get better results
We're already on the latest stable driver version, the 18.12.2 with everything on compute mode. We just tried the latest Clayrmore version (12.0), didn't make much difference, still stuck at 27.2mh/s on average with our memory clocks at 1850mhz
Did you read the guide by Mattthev?
https://bitcointalksearch.org/topic/guidetutorialxmrethhow-to-mod-bios-rx470570480580-vega-mining-1954245
Late reply but I actually followed the guide step by step and it just... works !
Went from 1850mhz OC and 27ish mh/s with GPU errors popping here and there to 2100Mhz and 29.1-29.2 mh/s 100% stable so far, with ZERO errors.
Can't go above 2100Mhz since this is the maximum I can get to on afterburner.
December 31, 2018, 03:09:58 AM
Same here
My 6 R9 290 are doing 21-22Mhs
Before they were doing 29mhs
However, this is not connected to ver 12.0
It happened gradually for me for months now
I thought it was connected with overheating because of the fans failing
Maybe it is connected with DAG file size getting larger?
Does anyone know what to do?
Have you tried running -oldkernells?
My 6 R9 290 are doing 21-22Mhs
Before they were doing 29mhs
However, this is not connected to ver 12.0
It happened gradually for me for months now
I thought it was connected with overheating because of the fans failing
Maybe it is connected with DAG file size getting larger?
Does anyone know what to do?
Have you tried running -oldkernells?
Basically its the DAG Thrashing bug which affected GPUs like the R9 280X and the RX 470/570 before AMD issued a driver fix.
When the DAG exceeds a certain size the GPU has a longer seek time due to some error, Nvidia GPUs never experienced this.
When the R9 280X was on DAG #0, it hashed at 28MH/s and now it hashes at less than 10MH/s. So the GPU is pretty much useless due to this bug.
Same issue happened with the RX series GPUs, however AMD issued a fix with the GPU compute drivers. The R9 280X never got that fix and most likely neither will the R9 290.
December 31, 2018, 03:04:48 AM
Same here
My 6 R9 290 are doing 21-22Mhs
Before they were doing 29mhs
However, this is not connected to ver 12.0
It happened gradually for me for months now
I thought it was connected with overheating because of the fans failing
Maybe it is connected with DAG file size getting larger?
Does anyone know what to do?
Have you tried running -oldkernells?
My 6 R9 290 are doing 21-22Mhs
Before they were doing 29mhs
However, this is not connected to ver 12.0
It happened gradually for me for months now
I thought it was connected with overheating because of the fans failing
Maybe it is connected with DAG file size getting larger?
Does anyone know what to do?
Have you tried running -oldkernells?
December 30, 2018, 11:26:57 PM
To those who have GPU 390 / 390X, have you seen that the hash is considerably low? but it only happens to me when I'm ETH or ETC (each gpu is giving a hash of 24 +/-) but in other dagger coins, it's around 30mhs +/-
(only with 390/390X, i have 380 too, and the hash is well with any coin)
(only with 390/390X, i have 380 too, and the hash is well with any coin)
Same here. It happens to 290/290X as well.
December 30, 2018, 10:11:08 PM
Hi there!
All my rigs are still on Windows 10 build 1709. Has there been any development regarding mining on Win10 build 1803 and later? Is it known what is/was causing the problem?
All my rigs are still on Windows 10 build 1709. Has there been any development regarding mining on Win10 build 1803 and later? Is it known what is/was causing the problem?
I've had no issues with Windows 10 builds 1803 and 1809.
December 30, 2018, 01:17:00 PM
To those who have GPU 390 / 390X, have you seen that the hash is considerably low? but it only happens to me when I'm ETH or ETC (each gpu is giving a hash of 24 +/-) but in other dagger coins, it's around 30mhs +/-
(only with 390/390X, i have 380 too, and the hash is well with any coin)
(only with 390/390X, i have 380 too, and the hash is well with any coin)
December 30, 2018, 10:49:34 AM
Hi there!
All my rigs are still on Windows 10 build 1709. Has there been any development regarding mining on Win10 build 1803 and later? Is it known what is/was causing the problem?
All my rigs are still on Windows 10 build 1709. Has there been any development regarding mining on Win10 build 1803 and later? Is it known what is/was causing the problem?
December 28, 2018, 08:09:54 AM
Just tried 12.0 version on NV 1060 3gb running Windows 7.
Mine ETH only with -eres 0. -eres 1 causes DAG errors.
Anyway, thanks for your miner!
Mine ETH only with -eres 0. -eres 1 causes DAG errors.
Anyway, thanks for your miner!
December 28, 2018, 06:32:50 AM
What did you meant by "the compute patcher turn all the gpus in one shot" is there a patcher that can puts all GPU to compute mode in one shot? if so could you provide a link?
There is one but you don't need it. Start claymore as administrator and press y. All cards will be in compute mode after reboot.
AMD-Compute-Switcher can be found here:
https://bitcointalksearch.org/topic/tool-amd-compute-switcher-for-switch-automatically-to-compute-mode-2815803
and if you have installed the AMD settings with the driver, do the DDU again and install the driver only, caust in the AMD settings you'll get the wattman that can cause headaches on compute mode with higher clocks
regards
December 28, 2018, 06:18:10 AM
What did you meant by "the compute patcher turn all the gpus in one shot" is there a patcher that can puts all GPU to compute mode in one shot? if so could you provide a link?
There is one but you don't need it. Start claymore as administrator and press y. All cards will be in compute mode after reboot.
AMD-Compute-Switcher can be found here:
https://bitcointalksearch.org/topic/tool-amd-compute-switcher-for-switch-automatically-to-compute-mode-2815803
December 28, 2018, 12:03:07 AM
@Claymore, I'm having problems with the ethman monitor when I close it, it says sometimes, "cannot save file, options_temp.ini make sure you have rights to create/write this file", I'm using windows 1709 and I have full access regarding write to a folder as administrator and this folder is on desktop, is not even in the c:/ drive root.
December 27, 2018, 06:37:07 PM
Any coin worth hitting on the dual mode then? Looks like the usual few are too difficult to get any recognised shares.
December 27, 2018, 06:01:42 PM
Re: Claymore v12.0
THANK YOU for this latest version, Claymore! We missed you.
THANK YOU for this latest version, Claymore! We missed you.
December 27, 2018, 04:04:23 PM
Claymore v12.0 added to https://www.minermonitoring.com/
Join our discord https://discord.gg/aGGaeqq
also, you can check the speed of the miner on different rigs using the benchmark page: https://minermonitoring.com/benchmark
Join our discord https://discord.gg/aGGaeqq
also, you can check the speed of the miner on different rigs using the benchmark page: https://minermonitoring.com/benchmark
December 27, 2018, 01:31:05 PM
try the driver versions 18.xxxx
and with the compute patcher turn all the gpus in one shot to the compute mode and share if you get better results
and with the compute patcher turn all the gpus in one shot to the compute mode and share if you get better results
What did you meant by "the compute patcher turn all the gpus in one shot" is there a patcher that can puts all GPU to compute mode in one shot? if so could you provide a link?
Jump to: