Post
Topic
Board Mining (Altcoins)
Re: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners
by
flhctroll
on 07/07/2022, 02:55:34 UTC
Hello. Got a weird issue here. This is on my main awesome miner rig that runs the main A.M. host(?). 5x 3080ti asus tuf LHR v512.59 using t-rex mining ETH. When i stop mining, the pc will crash. Sometimes just a soft crash with just a black screen flicker a couple times and some settings are not found like fan or power level in settings, or sometimes it will do a full restart, or a complete black screen hang. This happens ONLY when A.M. is open and running and i try to "stop" mining. Even when hitting stop using the web gui on my phone. If i close A.M. completely, wait a few seconds, then close the miner window, all is well, no crash. This crash will happen even at a 0 overclock. I can recreate this with a minute or 2 of mining. I used to have the 2 options in overclocking enabled, "reset gpu parameters" and "global fan control", but thought that may have something to do with it since i could hear the fans reset at the same time as the crash. But i now have those off and it still happens. Any ideas?
Hi and thanks for your report.

When stopping the mining software, Awesome Miner will by default reset all overclocking properties. Can you please try to disable this by going to the Options dialog, GPU Settings section and uncheck "Automatically reset GPU clocking parameters"?

That was the setting that i already disabled as i thought that was the cause.
Thanks for the update.

Please try these two changes as well, both located in the Options dialog, Mining settings section:
1) Increase the value for "Wait for process stop before terminating" to be significantly higher than the default value.
2) Check the box for "Use Ctrl+C event for closing mining process"

i applied both the ctrl+c and made the wait time longer, now it just takes longer to crash. I have found that i can manually "x" close t-rex with A.M. open and all is well, a.m. just sees it as a "miner not running" and will restart it. so its def something in the "stop" command causing the crash. Again, as long as i dont use a.m. to "stop" it, it never blackscreen reboots.