Bitcoin Forum
May 05, 2024, 04:05:11 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 [304] 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 ... 363 »
  Print  
Author Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching  (Read 237204 times)
thenextdinosaur
Newbie
*
Offline Offline

Activity: 13
Merit: 0


View Profile
February 27, 2019, 03:54:59 PM
 #6061

a logical thing to do would be to try out your wow settings without algo switching, so you will know is it related to gpu's not released correctly, driver crash, or it's just the algo.

Agreed. I left the miner mining exclusively cn-wow for the last 5 hours and had zero problems so far. In an algo-switching scenario I'd have already encountered at least 6-7 crashes in the same time frame - it really depends on how many times the algorithm switches. It might be also helpful to say that this crash happens sometimes and right after the algo switch. Sometimes it will switch to cn-wow and mine normally, sometimes it will lead to crashing GPUs and subsequently mining with 10-15% of the hashrate until miner restarts.

I can leave it mining wownero for a longer time, but I'm almost ready to discard this being an overclock issue.
1714925111
Hero Member
*
Offline Offline

Posts: 1714925111

View Profile Personal Message (Offline)

Ignore
1714925111
Reply with quote  #2

1714925111
Report to moderator
1714925111
Hero Member
*
Offline Offline

Posts: 1714925111

View Profile Personal Message (Offline)

Ignore
1714925111
Reply with quote  #2

1714925111
Report to moderator
1714925111
Hero Member
*
Offline Offline

Posts: 1714925111

View Profile Personal Message (Offline)

Ignore
1714925111
Reply with quote  #2

1714925111
Report to moderator
The network tries to produce one block per 10 minutes. It does this by automatically adjusting how difficult it is to produce blocks.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714925111
Hero Member
*
Offline Offline

Posts: 1714925111

View Profile Personal Message (Offline)

Ignore
1714925111
Reply with quote  #2

1714925111
Report to moderator
doktor83 (OP)
Hero Member
*****
Offline Offline

Activity: 2520
Merit: 626


View Profile WWW
February 27, 2019, 04:06:34 PM
 #6062

a logical thing to do would be to try out your wow settings without algo switching, so you will know is it related to gpu's not released correctly, driver crash, or it's just the algo.

Agreed. I left the miner mining exclusively cn-wow for the last 5 hours and had zero problems so far. In an algo-switching scenario I'd have already encountered at least 6-7 crashes in the same time frame - it really depends on how many times the algorithm switches. It might be also helpful to say that this crash happens sometimes and right after the algo switch. Sometimes it will switch to cn-wow and mine normally, sometimes it will lead to crashing GPUs and subsequently mining with 10-15% of the hashrate until miner restarts.

I can leave it mining wownero for a longer time, but I'm almost ready to discard this being an overclock issue.

Is the miner crashing or the video driver? Do you get the 'hardware blocked..' system message ?

SRBMiner-MULTI thread - HERE
http://www.srbminer.com
thenextdinosaur
Newbie
*
Offline Offline

Activity: 13
Merit: 0


View Profile
February 27, 2019, 04:22:11 PM
 #6063

Is the miner crashing or the video driver? Do you get the 'hardware blocked..' system message ?

The miner doesn't crash (the window doesn't close). The message I receive is from watchdog "GPU crash detected, miner will try to restart".
sharix80
Newbie
*
Offline Offline

Activity: 31
Merit: 0


View Profile
February 27, 2019, 08:26:39 PM
 #6064

Hi, doktor83!
Mox algo show rejected result on 1.7.9, but 1.7.8 works fine! Please, fix it. Thanks for you job!
Frianik
Newbie
*
Offline Offline

Activity: 23
Merit: 0


View Profile
February 27, 2019, 11:13:07 PM
 #6065

One issue that I've been getting since earlier versions is that, while mining on a pool with multi-algo support (MO), sometimes the miner will just close without any apparent reason. The command prompt window just closes. When checking the log, nothing abnormal was happening. Sometimes the last line on the log is an algo change, sometimes is submitting a share. Miner just closes. Any idea of what may cause that or what else can I do to test more and provide more feedback?
i have the same issue. randomly closes at multialgo and work like a charm for weeks at single algo. rigs 8-9 vegas. nothing unusual in logs.
GKumaran
Member
**
Offline Offline

Activity: 204
Merit: 10


View Profile
February 28, 2019, 01:40:14 AM
 #6066

Hi, doktor83!
Mox algo show rejected result on 1.7.9, but 1.7.8 works fine! Please, fix it. Thanks for you job!

