SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching

[doktor83]

Hello doktor,

first of all - thank you for your hard work and producing such a great miner.

Since the first days after fork srb miner unfortunately becomes unstable now. I had 3 crash downs in the last 48 hours with my Radeon RX Vegas 64. Something must have changed since the first days after the fork, Sun/Mon/Tue it was stable. Now it closes in the middle of the night for example. Hash rate is although slighly less than directly after fork ~ around 50 h/s (2000 > 1950).

Iam using the latest drivers.

The new algorithm isnt same as V8 was before, so you should experiment with your OC (clock/mem/voltage) settings.
Hashrate can vary a little bit from block to block, because of the random math that was added in the new algo CN/R.

[gyIQ]

Do they have hynix HBM?
My cards with samsung HBM hash around 1945 H/s

Yes, Hynix, hogy a fene egye meg.

[big_daddy]

@doktor83

Is possible to merge Your miner with ZIL miner? Something like a "dual mining"
The idea is to make a script that will start ZIL at their start POW epoch (on every *99 block, ~every 2 hours), mine ZIL for 1-2 minutes, than restart SRBminer and mine the Cryptonight coin, or even without stopping for the 1-2 minutes for the GPUs with 6GB & more, cause there is enough space to upload the ZIL DAG file

I'm doing it using 3 bat files, but sometimes it the miner stucks, it will be great if some developer/programmer could make a more stable script

Best regards

[gyIQ]

Doktor,

Any chance to create a linux version and integrate it to HIVEOS? Would love to mine with SRB on HIVE.

[akvilon888]

dok, having a problem with srb, the miner closes itself, have the same problem with 3-4 rigs...it closes randomly at any time, no matter what cards or driver, it closes on vegas 56/64 and the same on rx550...can you do something or recommend ? never had this problem before 1.8.0, and its a very disappointing thing, lost a lot of time without rigs working especially at night...

[doktor83]

Doktor,

Any chance to create a linux version and integrate it to HIVEOS? Would love to mine with SRB on HIVE.

Not at the moment, sorry.

dok, having a problem with srb, the miner closes itself, have the same problem with 3-4 rigs...it closes randomly at any time, no matter what cards or driver, it closes on vegas 56/64 and the same on rx550...can you do something or recommend ? never had this problem before 1.8.0, and its a very disappointing thing, lost a lot of time without rigs working especially at night...

I need more info :

1. Windows version
2. Are you algo switching or normal mining
3. Paste your config
4. Paste your pools file without the wallet address
5. Log file would be very good to have
6. How often does this happen
7. Are those rigs on the same internet
8. Are you using wifi on those rigs

[rotaryfurball]

Has anyone been having unreliability issues? Both my rigs just stop mining after a few hours. In the log all the GPU just go to hashing speed 0

[korz]

all is good except this message :

WARNING: Linking two modules of different data layouts!
WARNING: Linking two modules of different target triples: input.bc: 'amdil64-pc-unknown-amdopencl' and 'amdil-pc-unknown-amdopencl'

and this other little prob ... No monitoring ...

[2019-03-13 18:22:31] GPU0 :    372 H/s [T: 0c, RPM: 0, CC: 0 MHz, MC: 0 MHz][BUS:5]
[2019-03-13 18:22:31] GPU1 :    378 H/s [T: 0c, RPM: 0, CC: 0 MHz, MC: 0 MHz][BUS:4]
[2019-03-13 18:22:31] GPU2 :    348 H/s [T: 0c, RPM: 0, CC: 0 MHz, MC: 0 MHz][BUS:7]
[2019-03-13 18:22:31] GPU3 :    372 H/s [T: 0c, RPM: 0, CC: 0 MHz, MC: 0 MHz][BUS:1]
[2019-03-13 18:22:31] Total:    1470 H/s

if someone can explan me ...

thx a lot

You can dismiss those messages, those are not affecting your mining speeds.

Regarding the monitoring, try this parameter :

Code:

"adl_type" : 1 or 2 , 1 - USE OVERDRIVEN , 2 - USE OVERDRIVE 5. Default is 1 if not set. Option 2 (Overdrive 5) is suitable for older cards

Try setting it to 2

Thx a lot for yor fast answer .
Ok for the warning message ...

I have try  "adl_type" : 2 nothing .... i have try 1 it's same ...

Code:

 
{	
"cryptonight_type" : "normalv4",	
"intensity" : 0,	
"double_threads" : true,	
"off_temperature" : 90,	
"adl_type" : 2,
}

