MINING: Restart of the rig PLES HELP ME !!!

[Filippo Tognola]

Hi there,
First of all, let me say that I am not an expert in mining and I do not speak good English.
Every 10 minutes or so I get this error on my monitor and the rig restarts, (Watchdog triggering miner shutdown after restart script execution).
I currently have two rigs, the first with 6xAMD 6600 that never gave me any problems, and the second (the rig in question) with 1xAMD 5600XT.
They both have the same setup, same motherboard, same processor, same RAM, same Miner.
At the time of reboot the card is not overheated but is around 40°C.
I currently use TeamRedMiner (latest version 0.9.0) and as OS I use SimpleMining.
I attach the overclock settings, the miner settings and the error that comes out on the monitor.
I hope to find a solution and thank you very much in advance for an answer.

[Lafu]

I currently use TeamRedMiner

Hello Filippo Tognola as you see i quoted only the Miner you are using " TeamRedMiner " .
And as you have written that you not speak good english thats the only reason i writte this here now .
Because there 2 simple ways to find the problem.

1. Try to google the error your got " Watchdog triggering miner shutdown after restart script execution " (Thats what i have done)
2. You looking straight into the Thread of the TeamRedMiner .

And you will not believe it Google toke me straight to the Thread of TeamRedMiner with already written there the same problem.
Look at this post here and also read the next posts also and it maybe would be helping to fix the problem you got.
https://bitcointalk.org/index.php?topic=5059817.msg48416978#msg48416978

Good Luck and hope this will solve your problem.

[rdluffy]

If you didn't solve yet with the thread of Teamredminer, I suggest you to do the basics first:

1 - Put everything at stock settings, no overclock on GPU, this is the most common error

2 - Change the miner, test PhoenixMiner and Nbminer, these are two good miners

3 - Check every piece of cable and connectors, check riser cable too if you're using one

4 - And last, try another OS, like HiveOs or even windows

High chances that you'll solve your problem with these steps, most of times are bad overclock, changing the miner can help you too, there are some times that I solved issues only changing miners, riser cables are often defectives, or some cable can be detached, and last, changing the OS can solve issues with drivers and incompatibility.

[Lafu]

first of all thank you very much for the reply, I already tried to search on goggle for the solution but I didn't find anything that made me solve the problem.
THE link you indicated didn't help me either, as I couldn't find any good solution.

You are Welcome .
I was looking again today about the error message you got and found another link where they also have nearly the same problem or issue.
Dont know if that link will gets you closer to solve your problem but maybe take a look there.
The most of them write that they get the error message because of to much OC settings , as i guess that is the reason you get the message.
But yeah it also can be some kind of problem of a hardware as rdluffy has written.

Read the link here : https://forum.hiveos.farm/t/team-red-miner-error-gpu-2-detected-dead-07-00-0-will-execute-restart-script-watchdog-sh/16330
Hope you will find the problem soon.

[philipma1957]

Hi there,
First of all, let me say that I am not an expert in mining and I do not speak good English.
Every 10 minutes or so I get this error on my monitor and the rig restarts, (Watchdog triggering miner shutdown after restart script execution).
I currently have two rigs, the first with 6xAMD 6600 that never gave me any problems, and the second (the rig in question) with 1xAMD 5600XT.
They both have the same setup, same motherboard, same processor, same RAM, same Miner.
At the time of reboot the card is not overheated but is around 40°C.
I currently use TeamRedMiner (latest version 0.9.0) and as OS I use SimpleMining.
I attach the overclock settings, the miner settings and the error that comes out on the monitor.
I hope to find a solution and thank you very much in advance for an answer.

so you have a 1 card rig with an amd 5600

use phoenix miner.

give me a minute


set

core
1000


memory
880


core undervolt
700

memory uv mvdd mv
1275

memory uv mvddci
800


aggressive under volt
on
power stage
4
temp
70
fan
55


do phoenixminer v5.9d

-eres 4 -pool stratum+tcp://eth.viabtc.top:3333 -wal yourname.87 -pass x -proto 4 -rmode 2 -stales 0

