More
referral
Increase your income with Hive. Invite your friends and earn real cryptocurrency!

Team red miner error GPU 2: detected DEAD (07:00.0), will execute restart script watchdog.sh


switched back to teamredminer @Smining570
It used to works with ref 30 now i am testing ref 20.
But i never get past one day without the 580 rebooting the rig.
I am using the 009s riser an msi gaming plus max x470 , athlon 3000g paired with 16gb of ram and a xfx 750w power supply.

are u sure its 580 that causes reboot, if one of others “dies” it may be that the error is gpu0 dead when it reboits. have u ran 580 only for longer period? your values are fine, might as well drop vdd to 840 if Core 1150,im running 580’s now Mem 2060 vdd 840 core 1190 ref 30. these gives some invalids, usually on same gpu, xfx 590…but safe are for me 2140/840/1170 ref 30. these runs without any issues for days… usually i rise them ro higher values at some point then to the ones i mentioned earlier… :smile:
. and back again to stable when there is enough invalids. really hard to say what can cause Re oot after several hours… psu? Let us know how it goes with ref 20.hope it helps or u find another solution.

1 Like

i’ll keep you updated, the other two are in the t-rex miner, the error that i am getting is in the team red miner , could be the nvdia cards ?
Yesterday i tried in the phoenixminer and i saw when it happens suddenly the hashrate from the 580 goes to 0 and the other two keeps hashing until the phoenixminer reboots cause rx was reporting as 0mh/s.

I tried 2140/840/1170 ref 30 reboots after 5 hours +/- the only one that i didnt tried yet was Mem 2060 vdd 840 core 1190 ref 30.
If it reboots i’ll try those , if doesnt work too i will try to run the 580 alone.

yes, i belive your issue is with nvidia, team red for amd is solid, do try 580 solo or only nvidias…im quesing if u go with nvidia u will have same reboot later,but will see :wink:

1 Like

Buenos días, tengo este problema , como podría solucionarlos, muchas gracias de antemano.

no se si cambiar de team read miner por lolminer o tocar configuraciones de OC

I have 9 cards running but once I add my 10th, no matter the slot it will run for up to 6 minutes and say that GPU is detected dead and restart the rig.

Is this similar to what you were having an issue with?

si es muy similar a lo que me esta sucediendo, ahora de momento he cambiado la configuracion y no esta dándome problemas

have u tried to increace vdd on that one that allways dies…?

I had the same problem here, I solved it by raising the core voltage of my gpu (Radeon 6700 XT). This problems seems to happen when u have to low core voltage. U should raise it 25 by 25 till u can find a number witch u get the rig stable.

le subi el vdd a 980 y me ha dado fallo al dia y medio mas o menos, debería de ir subiéndole mas?

Usually this is an issue with cards that may have poor cooling or something related to OC changes. But that is absolutely no reason to be concerned. TeamRedMiner works a bit differently. It catches minor overvoltages on the core or memory and turns off the digging, then reboots and the whole rig runs smoothly for several weeks. Nothing to worry about!

Of course, if the card is damaged, it’s a different matter.

2 Likes

Same Here, its OC settings that need to be lowered

1 Like

SOLVED FOR ME :grin:

Thanks!
I have been 1 day and 10 hours without errors. I have uploaded 25 VVD. I hope it continues like this.

1 Like

Hola, pudiste arreglarlo?

This is true…
tried everything else, new risers, new power supply (as some other posts suggested that) but in the end it stopped rebooting after I lowered OC (memory speed).
It worked with higher memory speed before but I guess it’s too hot now during summer.

Had some minor stability issues and this is the new stable OC on that Rig

I have the exact same problem. I have two rigs with 5700 xt and in both of them I cannot install nothing above 0.6-203@210715 or I will have gpu as dead.
Even if I downclock everything to stock I will get crashes. Do someone have a solution for this?

It failed again erratically. But going down from 5 to 5 the memory clock I could now make it work for 2 days.

This kinda works for me, a restart here and there but better than restarts every few minutes.