My screenreader has no idea what you posted as the output from journalctl. Please post as pre-formatted text.
I’m very new with this stuff and only looked up a command to see which logs are for freezes. I might have messed with something in the command prompt while I was trying to fix my sleep issues. Pre-formatted text??
journalctl -b -1 -p err..emerg
That’s indeed the command, but I suspect you want to post the output of the command, rather than the command itself. 
journalctl -b -1 -p err..emerg
Aug 19 18:11:33 MAHLADY kernel: virt/tdx: TDX not supported by the host platform
Aug 19 18:11:33 MAHLADY kernel: integrity: Problem loading X.509 certificate -22
Aug 19 18:11:33 MAHLADY kernel: integrity: Problem loading X.509 certificate -22
Aug 19 18:11:41 MAHLADY bluetoothd[791]: Failed to set mode: Failed (0x03)
Aug 19 18:11:55 MAHLADY kwin_wayland[1522]: Applying output configuration failed!
Aug 19 18:11:58 MAHLADY bluetoothd[791]: Failed to set mode: Failed (0x03)
Aug 19 18:12:00 MAHLADY systemd[1756]: org.freedesktop.IBus.session.generic.service: Two services allocated for the same bus name org.freedesktop.IBus, refusing operation.
Aug 19 20:33:58 MAHLADY dbus-broker-launch[776]: Activation request for 'org.freedesktop.Avahi' failed.
Aug 19 20:33:58 MAHLADY dbus-broker-launch[776]: Activation request for 'org.bluez' failed.
Aug 19 20:33:58 MAHLADY dbus-broker-launch[776]: Activation request for 'org.bluez' failed.
Aug 19 20:33:58 MAHLADY dbus-broker-launch[1779]: Activation request for 'org.kde.ksystemstats1' failed.
Aug 19 20:33:58 MAHLADY dbus-broker-launch[776]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Aug 19 20:33:58 MAHLADY dbus-broker-launch[776]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Aug 19 20:33:59 MAHLADY dbus-broker-launch[776]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Can you provide us details about your GPU.
lspci -nnk | grep -A 3 -i vga
please share the output of this command.
When the system freezes, go to a new tty with ctrl+alt+f2, login there, and run top to see if any of the processes are hanging. If they are, look at the pid and kill them with eg kill 5334
You can then switch back to the original tty with the approraite f and see if the system resumes.
lspci -nnk | grep -A 3 -i vga
03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 48 [Radeon RX 9070/9070 XT/9070 GRE] [1002:7550] (rev c0)
Subsystem: Gigabyte Technology Co., Ltd Device [1458:2424]
Kernel driver in use: amdgpu
Kernel modules: amdgpu
Looking at this, i can say a few things
kwin_wayland[1522]: Applying output configuration failed!
shows KDE plasma display compositor is failing when your game changes resolution or display mode upon exiting that game.
Does this happen if you switch your desktop session to X11. X11 handles full-screen display changes differently.
Activation request for 'org.bluez' failed
I think, your connected bluetooth devices are triggering state changes when your system is suspended.
If you would like to see which hardware devices are permitted to wake your system up, run cat /proc/acpi/wakeup
You might want newest amdgpu driver improvement and kernel fixes, running
sudo dnf upgrade --refresh will do that, you will have to reboot your system to let your system use new modules.
Question - Do you have enough RAM to run your game? If not, you should either kill some processes or use GitHub - rfjakob/earlyoom: earlyoom - Early OOM Daemon for Linux · GitHub, which handles low-memory cases better—prevents your system from freezing (i find it quite useful for my 8GB ram laptop)
I have 32 ram, I don’t know about the X11 thing, I’m not familiar with it. It did freeze on another game recently by accidentally hitting the GUIDE button on my xbox controller, and that game never froze before so it has to be a resolution thing. I can’t use the kill command when it freezes, it’s completely unresponsive when it happens I have to force shutdown with the power button on the tower.
These are my blue tooth results, I would like to primary use only the keyboard to wake up, maybe the mouse should be disabled as well:
cat /proc/acpi/wakeup
Device S-state Status Sysfs node
GPP3 S4 *disabled
GPP4 S4 *disabled
GPP5 S4 *disabled
GPP6 S4 *disabled
GP17 S4 *enabled pci:0000:00:08.1
XHC0 S4 *enabled pci:0000:10:00.3
XHC1 S4 *enabled pci:0000:10:00.4
PS2K S3 *disabled
PS2M S3 *disabled
XHC2 S4 *enabled pci:0000:11:00.0
GPP0 S4 *enabled pci:0000:00:01.1
SWUS S4 *enabled pci:0000:01:00.0
SWDS S4 *enabled pci:0000:02:00.0
GPP1 S4 *disabled
GPP2 S4 *disabled
GPP7 S4 *enabled pci:0000:00:02.1
UP00 S4 *enabled pci:0000:04:00.0
DP00 S4 *enabled pci:0000:05:00.0
NV00 S4 *disabled
DP08 S4 *enabled pci:0000:05:01.0
EP00 S4 *disabled
DP10 S4 *disabled
WN00 S4 *disabled
DP18 S4 *enabled pci:0000:05:03.0
LN00 S4 *disabled pci:0000:08:00.0
DP20 S4 *enabled pci:0000:05:04.0
NV00 S4 *disabled
DP28 S4 *enabled pci:0000:05:05.0
EP00 S4 *disabled
DP30 S4 *enabled pci:0000:05:06.0
EP00 S4 *disabled
DP38 S4 *enabled pci:0000:05:07.0
EP00 S4 *disabled
DP40 S4 *enabled pci:0000:05:08.0
EP00 S4 *disabled
DP48 S4 *disabled
EP00 S4 *disabled
DP50 S4 *disabled
EP00 S4 *disabled
DP58 S4 *disabled
EP00 S4 *disabled
DP60 S4 *enabled pci:0000:05:0c.0
XH00 S4 *enabled pci:0000:0e:00.0
DP68 S4 *enabled pci:0000:05:0d.0
SA00 S4 *disabled pci:0000:0f:00.0
GPP8 S4 *disabled
also this is what I got with dnf upgrade, I have an AMD gpu:
Updating and loading repositories:
Fedora 44 - x86_64 - Updates 100% | 3.6 KiB/s | 23.2 KiB | 00m06s
Terra 44 100% | 318.0 B/s | 1.9 KiB | 00m06s
RPM Fusion for Fedora 44 - Nonfree - Updates 100% | 1.0 KiB/s | 5.9 KiB | 00m06s
RPM Fusion for Fedora 44 - Nonfree - Steam 100% | 1.0 KiB/s | 5.3 KiB | 00m05s
RPM Fusion for Fedora 44 - Nonfree - NVIDIA Driver Source 100% | 1.2 KiB/s | 5.5 KiB | 00m04s
RPM Fusion for Fedora 44 - Nonfree - NVIDIA Driver Debug 100% | 1.3 KiB/s | 5.1 KiB | 00m04s
RPM Fusion for Fedora 44 - Nonfree - NVIDIA Driver 100% | 1.7 KiB/s | 5.5 KiB | 00m03s
RPM Fusion for Fedora 44 - Nonfree 100% | 2.1 KiB/s | 5.7 KiB | 00m03s
RPM Fusion for Fedora 44 - Free - Updates 100% | 1.5 KiB/s | 3.4 KiB | 00m02s
RPM Fusion for Fedora 44 - Free 100% | 1.9 KiB/s | 3.0 KiB | 00m02s
google-chrome 100% | 3.1 KiB/s | 1.3 KiB | 00m00s
Fedora 44 openh264 (From Cisco) - x86_64 100% | 935.0 B/s | 986.0 B | 00m01s
Fedora 44 - x86_64 100% | 28.3 KiB/s | 24.0 KiB | 00m01s
Copr repo for PyCharm owned by phracek 100% | 5.0 KiB/s | 2.1 KiB | 00m00s
Repositories loaded.
Nothing to do.
Can you go to your KDE Display settings, and change Adaptive Sync from whatever it is to Never, and check if the freeze still happens.
Iam not sure about this one but, dont put your game in Exclusive Full screen—like some other Game Display mode maybe, like Borderless Windows.
I dont know how to do it, but what i know is USB controllers manages multiple ports at once, if you disable the USB Controllers it is going to disable both your keyboard and mouse.
the Adaptive sync is already on Never but I’ll try to run the games with borderless window