Getting ~660 h/s with Ryzen 2600X on stock setting for CN7
Sounds nice.
What ram speed and miner are you using?
Topic: AMD Ryzen hashrate? - page 8. (Read 85917 times)
Sounds nice.
What ram speed and miner are you using?
Getting ~660 h/s with Ryzen 2600X on stock setting for CN7
can any one give me a link for ati pixcel patcher 1.4.7 because i only find 1.4.6
Up to this date, there is no 1.4.7
can any one give me a link for ati pixcel patcher 1.4.7 because i only find 1.4.6
ATIkmdag 1.4.7 is ineffective with win 10 X64 build 1803
Can you detail that a bit please?Ineffective for which GPU & which driver?
I've updated one of my my RX 570 rigs to Win10 1803, using the latest Adrenalin driver and I was able to patch the bios flashed GPUs with ATIkmdag... On my Vega rig I was able to flash the 56 to 64 bios a while ago without Win10 complaining or throwing off error 43's. Wouldn't want 1803 to jopardise that...
GPUs: 3X RX570 all from different manufacturers, 1 has Samsung mem, the 2 others have Elpida/Hynix.
OS: win 10 build 1803 X64
What I do: DDU drivers, restart with basic windows 10 video driver. Install Adrenalin drivers then apply ATIkmdag without reboot. Then restart.
It works with Adrenalin 18.3.4. But with Q2 driver, only the Vega cores of the 2400G are properly setup, all RX 570s have a code 43 error.
With 1803 build, I can't use atiwinflash 2.77, several people have reported the same issue.
I wonder if the Vega cores of the 2400G are messing up the pixel patcher for you.
That's simple, the way things are now, I either can use the Vega cores, or the RX 570s. And almost no miner seems to work with the Vega 11 cores.
ATIkmdag 1.4.7 is ineffective with win 10 X64 build 1803
Can you detail that a bit please?Ineffective for which GPU & which driver?
I've updated one of my my RX 570 rigs to Win10 1803, using the latest Adrenalin driver and I was able to patch the bios flashed GPUs with ATIkmdag... On my Vega rig I was able to flash the 56 to 64 bios a while ago without Win10 complaining or throwing off error 43's. Wouldn't want 1803 to jopardise that...
GPUs: 3X RX570 all from different manufacturers, 1 has Samsung mem, the 2 others have Elpida/Hynix.
OS: win 10 build 1803 X64
What I do: DDU drivers, restart with basic windows 10 video driver. Install Adrenalin drivers then apply ATIkmdag without reboot. Then restart.
It works with Adrenalin 18.3.4. But with Q2 driver, only the Vega cores of the 2400G are properly setup, all RX 570s have a code 43 error.
With 1803 build, I can't use atiwinflash 2.77, several people have reported the same issue.
I wonder if the Vega cores of the 2400G are messing up the pixel patcher for you.
X399 chipset
Ryzen Threadripper 1920x @ 4GHz / mem@3466MHz
CN7 with NH Legacy miner 1.9.0.2, all cores = 900-1050H/s
Ryzen Threadripper 1920x @ 4GHz / mem@3466MHz
CN7 with NH Legacy miner 1.9.0.2, all cores = 900-1050H/s
ATIkmdag 1.4.7 is ineffective with win 10 X64 build 1803
Can you detail that a bit please?Ineffective for which GPU & which driver?
I've updated one of my my RX 570 rigs to Win10 1803, using the latest Adrenalin driver and I was able to patch the bios flashed GPUs with ATIkmdag... On my Vega rig I was able to flash the 56 to 64 bios a while ago without Win10 complaining or throwing off error 43's. Wouldn't want 1803 to jopardise that...
GPUs: 3X RX570 all from different manufacturers, 1 has Samsung mem, the 2 others have Elpida/Hynix.
OS: win 10 build 1803 X64
What I do: DDU drivers, restart with basic windows 10 video driver. Install Adrenalin drivers then apply ATIkmdag without reboot. Then restart.
It works with Adrenalin 18.3.4. But with Q2 driver, only the Vega cores of the 2400G are properly setup, all RX 570s have a code 43 error.
With 1803 build, I can't use atiwinflash 2.77, several people have reported the same issue.
ATIkmdag 1.4.7 is ineffective with win 10 X64 build 1803
Can you detail that a bit please?Ineffective for which GPU & which driver?
I've updated one of my my RX 570 rigs to Win10 1803, using the latest Adrenalin driver and I was able to patch the bios flashed GPUs with ATIkmdag... On my Vega rig I was able to flash the 56 to 64 bios a while ago without Win10 complaining or throwing off error 43's. Wouldn't want 1803 to jopardise that...
Ryzen 5 2400G in auto config with jce_cn_cpu_miner.027
Cryptonight V7: 170H/s max
Cryptonoght heavy: 85H/s max
Impossible to mine with the Vega IGP for the moment. A shame considering my mobo could divert 16GB DDR4 to the Vega 11 cores.
Cryptonight V7: 170H/s max
Cryptonoght heavy: 85H/s max
Impossible to mine with the Vega IGP for the moment. A shame considering my mobo could divert 16GB DDR4 to the Vega 11 cores.
Could you try your 2400G with the new 18.5.1 drivers.
Tried with the 2018 Q2, because of my bios mod I have a code 43 error. So can't mine with (it's my GPUs or vega core). ATIkmdag 1.4.7 is ineffective with win 10 X64 build 1803, so I have to revert to 18.3.4 drivers and disable the Vega core in my mobo bios. Annoying, very annoying.
Ryzen 5 2400G in auto config with jce_cn_cpu_miner.027
Cryptonight V7: 170H/s max
Cryptonoght heavy: 85H/s max
Impossible to mine with the Vega IGP for the moment. A shame considering my mobo could divert 16GB DDR4 to the Vega 11 cores.
Cryptonight V7: 170H/s max
Cryptonoght heavy: 85H/s max
Impossible to mine with the Vega IGP for the moment. A shame considering my mobo could divert 16GB DDR4 to the Vega 11 cores.
Could you try your 2400G with the new 18.5.1 drivers.
R5 1500x Cn7 8 threads : 400-450 H/s
R5 1500x CnHeavy 8 threads : 140-190 H/s
R5 1500x CnHeavy 4 threads : 250-290 H/S
R5 2600 Cn7 6 threads : 500-550 H/s
R5 2600 CnHeavy 6 threads : 200-220 H/S
R5 2600 CnHeavy 12 threads : 120-140 H/S
R5 2600 CnHeavy 4 threads : 280-300 H/S
R5 2600 CnHeavy 8 threads : 160-190 H/S
result on 2600 are a bit weird with CnHeavy
R5 1500x CnHeavy 8 threads : 140-190 H/s
R5 1500x CnHeavy 4 threads : 250-290 H/S
R5 2600 Cn7 6 threads : 500-550 H/s
R5 2600 CnHeavy 6 threads : 200-220 H/S
R5 2600 CnHeavy 12 threads : 120-140 H/S
R5 2600 CnHeavy 4 threads : 280-300 H/S
R5 2600 CnHeavy 8 threads : 160-190 H/S
result on 2600 are a bit weird with CnHeavy
Thats because CN Heavy uses double the amount of Cache, so if all cores use the full amount of cache it gets "overloaded". With JCE you can config so some cores share the cache.
CN Light on the other hand uses half the amount of cache, so you i got 2,2KH/s on my 2700X
Ryzen 5 2400G in auto config with jce_cn_cpu_miner.027
Cryptonight V7: 170H/s max
Cryptonoght heavy: 85H/s max
Impossible to mine with the Vega IGP for the moment. A shame considering my mobo could divert 16GB DDR4 to the Vega 11 cores.
Cryptonight V7: 170H/s max
Cryptonoght heavy: 85H/s max
Impossible to mine with the Vega IGP for the moment. A shame considering my mobo could divert 16GB DDR4 to the Vega 11 cores.
We should add entries to http://monerobenchmarks.info/, the first table is for GPUs, if you scroll down there's one for CPUs
Speaking of which, do you know if those benchmarks are updated for CN7?
Speaking of which, do you know if those benchmarks are updated for CN7?
R5 1500x Cn7 8 threads : 400-450 H/s
R5 1500x CnHeavy 8 threads : 140-190 H/s
R5 1500x CnHeavy 4 threads : 250-290 H/S
R5 2600 Cn7 6 threads : 500-550 H/s
R5 2600 CnHeavy 6 threads : 200-220 H/S
R5 2600 CnHeavy 12 threads : 120-140 H/S
R5 2600 CnHeavy 4 threads : 280-300 H/S
R5 2600 CnHeavy 8 threads : 160-190 H/S
result on 2600 are a bit weird with CnHeavy
R5 1500x CnHeavy 8 threads : 140-190 H/s
R5 1500x CnHeavy 4 threads : 250-290 H/S
R5 2600 Cn7 6 threads : 500-550 H/s
R5 2600 CnHeavy 6 threads : 200-220 H/S
R5 2600 CnHeavy 12 threads : 120-140 H/S
R5 2600 CnHeavy 4 threads : 280-300 H/S
R5 2600 CnHeavy 8 threads : 160-190 H/S
result on 2600 are a bit weird with CnHeavy
Cryptonight V7 I presume.
Just did a build with Ryzen 7 2700X on ASUS PRIME X470
Getting hash rate ~740 on stock settings
Getting hash rate ~740 on stock settings
CPU's often have first dibs on new coins before good GPU miners are made. Getting early mining on a coin before it reaches top 100 is indeed profitable...
Just to share, did some overclocking today on my 2700x. [email protected] (60C, 19C ambient) - 780 H/s cryptonight v7.
Mining does not load this CPU so much, so it is kept barely hot at this settings.
Mining does not load this CPU so much, so it is kept barely hot at this settings.
Power consumption should be too high for that hashrate.
When overclocking, power consumption increase not in a linear way, and you may actually loose money for a modest increase in hashrate.
My Ryzen 1700 does 520H/s at stock speeds (3.2ghz turbo). When overclocked to 3.8 ghz it does around 580-590, but power consumption goes from 65w to 100w...
r5 1600 3800 3466 cl14
CN 560H/s
CN Heavy 250 H/s
CN 560H/s
CN Heavy 250 H/s
Hey man, you mind to share what miner you're using and it's configuration?
I'm using xmr-stak, let me put the configs I have for both algos:
Code:
"cpu_threads_conf" :
[
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 1 },
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 3 },
{ "low_power_mode" : true, "no_prefetch" : true, "affine_to_cpu" : 5 },
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 7 },
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 9 },
{ "low_power_mode" : true, "no_prefetch" : true, "affine_to_cpu" : 11 },
],
[
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 1 },
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 3 },
{ "low_power_mode" : true, "no_prefetch" : true, "affine_to_cpu" : 5 },
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 7 },
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 9 },
{ "low_power_mode" : true, "no_prefetch" : true, "affine_to_cpu" : 11 },
],
Try this config:
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 1 }
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 3 }
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 4 }
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 5 }
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 7 }
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 9 }
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 10 }
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 11
Jump to: