Having the same issue with restarts using version 5.0c.  All my 34 rigs are restarting after DEVFee disconnects. Never had these kind of issues with 4.9c
I'm using simplemining ( linux ) with amd18.20 drivers


DevFee: GPU6: DevFee share found!
DevFee: Share actual difficulty: 5672 MH
DevFee: Share accepted in 43 ms
DevFee: Disconnected and stopped
GPU5: Starting up... (0)
GPU3: Starting up... (0)
GPU2: Starting up... (0)
GPU4: Starting up... (0)
GPU6: Starting up... (0)
GPU1: Starting up... (0)
GPU5: Allocating DAG for epoch #340 (3.66) GB
GPU5: Generating DAG for epoch #340
GPU3: Allocating DAG for epoch #340 (3.66) GB
GPU3: Generating DAG for epoch #340
GPU2: Allocating DAG for epoch #340 (3.66) GB
GPU2: Generating DAG for epoch #340
GPU4: Allocating DAG for epoch #340 (3.66) GB
GPU4: Generating DAG for epoch #340
=======and here it crashes =========


and here it is the last part from the DEBUD Dmesg data :


 1159.100648] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB
[ 1159.100649] Node 0 hugepages_total=128 hugepages_free=128 hugepages_surp=0 hugepages_size=2048kB
[ 1159.100649] 97718 total pagecache pages
[ 1159.100650] 0 pages in swap cache
[ 1159.100650] Swap cache stats: add 0, delete 0, find 0/0
[ 1159.100651] Free swap = 0kB
[ 1159.100651] Total swap = 0kB
[ 1159.100651] 967180 pages RAM
[ 1159.100652] 0 pages HighMem/MovableOnly
[ 1159.100652] 37451 pages reserved
[ 1159.100652] 0 pages cma reserved
[ 1159.100652] 0 pages hwpoisoned
[ 1159.127897] amdgpu_mn_invalidate_range_start_gfx+0x0/0x140 [amdgpu] callback failed with -11 in non-blockable context.
[ 1159.127932] amdgpu_mn_invalidate_range_start_gfx+0x0/0x140 [amdgpu] callback failed with -11 in non-blockable context.
[ 1159.127984] amdgpu_mn_invalidate_range_start_gfx+0x0/0x140 [amdgpu] callback failed with -11 in non-blockable context.
[ 1159.128012] amdgpu_mn_invalidate_range_start_gfx+0x0/0x140 [amdgpu] callback failed with -11 in non-blockable context.
[ 1159.128040] amdgpu_mn_invalidate_range_start_gfx+0x0/0x140 [amdgpu] callback failed with -11 in non-blockable context.
[ 1159.128068] amdgpu_mn_invalidate_range_start_gfx+0x0/0x140 [amdgpu] callback failed with -11 in non-blockable context.

I guess that hash-to-coins.com turned into a SCAM !!!! And still there are like 750 miners left mining on H2C ..

I changed my L3+ to multipool.us . Give it a try

Same here , 193.87580717 DGB locked on H2C for several days . Cannot withdraw them.  Same message that everybody else is seeing : You already have one active manual payout request.  Seen more angry ppl on discord too .

Also check https://bitcointalk.org/index.php?topic=2649729.640

Ppl are talking about it .

Have    DGB    DigiByte    193.87580717  on my H2C and was not able to withdraw since 3-4 days .. Changed my L3+ to a different pool .

The message I get every time when I try to withdraw is :  You already have one active manual payout request.

And another e-mail from coinpayments.net

Dear users of CoinPayments,

I wanted to give you a midweek update and personally tell you about the progress we have made regarding the recent Ripple incident. As pioneers in new frontiers solutions don't always come without challenges. Although contact has been made with many of the suspects, the funds have not been returned as hoped. This has made it very clear that most of the withdrawals were not done accidentally, but with malicious intent. We are now moving forward with prosecution of the perpetrators to the full extent of the law. This will set a precedent in this territory and deter future financial crimes in the space.

All the reimbursements to this date have come straight from the pockets of the CoinPayments team. Over the past week we have been able to acquire 55% of all of the XRP coins that were stolen through an enduring process with Ripple’s OTC desk. The funds have been distributed evenly amongst all accounts that were affected by this tragic loss. Moving forward, 50% of all CoinPayments’ revenue will be dedicated to acquiring XRP coins and reimbursing our users until we can put this incident behind us.

We thank you from the bottom of our hearts for your patience and support during this challenging time. Our aim is to not only make things right with you, our valued clients, but to also demonstrate that there is integrity and trust amongst our community. We hope you will take this opportunity to continue supporting CoinPayments as it grows, develops, and adapts, and cryptocurrencies pave the way to the future of finance.

Sincerely, your team at CoinPayments Inc

I just got a transfer from coinpayments.net

Hello Xxxx,

You have received a transfer of 1681.91933945 XRP from CoinPayments Support.

To view your current coin balances click https://www.coinpayments.net/acct-balances

Thank you,
CoinPayments.net
Support is available at: https://www.coinpayments.net/help-support

I dont know why they sent this exact value still. I had 2994 XRP in my wallet before they vanished.

It seems they kept their word... im waiting for the other transfer with the remaining balance now

 

Up to this moment coinpayments.net sent me no message regarding my ripple being stolen. I've seen a message from them on other forums that they are trying their best to solve the problem ...

I got the same e-mail. I lost all my Ripple. Had almost 1k usd worth of Ripple.  How will they recover the ripple from someone who joined with only an e-mail address? The person who stole all our ripple knew what he was doing so i am more then sure that he emptied his ripple account hosted with coinpayments.net

Dont know what else i can do to recover my ripple from coinpayments.net

Should i trust them holding more altcoins in their wallets ? Will see abt that..