nvidia Xid Error

Crabevariable · 2024-07-17 21:28:25

hi

sometimes the game that stress my computer the most crash (DD2,Cyberpunk even if i couldnt reproduce it again for cyberpunk)
in journal and Dmesg command in terminal after the crash i have a Xid error

Jul 16 20:37:48 femboy kernel: NVRM: GPU at PCI:0000:08:00: GPU-3fbda3e6-b6b1-d857-e870-a07b98b56ce8
Jul 16 20:37:48 femboy kernel: NVRM: Xid (PCI:0000:08:00): 109, pid=95784, name=DD2.exe, Ch 00000079, errorString CTX SWITCH TIMEOUT, Info 0x36c076

i search on NVidia Xid 109 and i find that it is Context Switch Timeout Error ?
and i would like to know if i can get more help on the subject as apparently my nvidia driver reset itself during gameplay of those 2 games only
the games freezes and i need to kill them myself from steam but all my pc work i have the sound of the game until i kill it

i have an RTX 2060 6gb
Ryzen 7 5700x
16gb of ram
and all the latest packages

thx in advance to everyone that want to help me

Edit;
i monitored everything i am not full ram or vram while gaming thoses games and temps are around 60 to 70 degres
and i tested on x11 and wayland both have the same problem

Last edited by Crabevariable (2024-07-17 21:49:10)

seth · 2024-07-18 07:09:57

https://docs.nvidia.com/deploy/xid-errors/index.html

"What can cause XID 109?"
"Yes."

If it's exclusive to DD2 it's most likely a bug in the game, though https://www.google.com/search?q=proton% … TIMEOUT%22
Random guess: what session do you run on X11? Is there a compositor? What if you disable that/use an uncomposited session?

apparently my nvidia driver reset itself during gameplay

Are there other errors you didn't post?

Crabevariable · 2024-07-18 13:42:41

for what can cause a xid 109

i tested my gpu on windows and linux
windows run fines with no problem at all

while linux one reset the driver not only on dd2 but also on cyberpunk if cyberpunk is in high as i dont crash under minimal option
so my guess as it work fine on windows is that it is a driver problem

my compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
how could i disable kwin wont it disable my driver as it say that it load my driver ?

those were the only error in journal and dmesg after crash and before there is no error

edit ; i tried doing shift+alt+f12 but nothing happens

Last edited by Crabevariable (2024-07-18 13:43:39)

seth · 2024-07-18 15:20:39

loginctl session-status
qdbus6 org.kde.KWin /KWin supportInformation

Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

I'd then assume you prime-run the game?
https://wiki.archlinux.org/title/PRIME# … _using_GPU

so my guess as it work fine on windows is that it is a driver problem

It might just as much be a protin/wine problem.
XID is as generic an error as it gets: *everything* can cause that.

Crabevariable · 2024-07-18 16:35:27

my Xorg run as root so the files is in root/var/log
so grep -e Log -e tty Xorg.0.log dont work
i did cat /var/log/Xorg.0.log | curl -F 'file=@-' 0x0.st
wich gave me that http://0x0.st/X9Vx.txt it is the same inside the file hope that work for you
it say my gpu disconnected ?

i didnt run the game as prime,now just tried and same result xid 109 error after some time
i tried running the game with a fps cap at 30 (the game was at 60) and the game run without problem so proton dont sems to be a issue if the game work at lower stress ?

Edit ;
i dont really understand what you wanted me to do with
loginctl session-status
qdbus6 org.kde.KWin /KWin supportInformation

as it give me a hell of a text in the prompt xd

i aslo did play with Proton 8, ge proton 9,2 9,7 and 9,10 and i am currently on Experimental as it is the one that seems to work the best

Last edited by Crabevariable (2024-07-18 16:40:15)

seth · 2024-07-18 20:29:07

There's only a single GPU, the nvidia one running on the binary driver - there's no need or point in prime-running anything here.
I misinterpreted "loaded: nvidia unloaded: modesetting"

i dont really understand what you wanted me to do with

Post it

(loginctl session-status; qdbus6 org.kde.KWin /KWin supportInformation) | curl -F 'file=@-' 0x0.st

i tried running the game with a fps cap at 30 (the game was at 60) and the game run without problem

You could try to enable triple buffering, https://wiki.archlinux.org/title/NVIDIA … en_tearing but let's first see whether you can deactivate the compositor

V1del · 2024-07-18 20:30:53

Those are diagnostic outputs, you should post them, either by pasting here, or using the

command | curl -F 'file=@-' 0x0.st

command you've learned about.

FF5 strikes again...

Last edited by V1del (2024-07-18 20:31:34)