and the os image is number below from the download page


SimpleMiningOS (SM-i021-5.10.60-1-a20.40-n470.74) - (mirror) (740 MB)
AMD RX 370 / 380 / 390 / 470 / 480 / 550 / 560 / 570 / 580 / 590 / Vega / Radeon VII / RX 5500 / 5600 / 5700 / 6600 / 6700 / 6800 / 6900 / PRO 6500M
NVIDIA 1050 / 1060 / 1070 / 1080 / P102 / P104 / P106 / 1650 / 1660 / 2060 / 2070 / 2080 / 3050 / 3060 / 3070 / 3080 / 3090 / 30HX / 40HX / 50HX / 70HX / 90HX

I get 37 hash and 73 watt on my 5600

[Filippo Tognola]

Hi there,
First of all, let me say that I am not an expert in mining and I do not speak good English.
Every 10 minutes or so I get this error on my monitor and the rig restarts, (Watchdog triggering miner shutdown after restart script execution).
I currently have two rigs, the first with 6xAMD 6600 that never gave me any problems, and the second (the rig in question) with 1xAMD 5600XT.
They both have the same setup, same motherboard, same processor, same RAM, same Miner.
At the time of reboot the card is not overheated but is around 40°C.
I currently use TeamRedMiner (latest version 0.9.0) and as OS I use SimpleMining.
I attach the overclock settings, the miner settings and the error that comes out on the monitor.
I hope to find a solution and thank you very much in advance for an answer.

so you have a 1 card rig with an amd 5600

use phoenix miner.

give me a minute


set

core
1000


memory
880


core undervolt
700

memory uv mvdd mv
1275

memory uv mvddci
800


aggressive under volt
on
power stage
4
temp
70
fan
55


do phoenixminer v5.9d

-eres 4 -pool stratum+tcp://eth.viabtc.top:3333 -wal yourname.87 -pass x -proto 4 -rmode 2 -stales 0

and the os image is number below from the download page


SimpleMiningOS (SM-i021-5.10.60-1-a20.40-n470.74) - (mirror) (740 MB)
AMD RX 370 / 380 / 390 / 470 / 480 / 550 / 560 / 570 / 580 / 590 / Vega / Radeon VII / RX 5500 / 5600 / 5700 / 6600 / 6700 / 6800 / 6900 / PRO 6500M
NVIDIA 1050 / 1060 / 1070 / 1080 / P102 / P104 / P106 / 1650 / 1660 / 2060 / 2070 / 2080 / 3050 / 3060 / 3070 / 3080 / 3090 / 30HX / 40HX / 50HX / 70HX / 90HX

I get 37 hash and 73 watt on my 5600

Hi, thank you so much for your response and your time.
I tried using phoemix and the settings you recommended.
It works for about 10/15 minutes at 40MH/s and then it restarts after telling me it crashed.
I put here the error code:

*** 0:03 *** 12/30 10:02 **************************************
Eth: Mining ETH on eth.2miners.com:2020 for 0:03
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:03
1 GPU(s) are auto-tuning. Hashrate may be low until they are ready.
Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
Eth: Average speed (5 min): 7.733 MH/s
Eth: Effective speed: 0.00 MH/s; at pool: 0.00 MH/s
Eth: New job #191b4133 from eth.2miners.com:2020; diff: 8726MH
GPU1: 28C 54% 23W
GPUs power: 23.0 W
Eth: New job #f929531d from eth.2miners.com:2020; diff: 8726MH
Eth: New job #7b3cb4f3 from eth.2miners.com:2020; diff: 8726MH
Rebooting
(by mining software). Check crash logs.
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:03
Eth: New job #b30336df from eth.2miners.com:2020; diff: 8726MH
Miner ended or crashed. Restarting miner in 30 seconds...

[Filippo Tognola]

I currently use TeamRedMiner

Hello Filippo Tognola as you see i quoted only the Miner you are using " TeamRedMiner " .
And as you have written that you not speak good english thats the only reason i writte this here now .
Because there 2 simple ways to find the problem.