if it helps, here are my gpu
GPU0: AMD Radeon(TM) R9 270 [pitcairn] [2048 MB][I: 24.0][W: 16][T: 2][F: 8][BUS: 5]
GPU1: AMD Radeon(TM) R9 270 [pitcairn] [2048 MB][I: 24.0][W: 16][T: 2][F: 8][BUS: 4]
GPU2: AMD Radeon(TM) R9 270 [pitcairn] [2048 MB][I: 24.0][W: 16][T: 2][F: 8][BUS: 7]
GPU3: AMD Radeon(TM) R9 270 [pitcairn] [2048 MB][I: 24.0][W: 16][T: 2][F: 8][BUS: 1]

[MagicSmoker]

Has anyone been having unreliability issues? Both my rigs just stop mining after a few hours. In the log all the GPU just go to hashing speed 0

Yes, and while I can't say I've claimed victory just yet, so far it appears that dialing back a little on the memory clock is helping. Prior to that Windows 10 would BSOD with a TDR video failure, sometimes before starting the miner, and even after I DDU'ed 18.6.1 and reinstalled it (pixel patched, etc.).

So far I have been mining for a couple hours at 1860 on the mem clock (1200 on the core clock) at full power and not really seeing a reduction in hashrate from when I was running at 1200/1900.

[rotaryfurball]

Has anyone been having unreliability issues? Both my rigs just stop mining after a few hours. In the log all the GPU just go to hashing speed 0

Yes, and while I can't say I've claimed victory just yet, so far it appears that dialing back a little on the memory clock is helping. Prior to that Windows 10 would BSOD with a TDR video failure, sometimes before starting the miner, and even after I DDU'ed 18.6.1 and reinstalled it (pixel patched, etc.).

So far I have been mining for a couple hours at 1860 on the mem clock (1200 on the core clock) at full power and not really seeing a reduction in hashrate from when I was running at 1200/1900.

Thank you. I will try that!

[chimaeraa]

hi doc and thanks .
after xmr fork my miner going unstable and close it self there is nothing no error no message ... just stop working. i use it for long time and i have no problem with it. i use cable  for Internet , my win 10 - v 1803 - build 17134.648-

i use both config auto and manual

"gpu_conf" :
[
   { "id" : 0, "intensity" : 123.1 , "worksize" : 16 , "threads" : 2},
   { "id" : 1, "intensity" : 123.3 , "worksize" : 16 , "threads" : 2},
   { "id" : 2, "intensity" : 123.3 , "worksize" : 16 , "threads" : 2},
   { "id" : 3, "intensity" : 123.1 , "worksize" : 16 , "threads" : 2},
   { "id" : 4, "intensity" : 123.3 , "worksize" : 16 , "threads" : 2},
   { "id" : 5, "intensity" : 123.3 , "worksize" : 16 , "threads" : 2},
   { "id" : 6, "intensity" : 123.3 , "worksize" : 16 , "threads" : 2},
   { "id" : 7, "intensity" : 123.5 , "worksize" : 16 , "threads" : 2},
   { "id" : 8, "intensity" : 123.5 , "worksize" : 16 , "threads" : 2},
   { "id" : 9, "intensity" : 123.3 , "worksize" : 16 , "threads" : 2}
]

and pool connection

   {
      "pool" : "pool.minexmr.com:7777",
      "wallet" : ".V64_Air+40000",
      "password" : "",
      "max_difficulty" :41000,
      "cryptonight_type" : "normalv4"   
   },

i use algo switch with reset vega setting .
i have two rig and one air and one liq cooling. i change oc but nothing change .

GPU_P0=852;900;0
GPU_P1=991;900;0
GPU_P2=1084;900;0
GPU_P3=1138;900;0
GPU_P4=1150;900;0
GPU_P5=1202;900;0
GPU_P6=1212;905
GPU_P7=1408;925
Mem_P0=167;900;0
Mem_P1=500;900;0
Mem_P2=800;900;0
Mem_P3=1099;905
Fan_Min=2000
Fan_Max=4900
Fan_Target=54
Fan_Acoustic=2400
Power_Temp=65
Power_Target=0

i have problem with new xmr algo  .other algo work fine.

[ManDoneKTM]

on the last version , with 5 gpu 580 and 8 gb ram i have super lag ... 99.8 % VM used ... i had to go back at 1.7.8 ...

[rotaryfurball]

Hello Doktor,

I'm using the latest version 1.8.0 since the fork. But suddenly I'm facing an issue which is my miner keeps crashing and close itself after like 3 or 4 hours later. After that happens, when you click on the start.bat file again it opens but immediately closes again. The only solution for them is to restart the computer otherwise it won't work. Can you help me?

I have the exact same problem

[Anakro]

I would love to see the ability to solo mine directly with your own daemon/ node/ wallet.