Crabevariable · 2024-07-18 21:02:20

the post of (loginctl session-status; qdbus6 org.kde.KWin /KWin supportInformation) | curl -F 'file=@-' 0x0.st
http://0x0.st/X9JA.txt

i just disable compositing on start up and i am gonna try the game after the reboot

seth · 2024-07-18 21:27:08

Also try what happens if you remove the HDMI output (which is running at 75Hz)

Crabevariable · 2024-07-18 22:37:51

so after disabling composing the game still crash
but then like you said i unplug my 75hz monitor
and idk what to say i play for 48 min without crash
could this be my monitor ? cable ? port ?

for info the monitor i unplug was 75hz and in game i put it in 60hz via ingame option

edit
i m gonna try a second session to see if it was only luck as i already had session above 30 min
edit 2;
again a smooth experience trying everything that made me crash before and there is no crash happening

so now lets go to see why it crash on my other monitor

edit 3;
i tried using my other monitor this time i use 60 hz in game and in display the game crash after 15 min same error xid 109

Last edited by Crabevariable (2024-07-19 00:43:56)

seth · 2024-07-19 07:03:08

i tried using my other monitor this time i use 60 hz in game and in display the game crash after 15 min same error xid 109

"Other monitor" exclusively or in a dualscreen setup?
What if you run the output at 60Hz as well?
You can control the output the driver is syncing to by exporting __GL_SYNC_DISPLAY_DEVICE
Try "export __GL_SYNC_DISPLAY_DEVICE=DP-2"

Crabevariable · 2024-07-19 07:43:47

dualscreen setup
i tried running it with 60hz on setting display & monitor option it sadly crashed

i tried running on a DP with dualscreen it crash on whatever monitor it is
but when i only have the DP connected it wasnt crashing

edit;
now it seems to be confirmed, if i only have one monitor the game dont crash or the crash isnt Xid

Last edited by Crabevariable (2024-07-19 09:15:39)

seth · 2024-07-19 15:02:00

if i only have one monitor the game dont crash or the crash isnt Xid

Regardless of which output (the DP or the HDMI one) at which framerate (60Hz or 75Hz) or the __GL_SYNC_DISPLAY_DEVICE ?

A multihead setup implies the full composition pipeline, if you enforce that, do you get the same crash w/ only one output?
https://wiki.archlinux.org/title/NVIDIA … en_tearing
… and see the notice there…
https://github.com/ValveSoftware/Proton … 1861716986 actually suggests that the active compositor (kwin shadows) would *prevent* those crashes

Crabevariable · 2024-07-19 19:45:58