Please read the release notes. Thanks for scrolling up.
thenextdinosaur
Newbie
*
Offline Offline

Activity: 13
Merit: 0


View Profile
February 28, 2019, 12:33:12 PM
 #6067

i have the same issue. randomly closes at multialgo and work like a charm for weeks at single algo. rigs 8-9 vegas. nothing unusual in logs.

The developer said he hoped this would be fixed in this new version, but today I experienced it again: the miner window closed by itself and there wasn't anything unusual in the logs, just normal mining.
doktor83 (OP)
Hero Member
*****
Offline Offline

Activity: 2520
Merit: 626


View Profile WWW
February 28, 2019, 12:42:07 PM
 #6068

i have the same issue. randomly closes at multialgo and work like a charm for weeks at single algo. rigs 8-9 vegas. nothing unusual in logs.

The developer said he hoped this would be fixed in this new version, but today I experienced it again: the miner window closed by itself and there wasn't anything unusual in the logs, just normal mining.

Could you guys tell me which version of windows 10 are you using?
I have a feeling it is older than 1809.

SRBMiner-MULTI thread - HERE
http://www.srbminer.com
thenextdinosaur
Newbie
*
Offline Offline

Activity: 13
Merit: 0


View Profile
February 28, 2019, 01:19:17 PM
 #6069

I have a feeling it is older than 1809.

1803.
jasonyslai
Newbie
*
Offline Offline

Activity: 11
Merit: 0


View Profile
February 28, 2019, 03:26:17 PM
 #6070

Will srbminer support CryptoNightR soon  Roll Eyes ?
Baikal miner
Newbie
*
Offline Offline

Activity: 53
Merit: 0


View Profile
February 28, 2019, 08:39:49 PM
 #6071

http://prntscr.com/mrj02u why webchain not work?
sharix80
Newbie
*
Offline Offline

Activity: 31
Merit: 0


View Profile
February 28, 2019, 08:57:22 PM
 #6072

Will srbminer support CryptoNightR soon  Roll Eyes ?

I think its Cryptonight V4 (R)
livada
Newbie
*
Offline Offline

Activity: 417
Merit: 0


View Profile WWW
February 28, 2019, 11:00:11 PM
 #6073

http://prntscr.com/mrj02u why webchain not work?

all work fine.

http://imgbox.com/TpGFLAvl
Frianik
Newbie
*
Offline Offline

Activity: 23
Merit: 0


View Profile
February 28, 2019, 11:34:56 PM
 #6074

i have the same issue. randomly closes at multialgo and work like a charm for weeks at single algo. rigs 8-9 vegas. nothing unusual in logs.

The developer said he hoped this would be fixed in this new version, but today I experienced it again: the miner window closed by itself and there wasn't anything unusual in the logs, just normal mining.

Could you guys tell me which version of windows 10 are you using?
I have a feeling it is older than 1809.
1803 too
sky2018miner
Newbie
*
Offline Offline

Activity: 33
Merit: 0


View Profile
March 01, 2019, 12:00:19 AM
Last edit: March 01, 2019, 12:12:35 AM by sky2018miner
 #6075

Hello dear developer
faced with incomprehensible message in miner:

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

strange but the message is not displayed in the log
what could be the problem
sky2018miner
Newbie
*
Offline Offline

Activity: 33
Merit: 0


View Profile
March 01, 2019, 12:01:38 AM
 #6076

