@Silenoz111:
Sorry, my boy not been well. I thought I fixed it as I read elsewhere about using Avast sandbox feature, so I turned it off and… no crashes. But tried it again the day after with Sandbox still turned off and it’s crashing again. So I’m now back to square 1.
The Avast-Sandbox thing is mostly mythical 😛
I’m not saying Avast sandbox cannot cause problems ever. But in all crashlogs, you see a path like this :
d:\sandbox\bmscode_public\...
```… that some people wrongly interpret as being a problem with Avast Sandbox. However, it has nothing to do with this, it is only the path where the .exe has been compiled on the developper computer. It appears in ALL crashlogs, including crashlogs on people without Avast and without even a d:\disk ;)
Anyway, on the CTD you are experiencing, this is not the first time it was reported.... however no one on the dev team was able to reproduce the bug, unfortunately :( It must be a particular combination of software/hardware that is not obvious.
EDIt : could you share the crashlogs with us ? Post the whole content here, **in between```
tags, so that we can see if there is a pattern here.
```**