1. Try to google the error your got " Watchdog triggering miner shutdown after restart script execution " (Thats what i have done)
2. You looking straight into the Thread of the TeamRedMiner .

And you will not believe it Google toke me straight to the Thread of TeamRedMiner with already written there the same problem.
Look at this post here and also read the next posts also and it maybe would be helping to fix the problem you got.
https://bitcointalk.org/index.php?topic=5059817.msg48416978#msg48416978

Good Luck and hope this will solve your problem.

first of all thank you very much for the reply, I already tried to search on goggle for the solution but I didn't find anything that made me solve the problem.
THE link you indicated didn't help me either, as I couldn't find any good solution.

[Filippo Tognola]

first of all thank you very much for the reply, I already tried to search on goggle for the solution but I didn't find anything that made me solve the problem.
THE link you indicated didn't help me either, as I couldn't find any good solution.

You are Welcome .
I was looking again today about the error message you got and found another link where they also have nearly the same problem or issue.
Dont know if that link will gets you closer to solve your problem but maybe take a look there.
The most of them write that they get the error message because of to much OC settings , as i guess that is the reason you get the message.
But yeah it also can be some kind of problem of a hardware as rdluffy has written.

Read the link here : cute-restart-script-watchdog-sh/16330
Hope you will find the problem soon.

hello, thanks for the reply, Before I proposed the question here on this forum I had already seen that forum with that question but I didn't find any good and concrete solution.
I am really desperate

[Filippo Tognola]

If you didn't solve yet with the thread of Teamredminer, I suggest you to do the basics first:

1 - Put everything at stock settings, no overclock on GPU, this is the most common error

2 - Change the miner, test PhoenixMiner and Nbminer, these are two good miners

3 - Check every piece of cable and connectors, check riser cable too if you're using one

4 - And last, try another OS, like HiveOs or even windows

High chances that you'll solve your problem with these steps, most of times are bad overclock, changing the miner can help you too, there are some times that I solved issues only changing miners, riser cables are often defectives, or some cable can be detached, and last, changing the OS can solve issues with drivers and incompatibility.

hello, at the moment I am not using any riser board, the overclock settings are mandatory and I am using the recommended ones, but with none of them works.
As operating system I use SimpleMining that on the other rigs works perfectly.
Cables and connectors I have changed them but nothing changes.
I've used phoemix and teamredminer and neither works for more than 10/15 minutes without rebooting.

[rdluffy]

hello, at the moment I am not using any riser board, the overclock settings are mandatory and I am using the recommended ones, but with none of them works.
As operating system I use SimpleMining that on the other rigs works perfectly.
Cables and connectors I have changed them but nothing changes.
I've used phoemix and teamredminer and neither works for more than 10/15 minutes without rebooting.

You need to test without any overclock, remember, you're trying to find the error, with overclock you're not doing right
Every gpu have it's own properties, and even with the same models, each one is different to achieve clocks and power
So, to test, it's important to be at stock settings
If works in stock, you'll know your overclock is high and you can start at stock and increase a bit until crash again

And last, try another OS, even if you have Simple mining working in another rigs

[Filippo Tognola]

hello, at the moment I am not using any riser board, the overclock settings are mandatory and I am using the recommended ones, but with none of them works.
As operating system I use SimpleMining that on the other rigs works perfectly.
Cables and connectors I have changed them but nothing changes.
I've used phoemix and teamredminer and neither works for more than 10/15 minutes without rebooting.

You need to test without any overclock, remember, you're trying to find the error, with overclock you're not doing right
Every gpu have it's own properties, and even with the same models, each one is different to achieve clocks and power
So, to test, it's important to be at stock settings
If works in stock, you'll know your overclock is high and you can start at stock and increase a bit until crash again

And last, try another OS, even if you have Simple mining working in another rigs

ok now i try to see how it behaves without overclocking.
I don't think I'll be able to change the operating system, nicehashOS didn't work, hiveOS didn't work either, simplemining is the only one that works well.

[Filippo Tognola]

