Search content
Sort by
Showing 20 of 26 results by _ap_
Re: [JCE]Fast & stable CN/v8/Heavy/Tube/XHV miner, CPU+GPU, Vega56 1800+ RX580 1200+
crash: please look at your antivirus and related (antispyware...) it may have corrupt/quarantined the binary since it's always detected as a virus, like all other miners. The attrib trick is documented and works this way since day one.
Maybe try to run the CPU 32-bits versions, it's a lot less detected. Just to test, as it mines slower.
Maybe try to run the CPU 32-bits versions, it's a lot less detected. Just to test, as it mines slower.
thx for your answer.
my antivirus quarantined it immediately, so my first thing was to add to the exceptions. now i downloaded again, but nothing changed.
the cpu 32 bit version works, but after I close the program, crash.
the gpu version available only 64 bit, right?
*update
problem solved. av exceptions isn't enough. I added the miner to the trusted files, now everything ok.
Re: [JCE]Fast & stable CN/v8/Heavy/Tube/XHV miner, CPU+GPU, Vega56 1800+ RX580 1200+
i tried the gpu version on my laptop (win7 64 bit) but the attrib.exe always crashed on start. then i tried the cpu version, but the result are same.
GPU version of miner works only on Windows 8.1+Re: [JCE]Fast & stable CN/v8/Heavy/Tube/XHV miner, CPU+GPU, Vega56 1800+ RX580 1200+
i tried the gpu version on my laptop (win7 64 bit) but the attrib.exe always crashed on start. then i tried the cpu version, but the result are same.
this is the win's log:
this is the win's log:
Code:
Problem signature:
Problem event name: APPCRASH
Application Name: attrib.exe
Application Version: 6.1.7600.16385
Application Time Stamp: 4a5bc262
Error Module Name: ntdll.dll
Error Module Version: 6.1.7601.24024
Error Module Time Stamp: 5a58e571
Exception code: c0000026
Exception - offset: 00000000000c8a08
Operating System Version: 6.1.7601.2.1.0.256.1
Locale identifier: 1038
More information 1: 18d9
More information 2: 18d92874322adbc162708e4fec1a6d55
More information 3: 81d9
More information 4: 81d9b1ae568ccfbf94a4305bb26177ca
Problem event name: APPCRASH
Application Name: attrib.exe
Application Version: 6.1.7600.16385
Application Time Stamp: 4a5bc262
Error Module Name: ntdll.dll
Error Module Version: 6.1.7601.24024
Error Module Time Stamp: 5a58e571
Exception code: c0000026
Exception - offset: 00000000000c8a08
Operating System Version: 6.1.7601.2.1.0.256.1
Locale identifier: 1038
More information 1: 18d9
More information 2: 18d92874322adbc162708e4fec1a6d55
More information 3: 81d9
More information 4: 81d9b1ae568ccfbf94a4305bb26177ca
Re: [JCE]Fast & stable CN-Heavy/Tube/XHV miner, low power, Vega56 1800+, RX580 1200+
My 580 card has only few accepted shares. The hashrate is ok, the consumption, the core and memory clock are ordinary. Apparently everything is fine. But the accepted shares is very low.
What can cause this?
What is you Rx580 multihash setting ? and does you use 1 thread or 2 threads in config file ?
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 2, "multi_hash":944 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 2, "multi_hash":944 },
But i think the problem isn't here. Everything worked perfekt for months with these values. This error occured only in the last day.
2 hours ago I restarted the rig, since then everything is okay.
I said: this is a strange problem
Try to log and send it here it will be easier for JCE to look over it
@Unclwish : in the config line after Alpha 64 there is Beta 8. Tried Beta 16
unfortunately i haven't log. i disable it :-S
Re: [JCE]Fast & stable CN-Heavy/Tube/XHV miner, low power, Vega56 1800+, RX580 1200+
My 580 card has only few accepted shares. The hashrate is ok, the consumption, the core and memory clock are ordinary. Apparently everything is fine. But the accepted shares is very low.
What can cause this?
What is you Rx580 multihash setting ? and does you use 1 thread or 2 threads in config file ?
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 2, "multi_hash":944 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 2, "multi_hash":944 },
But i think the problem isn't here. Everything worked perfekt for months with these values. This error occured only in the last day.
2 hours ago I restarted the rig, since then everything is okay.
I said: this is a strange problem
Re: [JCE]Fast & stable CN-Heavy/Tube/XHV miner, low power, Vega56 1800+, RX580 1200+
Hi!
I have a strange "problem". I have 2 rx570 (4gb) and 1 rx580 (8gb).
My miner's last 24 hours statistic is this:
rx570 = 940H/s (with samsung memory)
rx570 = 930H/s (with elpida memory)
rx580 = 1100H/s
Summary (with my cpu) 2995-3005 H/s.
I have 1,1,2 ignored and 0 invalid shares in this time.
My pool say, my hasrate is in the last 24/12/6/2/1 hours: 2000-2100H/s.
In the miner detailed statistic I saw this (accepted/invalid/rejected shares)
rx 570: 1301/1/0
rx570: 1292/1/0
rx580: 428/2/0
My 580 card has only few accepted shares. The hashrate is ok, the consumption, the core and memory clock are ordinary. Apparently everything is fine. But the accepted shares is very low.
What can cause this?
I have a strange "problem". I have 2 rx570 (4gb) and 1 rx580 (8gb).
My miner's last 24 hours statistic is this:
rx570 = 940H/s (with samsung memory)
rx570 = 930H/s (with elpida memory)
rx580 = 1100H/s
Summary (with my cpu) 2995-3005 H/s.
I have 1,1,2 ignored and 0 invalid shares in this time.
My pool say, my hasrate is in the last 24/12/6/2/1 hours: 2000-2100H/s.
In the miner detailed statistic I saw this (accepted/invalid/rejected shares)
rx 570: 1301/1/0
rx570: 1292/1/0
rx580: 428/2/0
My 580 card has only few accepted shares. The hashrate is ok, the consumption, the core and memory clock are ordinary. Apparently everything is fine. But the accepted shares is very low.
What can cause this?
Re: [JCE] Ultrafast CN-Heavy/Tube/XHV miner, low power, Vega56 1750+h/s
forget the b7 and try the new experimental (read: very untested) B-sync GPU
That's the lone .exe in the github page.
1. Stable and fast hashrate
2. new parameter --no-monitor to disable fan/temp monitoring (the purple report)
3. various optims for some cards and some algos, expect about +0.5%
4. Fees still 0.9%
so far it burns like fire on my rigs, i hope it really fixes all the hashrate and warmup problems.
That's the lone .exe in the github page.
1. Stable and fast hashrate
2. new parameter --no-monitor to disable fan/temp monitoring (the purple report)
3. various optims for some cards and some algos, expect about +0.5%
4. Fees still 0.9%
so far it burns like fire on my rigs, i hope it really fixes all the hashrate and warmup problems.
with:
- cpu: working perfect
- integral gpu: working perfect
- 8gb rx 580: working perfect
- 4gb rx570: after pool login, the miner stopped and i got: "Press any key to continue..." message
my config: "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 3, "multi_hash":944 },
any idea?
*update: algo = bittube
thanks!
4gb GPU multi_hash should be lower for 2 thread about 464 or 480.
yes, only 1 thread, and this config worked with all previous version.
I tried, but nothing. Then I switched to 2 thread mode, and with 464 values working now. Before the 2 thread mode didn't work.. :-O
This version is very stable. This is the best version so far.
Re: [JCE] Ultrafast CN-Heavy/Tube/XHV miner, low power, Vega56 1750+h/s
forget the b7 and try the new experimental (read: very untested) B-sync GPU
That's the lone .exe in the github page.
1. Stable and fast hashrate
2. new parameter --no-monitor to disable fan/temp monitoring (the purple report)
3. various optims for some cards and some algos, expect about +0.5%
4. Fees still 0.9%
so far it burns like fire on my rigs, i hope it really fixes all the hashrate and warmup problems.
That's the lone .exe in the github page.
1. Stable and fast hashrate
2. new parameter --no-monitor to disable fan/temp monitoring (the purple report)
3. various optims for some cards and some algos, expect about +0.5%
4. Fees still 0.9%
so far it burns like fire on my rigs, i hope it really fixes all the hashrate and warmup problems.
with:
- cpu: working perfect
- integral gpu: working perfect
- 8gb rx 580: working perfect
- 4gb rx570: after pool login, the miner stopped and i got: "Press any key to continue..." message
my config: "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 3, "multi_hash":944 },
any idea?
*update: algo = bittube
thanks!
4gb GPU multi_hash should be lower for 2 thread about 464 or 480.
yes, only 1 thread, and this config worked with all previous version.
Re: [JCE] Ultrafast CN-Heavy/Tube/XHV miner, low power, Vega56 1750+h/s
forget the b7 and try the new experimental (read: very untested) B-sync GPU
That's the lone .exe in the github page.
1. Stable and fast hashrate
2. new parameter --no-monitor to disable fan/temp monitoring (the purple report)
3. various optims for some cards and some algos, expect about +0.5%
4. Fees still 0.9%
so far it burns like fire on my rigs, i hope it really fixes all the hashrate and warmup problems.
That's the lone .exe in the github page.
1. Stable and fast hashrate
2. new parameter --no-monitor to disable fan/temp monitoring (the purple report)
3. various optims for some cards and some algos, expect about +0.5%
4. Fees still 0.9%
so far it burns like fire on my rigs, i hope it really fixes all the hashrate and warmup problems.
with:
- cpu: working perfect
- integral gpu: working perfect
- 8gb rx 580: working perfect
- 4gb rx570: after pool login, the miner stopped and i got: "Press any key to continue..." message
my config: "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 3, "multi_hash":944 },
any idea?
*update: algo = bittube
thanks!
many thanks, it's working now!
what steps recommend increase the multi hash? 580 hashrate is very good (prev miner: 930H/s, jce now: 1030H/s), but the 570 a little bit slow (prev miner: 760H/s, jce now: 680H/s)
All, as I thought... Miner used settings for 8gb card on 4gb card...what steps recommend increase the multi hash? 580 hashrate is very good (prev miner: 930H/s, jce now: 1030H/s), but the 570 a little bit slow (prev miner: 760H/s, jce now: 680H/s)
Optimal settings... For 8Gb try
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":944 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":944 },
for 4Gb:
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":472 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":472 },
If with 472 will be error try one of 472 lower to 464.
Thanks. I will try..
Code:
Detecting OpenCL-capable GPUs...
Found GPU 0, with:
Vendor: Intel
Processor: Intel(R) HD Graphics 510
Device: ff:ff
Compute-Units: 12
Cache Memory: 256 KB
Local Memory: 64 KB
Global Memory: 1603 MB
Addressing: 64-bits
Found GPU 1, with:
Vendor: AMD
Processor: Ellesmere
Device: 02:00
Compute-Units: 36
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 8192 MB
Addressing: 64-bits
Found GPU 2, with:
Vendor: AMD
Processor: Ellesmere
Device: 04:00
Compute-Units: 32
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 4096 MB
Addressing: 64-bits
Preparing 4 Mining Threads...
+-- Thread 0 config ------------------------+
| Run on GPU: 1 |
| Multi-hash: 864 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 16 |
+-------------------------------------------+
+-- Thread 1 config ------------------------+
| Run on GPU: 1 |
| Multi-hash: 864 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 16 |
+-------------------------------------------+
+-- Thread 2 config ------------------------+
| Run on GPU: 2 |
| Multi-hash: 864 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 16 |
+-------------------------------------------+
+-- Thread 3 config ------------------------+
| Run on GPU: 2 |
| Multi-hash: 864 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 16 |
+-------------------------------------------+
Cryptonight Variation: Cryptonight-BitTube v2 of July-2018
Low intensity.
Starting GPU Thread 0, on GPU 1
Created OpenCL Context for GPU 1 at 0000025e0971fba0
Created OpenCL Thread 0 Command-Queue for GPU 1 at 0000025e0971fd00
Scratchpad Allocation success for OpenCL Thread 0
Allocating big 3456MB scratchpad for OpenCL Thread 0...
Compiling kernels of OpenCL Thread 0...
Kernels of OpenCL Thread 0 compiled.
Starting GPU Thread 1, on GPU 1
Created OpenCL Thread 1 Command-Queue for GPU 1 at 0000025e0e028ec0
Scratchpad Allocation success for OpenCL Thread 1
Allocating big 3456MB scratchpad for OpenCL Thread 1...
Compiling kernels of OpenCL Thread 1...
Kernels of OpenCL Thread 1 compiled.
Starting GPU Thread 2, on GPU 2
Created OpenCL Context for GPU 2 at 0000025e09869370
Created OpenCL Thread 2 Command-Queue for GPU 2 at 0000025e0dd59790
Scratchpad Allocation success for OpenCL Thread 2
Allocating big 3456MB scratchpad for OpenCL Thread 2...
Compiling kernels of OpenCL Thread 2...
Kernels of OpenCL Thread 2 compiled.
Starting GPU Thread 3, on GPU 2
Created OpenCL Thread 3 Command-Queue for GPU 2 at 0000025e0dd59cd0
Scratchpad Allocation success for OpenCL Thread 3
Allocating big 3456MB scratchpad for OpenCL Thread 3...
Compiling kernels of OpenCL Thread 3...
Kernels of OpenCL Thread 3 compiled.
22:49:05 | BitTube (TUBE) Mining session starts!
22:49:05 | GPU Compute allocation starts at 80% and reaches 100% after ~5min,
22:49:05 | during this time, the hashrate may be unstable and inconsistent.
22:49:05 | Let the miner warm-up if you're tuning for performance.
22:49:06 | Connecting to mining pool tube.ingest.cryptoknight.cc:5631 ...
22:49:06 | Connected to pool. Now logging in...
22:49:06 | Successfuly logged as bxcAUWyAktcLcsdGA1YX7SLkqU3xjCt348An7KosnkCRfE3RoMZa3SYWyCJsp1C34oH3dyJ5dqFwigmfMbGZ844W1rRBDXW4R.50000
22:49:06 | Pool changes Difficulty to 50000.
22:49:19 | GPU 1 Thread 1 Lane 414 finds a Share, value 50000
22:49:19 | Accepted by the pool in 358 ms.
22:49:32 | GPU 1 Thread 1 Lane 785 finds a Share, value 50000
22:49:32 | Accepted by the pool in 388 ms.
22:49:36 | Hashrate GPU Thread 0: 335.78 h/s
22:49:36 | Hashrate GPU Thread 1: 398.09 h/s - Total GPU 1: 733.86 h/s
22:49:36 | Hashrate GPU Thread 2: 0.00 h/s
22:49:36 | Hashrate GPU Thread 3: 0.00 h/s - Total GPU 2: 0.00 h/s
22:49:36 | Total: 733.86 h/s - Max: 733.86 h/s
22:49:37 | Hashrate GPU Thread 0: 335.78 h/s
22:49:37 | Hashrate GPU Thread 1: 398.09 h/s - Total GPU 1: 733.86 h/s
22:49:37 | Hashrate GPU Thread 2: 0.00 h/s
22:49:37 | Hashrate GPU Thread 3: 0.00 h/s - Total GPU 2: 0.00 h/s
22:49:37 | Total: 733.86 h/s - Max: 733.86 h/s
22:49:54 | GPU 1: Temp: 48C - Fan: 0% -- Shares: Good: 2 Bad: 0
22:49:55 | GPU 2: Temp: 44C - Fan: 0% -- Shares: Good: 0 Bad: 0
Found GPU 0, with:
Vendor: Intel
Processor: Intel(R) HD Graphics 510
Device: ff:ff
Compute-Units: 12
Cache Memory: 256 KB
Local Memory: 64 KB
Global Memory: 1603 MB
Addressing: 64-bits
Found GPU 1, with:
Vendor: AMD
Processor: Ellesmere
Device: 02:00
Compute-Units: 36
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 8192 MB
Addressing: 64-bits
Found GPU 2, with:
Vendor: AMD
Processor: Ellesmere
Device: 04:00
Compute-Units: 32
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 4096 MB
Addressing: 64-bits
Preparing 4 Mining Threads...
+-- Thread 0 config ------------------------+
| Run on GPU: 1 |
| Multi-hash: 864 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 16 |
+-------------------------------------------+
+-- Thread 1 config ------------------------+
| Run on GPU: 1 |
| Multi-hash: 864 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 16 |
+-------------------------------------------+
+-- Thread 2 config ------------------------+
| Run on GPU: 2 |
| Multi-hash: 864 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 16 |
+-------------------------------------------+
+-- Thread 3 config ------------------------+
| Run on GPU: 2 |
| Multi-hash: 864 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 16 |
+-------------------------------------------+
Cryptonight Variation: Cryptonight-BitTube v2 of July-2018
Low intensity.
Starting GPU Thread 0, on GPU 1
Created OpenCL Context for GPU 1 at 0000025e0971fba0
Created OpenCL Thread 0 Command-Queue for GPU 1 at 0000025e0971fd00
Scratchpad Allocation success for OpenCL Thread 0
Allocating big 3456MB scratchpad for OpenCL Thread 0...
Compiling kernels of OpenCL Thread 0...
Kernels of OpenCL Thread 0 compiled.
Starting GPU Thread 1, on GPU 1
Created OpenCL Thread 1 Command-Queue for GPU 1 at 0000025e0e028ec0
Scratchpad Allocation success for OpenCL Thread 1
Allocating big 3456MB scratchpad for OpenCL Thread 1...
Compiling kernels of OpenCL Thread 1...
Kernels of OpenCL Thread 1 compiled.
Starting GPU Thread 2, on GPU 2
Created OpenCL Context for GPU 2 at 0000025e09869370
Created OpenCL Thread 2 Command-Queue for GPU 2 at 0000025e0dd59790
Scratchpad Allocation success for OpenCL Thread 2
Allocating big 3456MB scratchpad for OpenCL Thread 2...
Compiling kernels of OpenCL Thread 2...
Kernels of OpenCL Thread 2 compiled.
Starting GPU Thread 3, on GPU 2
Created OpenCL Thread 3 Command-Queue for GPU 2 at 0000025e0dd59cd0
Scratchpad Allocation success for OpenCL Thread 3
Allocating big 3456MB scratchpad for OpenCL Thread 3...
Compiling kernels of OpenCL Thread 3...
Kernels of OpenCL Thread 3 compiled.
22:49:05 | BitTube (TUBE) Mining session starts!
22:49:05 | GPU Compute allocation starts at 80% and reaches 100% after ~5min,
22:49:05 | during this time, the hashrate may be unstable and inconsistent.
22:49:05 | Let the miner warm-up if you're tuning for performance.
22:49:06 | Connecting to mining pool tube.ingest.cryptoknight.cc:5631 ...
22:49:06 | Connected to pool. Now logging in...
22:49:06 | Successfuly logged as bxcAUWyAktcLcsdGA1YX7SLkqU3xjCt348An7KosnkCRfE3RoMZa3SYWyCJsp1C34oH3dyJ5dqFwigmfMbGZ844W1rRBDXW4R.50000
22:49:06 | Pool changes Difficulty to 50000.
22:49:19 | GPU 1 Thread 1 Lane 414 finds a Share, value 50000
22:49:19 | Accepted by the pool in 358 ms.
22:49:32 | GPU 1 Thread 1 Lane 785 finds a Share, value 50000
22:49:32 | Accepted by the pool in 388 ms.
22:49:36 | Hashrate GPU Thread 0: 335.78 h/s
22:49:36 | Hashrate GPU Thread 1: 398.09 h/s - Total GPU 1: 733.86 h/s
22:49:36 | Hashrate GPU Thread 2: 0.00 h/s
22:49:36 | Hashrate GPU Thread 3: 0.00 h/s - Total GPU 2: 0.00 h/s
22:49:36 | Total: 733.86 h/s - Max: 733.86 h/s
22:49:37 | Hashrate GPU Thread 0: 335.78 h/s
22:49:37 | Hashrate GPU Thread 1: 398.09 h/s - Total GPU 1: 733.86 h/s
22:49:37 | Hashrate GPU Thread 2: 0.00 h/s
22:49:37 | Hashrate GPU Thread 3: 0.00 h/s - Total GPU 2: 0.00 h/s
22:49:37 | Total: 733.86 h/s - Max: 733.86 h/s
22:49:54 | GPU 1: Temp: 48C - Fan: 0% -- Shares: Good: 2 Bad: 0
22:49:55 | GPU 2: Temp: 44C - Fan: 0% -- Shares: Good: 0 Bad: 0
it's because 4GB GPU but it used 2 thread with multi_hash 864, so better use manual config. you can try below config :
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":944 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":944 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 2, "multi_hash":944 },
many thanks, it's working now!
what steps recommend increase the multi hash? 580 hashrate is very good (prev miner: 930H/s, jce now: 1030H/s), but the 570 a little bit slow (prev miner: 760H/s, jce now: 680H/s)
Hi!
I have asus rx 580 8gb cards and sapphire nitro+ rx 570 4gb cards.
The 580 cards working good, but the 570 cards dont start. When i start the miner, the gpu clock and the memory clock load are 100%, but after few seconds the memory clock reseted to default 300MHz. The gpu clock load dont change, it stay 100%. The hashrate is 0 (only the 570 cards) In this time the entire system is slowing down extremely.
What might be the problem? Any idea?
Details:
Win 10, Adrenalin 18.5.1.
jce_cn_gpu_miner64.exe --no-cpu --auto --any --forever --variation %FORK% --low -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %*
Thanks!
Try to disable OC and over/undervolting. Try original bios.I have asus rx 580 8gb cards and sapphire nitro+ rx 570 4gb cards.
The 580 cards working good, but the 570 cards dont start. When i start the miner, the gpu clock and the memory clock load are 100%, but after few seconds the memory clock reseted to default 300MHz. The gpu clock load dont change, it stay 100%. The hashrate is 0 (only the 570 cards) In this time the entire system is slowing down extremely.
What might be the problem? Any idea?
Details:
Win 10, Adrenalin 18.5.1.
jce_cn_gpu_miner64.exe --no-cpu --auto --any --forever --variation %FORK% --low -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %*
Thanks!
This is what I tried first. I flashed with original bios + otcp, but not working.
I use in auto mode:
jce_cn_gpu_miner64.exe --no-cpu --auto --any --forever --variation %FORK% --low -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %*
Code:
Detecting OpenCL-capable GPUs...
Found GPU 0, with:
Vendor: Intel
Processor: Intel(R) HD Graphics 510
Device: ff:ff
Compute-Units: 12
Cache Memory: 256 KB
Local Memory: 64 KB
Global Memory: 1603 MB
Addressing: 64-bits
Found GPU 1, with:
Vendor: AMD
Processor: Ellesmere
Device: 02:00
Compute-Units: 36
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 8192 MB
Addressing: 64-bits
Found GPU 2, with:
Vendor: AMD
Processor: Ellesmere
Device: 04:00
Compute-Units: 32
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 4096 MB
Addressing: 64-bits
Preparing 4 Mining Threads...
+-- Thread 0 config ------------------------+
| Run on GPU: 1 |
| Multi-hash: 864 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 16 |
+-------------------------------------------+
+-- Thread 1 config ------------------------+
| Run on GPU: 1 |
| Multi-hash: 864 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 16 |
+-------------------------------------------+
+-- Thread 2 config ------------------------+
| Run on GPU: 2 |
| Multi-hash: 864 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 16 |
+-------------------------------------------+
+-- Thread 3 config ------------------------+
| Run on GPU: 2 |
| Multi-hash: 864 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 16 |
+-------------------------------------------+
Cryptonight Variation: Cryptonight-BitTube v2 of July-2018
Low intensity.
Starting GPU Thread 0, on GPU 1
Created OpenCL Context for GPU 1 at 0000025e0971fba0
Created OpenCL Thread 0 Command-Queue for GPU 1 at 0000025e0971fd00
Scratchpad Allocation success for OpenCL Thread 0
Allocating big 3456MB scratchpad for OpenCL Thread 0...
Compiling kernels of OpenCL Thread 0...
Kernels of OpenCL Thread 0 compiled.
Starting GPU Thread 1, on GPU 1
Created OpenCL Thread 1 Command-Queue for GPU 1 at 0000025e0e028ec0
Scratchpad Allocation success for OpenCL Thread 1
Allocating big 3456MB scratchpad for OpenCL Thread 1...
Compiling kernels of OpenCL Thread 1...
Kernels of OpenCL Thread 1 compiled.
Starting GPU Thread 2, on GPU 2
Created OpenCL Context for GPU 2 at 0000025e09869370
Created OpenCL Thread 2 Command-Queue for GPU 2 at 0000025e0dd59790
Scratchpad Allocation success for OpenCL Thread 2
Allocating big 3456MB scratchpad for OpenCL Thread 2...
Compiling kernels of OpenCL Thread 2...
Kernels of OpenCL Thread 2 compiled.
Starting GPU Thread 3, on GPU 2
Created OpenCL Thread 3 Command-Queue for GPU 2 at 0000025e0dd59cd0
Scratchpad Allocation success for OpenCL Thread 3
Allocating big 3456MB scratchpad for OpenCL Thread 3...
Compiling kernels of OpenCL Thread 3...
Kernels of OpenCL Thread 3 compiled.
22:49:05 | BitTube (TUBE) Mining session starts!
22:49:05 | GPU Compute allocation starts at 80% and reaches 100% after ~5min,
22:49:05 | during this time, the hashrate may be unstable and inconsistent.
22:49:05 | Let the miner warm-up if you're tuning for performance.
22:49:06 | Connecting to mining pool tube.ingest.cryptoknight.cc:5631 ...
22:49:06 | Connected to pool. Now logging in...
22:49:06 | Successfuly logged as bxcAUWyAktcLcsdGA1YX7SLkqU3xjCt348An7KosnkCRfE3RoMZa3SYWyCJsp1C34oH3dyJ5dqFwigmfMbGZ844W1rRBDXW4R.50000
22:49:06 | Pool changes Difficulty to 50000.
22:49:19 | GPU 1 Thread 1 Lane 414 finds a Share, value 50000
22:49:19 | Accepted by the pool in 358 ms.
22:49:32 | GPU 1 Thread 1 Lane 785 finds a Share, value 50000
22:49:32 | Accepted by the pool in 388 ms.
22:49:36 | Hashrate GPU Thread 0: 335.78 h/s
22:49:36 | Hashrate GPU Thread 1: 398.09 h/s - Total GPU 1: 733.86 h/s
22:49:36 | Hashrate GPU Thread 2: 0.00 h/s
22:49:36 | Hashrate GPU Thread 3: 0.00 h/s - Total GPU 2: 0.00 h/s
22:49:36 | Total: 733.86 h/s - Max: 733.86 h/s
22:49:37 | Hashrate GPU Thread 0: 335.78 h/s
22:49:37 | Hashrate GPU Thread 1: 398.09 h/s - Total GPU 1: 733.86 h/s
22:49:37 | Hashrate GPU Thread 2: 0.00 h/s
22:49:37 | Hashrate GPU Thread 3: 0.00 h/s - Total GPU 2: 0.00 h/s
22:49:37 | Total: 733.86 h/s - Max: 733.86 h/s
22:49:54 | GPU 1: Temp: 48C - Fan: 0% -- Shares: Good: 2 Bad: 0
22:49:55 | GPU 2: Temp: 44C - Fan: 0% -- Shares: Good: 0 Bad: 0
Found GPU 0, with:
Vendor: Intel
Processor: Intel(R) HD Graphics 510
Device: ff:ff
Compute-Units: 12
Cache Memory: 256 KB
Local Memory: 64 KB
Global Memory: 1603 MB
Addressing: 64-bits
Found GPU 1, with:
Vendor: AMD
Processor: Ellesmere
Device: 02:00
Compute-Units: 36
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 8192 MB
Addressing: 64-bits
Found GPU 2, with:
Vendor: AMD
Processor: Ellesmere
Device: 04:00
Compute-Units: 32
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 4096 MB
Addressing: 64-bits
Preparing 4 Mining Threads...
+-- Thread 0 config ------------------------+
| Run on GPU: 1 |
| Multi-hash: 864 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 16 |
+-------------------------------------------+
+-- Thread 1 config ------------------------+
| Run on GPU: 1 |
| Multi-hash: 864 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 16 |
+-------------------------------------------+
+-- Thread 2 config ------------------------+
| Run on GPU: 2 |
| Multi-hash: 864 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 16 |
+-------------------------------------------+
+-- Thread 3 config ------------------------+
| Run on GPU: 2 |
| Multi-hash: 864 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 16 |
+-------------------------------------------+
Cryptonight Variation: Cryptonight-BitTube v2 of July-2018
Low intensity.
Starting GPU Thread 0, on GPU 1
Created OpenCL Context for GPU 1 at 0000025e0971fba0
Created OpenCL Thread 0 Command-Queue for GPU 1 at 0000025e0971fd00
Scratchpad Allocation success for OpenCL Thread 0
Allocating big 3456MB scratchpad for OpenCL Thread 0...
Compiling kernels of OpenCL Thread 0...
Kernels of OpenCL Thread 0 compiled.
Starting GPU Thread 1, on GPU 1
Created OpenCL Thread 1 Command-Queue for GPU 1 at 0000025e0e028ec0
Scratchpad Allocation success for OpenCL Thread 1
Allocating big 3456MB scratchpad for OpenCL Thread 1...
Compiling kernels of OpenCL Thread 1...
Kernels of OpenCL Thread 1 compiled.
Starting GPU Thread 2, on GPU 2
Created OpenCL Context for GPU 2 at 0000025e09869370
Created OpenCL Thread 2 Command-Queue for GPU 2 at 0000025e0dd59790
Scratchpad Allocation success for OpenCL Thread 2
Allocating big 3456MB scratchpad for OpenCL Thread 2...
Compiling kernels of OpenCL Thread 2...
Kernels of OpenCL Thread 2 compiled.
Starting GPU Thread 3, on GPU 2
Created OpenCL Thread 3 Command-Queue for GPU 2 at 0000025e0dd59cd0
Scratchpad Allocation success for OpenCL Thread 3
Allocating big 3456MB scratchpad for OpenCL Thread 3...
Compiling kernels of OpenCL Thread 3...
Kernels of OpenCL Thread 3 compiled.
22:49:05 | BitTube (TUBE) Mining session starts!
22:49:05 | GPU Compute allocation starts at 80% and reaches 100% after ~5min,
22:49:05 | during this time, the hashrate may be unstable and inconsistent.
22:49:05 | Let the miner warm-up if you're tuning for performance.
22:49:06 | Connecting to mining pool tube.ingest.cryptoknight.cc:5631 ...
22:49:06 | Connected to pool. Now logging in...
22:49:06 | Successfuly logged as bxcAUWyAktcLcsdGA1YX7SLkqU3xjCt348An7KosnkCRfE3RoMZa3SYWyCJsp1C34oH3dyJ5dqFwigmfMbGZ844W1rRBDXW4R.50000
22:49:06 | Pool changes Difficulty to 50000.
22:49:19 | GPU 1 Thread 1 Lane 414 finds a Share, value 50000
22:49:19 | Accepted by the pool in 358 ms.
22:49:32 | GPU 1 Thread 1 Lane 785 finds a Share, value 50000
22:49:32 | Accepted by the pool in 388 ms.
22:49:36 | Hashrate GPU Thread 0: 335.78 h/s
22:49:36 | Hashrate GPU Thread 1: 398.09 h/s - Total GPU 1: 733.86 h/s
22:49:36 | Hashrate GPU Thread 2: 0.00 h/s
22:49:36 | Hashrate GPU Thread 3: 0.00 h/s - Total GPU 2: 0.00 h/s
22:49:36 | Total: 733.86 h/s - Max: 733.86 h/s
22:49:37 | Hashrate GPU Thread 0: 335.78 h/s
22:49:37 | Hashrate GPU Thread 1: 398.09 h/s - Total GPU 1: 733.86 h/s
22:49:37 | Hashrate GPU Thread 2: 0.00 h/s
22:49:37 | Hashrate GPU Thread 3: 0.00 h/s - Total GPU 2: 0.00 h/s
22:49:37 | Total: 733.86 h/s - Max: 733.86 h/s
22:49:54 | GPU 1: Temp: 48C - Fan: 0% -- Shares: Good: 2 Bad: 0
22:49:55 | GPU 2: Temp: 44C - Fan: 0% -- Shares: Good: 0 Bad: 0
Hi!
I have asus rx 580 8gb cards and sapphire nitro+ rx 570 4gb cards.
The 580 cards working good, but the 570 cards dont start. When i start the miner, the gpu clock and the memory clock load are 100%, but after few seconds the memory clock reseted to default 300MHz. The gpu clock load dont change, it stay 100%. The hashrate is 0 (only the 570 cards) In this time the entire system is slowing down extremely.
What might be the problem? Any idea?
Details:
Win 10, Adrenalin 18.5.1.
jce_cn_gpu_miner64.exe --no-cpu --auto --any --forever --variation %FORK% --low -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %*
Thanks!
Try to disable OC and over/undervolting. Try original bios.I have asus rx 580 8gb cards and sapphire nitro+ rx 570 4gb cards.
The 580 cards working good, but the 570 cards dont start. When i start the miner, the gpu clock and the memory clock load are 100%, but after few seconds the memory clock reseted to default 300MHz. The gpu clock load dont change, it stay 100%. The hashrate is 0 (only the 570 cards) In this time the entire system is slowing down extremely.
What might be the problem? Any idea?
Details:
Win 10, Adrenalin 18.5.1.
jce_cn_gpu_miner64.exe --no-cpu --auto --any --forever --variation %FORK% --low -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %*
Thanks!
This is what I tried first. I flashed with original bios + otcp, but not working.
What you've described is pretty common crash behavior for too high clocks and/or too low voltages. It's more likely your OC settings than your bios.
Yes, that's what I was thinking. But after I restore the original state, I do not know what to think. Original rom, original gpu & memory clock, original voltages & power limit, (+ new adrenalin driver - 18.6.1) and the card get 0 mhs, and the system freeze. With another miner everything ok at this moment, so the card is working.
Hi!
I have asus rx 580 8gb cards and sapphire nitro+ rx 570 4gb cards.
The 580 cards working good, but the 570 cards dont start. When i start the miner, the gpu clock and the memory clock load are 100%, but after few seconds the memory clock reseted to default 300MHz. The gpu clock load dont change, it stay 100%. The hashrate is 0 (only the 570 cards) In this time the entire system is slowing down extremely.
What might be the problem? Any idea?
Details:
Win 10, Adrenalin 18.5.1.
jce_cn_gpu_miner64.exe --no-cpu --auto --any --forever --variation %FORK% --low -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %*
Thanks!
Try to disable OC and over/undervolting. Try original bios.I have asus rx 580 8gb cards and sapphire nitro+ rx 570 4gb cards.
The 580 cards working good, but the 570 cards dont start. When i start the miner, the gpu clock and the memory clock load are 100%, but after few seconds the memory clock reseted to default 300MHz. The gpu clock load dont change, it stay 100%. The hashrate is 0 (only the 570 cards) In this time the entire system is slowing down extremely.
What might be the problem? Any idea?
Details:
Win 10, Adrenalin 18.5.1.
jce_cn_gpu_miner64.exe --no-cpu --auto --any --forever --variation %FORK% --low -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %*
Thanks!
This is what I tried first. I flashed with original bios + otcp, but not working.
I use in auto mode:
jce_cn_gpu_miner64.exe --no-cpu --auto --any --forever --variation %FORK% --low -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %*
Hi!
I have asus rx 580 8gb cards and sapphire nitro+ rx 570 4gb cards.
The 580 cards working good, but the 570 cards dont start. When i start the miner, the gpu clock and the memory clock load are 100%, but after few seconds the memory clock reseted to default 300MHz. The gpu clock load dont change, it stay 100%. The hashrate is 0 (only the 570 cards) In this time the entire system is slowing down extremely.
What might be the problem? Any idea?
Details:
Win 10, Adrenalin 18.5.1.
jce_cn_gpu_miner64.exe --no-cpu --auto --any --forever --variation %FORK% --low -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %*
Thanks!
Try to disable OC and over/undervolting. Try original bios.I have asus rx 580 8gb cards and sapphire nitro+ rx 570 4gb cards.
The 580 cards working good, but the 570 cards dont start. When i start the miner, the gpu clock and the memory clock load are 100%, but after few seconds the memory clock reseted to default 300MHz. The gpu clock load dont change, it stay 100%. The hashrate is 0 (only the 570 cards) In this time the entire system is slowing down extremely.
What might be the problem? Any idea?
Details:
Win 10, Adrenalin 18.5.1.
jce_cn_gpu_miner64.exe --no-cpu --auto --any --forever --variation %FORK% --low -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %*
Thanks!
This is what I tried first. I flashed with original bios + otcp, but not working.
Hi!
I have asus rx 580 8gb cards and sapphire nitro+ rx 570 4gb cards.
The 580 cards working good, but the 570 cards dont start. When i start the miner, the gpu clock and the memory clock load are 100%, but after few seconds the memory clock reseted to default 300MHz. The gpu clock load dont change, it stay 100%. The hashrate is 0 (only the 570 cards) In this time the entire system is slowing down extremely.
What might be the problem? Any idea?
Details:
Win 10, Adrenalin 18.5.1.
jce_cn_gpu_miner64.exe --no-cpu --auto --any --forever --variation %FORK% --low -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %*
Thanks!
I have asus rx 580 8gb cards and sapphire nitro+ rx 570 4gb cards.
The 580 cards working good, but the 570 cards dont start. When i start the miner, the gpu clock and the memory clock load are 100%, but after few seconds the memory clock reseted to default 300MHz. The gpu clock load dont change, it stay 100%. The hashrate is 0 (only the 570 cards) In this time the entire system is slowing down extremely.
What might be the problem? Any idea?
Details:
Win 10, Adrenalin 18.5.1.
jce_cn_gpu_miner64.exe --no-cpu --auto --any --forever --variation %FORK% --low -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %*
Thanks!
Re: SRBMiner Cryptonight AMD GPU Miner V1.6.8 - V8 & algo switching
Can anyone help me out with this situation ?
I had BETA drivers installed, everything was working, and i wanted to update the drivers to 18.6.1.
Removed BETA drivers with DDU, installed 18.6.1 drivers but now SRB Miner does not start.
http://prnt.sc/l5fi4q
The pointer blinks, but nothing ....
Anyone experienced something similar ?
I had BETA drivers installed, everything was working, and i wanted to update the drivers to 18.6.1.
Removed BETA drivers with DDU, installed 18.6.1 drivers but now SRB Miner does not start.
http://prnt.sc/l5fi4q
The pointer blinks, but nothing ....
Anyone experienced something similar ?
maybe atidagpatcher?
Re: SRBMiner Cryptonight AMD GPU Miner V1.6.8 - V8 & algo switching
1.6.8 hashrates is lower for me
cards (both sapphire nitro+ 4gb) / hashrate 1.6.7 / hashrate 1.6.8
rx470 / 740 / 720
rx570 / 760 / 740
algo: bittubev2
i switch back to 1.6.7
I tried the new 1.6.8 version, the result was worse than previous 1.6.8.
rx470: 706H/s
rx570: 736H/s
I= 0, T=2, WS=8
I don't know what is happening there but i ran 2 tests on TUBE:
Intensity:28
Worksize:8
Threads:2
Rx470 4g Sapphire Nitro [1050/1950]
1.6.7 : 588 HS
1.6.8 : 613 HS
This is the latest 1.6.8 i uploaded today.
My card settings (with the newest miner):
rx 470 nitro+ 4gb
rom modded: otcp, gpu: 1300MHz/950mv, mem: 2000MHz/850mv
afterburner settings: -15% power limit
miner: I=29,5, T=2, WS=8
rx 570 nitro+ 4gb
rom modded: otcp, gpu 1340MHz/1000mv, mem: 2000MHz/850mv
afterburner settings: -15% power limit
miner: I=29,5, T=2, WS=8
Total consumption of the two cards: 190W (470=95-100W, 580=90-95W)
https://kepkuldes.com/images/d5a6676678722ca7295347b34414ffd8.png
Re: SRBMiner Cryptonight AMD GPU Miner V1.6.8 - V8 & algo switching
1.6.8 hashrates is lower for me
cards (both sapphire nitro+ 4gb) / hashrate 1.6.7 / hashrate 1.6.8
rx470 / 740 / 720
rx570 / 760 / 740
algo: bittubev2
i switch back to 1.6.7
I tried the new 1.6.8 version, the result was worse than previous 1.6.8.
rx470: 706H/s
rx570: 736H/s
I= 0, T=2, WS=8
Set intensity by hand, i lowered the auto intensity values a little bit.
You probably know the previous auto intensity value.
I tried these (in chronological order):
auto intensity 1.6.7 = 29. Results: 760/740
auto intensity 1.6.8 = 29. Results: 736/706
manual intensity 1.6.8 = 29. Results: 748/730
manual intensity 1.6.8 = 29.5 Results: 760/740
manual intensity 1.6.8 = 29.9 Results: crash miner
manual intensity 1.6.8 = 29.7 Results: crash miner
manual intensity 1.6.8 = 29.6 Results: windows crash
manual intensity 1.6.8 = 29.6 again. Results: crash miner
So, the hashrate with manual mode are same with the 1.6.7 auto mode.
Thanks!