This is the only place I know of to request such a thing.

Pretty please :-)

[doktor83]

hi doc and thanks .
after xmr fork my miner going unstable and close it self there is nothing no error no message ... just stop working. i use it for long time and i have no problem with it. i use cable  for Internet , my win 10 - v 1803 - build 17134.648-

and pool connection

   {
      "pool" : "pool.minexmr.com:7777",
      "wallet" : ".V64_Air+40000",
      "password" : "",
      "max_difficulty" :41000,
      "cryptonight_type" : "normalv4"   
   },

i use algo switch with reset vega setting .

i have problem with new xmr algo  .other algo work fine.

Why are you using algo switching when you are mining on a pool that does not support algo switching?
It is hard to help without a log file, there i could at least see what were the last messages, maybe that can help me find the bug.

[chimaeraa]

hi doc and thanks .
after xmr fork my miner going unstable and close it self there is nothing no error no message ... just stop working. i use it for long time and i have no problem with it. i use cable  for Internet , my win 10 - v 1803 - build 17134.648-

and pool connection

   {
      "pool" : "pool.minexmr.com:7777",
      "wallet" : ".V64_Air+40000",
      "password" : "",
      "max_difficulty" :41000,
      "cryptonight_type" : "normalv4"   
   },

i use algo switch with reset vega setting .

i have problem with new xmr algo  .other algo work fine.

Why are you using algo switching when you are mining on a pool that does not support algo switching?
It is hard to help without a log file, there i could at least see what were the last messages, maybe that can help me find the bug.

i switch it manually .
why not ?