hello, at the moment I am not using any riser board, the overclock settings are mandatory and I am using the recommended ones, but with none of them works.
As operating system I use SimpleMining that on the other rigs works perfectly.
Cables and connectors I have changed them but nothing changes.
I've used phoemix and teamredminer and neither works for more than 10/15 minutes without rebooting.

You need to test without any overclock, remember, you're trying to find the error, with overclock you're not doing right
Every gpu have it's own properties, and even with the same models, each one is different to achieve clocks and power
So, to test, it's important to be at stock settings
If works in stock, you'll know your overclock is high and you can start at stock and increase a bit until crash again

And last, try another OS, even if you have Simple mining working in another rigs

Hi, I've tried running the GPU without overclocking settings and after 2 hours it still hasn't rebooted and remains stable at 32MH/s, so I think it's the fault of some overclocking settings.
The overclock settings I was using were:
Core clock: 1250
Memory clock: 870
Core Voltage: 725
Memory voltage: 1300
Memory control voltage: 800
Can you tell me what to change or why with these settings the rig restarts every 10 minutes and without it works fine?

[rdluffy]

Hi, I've tried running the GPU without overclocking settings and after 2 hours it still hasn't rebooted and remains stable at 32MH/s, so I think it's the fault of some overclocking settings.
The overclock settings I was using were:
Core clock: 1250
Memory clock: 870
Core Voltage: 725
Memory voltage: 1300
Memory control voltage: 800
Can you tell me what to change or why with these settings the rig restarts every 10 minutes and without it works fine?

Let it running for a couple of hours, just to be sure

It's simple, your card can't handle the settings you put on overclock, as I said, every card is different, each piece of silicon is different, even in same model of GPUs

Look at above, philipma1957 put his config

I have 5600XT too, Asus, with Micron memories, and my settings are:

Core clock - 1299
Memory clock - 925
Core voltage - 805
Memory voltage - 1325
Memory Controller voltage - 845


In your case I would do overclock step by step, put your clock at 1250 or 1300, and set your memory at 850, fan speed to 80% and everything else on stock, and you will test, if works, put more clock on memories, until crashes, and then get back 1 step to the last stable clock

After that, and only after that, you can change the rest of settings

[Filippo Tognola]

Hi, I've tried running the GPU without overclocking settings and after 2 hours it still hasn't rebooted and remains stable at 32MH/s, so I think it's the fault of some overclocking settings.
The overclock settings I was using were:
Core clock: 1250
Memory clock: 870
Core Voltage: 725
Memory voltage: 1300
Memory control voltage: 800
Can you tell me what to change or why with these settings the rig restarts every 10 minutes and without it works fine?

Let it running for a couple of hours, just to be sure

It's simple, your card can't handle the settings you put on overclock, as I said, every card is different, each piece of silicon is different, even in same model of GPUs

Look at above, philipma1957 put his config

I have 5600XT too, Asus, with Micron memories, and my settings are:

Core clock - 1299
Memory clock - 925
Core voltage - 805
Memory voltage - 1325
Memory Controller voltage - 845


In your case I would do overclock step by step, put your clock at 1250 or 1300, and set your memory at 850, fan speed to 80% and everything else on stock, and you will test, if works, put more clock on memories, until crashes, and then get back 1 step to the last stable clock

After that, and only after that, you can change the rest of settings

thank you so much for your response and help, I really appreciate it.
I've already tried Philipma1957's settings, and the card would still reboot.
I must say that I am not an expert in the field of overclocking, I have always relied on models found online.
One thing I did not understand, is what it means to put the rest in stock. Does it mean don't put any memory voltage and memory control voltage fields?
Tonight I will try to do as you say, set core clock to 1300, put memory clock at 850 and the fan on 80%. and if it works I will increase the clock until it stops working right ?

[rdluffy]

thank you so much for your response and help, I really appreciate it.

Don't worry, we are here to help each other 

One thing I did not understand, is what it means to put the rest in stock. Does it mean don't put any memory voltage and memory control voltage fields?

Exactly, because your overclock is unstable.
If you try to modify all the settings at the same time, it's a mess to find which setting is the problem, so you leave voltages at stock and only modify the clocks first

