One of users uploaded this log file:
...
Hmm, I don't see any problems in this log file. If it's a bug, it's difficult to catch it since I cannot reproduce it, the log is ok and it takes a lot of time to get it (about 80 hours in this log). It's not related to the running time directly since I have some systems running >200 hours completely stable. Another thing is that you can get this error if drivers fail due to some reason, in most cases OpenCL call just hangs so watchdog can catch it, but sometimes it can crash entire application or entire system.
I will try to find the reason, but the best solution currently is to restart miner from .bat file automatically (or better reboot the system). As far as I remember Windows has a way to disable that dialog about crash...
I will also put some rigs to your pool in "-esm 3" mode to check if I can see this error.
BTW, tell to your user that the miner detected devfee cheating and works a bit slower as described in Readme. Some people ignore Readme or think that I'm not smart enough to detect public tools, private networks, local proxies, etc. Be smarter if it's really important for you, or use Linux version, it's free of any cheat detection.
Claymore gone very quiet these days, hope everything is ok?
I'm fine, thanks, is v11.7 too old and you want v11.8 right now?