log
[2019-03-01 01:43:50] Miner version: 1.7.9
[2019-03-01 01:43:50] Windows version: 10.0 build 16299
[2019-03-01 01:43:50] Video driver version: 24.20.11021.1000
[2019-03-01 01:43:50] Startup monitor attached
[2019-03-01 01:43:58] AMD Platform ID: 0
[2019-03-01 01:43:58] AMD platform FOUND
[2019-03-01 01:43:58] Found 6 AMD devices
[2019-03-01 01:43:58] CPU AES-NI: FALSE
[2019-03-01 01:43:58] GPU0: AMD Radeon R9 200 Series [tonga] [2048 MB][I: 30.0][W: 16][T: 2][F: 16][BUS: 8]
[2019-03-01 01:43:58] GPU1: Radeon(TM) RX 460 Graphics [baffin] [2048 MB][I: 27.0][W: 16][T: 2][F: 16][BUS: 4]
[2019-03-01 01:43:58] GPU2: AMD Radeon R7 200 Series [pitcairn] [2048 MB][I: 30.0][W: 16][T: 2][F: 16][BUS: 10]
[2019-03-01 01:43:58] GPU3: AMD Radeon (TM) R7 370 Series [pitcairn] [2048 MB][I: 30.0][W: 16][T: 2][F: 16][BUS: 9]
[2019-03-01 01:43:58] GPU4: AMD Radeon (TM) R7 370 Series [pitcairn] [2048 MB][I: 30.0][W: 16][T: 2][F: 16][BUS: 11]
[2019-03-01 01:43:58] GPU5: Radeon(TM) RX 460 Graphics [baffin] [2048 MB][I: 17.0][W: 16][T: 2][F: 16][BUS: 1]
[2019-03-01 01:43:58] ADL is enabled
[2019-03-01 01:43:58] Algorithm: Cryptonight Wownero
[2019-03-01 01:43:58] Algo switching: disabled
[2019-03-01 01:43:58] Startup monitor: enabled
[2019-03-01 01:43:58] Gpu watchdog: enabled [gpu disable mode]
[2019-03-01 01:43:58] Coin forking: disabled
[2019-03-01 01:43:58] Starting init of mining threads
[2019-03-01 01:43:58] Created OCL context
[2019-03-01 01:43:58] Using fragments 16 for DeviceID 0 (Thread 0)
[2019-03-01 01:43:58] Using heavy_mode 1 for DeviceID 0 (Thread 0)
[2019-03-01 01:43:58] Using thread_delay 319 for DeviceID 0 (Thread 0)
[2019-03-01 01:43:59] Created OCL input buffer for DeviceID 0 (Thread 0)
[2019-03-01 01:43:59] Loading [wownero] kernel for DEVICE BUS_ID[8]
[2019-03-01 01:43:59] ctx->Program for DeviceID 0 (Thread 0) loaded
[2019-03-01 01:43:59] Using fragments 16 for DeviceID 0 (Thread 1)
[2019-03-01 01:43:59] Using heavy_mode 1 for DeviceID 0 (Thread 1)
[2019-03-01 01:43:59] Using thread_delay 319 for DeviceID 0 (Thread 1)
[2019-03-01 01:43:59] Created OCL input buffer for DeviceID 0 (Thread 1)
[2019-03-01 01:43:59] Loading [wownero] kernel for DEVICE BUS_ID[8]
[2019-03-01 01:43:59] ctx->Program for DeviceID 0 (Thread 1) loaded
[2019-03-01 01:43:59] Using fragments 16 for DeviceID 1 (Thread 2)
[2019-03-01 01:43:59] Using heavy_mode 1 for DeviceID 1 (Thread 2)
[2019-03-01 01:43:59] Using thread_delay 319 for DeviceID 1 (Thread 2)
[2019-03-01 01:43:59] Created OCL input buffer for DeviceID 1 (Thread 2)
[2019-03-01 01:43:59] Loading [wownero] kernel for DEVICE BUS_ID[4]
[2019-03-01 01:43:59] ctx->Program for DeviceID 1 (Thread 2) loaded
[2019-03-01 01:43:59] Using fragments 16 for DeviceID 1 (Thread 3)
[2019-03-01 01:43:59] Using heavy_mode 1 for DeviceID 1 (Thread 3)
[2019-03-01 01:43:59] Using thread_delay 319 for DeviceID 1 (Thread 3)
[2019-03-01 01:43:59] Created OCL input buffer for DeviceID 1 (Thread 3)
[2019-03-01 01:43:59] Loading [wownero] kernel for DEVICE BUS_ID[4]
[2019-03-01 01:43:59] ctx->Program for DeviceID 1 (Thread 3) loaded
[2019-03-01 01:43:59] Using fragments 16 for DeviceID 2 (Thread 4)
[2019-03-01 01:43:59] Using heavy_mode 1 for DeviceID 2 (Thread 4)
[2019-03-01 01:43:59] Using thread_delay 319 for DeviceID 2 (Thread 4)
[2019-03-01 01:43:59] Created OCL input buffer for DeviceID 2 (Thread 4)
[2019-03-01 01:43:59] Loading [wownero] kernel for DEVICE BUS_ID[10]
[2019-03-01 01:43:59] ctx->Program for DeviceID 2 (Thread 4) loaded
[2019-03-01 01:43:59] Using fragments 16 for DeviceID 2 (Thread 5)
[2019-03-01 01:43:59] Using heavy_mode 1 for DeviceID 2 (Thread 5)
[2019-03-01 01:43:59] Using thread_delay 319 for DeviceID 2 (Thread 5)
[2019-03-01 01:43:59] Created OCL input buffer for DeviceID 2 (Thread 5)
[2019-03-01 01:43:59] Loading [wownero] kernel for DEVICE BUS_ID[10]
[2019-03-01 01:43:59] ctx->Program for DeviceID 2 (Thread 5) loaded
[2019-03-01 01:43:59] Using fragments 16 for DeviceID 3 (Thread 6)
[2019-03-01 01:43:59] Using heavy_mode 1 for DeviceID 3 (Thread 6)
[2019-03-01 01:43:59] Using thread_delay 319 for DeviceID 3 (Thread 6)
[2019-03-01 01:43:59] Created OCL input buffer for DeviceID 3 (Thread 6)
[2019-03-01 01:43:59] Loading [wownero] kernel for DEVICE BUS_ID[9]
[2019-03-01 01:43:59] ctx->Program for DeviceID 3 (Thread 6) loaded
[2019-03-01 01:43:59] Using fragments 16 for DeviceID 3 (Thread 7)
[2019-03-01 01:43:59] Using heavy_mode 1 for DeviceID 3 (Thread 7)
[2019-03-01 01:43:59] Using thread_delay 319 for DeviceID 3 (Thread 7)
[2019-03-01 01:43:59] Created OCL input buffer for DeviceID 3 (Thread 7)
[2019-03-01 01:43:59] Loading [wownero] kernel for DEVICE BUS_ID[9]
[2019-03-01 01:43:59] ctx->Program for DeviceID 3 (Thread 7) loaded
[2019-03-01 01:43:59] Using fragments 16 for DeviceID 4 (Thread Cool
[2019-03-01 01:43:59] Using heavy_mode 1 for DeviceID 4 (Thread Cool
[2019-03-01 01:43:59] Using thread_delay 319 for DeviceID 4 (Thread Cool
[2019-03-01 01:44:00] Created OCL input buffer for DeviceID 4 (Thread Cool
[2019-03-01 01:44:00] Loading [wownero] kernel for DEVICE BUS_ID[11]
[2019-03-01 01:44:00] ctx->Program for DeviceID 4 (Thread Cool loaded
[2019-03-01 01:44:00] Using fragments 16 for DeviceID 4 (Thread 9)
[2019-03-01 01:44:00] Using heavy_mode 1 for DeviceID 4 (Thread 9)
[2019-03-01 01:44:00] Using thread_delay 319 for DeviceID 4 (Thread 9)
[2019-03-01 01:44:00] Created OCL input buffer for DeviceID 4 (Thread 9)
[2019-03-01 01:44:00] Loading [wownero] kernel for DEVICE BUS_ID[11]
[2019-03-01 01:44:00] ctx->Program for DeviceID 4 (Thread 9) loaded
[2019-03-01 01:44:00] Using fragments 16 for DeviceID 5 (Thread 10)
[2019-03-01 01:44:00] Using heavy_mode 1 for DeviceID 5 (Thread 10)
[2019-03-01 01:44:00] Using thread_delay 319 for DeviceID 5 (Thread 10)
[2019-03-01 01:44:00] Created OCL input buffer for DeviceID 5 (Thread 10)
[2019-03-01 01:44:00] Loading [wownero] kernel for DEVICE BUS_ID[1]
[2019-03-01 01:44:00] ctx->Program for DeviceID 5 (Thread 10) loaded
[2019-03-01 01:44:00] Using fragments 16 for DeviceID 5 (Thread 11)
[2019-03-01 01:44:00] Using heavy_mode 1 for DeviceID 5 (Thread 11)
[2019-03-01 01:44:00] Using thread_delay 319 for DeviceID 5 (Thread 11)
[2019-03-01 01:44:00] Created OCL input buffer for DeviceID 5 (Thread 11)
[2019-03-01 01:44:00] Loading [wownero] kernel for DEVICE BUS_ID[1]
[2019-03-01 01:44:00] ctx->Program for DeviceID 5 (Thread 11) loaded
[2019-03-01 01:44:00] ADL initialised successfully!
[2019-03-01 01:44:00] Finished init of mining threads
[2019-03-01 01:44:01] Startup monitor detached
[2019-03-01 01:44:01] Gpu watchdog started
[2019-03-01 01:44:01] GPU temperature protection monitor started
[2019-03-01 01:44:01] API disabled
[2019-03-01 01:44:01] json_send[250]: {"id":1,"jsonrpc": "2.0","method":"login","params":{"login":"So2ifgjqGMZJhCrqpFMotQQAiJAiATuJLNAK2HrPLoNzK8hkqNbf9t8gmx6bzAQrXRMnWnoELoiD6GT v8guPBRwH5yoQbDfkcfs148iNYUiP","pass":"rig01","agent":"SRBMiner Cryptonight AMD GPU miner/1.7.9","rigid":""}}
[2019-03-01 01:44:01] json_receive[411]: {"id":1,"jsonrpc":"2.0","error":null,"result":{"id":"1ac87293-fd83-45f7-8933-ea1b00abff8a","job":{"blob":"0c0ccae1e1e305a14eb0a93d45fc16ec846a1d38b67bc410b1051b68289a2dfacd2f207af33e470 0000000c59b260cbf902571a1df08cc87917c2a4b2b80f45858cbad0364511943282e0f01","height":84726,"algo":"cn/wow","job_id":"ID+34V//NiO7iBMfqtSh9doqSXWb","target":"b88d0600","id":"1ac87293-fd83-45f7-8933-ea1b00abff8a"},"status":"OK"}}
[2019-03-01 01:44:01] Connected to pool.wowne.ro:5555
[2019-03-01 01:44:01] sock_ready: User logged in
[2019-03-01 01:44:01] pool_have_job: Pool sent a new job, block height 84726 (ID: ID+34V//NiO7iBMfqtSh9doqSXWb)
[2019-03-01 01:44:04] miner_result: Sending user result to pool
[2019-03-01 01:44:04] json_send[234]: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"1ac87293-fd83-45f7-8933-ea1b00abff8a","job_id":"ID+34V//NiO7iBMfqtSh9doqSXWb","nonce":"c15555d5","result":"54275643272ff8423d35dbfc83564499df29155ef53011ad86c5a85b3f440400"}}
[2019-03-01 01:44:04] json_receive[340]: {"jsonrpc":"2.0","method":"job","params":{"blob":"0c0ccae1e1e305a14eb0a93d45fc16ec846a1d38b67bc410b1051b68289a2dfacd2f207af33e470 00000005b8be802115faab87ab9f6796701fdd7cd2355a4170eafb36a2bffd8715741c001","height":84726,"algo":"cn/wow","job_id":"NzAX8Gp6nHYlWTgv4uXFs22tugWI","target":"bc9a0300","id":"1ac87293-fd83-45f7-8933-ea1b00abff8a"}}
[2019-03-01 01:44:04] pool_have_job: Pool sent a new job, block height 84726 (ID: NzAX8Gp6nHYlWTgv4uXFs22tugWI)
[2019-03-01 01:44:04] json_receive[62]: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2019-03-01 01:44:04] miner_result: Pool accepted result 0x0004443F [142ms]
[2019-03-01 01:44:07] miner_result: Sending user result to pool
[2019-03-01 01:44:07] json_send[234]: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"1ac87293-fd83-45f7-8933-ea1b00abff8a","job_id":"ID+34V//NiO7iBMfqtSh9doqSXWb","nonce":"86abaa6a","result":"3ac719dc9fbfd37ff7b618aa6fb282a3160576a8a8ef898b28526ce33d210100"}}
[2019-03-01 01:44:07] json_receive[62]: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2019-03-01 01:44:07] miner_result: Pool accepted result 0x0001213D [80ms]
alibabacool
Full Member
***
Offline Offline

