Complete freeze after several minutes of gameplay on Windows 11.

[andrienko]

I have Windows 11, and I play on built-in intel GPU. It worked just fine on windows 10 (at least it never happened there)

So, the issue is - game runs just fine for first several minutes. Then, after ~5-10 minutes of playing it just freezes completely
(and Windows does that thing when it says program is not responding and proposes to close it)

This typically happens in these huge map packs. For example, alkaline (uses modified some parts from copper?) or the brutalist jam which uses copper. This also happens on Quoth (run via either -quoth or +game quoth). The base game seems just fine, though. Looks like this happens regardless of whether I'm playing mods or base game. In base game it happens slower, though.

Another thing - the game just freezes sometimes this way (not always tho) when I type "quit" into console.

This also happens in vkQuake, Quakespasm and Quakespasm-Spiked.

Where do I start to find what is wrong with it?
Is there some debug information, crash log or something somewhere to find what might be awry?

condump.txt

[andrienko]

Forgot to mention: my mods dir and main game dir are not the same directory:

I have a dir (D:/games/quake2), where I have two dirs - games and engines. This D:/games/quake2 is the working directory, and I run quake (in case of ironwail - engines/ironwail-0.8.0-win64/ironwail.exe) with -basedir .\games.

And it works just fine this way: prefectly playable, no errors, etc... but then after some time freezes.

If I do things the "traditional" way - put the client into a separate dir, and in that dir put, say, ID1 and alkaline dir and run `ironwail -game alkaline" it does not freeze at all. I also tried to change working dir/cwd to client's dir - also freezes this way.

So looks like the problem is related to basedir somehow?

[j4reporting]

It's probably a gfx driver issue. Have you tried a newer Lenovo OEM driver or the latest generic driver from Intel?