Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching - page 58. (Read 237247 times)

ok so I tried again with default setting and no overclock. Still no go. Same errors.

I used 1.7.0 before. So I just copied pool.txt and start.bat to new 1.7.9 folder. Is there anything else I need to do? Seemed I missed something.

Jason's pool does not work.

Use the Graft Dev's testnet pool below.

http://3.83.140.241/

You can guess, the script can be empty.

Cool, thanks.

Last question. Is there any option / way to have the miner quit without any restarts when one of GPU's crash?

It goes in the appropriate config file, so yes, put it in normalv8 config if you want it to be enabled when using that config file.

Thanks for reply.

Do I need to create config.txt for this command or can it go in Config/config-normalv8.txt ?

If you could login to MO earlier then its not the bug i described your problem, then probably just MO wasn't working properly.
MO pools disconnect a lot...

After I've ran a new benchmark, now it is working. But I will tidy up the algos.txt, thanks for the info.
Could a VCredist reinstall help?
For the priority, I understand, no problem. Sometimes a few good words helps also. 

Regarding rhe crash, i cant really help, i have a few different crash cases that i am trying to hunt down and fix..

As with the login, try to remove a few algos that are not used from algos.txt, theres a bug that will be fixed in next version and its related to too many algos in algos.txt

Hello Doc,

New error:

In the morning it has started to mine after a reboot, but shortly after this the error comes again.

1. Going to check it out, but how is 20:10:48 after 20:10:50 ?  
2. Stats are read only, so really no need to protect anything, but i will consider it for a future version



No, but next version will support full cmd line parameters



Yes, i'm on discord, but thanks for your effort
Now we wait for block 286500

Jason has set up a Graft test pool, so I have found info below. I think you can test your implementation.

fork will be at 286500 block.

testnet explorer
https://testnet.graft.observer/

testnet testpool
https://testnet.graft.community

You can use my test wallet address below.
F9BptkHtPuRVRWv3WEa78uidriZZkxh3u5DjNSuYRqbhaW1hEiCfX1ZGMyf4EGfJt3EEMBVDoxGk9N7 MRUBGmZkhVnMVbjS

Does anyone know if "reboot_script_gpu_watchdog" command can be set in the start.bat file?

Hi, Doc!
1. In the last version there is a bug with watchdog, which cause random restart:

[2019-03-04 20:10:23] json_send[234]: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"96b65627-09c7-416c-b714-b9b7b0db8e27","job_id":"spBTylKdrhgNUGztZDhpBNKzxe/+","nonce":"a9090080","result":"478c71f8d734ba5d3f6d3fdc007ac0ef71f2a461f71ae8cfabb0f820c6120000"}}
[2019-03-04 20:10:23] json_receive[62]: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2019-03-04 20:10:23] miner_result: Pool accepted result 0x000012C6 [39ms]
[2019-03-04 20:10:44] hashrate: GPU0: 524 H/s [T:50c][BUS:1]
[2019-03-04 20:10:44] hashrate: GPU1: 524 H/s [T:50c][BUS:2]
[2019-03-04 20:10:44] hashrate: GPU2: 524 H/s [T:50c][BUS:3]
[2019-03-04 20:10:44] hashrate: GPU3: 524 H/s [T:52c][BUS:4]
[2019-03-04 20:10:44] hashrate: GPU4: 524 H/s [T:50c][BUS:5]
[2019-03-04 20:10:44] hashrate: Total: 2620 H/s
[2019-03-04 20:10:50] miner_result: Sending user result to pool
[2019-03-04 20:10:50] json_send[234]: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"96b65627-09c7-416c-b714-b9b7b0db8e27","job_id":"spBTylKdrhgNUGztZDhpBNKzxe/+","nonce":"8f5733b3","result":"80dfc0bacfcf0e18a6c7ca971e003b8b11548d6145f771b4ecc847cb6fa10000"}}
[2019-03-04 20:10:50] json_receive[62]: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2019-03-04 20:10:50] miner_result: Pool accepted result 0x0000A16F [39ms]
[2019-03-04 20:10:48] watchdog: No share sent for more than 71582788 minutes! Miner will restart
[2019-03-04 20:10:48] Restarting miner process

2. And what about to add feature to set up password for api and http access?

https://github.com/graft-project/GraftNetwork/pull/234

They have merged PR 234, so Fork will be at 299200 in about 3 days, and it looks like that xmrig and xmr-stak are ready now.

https://github.com/xmrig/xmrig/pull/963
https://github.com/fireice-uk/xmr-stak/pull/2261

Hello

After I've started using the 1.7.9 version in algoswitch mode (MoneroOcean) the miner crashes ~every two days.
In the Event Viewer I found the following:

Should I reinstall the VCredist?
Is there any built-in option to run a watchdog that restarts the SRB Miner after a crash?
This is my .bat file:

My config: Win10 up-to-date, Adrenalin 18.6.1, 6*Vega56 Strix

Thank you in advance!

yes.

before i fck my wife 2-3 time  on day but now i dont

mybe your GPU dirty. - new card have  beter hr. old card have lower and have high temperature.
new CAR  work fine but  old CAR dont work fine and you must old CAR drive litle slowly or  machine die.

comput eror = so high memory clock and to low power.

reduce clock and try.

example my card have many compute error- 30 in hour on 1100mhz 900mv but on 1098mhz 900mv dont have any compute error in 1 day

cn-v8 need more power for stable work. 1.7.8 same trouble?

Come on. They have been working for years now with new algo we have to clock down?

reduce memory clock or add power to memory