[2019-03-12 10:00:57] Restarting miner with normalv4 algo
[2019-03-12 10:00:57] Miner version: 1.7.9
[2019-03-12 10:00:57] Windows version: 10.0 build 17134
[2019-03-12 10:00:57] Video driver version: 24.20.11019.1004
[2019-03-12 10:01:19] Startup monitor attached
[2019-03-12 10:01:23] AMD Platform ID: 0
[2019-03-12 10:01:23] AMD platform FOUND
[2019-03-12 10:01:23] Found 11 AMD devices
[2019-03-12 10:01:23] CPU AES-NI: TRUE
[2019-03-12 10:01:23] GPU0: Radeon RX Vega [gfx900] [8176 MB][I: 112.0][W: 16][T: 2][F: 4][BUS: 25]
[2019-03-12 10:01:23] GPU1: Radeon RX Vega [gfx900] [8176 MB][I: 112.0][W: 16][T: 2][F: 4][BUS: 34]
[2019-03-12 10:01:23] GPU2: Radeon RX Vega [gfx900] [8176 MB][I: 112.0][W: 16][T: 2][F: 4][BUS: 19]
[2019-03-12 10:01:23] GPU3: Radeon RX Vega [gfx900] [8176 MB][I: 112.0][W: 16][T: 2][F: 4][BUS: 28]
[2019-03-12 10:01:23] GPU4: Radeon RX Vega [gfx900] [8176 MB][I: 112.0][W: 16][T: 2][F: 4][BUS: 9]
[2019-03-12 10:01:23] GPU5: Radeon RX Vega [gfx900] [8176 MB][I: 112.0][W: 16][T: 2][F: 4][BUS: 13]
[2019-03-12 10:01:23] GPU6: Radeon RX Vega [gfx900] [8176 MB][I: 112.0][W: 16][T: 2][F: 4][BUS: 16]
[2019-03-12 10:01:23] GPU7: Radeon RX Vega [gfx900] [8176 MB][I: 112.0][W: 16][T: 2][F: 4][BUS: 37]
[2019-03-12 10:01:23] GPU8: Radeon RX Vega [gfx900] [8176 MB][I: 112.0][W: 16][T: 2][F: 4][BUS: 22]
[2019-03-12 10:01:23] GPU9: Radeon RX Vega [gfx900] [8176 MB][I: 112.0][W: 16][T: 2][F: 4][BUS: 31]
[2019-03-12 10:01:23] GPU10: Radeon RX Vega [gfx900] [8176 MB][I: 112.0][W: 16][T: 2][F: 4][BUS: 5]
[2019-03-12 10:01:23] ADL is enabled
[2019-03-12 10:01:23] Algo switching mode enabled
[2019-03-12 10:01:23] Algo switch minimum time : 600 seconds
[2019-03-12 10:01:23] Algorithm: Cryptonight V4 (R)
[2019-03-12 10:01:23] Algo switching: enabled
[2019-03-12 10:01:23] Startup monitor: enabled
[2019-03-12 10:01:23] Gpu watchdog: enabled [gpu disable mode]
[2019-03-12 10:01:23] Coin forking: disabled
[2019-03-12 10:01:23] Starting init of mining threads
[2019-03-12 10:01:23] Created OCL context
[2019-03-12 10:01:23] Using fragments 4 for DeviceID 0 (Thread 0)
[2019-03-12 10:01:23] Using heavy_mode 1 for DeviceID 0 (Thread 0)
[2019-03-12 10:01:23] Using thread_delay 319 for DeviceID 0 (Thread 0)
[2019-03-12 10:01:23] Created OCL input buffer for DeviceID 0 (Thread 0)
[2019-03-12 10:01:23] Loading [normalv4] kernel for DEVICE BUS_ID[25]
[2019-03-12 10:01:23] ctx->Program for DeviceID 0 (Thread 0) loaded
[2019-03-12 10:01:23] Using fragments 4 for DeviceID 0 (Thread 1)
[2019-03-12 10:01:23] Using heavy_mode 1 for DeviceID 0 (Thread 1)
[2019-03-12 10:01:23] Using thread_delay 319 for DeviceID 0 (Thread 1)
[2019-03-12 10:01:23] Created OCL input buffer for DeviceID 0 (Thread 1)
[2019-03-12 10:01:23] Loading [normalv4] kernel for DEVICE BUS_ID[25]
[2019-03-12 10:01:23] ctx->Program for DeviceID 0 (Thread 1) loaded
[2019-03-12 10:01:23] Using fragments 4 for DeviceID 1 (Thread 2)
[2019-03-12 10:01:23] Using heavy_mode 1 for DeviceID 1 (Thread 2)
[2019-03-12 10:01:23] Using thread_delay 319 for DeviceID 1 (Thread 2)
[2019-03-12 10:01:23] Created OCL input buffer for DeviceID 1 (Thread 2)
[2019-03-12 10:01:23] Loading [normalv4] kernel for DEVICE BUS_ID[34]
[2019-03-12 10:01:23] ctx->Program for DeviceID 1 (Thread 2) loaded
[2019-03-12 10:01:23] Using fragments 4 for DeviceID 1 (Thread 3)
[2019-03-12 10:01:23] Using heavy_mode 1 for DeviceID 1 (Thread 3)
[2019-03-12 10:01:23] Using thread_delay 319 for DeviceID 1 (Thread 3)
[2019-03-12 10:01:23] Created OCL input buffer for DeviceID 1 (Thread 3)
[2019-03-12 10:01:23] Loading [normalv4] kernel for DEVICE BUS_ID[34]
[2019-03-12 10:01:23] ctx->Program for DeviceID 1 (Thread 3) loaded
[2019-03-12 10:01:23] Using fragments 4 for DeviceID 2 (Thread 4)
[2019-03-12 10:01:23] Using heavy_mode 1 for DeviceID 2 (Thread 4)
[2019-03-12 10:01:23] Using thread_delay 319 for DeviceID 2 (Thread 4)
[2019-03-12 10:01:23] Created OCL input buffer for DeviceID 2 (Thread 4)
[2019-03-12 10:01:23] Loading [normalv4] kernel for DEVICE BUS_ID[19]
[2019-03-12 10:01:23] ctx->Program for DeviceID 2 (Thread 4) loaded
[2019-03-12 10:01:23] Using fragments 4 for DeviceID 2 (Thread 5)
[2019-03-12 10:01:23] Using heavy_mode 1 for DeviceID 2 (Thread 5)
[2019-03-12 10:01:23] Using thread_delay 319 for DeviceID 2 (Thread 5)
[2019-03-12 10:01:24] Created OCL input buffer for DeviceID 2 (Thread 5)
[2019-03-12 10:01:24] Loading [normalv4] kernel for DEVICE BUS_ID[19]
[2019-03-12 10:01:24] ctx->Program for DeviceID 2 (Thread 5) loaded
[2019-03-12 10:01:24] Using fragments 4 for DeviceID 3 (Thread 6)
[2019-03-12 10:01:24] Using heavy_mode 1 for DeviceID 3 (Thread 6)
[2019-03-12 10:01:24] Using thread_delay 319 for DeviceID 3 (Thread 6)
[2019-03-12 10:01:24] Created OCL input buffer for DeviceID 3 (Thread 6)
[2019-03-12 10:01:24] Loading [normalv4] kernel for DEVICE BUS_ID[28]
[2019-03-12 10:01:24] ctx->Program for DeviceID 3 (Thread 6) loaded
[2019-03-12 10:01:24] Using fragments 4 for DeviceID 3 (Thread 7)
[2019-03-12 10:01:24] Using heavy_mode 1 for DeviceID 3 (Thread 7)
[2019-03-12 10:01:24] Using thread_delay 319 for DeviceID 3 (Thread 7)
[2019-03-12 10:01:24] Created OCL input buffer for DeviceID 3 (Thread 7)
[2019-03-12 10:01:24] Loading [normalv4] kernel for DEVICE BUS_ID[28]
[2019-03-12 10:01:24] ctx->Program for DeviceID 3 (Thread 7) loaded
[2019-03-12 10:01:24] Using fragments 4 for DeviceID 4 (Thread
[2019-03-12 10:01:24] Using heavy_mode 1 for DeviceID 4 (Thread
[2019-03-12 10:01:24] Using thread_delay 319 for DeviceID 4 (Thread
[2019-03-12 10:01:24] Created OCL input buffer for DeviceID 4 (Thread
[2019-03-12 10:01:24] Loading [normalv4] kernel for DEVICE BUS_ID[9]
[2019-03-12 10:01:24] ctx->Program for DeviceID 4 (Thread loaded
[2019-03-12 10:01:24] Using fragments 4 for DeviceID 4 (Thread 9)
[2019-03-12 10:01:24] Using heavy_mode 1 for DeviceID 4 (Thread 9)
[2019-03-12 10:01:24] Using thread_delay 319 for DeviceID 4 (Thread 9)
[2019-03-12 10:01:24] Created OCL input buffer for DeviceID 4 (Thread 9)
[2019-03-12 10:01:24] Loading [normalv4] kernel for DEVICE BUS_ID[9]
[2019-03-12 10:01:24] ctx->Program for DeviceID 4 (Thread 9) loaded
[2019-03-12 10:01:24] Using fragments 4 for DeviceID 5 (Thread 10)
[2019-03-12 10:01:24] Using heavy_mode 1 for DeviceID 5 (Thread 10)
[2019-03-12 10:01:24] Using thread_delay 319 for DeviceID 5 (Thread 10)
[2019-03-12 10:01:24] Created OCL input buffer for DeviceID 5 (Thread 10)
[2019-03-12 10:01:24] Loading [normalv4] kernel for DEVICE BUS_ID[13]
[2019-03-12 10:01:24] ctx->Program for DeviceID 5 (Thread 10) loaded
[2019-03-12 10:01:24] Using fragments 4 for DeviceID 5 (Thread 11)
[2019-03-12 10:01:24] Using heavy_mode 1 for DeviceID 5 (Thread 11)
[2019-03-12 10:01:24] Using thread_delay 319 for DeviceID 5 (Thread 11)
[2019-03-12 10:01:24] Created OCL input buffer for DeviceID 5 (Thread 11)
[2019-03-12 10:01:24] Loading [normalv4] kernel for DEVICE BUS_ID[13]
[2019-03-12 10:01:24] ctx->Program for DeviceID 5 (Thread 11) loaded
[2019-03-12 10:01:24] Using fragments 4 for DeviceID 6 (Thread 12)
[2019-03-12 10:01:24] Using heavy_mode 1 for DeviceID 6 (Thread 12)
[2019-03-12 10:01:24] Using thread_delay 319 for DeviceID 6 (Thread 12)
[2019-03-12 10:01:24] Created OCL input buffer for DeviceID 6 (Thread 12)
[2019-03-12 10:01:24] Loading [normalv4] kernel for DEVICE BUS_ID[16]
[2019-03-12 10:01:24] ctx->Program for DeviceID 6 (Thread 12) loaded
[2019-03-12 10:01:24] Using fragments 4 for DeviceID 6 (Thread 13)
[2019-03-12 10:01:24] Using heavy_mode 1 for DeviceID 6 (Thread 13)
[2019-03-12 10:01:24] Using thread_delay 319 for DeviceID 6 (Thread 13)
[2019-03-12 10:01:24] Created OCL input buffer for DeviceID 6 (Thread 13)
[2019-03-12 10:01:24] Loading [normalv4] kernel for DEVICE BUS_ID[16]
[2019-03-12 10:01:24] ctx->Program for DeviceID 6 (Thread 13) loaded
[2019-03-12 10:01:24] Using fragments 4 for DeviceID 7 (Thread 14)
[2019-03-12 10:01:24] Using heavy_mode 1 for DeviceID 7 (Thread 14)
[2019-03-12 10:01:24] Using thread_delay 319 for DeviceID 7 (Thread 14)
[2019-03-12 10:01:25] Created OCL input buffer for DeviceID 7 (Thread 14)
[2019-03-12 10:01:25] Loading [normalv4] kernel for DEVICE BUS_ID[37]
[2019-03-12 10:01:25] ctx->Program for DeviceID 7 (Thread 14) loaded
[2019-03-12 10:01:25] Using fragments 4 for DeviceID 7 (Thread 15)
[2019-03-12 10:01:25] Using heavy_mode 1 for DeviceID 7 (Thread 15)
[2019-03-12 10:01:25] Using thread_delay 319 for DeviceID 7 (Thread 15)
[2019-03-12 10:01:25] Created OCL input buffer for DeviceID 7 (Thread 15)
[2019-03-12 10:01:25] Loading [normalv4] kernel for DEVICE BUS_ID[37]
[2019-03-12 10:01:25] ctx->Program for DeviceID 7 (Thread 15) loaded
[2019-03-12 10:01:25] Using fragments 4 for DeviceID 8 (Thread 16)
[2019-03-12 10:01:25] Using heavy_mode 1 for DeviceID 8 (Thread 16)
[2019-03-12 10:01:25] Using thread_delay 319 for DeviceID 8 (Thread 16)
[2019-03-12 10:01:25] Created OCL input buffer for DeviceID 8 (Thread 16)
[2019-03-12 10:01:25] Loading [normalv4] kernel for DEVICE BUS_ID[22]
[2019-03-12 10:01:25] ctx->Program for DeviceID 8 (Thread 16) loaded
[2019-03-12 10:01:25] Using fragments 4 for DeviceID 8 (Thread 17)
[2019-03-12 10:01:25] Using heavy_mode 1 for DeviceID 8 (Thread 17)
[2019-03-12 10:01:25] Using thread_delay 319 for DeviceID 8 (Thread 17)
[2019-03-12 10:01:25] Created OCL input buffer for DeviceID 8 (Thread 17)
[2019-03-12 10:01:25] Loading [normalv4] kernel for DEVICE BUS_ID[22]
[2019-03-12 10:01:25] ctx->Program for DeviceID 8 (Thread 17) loaded
[2019-03-12 10:01:25] Using fragments 4 for DeviceID 9 (Thread 18)
[2019-03-12 10:01:25] Using heavy_mode 1 for DeviceID 9 (Thread 18)
[2019-03-12 10:01:25] Using thread_delay 319 for DeviceID 9 (Thread 18)
[2019-03-12 10:01:25] Created OCL input buffer for DeviceID 9 (Thread 18)
[2019-03-12 10:01:25] Loading [normalv4] kernel for DEVICE BUS_ID[31]
[2019-03-12 10:01:25] ctx->Program for DeviceID 9 (Thread 18) loaded
[2019-03-12 10:01:25] Using fragments 4 for DeviceID 9 (Thread 19)
[2019-03-12 10:01:25] Using heavy_mode 1 for DeviceID 9 (Thread 19)
[2019-03-12 10:01:25] Using thread_delay 319 for DeviceID 9 (Thread 19)
[2019-03-12 10:01:25] Created OCL input buffer for DeviceID 9 (Thread 19)
[2019-03-12 10:01:25] Loading [normalv4] kernel for DEVICE BUS_ID[31]
[2019-03-12 10:01:25] ctx->Program for DeviceID 9 (Thread 19) loaded
[2019-03-12 10:01:25] Using fragments 4 for DeviceID 10 (Thread 20)
[2019-03-12 10:01:25] Using heavy_mode 1 for DeviceID 10 (Thread 20)
[2019-03-12 10:01:25] Using thread_delay 319 for DeviceID 10 (Thread 20)
[2019-03-12 10:01:25] Created OCL input buffer for DeviceID 10 (Thread 20)
[2019-03-12 10:01:25] Loading [normalv4] kernel for DEVICE BUS_ID[5]
[2019-03-12 10:01:25] ctx->Program for DeviceID 10 (Thread 20) loaded
[2019-03-12 10:01:25] Using fragments 4 for DeviceID 10 (Thread 21)
[2019-03-12 10:01:25] Using heavy_mode 1 for DeviceID 10 (Thread 21)
[2019-03-12 10:01:25] Using thread_delay 319 for DeviceID 10 (Thread 21)
[2019-03-12 10:01:25] Created OCL input buffer for DeviceID 10 (Thread 21)
[2019-03-12 10:01:25] Loading [normalv4] kernel for DEVICE BUS_ID[5]
[2019-03-12 10:01:25] ctx->Program for DeviceID 10 (Thread 21) loaded
[2019-03-12 10:01:25] ADL initialised successfully!
[2019-03-12 10:01:25] Finished init of mining threads
[2019-03-12 10:01:26] Startup monitor detached
[2019-03-12 10:01:26] Gpu watchdog started
[2019-03-12 10:01:26] API disabled
[2019-03-12 10:01:26] json_send[973]: {"id":1,"jsonrpc": "2.0","method":"login","params":{"login":".V64_Liq+44000","pass":"","agent":"SRBMiner Cryptonight AMD GPU miner/1.7.9","rigid":"","algo":["cn/xao","cn/rto","cn/b2n","cn-heavy/tube","cn/ccx","cn/msr","cn/fast2","cn/half","cn/gpu","cn-heavy/xhv","cn-heavy/0","cn/hosp","cn/hyc","cn/ita","cn-lite/1","cn/mkt","cn/mox","cn/0","cn/r","cn/1","cn/2","cn/xtlv9","cn-pico/trtl","cn/upx","cn/web","cn/wow","cn/heavyx","cn/zls"],"algo-perf":{"cn/xao": 1.0,"cn/rto": 1.0,"cn/b2n": 1.0,"cn-heavy/tube": 1.0,"cn/ccx": 1.0,"cn/msr": 1.0,"cn/fast2": 1.0,"cn/gpu": 1.0,"cn-heavy/xhv": 1.0,"cn-heavy/0": 1.0,"cn/hosp": 1.0,"cn/hyc": 1.0,"cn/ita": 1.0,"cn-lite/1": 1.0,"cn/mkt": 1.0,"cn/mox": 1.0,"cn/0": 1.0,"cn/r": 1.0,"cn/1": 1.0,"cn/2": 1.0,"cn/xtlv9": 1.0,"cn-pico/trtl": 1.0,"cn/upx": 1.0,"cn/web": 1.0,"cn/wow": 1.0,"cn/heavyx": 1.0,"cn/zls": 1.0},"algo-min-time": 600}}
[2019-03-12 10:01:26] json_receive[319]: {"id":1,"jsonrpc":"2.0","error":null,"result":{"id":"267799770032539","job":{"height":1788847,"blob":"0b0bd7a39de40531afb4d90c10faa09d9e6beb0d7862e19e8bd3ca2264c573281e1e76369ed03d0 00000005c90b00426e0430be5b3a8cf6418e1393d13b48f8c1a0a5ea43c24131722c84701","job_id":"954352909803987","target":"4c7d0100"},"status":"OK"}}

[2019-03-12 10:03:16] stats: Algo switches: 1
[2019-03-12 10:03:16] stats: Last algo switch: 110 seconds ago
[2019-03-12 10:03:16] stats: Max allowed pool difficulty: 46000
[2019-03-12 10:03:16] stats: Pool: pool.minexmr.com:7777
[2019-03-12 10:03:16] stats: Connected since: 2019-03-12 10:01:26
[2019-03-12 10:03:16] stats: Last job received : 52 seconds ago
[2019-03-12 10:03:16] stats: Accepted(Stale)/Total shares: 70[1]/70

[2019-03-12 10:03:16] stats: Average time to find share: 1 seconds
[2019-03-12 10:03:16] stats: HW error: BUS_ID_19: 1
[2019-03-12 10:03:16] stats: HW error: BUS_ID_5: 1
[2019-03-12 10:03:16] stats: HW error: BUS_ID_22: 1
[2019-03-12 10:03:17] stats: Algo: normalv4
[2019-03-12 10:03:17] stats: Mining time: 0 days, 0 hours, 2 minutes, 27 seconds
[2019-03-12 10:03:17] stats: Algo switches: 1
[2019-03-12 10:03:17] stats: Last algo switch: 111 seconds ago
[2019-03-12 10:03:17] stats: Max allowed pool difficulty: 46000
[2019-03-12 10:03:17] stats: Pool: pool.minexmr.com:7777
[2019-03-12 10:03:17] stats: Connected since: 2019-03-12 10:01:26
[2019-03-12 10:03:17] stats: Last job received : 53 seconds ago
[2019-03-12 10:03:17] stats: Accepted(Stale)/Total shares: 70[1]/70

[2019-03-12 10:03:17] stats: Average time to find share: 1 seconds
[2019-03-12 10:03:17] stats: HW error: BUS_ID_19: 1
[2019-03-12 10:03:17] stats: HW error: BUS_ID_5: 1
[2019-03-12 10:03:17] stats: HW error: BUS_ID_22: 1
[2019-03-12 10:03:18] json_receive[269]: {"jsonrpc":"2.0","method":"job","params":{"height":1788850,"blob":"0b0bada59de405a3ade9d53f3a1fd0829f356da6d50fa77c64b56f17fec08bf881bfa0e1d2151b0 000000071ea72b18f5d09342e0586ebc175e474cd0ba6362f2ac4f984e1af0bdb8da33e02","job_id":"668582616041147","target":"4c7d0100"}}
[2019-03-12 10:03:18] pool_have_job: Pool sent a new job, block height 1788850 (ID: 668582616041147) [normalv4]
[2019-03-12 10:03:21] miner_result: Sending user result to pool
[2019-03-12 10:03:21] json_send[214]: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"267799770032539","job_id":"668582616041147","nonce":"375f74d1","result":"9f0f0504a3640008020d82dc59e99d9c91d0a363700fedaee807fbe7fdaa0000","algo":"cn/r"}}
[2019-03-12 10:03:21] json_receive[62]: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2019-03-12 10:03:21] miner_result: Pool accepted result 0x0000AAFD [152ms]
[2019-03-12 10:03:23] miner_result: Sending user result to pool
[2019-03-12 10:03:23] json_send[214]: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"267799770032539","job_id":"668582616041147","nonce":"45090000","result":"965872f2f062e38998347b80b58efb486828b18f965d1822bd1f0f42c3bd0000","algo":"cn/r"}}
[2019-03-12 10:03:23] json_receive[62]: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2019-03-12 10:03:23] miner_result: Pool accepted result 0x0000BDC3 [148ms]
[2019-03-12 10:03:24] miner_result: Sending user result to pool
[2019-03-12 10:03:24] json_send[214]: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"267799770032539","job_id":"668582616041147","nonce":"559e2eba","result":"712770f4e6618e350a2c425ac02273eaceb43d0414da0f8f75f343f659120100","algo":"cn/r"}}
[2019-03-12 10:03:24] json_receive[62]: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2019-03-12 10:03:24] miner_result: Pool accepted result 0x00011259 [144ms]

