Quote from: STSMiner on November 29, 2021, 01:44:21 PM

Quote from: sxemini on November 29, 2021, 01:00:55 PM

Quote from: STSMiner on November 29, 2021, 12:03:56 PM

Quote from: Commie on November 21, 2021, 08:38:18 AM

Since 9.0.4 or 9.0.5 weird things are happening to AM and one of my rigs. Whenever it reboots AM just doesn't see it until minutes later, then reports rig as stopped and doesn't start the miner (manually or automatically) until I restart the AM on my controlling PC. All machines run Win10 with latest Nvidia drivers, I tried reinstalling both but it didn't solve the problem. Another rig works just fine. Has anyone else experienced this?

PS Reboots started happening a week or two ago with BSOD indicating nvlddmkm.sys pagefile error, no idea how to fix this so far Sad

Yup, been having the same issue here, remote rigs are not seen for a good minute or two, even re-installed the main program and clients and drivers for GPU's, still get the same results.

Not getting the reboots tho, using the latest Nvidia DCH drivers here.

@patrike, maybe you can look into the first issue to see what's causing this.

This happens if something is wrong with your Remote client installation or the windows of the remote client. And sometimes AM need a little bit to recognize a client after the reboot, but i think it is normal.

Did not have this issue before until version 9.0.X .... and nothing has changed here on the rigs other than drivers for the GPU's and the re-install of the client and main app in an attempt to fix the issue, but it still persists and can take up to 2 minutes to see the remote rigs on the same network / submask.

Can you please send me the Awesome Miner and Remote Agent log file and let me know the time of the issue? I will of course investigate to see what the issue might be. As Commie pointed out, his case was related to running two Awesome Miner instances connected to the same Remote Agent.