Hello.

Thank you for the report. Drift did you already try the possible solutions here?

I'm getting the same.

@Wulf It's still occurring, it seems. I've updated my graphics driver and I don't use the steam overlay.

I doubt I'm having temperature issues as I would likely experience problems in other games. Plus it's the middle of winter here. I can test with Furmark and Prime95 running at the same time if you need me to.

Log doesn't seem to have the same error this time and there's no memory dump. But it did the exact same thing with a black screen after alt-tabbing.

Drift_91 just a confirmation are you using windowed or fullscreen? Trying it and can't seem to trigger it, without a repro it's really hard to pinpoint what the issue might be. The eternal curse of random issues.

@Wulf I was using fullscreen and it was causing my game to crash. After changing it to windowed, no more issues.

@Wulf I'm using fullscreen. Fullscreen-windowed has the flaw of blocking me from accessing the desktop in Windows 10, which I believe is Microsoft's fault and not BI's, otherwise I would be using it.

I haven't been paying enough attention every time it's happened to notice exactly the cause; But I have noticed that another program or window seems to interfere with tabbing back into the game when it happens. I think once I tried to tab back in and the task manager, which was set to 'always on top', tried to open or unminimize itself at the exact same time.

Btw it happened again earlier today. Idk if this crash dump is of any more use than the previous ones. I'll have to see if I can find a way to reliably reproduce it.

I did just update my graphics driver today, doing a clean install with wagnardsoft's Display Driver Uninstaller, before the above crash dump. So I expect any potential flaws in my driver install from before should be fixed now except for the game profiles which I backed up and restored with Nvidia Inspector. Let me know if you need to see my Nvidia control panel or Nvidia Inspector settings.

@BlackShot Do you mind if I ask which brand of video card you have and which version of Windows? Trying to rule out any possibility of it being a graphics driver or OS issue. I never had any issues on Windows 7; Although that might be because I used borderless window mode the whole time.

I just realized that I never mentioned this but the game doesn't immediately crash. When I tab back in and it gets blocked by another window the game turns to a black screen and needs to be killed with task manager. With the crash dump in my last post I had enough time to reopen the launcher before killing the game with task manager and the launcher still acted like the game had crashed and not been simply closed.

@Drift_91 @Wulf Nvidia Galax GTX 1060. Windows 10 Pro, latest version.

@BlackShot could possibly be a Nvidia or Windows 10 problem then I guess.

@Wulf It appears to be doing it in fullscreen as well now. If it helps with reproducability, it appears to happen when I alt-tab out and then accidentally alt-tab back in before the game can recognize it's been alt-tabbed out of; Due to lack of available physical memory the game has a hard time minimizing when I alt-tab.

@dedmen, I'm not sure if you're actually working on this or not, but it still happens to me on the rare occasion. Though, since I've built a new PC with an NVMe M.2 it happens far less. My friend who has Arma installed on a mechanical hard drive still experiences it quite often, apparently he has like a 98% chance of it happening if he alt-tabs while the game is loading past the splash screens.

I finally managed to get a crash dump out of it, which I don't believe I was able to previously. Unfortunately it's only the .bidmp and not an .mdmp with it.

I'm fairly certain that it's not caused by the mods, but is aggravated by the slowdown of having so many eating up memory. I did have it happen once, and only once, in the vanilla game.

Not sure if it matters, but I'm using a custom malloc which is GoldJohnKing's mimalloc, with some changes to the project settings and compiled with Intel's compiler using profile guided optimizations and AVX2. However I'm fairly certain I've experienced this issue in the past with the stock BI malloc.

I have recently started getting the same error. However it only happens after a BIS_fnc_playVideo have been used. If I alt-tab after a video have been started with that, I will get that error. I have also tried to run [""] call BIS_fnc_playVideo to stop the video before alt-tabbing, or waited for the video to stop by itself. I still get the black-screen that requires killing it with task manager.

I am running:
Windows 10
GTX 2070
AMD Ryzen 7 5800x
Fullscreen mode.

I have tried both with JEMalloc allocator and Windows allocator (system), with no change in behaviour.

I seem to recall initially when I started playing around with BIS_fnc_playVideo it did not happen, so it's something that has started at some point recently. Although I don't use the function that often, so not sure when the change happened specifically. I have attached the logs/dumps I got from one of these freezes.