Activity: 139
Merit: 100


View Profile
March 01, 2019, 01:08:27 AM
 #6077

Hi, Doc!
Could you add feature to set up password for api and http access?
Paullus
Newbie
*
Offline Offline

Activity: 21
Merit: 0


View Profile WWW
March 01, 2019, 08:35:11 AM
 #6078

Dear developer. AMD RX470 algorithm webchain don't work! Can immediately stale balls to pour, can after 10 minutes. And the miner closes.
nordmann666
Member
**
Offline Offline

Activity: 361
Merit: 16


View Profile
March 01, 2019, 08:48:35 AM
 #6079

Dear developer. AMD RX470 algorithm webchain don't work! Can immediately stale balls to pour, can after 10 minutes. And the miner closes.

dont ask for webchain support - he wont fix or something..it´s the algo that is "shit"
Paullus
Newbie
*
Offline Offline

Activity: 21
Merit: 0


View Profile WWW
March 01, 2019, 09:00:48 AM
 #6080

Dear developer. AMD RX470 algorithm webchain don't work! Can immediately stale balls to pour, can after 10 minutes. And the miner closes.

dont ask for webchain support - he wont fix or something..it´s the algo that is "shit"
according to reviews VEGA 64 works with a Bang, and 470 no
Pages: « 1 ... 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 [304] 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 ... 363 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!