Search content
Sort by
Showing 20 of 54 results by Lermite
Re: [JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+h/s
A tiny bug: the miner keeps getting new jobs from the pool while everything is paused:
Code:
13:54:49 | CPU Thread 3 finds a Share, value 25000
13:54:49 | Accepted by the pool in 42 ms.
13:55:02 | Pause All
13:55:23 | Pool sends a new Job.
13:57:23 | Pool sends a new Job.
14:00:42 | Pool sends a new Job.
14:01:01 | Pool sends a new Job.
14:04:52 | Pool sends a new Job.
14:07:24 | Pool sends a new Job.
14:08:52 | Pool sends a new Job.
14:10:22 | Pool sends a new Job.
14:12:00 | Pool sends a new Job.
14:12:07 | Pool sends a new Job.
14:15:13 | Pool sends a new Job.
14:16:24 | Pool sends a new Job.
14:17:59 | Pool sends a new Job.
14:18:06 | Pool sends a new Job.
14:18:43 | Pool sends a new Job.
14:19:19 | Unpause All
14:19:19 | CPU Thread 5 finds a Share, value 25000
14:19:19 | Accepted by the pool in 41 ms.
13:54:49 | Accepted by the pool in 42 ms.
13:55:02 | Pause All
13:55:23 | Pool sends a new Job.
13:57:23 | Pool sends a new Job.
14:00:42 | Pool sends a new Job.
14:01:01 | Pool sends a new Job.
14:04:52 | Pool sends a new Job.
14:07:24 | Pool sends a new Job.
14:08:52 | Pool sends a new Job.
14:10:22 | Pool sends a new Job.
14:12:00 | Pool sends a new Job.
14:12:07 | Pool sends a new Job.
14:15:13 | Pool sends a new Job.
14:16:24 | Pool sends a new Job.
14:17:59 | Pool sends a new Job.
14:18:06 | Pool sends a new Job.
14:18:43 | Pool sends a new Job.
14:19:19 | Unpause All
14:19:19 | CPU Thread 5 finds a Share, value 25000
14:19:19 | Accepted by the pool in 41 ms.
Re: [JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+h/s
It looks like the pause function has some bug:
I was mining HXV (CN Heavy) with the 0.33b6, with two RX 570 and a Ryzen 1700.
After several hours of mining with stable hashrates, pausing the CPU made the hashrates of both my RX 570 to drop and they didn't get back to their normal values until I restart the miner:
I was mining HXV (CN Heavy) with the 0.33b6, with two RX 570 and a Ryzen 1700.
After several hours of mining with stable hashrates, pausing the CPU made the hashrates of both my RX 570 to drop and they didn't get back to their normal values until I restart the miner:
Code:
13:52:33 | Hashrate CPU Thread 0: 57.66 h/s
13:52:33 | Hashrate CPU Thread 1: 4.41 h/s
13:52:33 | Hashrate CPU Thread 2: 4.43 h/s
13:52:33 | Hashrate CPU Thread 3: 55.15 h/s
13:52:33 | Hashrate CPU Thread 4: 3.88 h/s
13:52:33 | Hashrate CPU Thread 5: 4.28 h/s
13:52:33 | Hashrate CPU Thread 6: 57.14 h/s
13:52:33 | Hashrate CPU Thread 7: 4.19 h/s
13:52:33 | Hashrate CPU Thread 8: 4.40 h/s
13:52:33 | Hashrate CPU Thread 9: 56.17 h/s
13:52:33 | Hashrate CPU Thread 10: 4.11 h/s
13:52:33 | Hashrate CPU Thread 11: 4.39 h/s - Total CPUs: 260.17 h/s
13:52:33 | Hashrate GPU Thread 12: 476.62 h/s
13:52:33 | Hashrate GPU Thread 13: 476.70 h/s - Total GPU 0: 953.31 h/s
13:52:33 | Hashrate GPU Thread 14: 470.81 h/s
13:52:33 | Hashrate GPU Thread 15: 470.81 h/s - Total GPU 1: 941.62 h/s
13:52:34 | Total: 2155.09 h/s - Max: 2235.68 h/s
13:52:36 | GPU 1 Thread 14 Lane 419 finds a Share, value 78000
13:52:36 | Accepted by the pool in 90 ms.
13:53:27 | GPU 0: Temp: 61C - Fan: 17% -- Shares: Good: 176 Bad: 0
13:53:27 | GPU 1: Temp: 56C - Fan: 17% -- Shares: Good: 198 Bad: 0
13:54:23 | Pool sends a new Job.
13:54:43 | GPU 1 Thread 15 Lane 329 finds a Share, value 78000
13:54:43 | Accepted by the pool in 78 ms.
13:55:06 | Pause CPUs
13:56:07 | Hashrate CPU Thread 0: 0.00 h/s
13:56:07 | Hashrate CPU Thread 1: 0.00 h/s
13:56:07 | Hashrate CPU Thread 2: 0.00 h/s
13:56:07 | Hashrate CPU Thread 3: 0.00 h/s
13:56:07 | Hashrate CPU Thread 4: 0.00 h/s
13:56:07 | Hashrate CPU Thread 5: 0.00 h/s
13:56:07 | Hashrate CPU Thread 6: 0.00 h/s
13:56:07 | Hashrate CPU Thread 7: 0.00 h/s
13:56:07 | Hashrate CPU Thread 8: 0.00 h/s
13:56:07 | Hashrate CPU Thread 9: 0.00 h/s
13:56:07 | Hashrate CPU Thread 10: 0.00 h/s
13:56:07 | Hashrate CPU Thread 11: 0.00 h/s - Total CPUs: 0.00 h/s
13:56:07 | Hashrate GPU Thread 12: 464.50 h/s
13:56:07 | Hashrate GPU Thread 13: 464.23 h/s - Total GPU 0: 928.72 h/s
13:56:07 | Hashrate GPU Thread 14: 452.25 h/s
13:56:07 | Hashrate GPU Thread 15: 452.25 h/s - Total GPU 1: 904.49 h/s
13:56:07 | Total: 1833.21 h/s - Max: 2235.68 h/s
13:52:33 | Hashrate CPU Thread 1: 4.41 h/s
13:52:33 | Hashrate CPU Thread 2: 4.43 h/s
13:52:33 | Hashrate CPU Thread 3: 55.15 h/s
13:52:33 | Hashrate CPU Thread 4: 3.88 h/s
13:52:33 | Hashrate CPU Thread 5: 4.28 h/s
13:52:33 | Hashrate CPU Thread 6: 57.14 h/s
13:52:33 | Hashrate CPU Thread 7: 4.19 h/s
13:52:33 | Hashrate CPU Thread 8: 4.40 h/s
13:52:33 | Hashrate CPU Thread 9: 56.17 h/s
13:52:33 | Hashrate CPU Thread 10: 4.11 h/s
13:52:33 | Hashrate CPU Thread 11: 4.39 h/s - Total CPUs: 260.17 h/s
13:52:33 | Hashrate GPU Thread 12: 476.62 h/s
13:52:33 | Hashrate GPU Thread 13: 476.70 h/s - Total GPU 0: 953.31 h/s
13:52:33 | Hashrate GPU Thread 14: 470.81 h/s
13:52:33 | Hashrate GPU Thread 15: 470.81 h/s - Total GPU 1: 941.62 h/s
13:52:34 | Total: 2155.09 h/s - Max: 2235.68 h/s
13:52:36 | GPU 1 Thread 14 Lane 419 finds a Share, value 78000
13:52:36 | Accepted by the pool in 90 ms.
13:53:27 | GPU 0: Temp: 61C - Fan: 17% -- Shares: Good: 176 Bad: 0
13:53:27 | GPU 1: Temp: 56C - Fan: 17% -- Shares: Good: 198 Bad: 0
13:54:23 | Pool sends a new Job.
13:54:43 | GPU 1 Thread 15 Lane 329 finds a Share, value 78000
13:54:43 | Accepted by the pool in 78 ms.
13:55:06 | Pause CPUs
13:56:07 | Hashrate CPU Thread 0: 0.00 h/s
13:56:07 | Hashrate CPU Thread 1: 0.00 h/s
13:56:07 | Hashrate CPU Thread 2: 0.00 h/s
13:56:07 | Hashrate CPU Thread 3: 0.00 h/s
13:56:07 | Hashrate CPU Thread 4: 0.00 h/s
13:56:07 | Hashrate CPU Thread 5: 0.00 h/s
13:56:07 | Hashrate CPU Thread 6: 0.00 h/s
13:56:07 | Hashrate CPU Thread 7: 0.00 h/s
13:56:07 | Hashrate CPU Thread 8: 0.00 h/s
13:56:07 | Hashrate CPU Thread 9: 0.00 h/s
13:56:07 | Hashrate CPU Thread 10: 0.00 h/s
13:56:07 | Hashrate CPU Thread 11: 0.00 h/s - Total CPUs: 0.00 h/s
13:56:07 | Hashrate GPU Thread 12: 464.50 h/s
13:56:07 | Hashrate GPU Thread 13: 464.23 h/s - Total GPU 0: 928.72 h/s
13:56:07 | Hashrate GPU Thread 14: 452.25 h/s
13:56:07 | Hashrate GPU Thread 15: 452.25 h/s - Total GPU 1: 904.49 h/s
13:56:07 | Total: 1833.21 h/s - Max: 2235.68 h/s
Re: [JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+ h/s
I currently use SRB to mine XMR.
The timings of both my RX 570 are optimized with Polaris Bios Editor 1.6.7 which gives more performance than SRB Polaris.
RX 570 4G Samsung
GPU 1280 MHz 990 mV
Memory 2110 990 mV
989 h/s
RX 570 8G Micron
GPU 1280 Hz 980 mV
Memory 2220 Mhz 980 mV
977 h/s
Their config for SRB Miner is pretty simple:
{ "id": 0, "intensity": 0, "threads": 2},
{ "id": 1, "intensity": 0, "threads": 2},
The timings of both my RX 570 are optimized with Polaris Bios Editor 1.6.7 which gives more performance than SRB Polaris.
RX 570 4G Samsung
GPU 1280 MHz 990 mV
Memory 2110 990 mV
989 h/s
RX 570 8G Micron
GPU 1280 Hz 980 mV
Memory 2220 Mhz 980 mV
977 h/s
Their config for SRB Miner is pretty simple:
{ "id": 0, "intensity": 0, "threads": 2},
{ "id": 1, "intensity": 0, "threads": 2},
Re: [JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+ h/s
I still have hashrate droops with the 0.33b6.
One has just occurs on my RX 570 4G after two hours of mining CN V8: from 1100 to 965 h/s.
It's the same hashrate droop I had with the b4 and b5 versions.
One has just occurs on my RX 570 4G after two hours of mining CN V8: from 1100 to 965 h/s.
It's the same hashrate droop I had with the b4 and b5 versions.
Re: [JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+ h/s
Maybe you forgot that the 2+% fee is only for heavy algo and heavy based algos. For v8 and all other algos based on v7 or v8 fee is still 0.9%.
The 2.5% fee is applied to CN Saber too.
Re: [JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+ h/s
The hashrate instability issue doesn't affect only CN V8 and Heavy.
It also concerns CN Fast (MSR) with the 0.33b4.
One of my RX 570 hashratr went from ~1200 to ~900 h/s.
That made me to switch to the 0.33b3 which seems to work fine so far but I yet have to compare its hashrates with SRB's.
It also concerns CN Fast (MSR) with the 0.33b4.
One of my RX 570 hashratr went from ~1200 to ~900 h/s.
That made me to switch to the 0.33b3 which seems to work fine so far but I yet have to compare its hashrates with SRB's.
Re: [JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+ h/s
JCE, I have vega rigs only and was thinking to move all my rigs from cn v8 (TMR) to heavy algos to see if i can reduce power consumption a bit for similar profit. Can I go with current version of miner, or wait for b6? You plan to introduce some changes for Vegas or I can start changing slowly?
The b5 brings a big improvement on CH Heavy but its hashrates are unstable.
That's why you should wait for the coming b6.
Re: [JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+ h/s
You (or someone else with proper skills) need to bake a proper x16r miner for AMD. Anything so far has been grossly underwhelming.
Did you try Wildrig on X16R?
https://bitcointalk.org/index.php?topic=5023676.0
I've just begun testing it and I don't know yet if it's worth.
Re: [JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+ h/s
Hmmm I think I have an idea, I might have left some CPU-config code in the file. Editing that away.
I assume the conf above is ths only parameters you've set? Nothing else?
Here is my whole config for CN Heavy:I assume the conf above is ths only parameters you've set? Nothing else?
"GPU 0" is the RX 570 4G:
Code:
"cpu_threads_conf" :
[
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 1, "use_cache" : true },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 2, "use_cache" : false },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 3, "use_cache" : false },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 5, "use_cache" : true },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 6, "use_cache" : false },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 7, "use_cache" : false },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 9, "use_cache" : true },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 10, "use_cache" : false },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 11, "use_cache" : false },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 13, "use_cache" : true },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 14, "use_cache" : false },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 15, "use_cache" : false },
],
"gpu_threads_conf" :
[
{ "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 0, "multi_hash": 480 },
{ "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 0, "multi_hash": 480 },
{ "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 1, "multi_hash": 496 },
{ "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 1, "multi_hash": 496 },
{ "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 2, "multi_hash": 464 },
{ "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 2, "multi_hash": 464 },
]
[
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 1, "use_cache" : true },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 2, "use_cache" : false },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 3, "use_cache" : false },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 5, "use_cache" : true },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 6, "use_cache" : false },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 7, "use_cache" : false },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 9, "use_cache" : true },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 10, "use_cache" : false },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 11, "use_cache" : false },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 13, "use_cache" : true },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 14, "use_cache" : false },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 15, "use_cache" : false },
],
"gpu_threads_conf" :
[
{ "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 0, "multi_hash": 480 },
{ "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 0, "multi_hash": 480 },
{ "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 1, "multi_hash": 496 },
{ "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 1, "multi_hash": 496 },
{ "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 2, "multi_hash": 464 },
{ "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 2, "multi_hash": 464 },
]
https://puissanceled.com/vrac/OverdriveNTool_CG6_CNH.png
https://puissanceled.com/vrac/GPUZ_CG6_CNH.png
I don't know why this forum replaces my images by link.
Some possible explanations of your issue:
- your card "Workload" value is "Graphics" instead of "Compute"
- Crossfire is enabled
- The index in your config file doesn't point the right card.
The JCE miner is provided with a file "probe.bat". You should launch it because it displays all the mining capable devices, including the graphic cards in their index order.
Re: [JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+ h/s
Multihash 480? Wow that's quite a bit lower than what I was trying to tweak with. No wonder it wasn't even starting.
Ok so that seems to work now... however speeds are terrible. avg 270 h/s per 570. What am I doing wrong?
I have no clue.Ok so that seems to work now... however speeds are terrible. avg 270 h/s per 570. What am I doing wrong?
Mine is mining XHV at 945 h/s with:
GPU clock: 1380 MHz
GPU voltage: 1000 mV
Mem clock: 2110 MHz
Timing from PBE 1.6.7 and Samsung memory.
Re: [JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+ h/s
Is there any known problem with RX570 (4GB) initialisation on auto mode?
Can anybody share a working manual config for CN_Haven algo please?
Can anybody share a working manual config for CN_Haven algo please?
Here is mine:
Code:
{ "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 0, "multi_hash": 480 },
{ "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 0, "multi_hash": 480 },
{ "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 0, "multi_hash": 480 },
Re: [JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+ h/s
I have a weird issue with the 0.33b5 on the CN V8 (XMR).
Both my two RX 570 start running at ~1005 h/s, which is nice.
But after a random time, from 2 minutes to several hours, one of the cards (randomly again) has his hashrate suddenly dropping to ~960 h/s and it stays at this value until the miner is restarted.
If my settings were wrong, such with a too high multi-hash, the hashrate would drop always after the same duration, pretty soon after the miner is started, and not randomly as it happens to both my cards.
Both my two RX 570 start running at ~1005 h/s, which is nice.
But after a random time, from 2 minutes to several hours, one of the cards (randomly again) has his hashrate suddenly dropping to ~960 h/s and it stays at this value until the miner is restarted.
If my settings were wrong, such with a too high multi-hash, the hashrate would drop always after the same duration, pretty soon after the miner is started, and not randomly as it happens to both my cards.
and your config?
Code:
"cpu_threads_conf":
[
{ "cpu_architecture": "ryzen", "affine_to_cpu": 1, "use_cache": true, "multi_hash": 1 },
{ "cpu_architecture": "ryzen", "affine_to_cpu": 3, "use_cache": true, "multi_hash": 1 },
{ "cpu_architecture": "ryzen", "affine_to_cpu": 5, "use_cache": true, "multi_hash": 1 },
{ "cpu_architecture": "ryzen", "affine_to_cpu": 7, "use_cache": true, "multi_hash": 1 },
{ "cpu_architecture": "ryzen", "affine_to_cpu": 9, "use_cache": true, "multi_hash": 1 },
{ "cpu_architecture": "ryzen", "affine_to_cpu": 11, "use_cache": true, "multi_hash": 1 },
{ "cpu_architecture": "ryzen", "affine_to_cpu": 13, "use_cache": true, "multi_hash": 1 },
{ "cpu_architecture": "ryzen", "affine_to_cpu": 15, "use_cache": true, "multi_hash": 1 },
],
"gpu_threads_conf":
[
{ "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 0, "multi_hash": 976 },
{ "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 0, "multi_hash": 976 },
{ "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 1, "multi_hash": 1008 },
{ "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 1, "multi_hash": 1008 },
]
[
{ "cpu_architecture": "ryzen", "affine_to_cpu": 1, "use_cache": true, "multi_hash": 1 },
{ "cpu_architecture": "ryzen", "affine_to_cpu": 3, "use_cache": true, "multi_hash": 1 },
{ "cpu_architecture": "ryzen", "affine_to_cpu": 5, "use_cache": true, "multi_hash": 1 },
{ "cpu_architecture": "ryzen", "affine_to_cpu": 7, "use_cache": true, "multi_hash": 1 },
{ "cpu_architecture": "ryzen", "affine_to_cpu": 9, "use_cache": true, "multi_hash": 1 },
{ "cpu_architecture": "ryzen", "affine_to_cpu": 11, "use_cache": true, "multi_hash": 1 },
{ "cpu_architecture": "ryzen", "affine_to_cpu": 13, "use_cache": true, "multi_hash": 1 },
{ "cpu_architecture": "ryzen", "affine_to_cpu": 15, "use_cache": true, "multi_hash": 1 },
],
"gpu_threads_conf":
[
{ "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 0, "multi_hash": 976 },
{ "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 0, "multi_hash": 976 },
{ "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 1, "multi_hash": 1008 },
{ "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 1, "multi_hash": 1008 },
]
BTW: after a longer use, the hashrate of my 4 GB (GPU 0) remains stable around 1010 h/s but the 8 GB (GPU 1)'s one ends up to 961 h/s.
But I didn't try to optimize the settings yet with the 0.33b4.
Great job with the 0.33b4 
GPU 0: RX 570 4G Samsung
GPU 1: RX 570 8G Micron
You're now far beyond SRB, and your miner works fine, unlike TRM that only manage to crash my graphic cards.
GPU 0: RX 570 4G Samsung
GPU 1: RX 570 8G Micron
Code:
13:00:28 | Hashrate CPU Thread 0: 81.44 h/s
13:00:28 | Hashrate CPU Thread 1: 82.17 h/s
13:00:28 | Hashrate CPU Thread 2: 82.37 h/s
13:00:28 | Hashrate CPU Thread 3: 82.37 h/s
13:00:28 | Hashrate CPU Thread 4: 83.51 h/s
13:00:28 | Hashrate CPU Thread 5: 83.66 h/s
13:00:28 | Hashrate CPU Thread 6: 83.28 h/s
13:00:28 | Hashrate CPU Thread 7: 83.34 h/s - Total CPUs: 662.11 h/s
13:00:28 | Hashrate GPU Thread 8: 505.92 h/s
13:00:28 | Hashrate GPU Thread 9: 505.83 h/s - Total GPU 0: 1011.74 h/s
13:00:28 | Hashrate GPU Thread 10: 502.48 h/s
13:00:28 | Hashrate GPU Thread 11: 502.48 h/s - Total GPU 1: 1004.95 h/s
13:00:28 | Hashrate CPU Thread 1: 82.17 h/s
13:00:28 | Hashrate CPU Thread 2: 82.37 h/s
13:00:28 | Hashrate CPU Thread 3: 82.37 h/s
13:00:28 | Hashrate CPU Thread 4: 83.51 h/s
13:00:28 | Hashrate CPU Thread 5: 83.66 h/s
13:00:28 | Hashrate CPU Thread 6: 83.28 h/s
13:00:28 | Hashrate CPU Thread 7: 83.34 h/s - Total CPUs: 662.11 h/s
13:00:28 | Hashrate GPU Thread 8: 505.92 h/s
13:00:28 | Hashrate GPU Thread 9: 505.83 h/s - Total GPU 0: 1011.74 h/s
13:00:28 | Hashrate GPU Thread 10: 502.48 h/s
13:00:28 | Hashrate GPU Thread 11: 502.48 h/s - Total GPU 1: 1004.95 h/s
You're now far beyond SRB, and your miner works fine, unlike TRM that only manage to crash my graphic cards.
The latest GPU miner is jce_cn_gpu_miner.032q.zip?
On the first post of this thread the latest is 032p version.
On the first post of this thread the latest is 032p version.
What matter are the available versions on the Github page: https://github.com/jceminer/cn_gpu_miner
You explained the cpu fee which wasn't voided while the cpu is paused.
Is this bug corrected in the 0.32q?
It bothers me because having to stop then restart the mining only to disabled the cpu is much longer than pausing it, but it's still worth if it avoids some buggy fees.
Is this bug corrected in the 0.32q?
It bothers me because having to stop then restart the mining only to disabled the cpu is much longer than pausing it, but it's still worth if it avoids some buggy fees.
edit:
0.32p GPU is online
0.32p GPU is online
I can't find it on your Github page: https://github.com/jceminer/cn_gpu_miner
Did I miss something?
There is an issue with APUs and bios modded GPUs, they can't go along on win 10 build 1803. There is a driver issue caused by win 10 (error 43). You must keep your original bios to use the Vega cores from Ryzen G series.
This error 43 occurring in case of a modded bios has nothing to do with JCE Miner.
The culprit is the AMD graphic driver which rejects every modded bios.
The workaround is simple: The tiny application atikmdag-patcher patches the driver to make it to accept any bios, bypassing its signature inspection.
This patch is required after each install or update of the graphic drivers, if at least one GPU has a modded bios.