[SOLVED] X Server crashes (apparently) randomly when playing Counterstrike Global Offensive

Hello,

when playing CS:GO, the X Server will hang up after some time.
I have not yet accomplished replicating the issue reliably, for me it is totally random.
This is the output from Steam after the crash happened: https://gist.github.com/Takios/91e8c9aed5f8b3947f23

This is the output from the X Server: https://gist.github.com/Takios/e76fab03b3142a78f5ac
The backtrace includes the nvidia drivers but I am not sure if they are the source of the crash.

Haven’t had this problem with other applications so I already reported it to the CS:GO Linux guys but to no avail yet (https://github.com/ValveSoftware/Counter-Strike-Global-Offensive/issues/203).

I’d be glad if someone could help me or point me to the right place for this.

Greetings
Takios
nvidia-bug-report.log.gz (212 KB)

Takios, Did you test with drivers 346.16 , 343.22 , 340.17 ? What desktop environment your are running - like gnome, kde ete ? I think you have connected 3 displays , Is this reproduce with only one monitor connected to gpu ? Also default nvidia xorg.conf file has not been generated ? nouveau is not blacklisted ? can you only just play the game and find at what point its crashing ? Any specific settings done in game?

Hello sandipt,

thanks for your time.
Sadly, I had no luck getting those driver versions to work with their .run script, the X Server won’t start with them installed (quits saying that it cannot find any devices). I will continue trying though.
Currently, I’m using the driver from the repository ftp://download.nvidia.com/opensuse/13.2/ , I don’t know what it does differently than the .run script, but it works.

I’m using Gnome with 3 displays, one of them disabled most of the time. Will try to reproduce the error with only 1 display connected.
My xorg.conf is generated by nvidia and nouveau is blacklisted.

Though modprobe -c | grep nouveau gives:

blacklist nouveau
alias pci:v000010DEd*sv*sd*bc03sc*i* nouveau
alias pci:v000012D2d*sv*sd*bc03sc*i* nouveau

Does that mean it gets loaded anyway?

Addressing the ingame settings, I have been gradually lowering them with every crash, but to no avail. It makes no difference. Crashes happen even on the lowest settings.

Again, thank you for your time.

Greetings,
Takios

Just crashed again while clicking something in the Buy menu and found some new messages in the logs:

Nov 26 16:23:07 mothership kernel: NVRM: GPU at PCI:0000:01:00: GPU-9dd8f36b-f875-5506-0929-f3691a5dd223
Nov 26 16:23:07 mothership kernel: NVRM: Xid (PCI:0000:01:00): 8, Channel 00000007
Nov 26 16:23:11 mothership kernel: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Nov 26 16:23:08 mothership pulseaudio[1936]: q overrun, queuing locally
Nov 26 16:23:08 mothership pulseaudio[1936]: q overrun, queuing locally
Nov 26 16:23:08 mothership pulseaudio[1936]: q overrun, queuing locally
Nov 26 16:23:08 mothership pulseaudio[1936]: q overrun, queuing locally
Nov 26 16:23:08 mothership pulseaudio[1936]: q overrun, queuing locally
Nov 26 16:23:08 mothership pulseaudio[1936]: q overrun, queuing locally
Nov 26 16:23:08 mothership pulseaudio[1936]: q overrun, queuing locally
Nov 26 16:23:08 mothership pulseaudio[1936]: q overrun, queuing locally
Nov 26 16:23:08 mothership pulseaudio[1936]: q overrun, queuing locally
Nov 26 16:23:11 mothership pulseaudio[1936]: q overrun, queuing locally
Nov 26 16:23:11 mothership pulseaudio[1936]: snd_pcm_avail() gibt einen Wert zurück, der ausserordentlich gross ist: 705776 bytes (4000 ms).
Nov 26 16:23:11 mothership pulseaudio[1936]: Dies ist wahrscheinlich ein Fehler im ALSA-Treiber 'snd_usb_audio'. Bitte melden Sie dieses Problem den ALSA-Entwicklern.
Nov 26 16:23:11 mothership pulseaudio[1936]: snd_pcm_dump():
Nov 26 16:23:11 mothership pulseaudio[1936]: Hardware PCM card 0 'Logitech G35 Headset' device 0 subdevice 0
Nov 26 16:23:11 mothership pulseaudio[1936]: Its setup is:
Nov 26 16:23:11 mothership pulseaudio[1936]:   stream       : PLAYBACK
Nov 26 16:23:11 mothership pulseaudio[1936]:   access       : MMAP_INTERLEAVED
Nov 26 16:23:11 mothership pulseaudio[1936]:   format       : S16_LE
Nov 26 16:23:11 mothership pulseaudio[1936]:   subformat    : STD
Nov 26 16:23:11 mothership pulseaudio[1936]:   channels     : 2
Nov 26 16:23:11 mothership pulseaudio[1936]:   rate         : 44100
Nov 26 16:23:11 mothership pulseaudio[1936]:   exact rate   : 44100 (44100/1)
Nov 26 16:23:11 mothership pulseaudio[1936]:   msbits       : 16
Nov 26 16:23:11 mothership pulseaudio[1936]:   buffer_size  : 880
Nov 26 16:23:11 mothership pulseaudio[1936]:   period_size  : 220
Nov 26 16:23:11 mothership pulseaudio[1936]:   period_time  : 4988
Nov 26 16:23:11 mothership pulseaudio[1936]:   tstamp_mode  : ENABLE
Nov 26 16:23:11 mothership pulseaudio[1936]:   tstamp_type  : MONOTONIC
Nov 26 16:23:11 mothership pulseaudio[1936]:   period_step  : 1
Nov 26 16:23:11 mothership pulseaudio[1936]:   avail_min    : 220
Nov 26 16:23:11 mothership pulseaudio[1936]:   period_event : 1
Nov 26 16:23:11 mothership pulseaudio[1936]:   start_threshold  : -1
Nov 26 16:23:11 mothership pulseaudio[1936]:   stop_threshold   : 7926335344172072960
Nov 26 16:23:11 mothership pulseaudio[1936]:   silence_threshold: 0
Nov 26 16:23:11 mothership pulseaudio[1936]:   silence_size : 0
Nov 26 16:23:11 mothership pulseaudio[1936]:   boundary     : 7926335344172072960
Nov 26 16:23:11 mothership pulseaudio[1936]:   appl_ptr     : 83571847
Nov 26 16:23:11 mothership pulseaudio[1936]:   hw_ptr       : 83747411
Nov 26 16:23:11 mothership pulseaudio[1936]: snd_pcm_delay() gibt einen Wert zurück, der ausserordentlich gross ist: -667052 bytes (-3781 ms).
Nov 26 16:23:11 mothership pulseaudio[1936]: Dies ist wahrscheinlich ein Fehler im ALSA-Treiber 'snd_usb_audio'. Bitte melden Sie dieses Problem den ALSA-Entwicklern.
Nov 26 16:23:11 mothership pulseaudio[1936]: snd_pcm_dump():
Nov 26 16:23:11 mothership pulseaudio[1936]: Hardware PCM card 0 'Logitech G35 Headset' device 0 subdevice 0
Nov 26 16:23:11 mothership pulseaudio[1936]: Its setup is:
Nov 26 16:23:11 mothership pulseaudio[1936]:   stream       : PLAYBACK
Nov 26 16:23:11 mothership pulseaudio[1936]:   access       : MMAP_INTERLEAVED
Nov 26 16:23:11 mothership pulseaudio[1936]:   format       : S16_LE
Nov 26 16:23:11 mothership pulseaudio[1936]:   subformat    : STD
Nov 26 16:23:11 mothership pulseaudio[1936]:   channels     : 2
Nov 26 16:23:11 mothership pulseaudio[1936]:   rate         : 44100
Nov 26 16:23:11 mothership pulseaudio[1936]:   exact rate   : 44100 (44100/1)
Nov 26 16:23:11 mothership pulseaudio[1936]:   msbits       : 16
Nov 26 16:23:11 mothership pulseaudio[1936]:   buffer_size  : 880
Nov 26 16:23:11 mothership pulseaudio[1936]:   period_size  : 220
Nov 26 16:23:11 mothership pulseaudio[1936]:   period_time  : 4988
Nov 26 16:23:11 mothership pulseaudio[1936]:   tstamp_mode  : ENABLE
Nov 26 16:23:11 mothership pulseaudio[1936]:   tstamp_type  : MONOTONIC
Nov 26 16:23:11 mothership pulseaudio[1936]:   period_step  : 1
Nov 26 16:23:11 mothership pulseaudio[1936]:   avail_min    : 220
Nov 26 16:23:11 mothership pulseaudio[1936]:   period_event : 1
Nov 26 16:23:11 mothership pulseaudio[1936]:   start_threshold  : -1
Nov 26 16:23:11 mothership pulseaudio[1936]:   stop_threshold   : 7926335344172072960
Nov 26 16:23:11 mothership pulseaudio[1936]:   silence_threshold: 0
Nov 26 16:23:11 mothership pulseaudio[1936]:   silence_size : 0
Nov 26 16:23:11 mothership pulseaudio[1936]:   boundary     : 7926335344172072960
Nov 26 16:23:11 mothership pulseaudio[1936]:   appl_ptr     : 83580647
Nov 26 16:23:11 mothership pulseaudio[1936]:   hw_ptr       : 83747631
Nov 26 16:23:11 mothership pulseaudio[1936]: snd_pcm_avail() gibt einen Wert zurück, der ausserordentlich gross ist: 202456 bytes (2295 ms).
Nov 26 16:23:11 mothership pulseaudio[1936]: Dies ist wahrscheinlich ein Fehler im ALSA-Treiber 'snd_usb_audio'. Bitte melden Sie dieses Problem den ALSA-Entwicklern.
Nov 26 16:23:11 mothership pulseaudio[1936]: snd_pcm_dump():
Nov 26 16:23:11 mothership pulseaudio[1936]: Hardware PCM card 0 'Logitech G35 Headset' device 0 subdevice 0
Nov 26 16:23:11 mothership pulseaudio[1936]: Its setup is:
Nov 26 16:23:11 mothership pulseaudio[1936]:   stream       : CAPTURE
Nov 26 16:23:11 mothership pulseaudio[1936]:   access       : MMAP_INTERLEAVED
Nov 26 16:23:11 mothership pulseaudio[1936]:   format       : S16_LE
Nov 26 16:23:11 mothership pulseaudio[1936]:   subformat    : STD
Nov 26 16:23:11 mothership pulseaudio[1936]:   channels     : 1
Nov 26 16:23:11 mothership pulseaudio[1936]:   rate         : 44100
Nov 26 16:23:11 mothership pulseaudio[1936]:   exact rate   : 44100 (44100/1)
Nov 26 16:23:11 mothership pulseaudio[1936]:   msbits       : 16
Nov 26 16:23:11 mothership pulseaudio[1936]:   buffer_size  : 880
Nov 26 16:23:11 mothership pulseaudio[1936]:   period_size  : 220
Nov 26 16:23:11 mothership pulseaudio[1936]:   period_time  : 4988
Nov 26 16:23:11 mothership pulseaudio[1936]:   tstamp_mode  : ENABLE
Nov 26 16:23:11 mothership pulseaudio[1936]:   tstamp_type  : MONOTONIC
Nov 26 16:23:11 mothership pulseaudio[1936]:   period_step  : 1
Nov 26 16:23:11 mothership pulseaudio[1936]:   avail_min    : 220
Nov 26 16:23:11 mothership pulseaudio[1936]:   period_event : 1
Nov 26 16:23:11 mothership pulseaudio[1936]:   start_threshold  : -1
Nov 26 16:23:11 mothership pulseaudio[1936]:   stop_threshold   : 7926335344172072960
Nov 26 16:23:11 mothership pulseaudio[1936]:   silence_threshold: 0
Nov 26 16:23:11 mothership pulseaudio[1936]:   silence_size : 0
Nov 26 16:23:11 mothership pulseaudio[1936]:   boundary     : 7926335344172072960
Nov 26 16:23:11 mothership pulseaudio[1936]:   appl_ptr     : 82019543
Nov 26 16:23:11 mothership pulseaudio[1936]:   hw_ptr       : 82121609

I guess the pulseaudio messages are only a symptom and the XID 8 error is the cause.
http://docs.nvidia.com/deploy/xid-errors/index.html lists this as “GPU stopped processing” which does not help me at all debugging this :/

I attached a new nvidia bug report log.

Greetings,
Takios
nvidia-bug-report.log.gz (81.6 KB)

Hello, I’m experiencing similar issues. CS:GO is freezing

  • from above version I’ve tried 346.16 and 343.22. not sure about the last one, but definitely used some around that since this issue with me for a few weeks/months
  • KDE
  • same thing happens with 1 monitor only
  • not using noveau

I’ve made more extensive post over on CS:GO steam forums:

as a conclusion, this seems to be a problem of steam+cs:go combination. Other steam games (cs:s, antichamber) don’t freeze, but adding a non-steam game (Strife) to steam produces freezes.

So an update to this one. I’ve had 660Ti and upgraded it to 970GTX. When I plugged it in, the GLX extension didn’t want to work (on the same version of drivers as before). After a bit of digging I’ve found that X.org loads its default libGL instead of nVidia’s. Reinstalling drivers didn’t work, so I did the following 3 things at the same time

  • removed nVidia drivers and installed them back in fresh
  • rm /etc/X11/xorg.conf
  • switched to opengl interface and back to nvidia in gentoo’s eselect

and restarted X

… one of those (or a combination of them) did the trick, I can run CS:GO on maximum details, I’ve experienced no freezes since then (~16 hours of play).