Tonight I will try to do as you say, set core clock to 1300, put memory clock at 850 and the fan on 80%. and if it works I will increase the clock until it stops working right ?

Yes, right, you start with 850, and then 875, then 900, 925...until crashes and you'll see the limit, and you'll use the last stable clock

[Lafu]

At OP , glad to hearr that you soilved your problem now and its working again.
But if was reading right and more on the last link i have posted there was this solution and issue also with the OC.
Anyway you got it solved now and that the main thing , mostly to much OC brings the problems and it also can damage your GPUs.

[Filippo Tognola]

thank you so much for your response and help, I really appreciate it.

Don't worry, we are here to help each other 

One thing I did not understand, is what it means to put the rest in stock. Does it mean don't put any memory voltage and memory control voltage fields?

Exactly, because your overclock is unstable.
If you try to modify all the settings at the same time, it's a mess to find which setting is the problem, so you leave voltages at stock and only modify the clocks first

Tonight I will try to do as you say, set core clock to 1300, put memory clock at 850 and the fan on 80%. and if it works I will increase the clock until it stops working right ?

Yes, right, you start with 850, and then 875, then 900, 925...until crashes and you'll see the limit, and you'll use the last stable clock

thank you very much for your answer and your help, you are very kind.
Once I found the core and memory clock values, how do I proceed for the voltage values?
And another question was if the clock should I leave it stable at 1300 or even that I have to increase?
Now I started as you said with 1300 clock and 850 memory, and I wanted to see if it is stable for 1/2 hours, then I will increase.
Without overclocking it was stable for 5 hours without any problems.

[rdluffy]

thank you very much for your answer and your help, you are very kind.

  Thanks again

Once I found the core and memory clock values, how do I proceed for the voltage values?

It's the same as you're doing, step by step

Memory controller voltage have default value of 850mv
Memory voltage is 1350mv
Core voltage I think it's 984mv

You can put these manually, and reduce little by little, but only if you want to reduce temperature or power consumption, if you are satisfied, you can leave stock

Let's say for first test you can set to:

Memory controller voltage have default value of 840mv
Memory voltage is 1330mv
Core voltage I think it's 964mv

And another question was if the clock should I leave it stable at 1300 or even that I have to increase?
Now I started as you said with 1300 clock and 850 memory, and I wanted to see if it is stable for 1/2 hours, then I will increase.
Without overclocking it was stable for 5 hours without any problems.

For core clock, most of cards will work good with 1300, you can reduce and card will save power, but will reduce hashrate
I prefer to leave at 1300mhz, but it's up to you

You see, without overclocking your rig is stable, you found the problem, I think this is the best way to find and fix problems with rigs and PCs in general

[Filippo Tognola]

thank you very much for your answer and your help, you are very kind.

  Thanks again

Once I found the core and memory clock values, how do I proceed for the voltage values?

It's the same as you're doing, step by step

Memory controller voltage have default value of 850mv
Memory voltage is 1350mv
Core voltage I think it's 984mv

You can put these manually, and reduce little by little, but only if you want to reduce temperature or power consumption, if you are satisfied, you can leave stock

Let's say for first test you can set to:

Memory controller voltage have default value of 840mv
Memory voltage is 1330mv
Core voltage I think it's 964mv

And another question was if the clock should I leave it stable at 1300 or even that I have to increase?
Now I started as you said with 1300 clock and 850 memory, and I wanted to see if it is stable for 1/2 hours, then I will increase.
Without overclocking it was stable for 5 hours without any problems.

For core clock, most of cards will work good with 1300, you can reduce and card will save power, but will reduce hashrate
I prefer to leave at 1300mhz, but it's up to you

You see, without overclocking your rig is stable, you found the problem, I think this is the best way to find and fix problems with rigs and PCs in general

ok thank you very much for all the advice, I have learned a lot.
So doing some tests, I found that with memory clock at 850 and core clock at 1300 it works fine and I have about 39.7MH/s , however with memory clock at 875 the GPU starts to crash every 10 minutes.
So I've solved my problem thanks to you, you've been very kind and helpful, I wish you a good day and a happy 2022!