Rig Not hashing error in ethos with P106 cards

[parshuram]

Hello.

Greetings.

I have been mining with 6xP106 on Ethos.

OC at +750 mem and power at 80 watts.
Have not filled the CC yet.

The cards whenever they crash the rigs shows in the panel 'possible pool connection problem, rig is not hashing' with a Red Triangle mark. (You will know the sign if you are familiar with ethos).

http://imgur.com/a/6W8c3

The miner shows 0 Hash rate during the error. Then I have to reboot the rigs and they work properly afterwards.

The pools, failover and wallet are obviously correct. It has to be noted that it does not happens to all P106 rigs together, if pool connection was the problem it should happen to all rigs.

This I thought was happening due to ethminer but then I shifted to Claymore and its happening with it too.

the rigs were very stable with Windows though and no such error ever came.
No Clue why only on Ethos.

Any help or input from the community would be appreciated

Thanks

[1715180269]

1715180269

[1715180269]

1715180269

[1715180269]

1715180269

[1715180269]

1715180269

[1715180269]

1715180269

[roctill7]

Been having exactly same issue with all my nvidia 1060 cards and p106 too. Somedays even simple restart would not solve this problem, and I end up with 1-2hours restarting back and forward until randomly it starts working ... Very frustrating. Would appreciate if anyone can shine some light on this issue too.

[GaryH]

Hello.

Greetings.

I have been mining with 6xP106 on Ethos.

OC at +750 mem and power at 80 watts.
Have not filled the CC yet.

The cards whenever they crash the rigs shows in the panel 'possible pool connection problem, rig is not hashing' with a Red Triangle mark. (You will know the sign if you are familiar with ethos).

http://imgur.com/a/6W8c3

The miner shows 0 Hash rate during the error. Then I have to reboot the rigs and they work properly afterwards.

The pools, failover and wallet are obviously correct. It has to be noted that it does not happens to all P106 rigs together, if pool connection was the problem it should happen to all rigs.

This I thought was happening due to ethminer but then I shifted to Claymore and its happening with it too.

the rigs were very stable with Windows though and no such error ever came.
No Clue why only on Ethos.

Any help or input from the community would be appreciated

Thanks

Why not go back to Windows? 

[kjs]

Hello.

Greetings.

I have been mining with 6xP106 on Ethos.

OC at +750 mem and power at 80 watts.
Have not filled the CC yet.

The cards whenever they crash the rigs shows in the panel 'possible pool connection problem, rig is not hashing' with a Red Triangle mark. (You will know the sign if you are familiar with ethos).

http://imgur.com/a/6W8c3

The miner shows 0 Hash rate during the error. Then I have to reboot the rigs and they work properly afterwards.

The pools, failover and wallet are obviously correct. It has to be noted that it does not happens to all P106 rigs together, if pool connection was the problem it should happen to all rigs.

This I thought was happening due to ethminer but then I shifted to Claymore and its happening with it too.

the rigs were very stable with Windows though and no such error ever came.
No Clue why only on Ethos.

Any help or input from the community would be appreciated

Thanks

Try lowering your memory clocks and see whether that improves stability.

[roctill7]

Hello.

Greetings.

I have been mining with 6xP106 on Ethos.

OC at +750 mem and power at 80 watts.
Have not filled the CC yet.

The cards whenever they crash the rigs shows in the panel 'possible pool connection problem, rig is not hashing' with a Red Triangle mark. (You will know the sign if you are familiar with ethos).

http://imgur.com/a/6W8c3

The miner shows 0 Hash rate during the error. Then I have to reboot the rigs and they work properly afterwards.

The pools, failover and wallet are obviously correct. It has to be noted that it does not happens to all P106 rigs together, if pool connection was the problem it should happen to all rigs.

This I thought was happening due to ethminer but then I shifted to Claymore and its happening with it too.

the rigs were very stable with Windows though and no such error ever came.
No Clue why only on Ethos.

Any help or input from the community would be appreciated

Thanks

Try lowering your memory clocks and see whether that improves stability.

Lowering overclock settings seems to be helping

[kjs]

Lowering overclock settings seems to be helping

No surprises there