GZDoom keeps freezing

[joshescue18]

I was playing Frozen Time was on GZDoom 4.5.0 for the first 15 minutes, and then the screen froze but the sounds and music kept playing. Can you help me?

[Redneckerz]

I was playing Frozen Time was on GZDoom 4.5.0 for the first 15 minutes, and then the screen froze but the sounds and music kept playing. Can you help me?

Can you post a log or your ini file?
Where exactly in that WAD did the error occur?
What are your computer specs?

[Starman the Blaziken]

I was playing Frozen Time was on GZDoom 4.5.0 for the first 15 minutes, and then the screen froze but the sounds and music kept playing. Can you help me?

I am having the same problem as well when playing mods like Guncaster, Brutal Doom, Spaghetti, and Li$ter's Simple Doom for some reason.
It happens on any map set no matter what I play the mods with. And it is only GZDoom, not Zandronum or any other platform ether.

[Starman the Blaziken]

When it happens, it just happens out of nowhere no matter what I do and when I alt + tab out and then go back into it, it just goes to a black screen and some screen and flashes between the two rather constantly although OBS Studio did not pick that up when I tried to record it and yet the file size is too big even with a ZIP file to upload it.

[Graf Zahl]

What's your graphics hardware? There is a known issue with some Intel drivers shutting down unexpectedly under high load, and your description suspiciously sounds like that.

[yaboi]

I'm having the same issue with both 4.4.2 and 4.5.0 versions of GZDoom

I've got a Dell Inspiron with a i7-10510U processor and basic Intel UHD 620 graphics (I should've shelled out the extra £200 for the one with a geforce card, I know)

Edit: Just updated my drivers, and now the issue happens after 1 minute of play instead of 10/15 mins.

[Starman the Blaziken]

What's your graphics hardware? There is a known issue with some Intel drivers shutting down unexpectedly under high load, and your description suspiciously sounds like that.

An Intel core i7 that I had since my parents bought me the laptop several years ago, and having much of the same version issues with 4.4.2 and 4.5.0 as well. I had 4.4.2 for some good time and it never had the problem until this issue happened unexpectedly while playing a mod with a normal map set. Now it has gone all over with anything I play with in the port.
Although I only been playing stuff with mods as of recent, so I dunno what would happen with a normal Doom run.

[joshescue18]

I've got an HP with a i3-8130U processor and an Intel UHD Graphics 620 driver.
And the operating system is Windows 10.

[Starman the Blaziken]

I've got an HP with a i3-8130U processor and an Intel UHD Graphics 620 driver.
And the operating system is Windows 10.

Are you having the same problem related to this topic or something?

[Swampat]

I could use some help with this problem. I been trying to figure out what to do and I'm stumped at this point.

[wildweasel]

I could use some help with this problem. I been trying to figure out what to do and I'm stumped at this point.

Okay - have you got more information you can give us? System specs, GZDoom version, what mods you have loaded if any?

[Swampat]

I could use some help with this problem. I been trying to figure out what to do and I'm stumped at this point.

Okay - have you got more information you can give us? System specs, GZDoom version, what mods you have loaded if any?

I'm playing with the dev build of 4.5.0 and playing winters fury. My specs are:
8gb of ram
SSD SATA3/128G M.2
i3-8130U Processor 2.2GHz goes up to 3.4 GHz

It plays pretty well until about 20 or so minutes later then the game freezes. I still hear the game itself playing, but my video is static and I have to close the game from the task manager. If I leave the game and try going back in, the screen just flashes a bunch and I still hear sound but no video.

[Rachael]

This is a known issue with Intel graphics, with no known cause or real solution. It can be mitigated by taxing the processor less, i.e. turning down shaders or detail settings, reducing the render resolution, or other things.

[Swampat]

This is a known issue with Intel graphics, with no known cause or real solution. It can be mitigated by taxing the processor less, i.e. turning down shaders or detail settings, reducing the render resolution, or other things.

Alright then, thanks for the help regardless.