all log is the same stop without any error or message . i change every parameter  singly to find reason of error but i cant find it .
i just got HW error in Normal v4 -v4 R other algo work fine or have 1 or 2  error in few day.

[doktor83]

[2019-03-12 10:00:57] Restarting miner with normalv4 algo
[2019-03-12 10:00:57] Miner version: 1.7.9
[2019-03-12 10:00:57] Windows version: 10.0 build 17134
[2019-03-12 10:00:57] Video driver version: 24.20.11019.1004
.
.
.

Oh 1.7.9.. Please try 1.8.0, it may be possible that i already fixed this issue because i had users who reported they dont have crashes anymore in 1.8.0.

Also you could use much higher difficulty, better for you, better for the pool

[chimaeraa]

[2019-03-12 10:00:57] Restarting miner with normalv4 algo
[2019-03-12 10:00:57] Miner version: 1.7.9
[2019-03-12 10:00:57] Windows version: 10.0 build 17134
[2019-03-12 10:00:57] Video driver version: 24.20.11019.1004
.
.
.

Oh 1.7.9.. Please try 1.8.0, it may be possible that i already fixed this issue because i had users who reported they dont have crashes anymore in 1.8.0.

Also you could use much higher difficulty, better for you, better for the pool

tanx . i try it.

yes i know that but i got lot of stale shares.

