iGPU driver crash while playing stellaris

While playing stellaris (after already playing for like 2h) seemingly the GPU driver crashed, everything froze, mouse movement still worked but nothing else. This already happened to me 3 times in 3 days.
Here is the relevant excerpt from the journal:

Sep 27 20:17:16 nixos systemd-logind[881]: Power key pressed short.
Sep 27 20:17:09 nixos assert_20240927201709_81.dmp[55835]: file ''/tmp/dumps/assert_20240927201709_81.dmp'', upload no: ''SSL peer certificate or SSH remote key was not OK>
Sep 27 20:17:09 nixos steam[3463]: assert_20240927201709_81.dmp[55835]: file ''/tmp/dumps/assert_20240927201709_81.dmp'', upload no: ''SSL peer certificate or SSH remote k>
Sep 27 20:17:09 nixos steam[3463]: assert_20240927201709_81.dmp[55835]: error: SSL peer certificate or SSH remote key was not OK
Sep 27 20:17:09 nixos steam[3463]: assert_20240927201709_81.dmp[55835]: Finished uploading minidump (out-of-process): success = no
Sep 27 20:17:09 nixos assert_20240927201709_81.dmp[55835]: error: SSL peer certificate or SSH remote key was not OK
Sep 27 20:17:09 nixos assert_20240927201709_81.dmp[55835]: Finished uploading minidump (out-of-process): success = no
Sep 27 20:17:09 nixos assert_20240927201709_81.dmp[55835]: Uploading dump (out-of-process)
                                                           /tmp/dumps/assert_20240927201709_81.dmp
Sep 27 20:17:09 nixos steam[3463]: /tmp/dumps/assert_20240927201709_81.dmp
Sep 27 20:17:09 nixos steam[3463]: assert_20240927201709_81.dmp[55835]: Uploading dump (out-of-process)
Sep 27 20:17:09 nixos steam[3463]: src/clientdll/steamengine.cpp (2764) : Assertion Failed: CSteamEngine::BMainLoop appears to have stalled > 15 seconds without event sign>
Sep 27 20:17:09 nixos steam[3463]: src/clientdll/steamengine.cpp (2764) : Assertion Failed: CSteamEngine::BMainLoop appears to have stalled > 15 seconds without event sign>
Sep 27 20:17:06 nixos systemd-logind[881]: Power key pressed short.
Sep 27 20:16:49 nixos xserver-wrapper[1164]: (II) modeset(0): Modeline "1920x1080"x0.0  152.84  1920 1968 2000 2250  1080 1083 1088 1415 +hsync -vsync (67.9 kHz e)
Sep 27 20:16:49 nixos xserver-wrapper[1164]: (II) modeset(0): Modeline "1920x1080"x0.0  152.84  1920 1968 2000 2250  1080 1083 1088 1132 +hsync -vsync (67.9 kHz eP)
Sep 27 20:16:49 nixos xserver-wrapper[1164]: (II) modeset(0): Printing DDC gathered Modelines:
Sep 27 20:16:49 nixos xserver-wrapper[1164]: (II) modeset(0): EDID vendor "CMN", prod id 5352
Sep 27 20:16:49 nixos ksmserver[1988]: [GFX1-]: Detect DeviceReset DeviceResetReason::DRIVER_ERROR DeviceResetDetectPlace::WR_POST_UPDATE in Parent process
Sep 27 20:16:49 nixos kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
Sep 27 20:16:49 nixos kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
Sep 27 20:16:49 nixos kernel: i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads
Sep 27 20:16:49 nixos kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
Sep 27 20:16:49 nixos kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.29.2
Sep 27 20:16:49 nixos kernel: i915 0000:00:02.0: [drm] stellaris[53595] context reset due to GPU hang
Sep 27 20:16:49 nixos kernel: i915 0000:00:02.0: [drm] X[1164] context reset due to GPU hang
Sep 27 20:16:49 nixos kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Sep 27 20:16:49 nixos kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Sep 27 20:16:49 nixos kernel: i915 0000:00:02.0: [drm] GT0: Resetting chip for GuC failed to reset engine mask=0x1
Sep 27 20:16:49 nixos kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:84dffffb, in stellaris [53595]
Sep 27 20:16:49 nixos kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: GUC: Engine reset failed on 0:0 (rcs0) because 0x00000000

This is my system configuration

This is unlikely to be something anyone not in the Intel Linux graphics team can do anything about. You should report this to them.

The only things you could try is using a newer kernel (they’ll likely request you to try the latest) and/or enabling the new Xe kernel module thingy but I don’t know if it’s ready for your specific chip yet.