PC got frozen when heavy games in full screen

NVIDIA Open GPU Kernel Modules Version

610.43.02 (nvidia-open-dkms)

Please confirm this issue does not happen with the proprietary driver (of the same version). This issue tracker is only for bugs specific to the open kernel driver.

• I confirm that this does not happen with the proprietary driver package.

Operating System and Version

EndeavourOS Linux (x86_64)

Kernel Release

7.0.10-zen1-1-zen

Please confirm you are running a stable release kernel (e.g. not a -rc). We do not accept bug reports for unreleased kernels.

• I am running on a stable kernel release.

Hardware: GPU

NVIDIA GeForce RTX 3060 Ti Lite Hash Rate [Discrete]

Describe the bug

i had nvidia-dkms, while updating with

sudo pacman -Syu && yay -Syu

command, my Kitty terminal crashed, and the whole PC does not let me open almost any apps. After restarting my PC, I got a broken lightdm (something is wrong with the display/GPU in some files), and lightdm is not working. I got stuck in something like "reaching graphics". I got to the TTY. After that, all my drivers disappeared. I did update again, and after that, all pacman can't find nvidia-dkms, ok, after that i install nvidia-open-dkms and lightdm did not get fixed, i have started to use sddminstead oflightdm`, but when playing heavy games like Dead By Daylight (using any Proton), my PC got frozen in fullscreen mode.

The problem with games both on i3wm and Cinnamon, (Wayland is so laggy and not usable)

To Reproduce

1. Do updates using this command (using Kitty terminal):

sudo pacman -Syu && yay -Syu

2. After the Kitty got crashed, restart the PC
3. When you're stuck in "reach graphics" or something similar, you need to go to the terminal and do

sudo pkill lightdm

4. do updates again

sudo pacman -Syu && yay -Syu

5. rebuild system using dracut to fix screen resolution

sudo dracut rebuild

6. install sddm using

sudo pacman -S sddm

7. enable sddm

sudo systemctl enable sddm

8. start sddm

sudo systemctl start sddm

9. log in to i3wm/Cinnamon
10. start any heavy games like Dead By Daylight (idk but with s&box the problem got fixed after launch a lot of times)

Bug Incidence

Always with some heavy games in fullscreen (any proton or native)

nvidia-bug-report.log.gz

system and create the file 'nvidia-bug-report.log.gz' in the current
directory.  It may take several seconds to run.  In some
cases, it may hang trying to capture data generated dynamically
by the Linux kernel and/or the NVIDIA kernel module.  While
the bug report log file will be incomplete if this happens, it
may still contain enough data to diagnose your problem.

If nvidia-bug-report.sh hangs, consider running with the --safe-mode
and --extra-system-data command line arguments.

Please include the 'nvidia-bug-report.log.gz' log file when reporting
your bug via the NVIDIA Linux forum (see forums.developer.nvidia.com)
or by sending email to 'linux-bugs@nvidia.com'.

By delivering 'nvidia-bug-report.log.gz' to NVIDIA, you acknowledge
and agree that personal information may inadvertently be included in
the output.  Notwithstanding the foregoing, NVIDIA will use the
output only for the purpose of investigating your reported issue.

Running nvidia-bug-report.sh...
Detected driver type: Running RM Driver on GPUs
 complete.


Summary of Skipped Sections:

Skipped Component                   | Details
================================================================================
ibstat output                       | ibstat not found 
--------------------------------------------------------------------------------
acpidump output                     | acpidump not found 
--------------------------------------------------------------------------------
mst output                          | mst not found 
--------------------------------------------------------------------------------
nvlsm-bug-report.sh output          | nvlsm-bug-report.sh not found 
--------------------------------------------------------------------------------

Summary of Errors:

Error Component                     | Details                                                      | Resolution          
=========================================================================================================================

More Info

My PC:

                     ./o.                   melvinsgjr@EndeavourOS-PC
                   ./sssso-                 -------------------------
                 `:osssssss+-               OS: EndeavourOS x86_64
               `:+sssssssssso/.             Kernel: Linux 7.0.10-zen1-1-zen
             `-/ossssssssssssso/.           Uptime: 18 mins
           `-/+sssssssssssssssso+:`         Packages: 4 (appimage), 37 (flatpak), 1436 (pacman)
         `-:/+sssssssssssssssssso+/.        Shell: bash 5.3.9
       `.://osssssssssssssssssssso++-       Display (VSC342C): 1920x1080 in 23", 60 Hz [External]
      .://+ssssssssssssssssssssssso++:      WM: i3 4.25.1 (X11)
    .:///ossssssssssssssssssssssssso++:     Theme: WhiteSur-Dark-pink [GTK3], MacTahoe-Dark [GTK4]
  `:////ssssssssssssssssssssssssssso+++.    Icons: int_clay [GTK3/4]
`-////+ssssssssssssssssssssssssssso++++-    Font: Noto Sans (10pt) [GTK3/4]
 `..-+oosssssssssssssssssssssssso+++++/`    Cursor: MacOS-Tahoe (24px)
   ./++++++++++++++++++++++++++++++/:.      Terminal: kitty 0.46.2
  `:::::::::::::::::::::::::------``        Terminal Font: NotoSansMono-Regular (10pt)
                                            CPU: Intel(R) Xeon(R) E3-1220 v5 (4) @ 3.50 GHz
                                            GPU: NVIDIA GeForce RTX 3060 Ti Lite Hash Rate [Discrete]
                                            Memory: 4.60 GiB / 15.55 GiB (30%)
                                            Swap: 0 B / 8.00 GiB (0%)
                                            Disk (/): 841.23 GiB / 913.85 GiB (92%) - ext4
                                            Locale: en_US.UTF-8

Start by reproducing the fullscreen freeze after the listed pacman/yay update sequence and collect an actual nvidia-bug-report.log.gz; the issue currently contains the report tool's instructions rather than its diagnostic output. Compare the lightdm and sddm paths described, and consider the issue ready when a minimal reproducible configuration and supporting logs identify whether the open kernel driver is responsible.