[doktor83]

[2019-03-12 10:00:57] Restarting miner with normalv4 algo
[2019-03-12 10:00:57] Miner version: 1.7.9
[2019-03-12 10:00:57] Windows version: 10.0 build 17134
[2019-03-12 10:00:57] Video driver version: 24.20.11019.1004
.
.
.

Oh 1.7.9.. Please try 1.8.0, it may be possible that i already fixed this issue because i had users who reported they dont have crashes anymore in 1.8.0.

Also you could use much higher difficulty, better for you, better for the pool

tanx . i try it.

yes i know that but i got lot of stale shares.

Stales you see in miner are only informative, it just shows how many results were sent to the pool after a new job arrived.
Pool decides if a share is stale or not, or will it be accepted or not.

[chimaeraa]

[2019-03-12 10:00:57] Restarting miner with normalv4 algo
[2019-03-12 10:00:57] Miner version: 1.7.9
[2019-03-12 10:00:57] Windows version: 10.0 build 17134
[2019-03-12 10:00:57] Video driver version: 24.20.11019.1004
.
.
.

Oh 1.7.9.. Please try 1.8.0, it may be possible that i already fixed this issue because i had users who reported they dont have crashes anymore in 1.8.0.

Also you could use much higher difficulty, better for you, better for the pool

tanx . i try it.

yes i know that but i got lot of stale shares.

Stales you see in miner are only informative, it just shows how many results were sent to the pool after a new job arrived.
Pool decides if a share is stale or not, or will it be accepted or not.

ops. i don't know that. thank you .
can you give more details about --randomnonce  . some times i'm mining solo. it have any benefit or ... ?