on 1 monitor
on both dp and hdmi with 60 and 75hz it didnt crash or the crash wasnt xid error (one time where it just crashed while saving exiting with no xid error for me this time it was the game as i already had that crash a long time ago on windows it can happens

on dual screen
i deactivated block to compositor,
it crashed, same error

i force full composition with nvidia x server
it crashed, same error

seth · 2024-07-20 07:22:57

You could try to forcefully disable the full composition pipeline but I'm not sure
1. whether the driver will actually care in the multihead condition
2. whether that's a good idea at all for the overall performance

There was

Option  "UseNvKmsCompositionPipeline" "false" # https://devtalk.nvidia.com/default/topic/1029484/-various-all-distros-numerous-performance-amp-rendering-issues-on-390-25/?offset=110#reply

but idk even know whether that is still parsed on the newer driver versions.

Edit: so the most likely workaround would be to simply disable one output to play the specific games.

Last edited by seth (2024-07-20 07:23:27)

Crabevariable · 2024-07-20 11:28:36

if you are not sure about
Option "UseNvKmsCompositionPipeline" "false" # https://devtalk.nvidia.com/default/topi … =110#reply

i will not do it xd i saw you seth in all forum you're the man xd

well yeah if thats the only thing that work it sucks but well thats my best game
i really hope an update can help this

seth · 2024-07-20 11:48:26

You can just try whether it has an impact - worst case the legacy code has long been removed and it does nothing and maybe you get a warning in the xorg log.
Best case, it solves you problem.

Crabevariable · 2024-07-20 12:27:29

option command not found unfortunately

seth · 2024-07-20 12:29:19

That is not a command - it's an X11 config option, see the previously linked https://wiki.archlinux.org/title/NVIDIA … en_tearing for a general config pattern.

Crabevariable · 2024-07-20 13:57:18

isnt that the same as force full composition pipeline on x server setting app ?

edit ;
the nvidia-settings --assign CurrentMetaMode="nvidia-auto-select +0+0 { ForceFullCompositionPipeline = On }"
disable my 60hz monitor, only letting my 75hz display on

Last edited by Crabevariable (2024-07-20 15:15:35)

seth · 2024-07-20 15:47:43

The plan would have been, iff all to set FFCP to off and also you chose the wrong kind of meta mode and ultimately the later point was to first try the legacy composition pipeline…

/etc/X11/xorg.conf.d/20-nvidia.conf

Section "Device"
        Identifier "NVIDIA Card"
        Driver     "nvidia"
        VendorName "NVIDIA Corporation"
        BoardName  "GeForce RTX 2060"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "NVIDIA Card"
    Option         "ForceFullCompositionPipeline" "off"
    Option  "UseNvKmsCompositionPipeline" "false" # https://devtalk.nvidia.com/default/topic/1029484/-various-all-distros-numerous-performance-amp-rendering-issues-on-390-25/?offset=110#reply
    Option         "TripleBuffer" "on" # you can or not also enable triple buffering at this point
EndSection

Crabevariable · 2024-07-20 15:54:15

i still crash with nvidia-settings --assign CurrentMetaMode="nvidia-auto-select +0+0 { ForceFullCompositionPipeline = On }"
in /etc/X11/xorg.conf.d i have no file at all and if i try to save x configuration it say i cant write because i dont have permission maybe there is a problem here

seth · 2024-07-20 15:56:16

Yes, we know the full compositon pipeline causes problems with steam and it's normal that you need root privileges to write in that path, "man sudoedit"

Edt: to be clear, the snippet has three options
1. forcefully disable the FCP (might help w/ the game and multihead but make the overall multihead experience much worse)
2. avoid the kms composition pipeline (might not be a valid option anymore at all)
3. enable triple buffering (just a bonus and unrelated to the situation at hand)

Last edited by seth (2024-07-20 15:58:46)

Crabevariable · 2024-07-21 04:25:51

without force composition pipeline and force full composition pipeline on x display server setting the game still crash with xid 109

i just crated the 20-nvidia.conf with this command sudo nano /etc/X11/xorg.conf.d/20-nvidia.conf
copy paste
Section "Device"
Identifier "NVIDIA Card"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce RTX 2060"
EndSection

Section "Screen"
Identifier "Screen0"
Device "NVIDIA Card"
Option "ForceFullCompositionPipeline" "off"
Option "UseNvKmsCompositionPipeline" "false"
Option "TripleBuffer" "on"
EndSection

and this will enable triple buffering ?
i also did sudo nvidia-xconfig

Last edited by Crabevariable (2024-07-21 05:47:29)

seth · 2024-07-21 06:13:40

i also did sudo nvidia-xconfig

DON'T. Remove that config again!

and this will enable triple buffering ?

Yes, but the main point are the compositionpipeline settings.

Post your Xorg log, https://wiki.archlinux.org/title/Xorg#General
Also, probably, https://deepl.com

Arch Linux

#1 2024-07-17 21:28:25

nvidia Xid Error

#2 2024-07-18 07:09:57

Re: nvidia Xid Error

#3 2024-07-18 13:42:41

Re: nvidia Xid Error

#4 2024-07-18 15:20:39

Re: nvidia Xid Error

#5 2024-07-18 16:35:27

Re: nvidia Xid Error

#6 2024-07-18 20:29:07

Re: nvidia Xid Error

#7 2024-07-18 20:30:53

Re: nvidia Xid Error

#8 2024-07-18 21:02:20

Re: nvidia Xid Error

#9 2024-07-18 21:27:08

Re: nvidia Xid Error

#10 2024-07-18 22:37:51

Re: nvidia Xid Error

#11 2024-07-19 07:03:08

Re: nvidia Xid Error

#12 2024-07-19 07:43:47

Re: nvidia Xid Error

#13 2024-07-19 15:02:00

Re: nvidia Xid Error

#14 2024-07-19 19:45:58

Re: nvidia Xid Error

#15 2024-07-20 07:22:57

Re: nvidia Xid Error

#16 2024-07-20 11:28:36

Re: nvidia Xid Error

#17 2024-07-20 11:48:26

Re: nvidia Xid Error

#18 2024-07-20 12:27:29

Re: nvidia Xid Error

#19 2024-07-20 12:29:19

Re: nvidia Xid Error

#20 2024-07-20 13:57:18

Re: nvidia Xid Error

#21 2024-07-20 15:47:43

Re: nvidia Xid Error

#22 2024-07-20 15:54:15

Re: nvidia Xid Error

#23 2024-07-20 15:56:16

Re: nvidia Xid Error

#24 2024-07-21 04:25:51

Re: nvidia Xid Error

#25 2024-07-21 06:13:40

Re: nvidia Xid Error

Board footer