• DOOM 2016 - System freeze


    I have installed DOOM with PoL and it is running smoothly with Vulkan on. I mean, 80 fps minimum. It is like a dream come true :D

    However I just noticed that I have a hardware freeze randomly between 5 to 30 minutes. I can’t do anything after and the only output I have is the game sound that continues playing normally. I googled a lot and found no answer yet.

    Any tips?

    Wine -v: 2.3 -staging
    Virtual Drive 64 bits
    Emulate a virtual desktop on with 1920x1080
    CSMT enabled

    System: Host: JTBIGARCH Kernel: 4.9.11-1-ARCH x86_64 (64 bit gcc: 6.3.1) Desktop: Gnome 3.22.3 (Gtk 3.22.9)
    Distro: Antergos Linux
    Machine: Device: desktop System: ASUS product: All Series
    Mobo: ASUSTeK model: Z87-PLUS v: Rev 1.xx UEFI: American Megatrends v: 2103 date: 08/15/2014
    CPU: Quad core Intel Core i5-4670K (-MCP-) cache: 6144 KB
    flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 27195
    clock speeds: max: 3800 MHz 1: 2098 MHz 2: 2262 MHz 3: 2197 MHz 4: 2043 MHz
    Graphics: Card-1: NVIDIA GK110 [GeForce GTX 780] bus-ID: 01:00.0
    Card-2: NVIDIA GK110 [GeForce GTX 780] bus-ID: 02:00.0
    Display Server: X.Org 1.19.2 driver: nvidia Resolution: [email protected], [email protected]
    GLX Renderer: GeForce GTX 780/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 378.13 Direct Rendering: Yes
    Audio: Card-1 Intel 8 Series/C220 Series High Definition Audio Controller
    driver: snd_hda_intel bus-ID: 00:1b.0
    Card-2 2x NVIDIA GK110 HDMI Audio driver: snd_hda_intelsnd_hda_intel bus-ID: 02:00.1
    Card-3 Microsoft LifeCam Cinema driver: USB Audio usb-ID: 001-007
    Card-4 Plantronics driver: USB Audio usb-ID: 001-006
    Sound: Advanced Linux Sound Architecture v: k4.9.11-1-ARCH

    PlayOnLinux logfile

    Date: 03/05/17 11:28:55

    PlayOnLinux Version
    uname -a
    Linux JTBIGARCH 4.9.11-1-ARCH #1 SMP PREEMPT Sun Feb 19 13:45:52 UTC 2017 x86_64 GNU/Linux
    lsb_release -a

    wine --version

    glxinfo | grep rendering
    direct rendering: Yes
    GL_NV_path_rendering, GL_NV_pixel_data_range, GL_NV_point_sprite,
    GL_NV_path_rendering, GL_NV_pixel_data_range, GL_NV_point_sprite,
    GL_NV_packed_float_linear, GL_NV_path_rendering,
    glxinfo | grep renderer
    OpenGL renderer string: GeForce GTX 780/PCIe/SSE2
    OpenGL libs (Direct rendering testing)
    32bits direct rendering is enabled
    64bits direct rendering is enabled

    [Edit] journalctl

  • Hi,

    When it freezes, reboot and check your log with
    journalctl --since=today

    It looks like a graphics card driver problem, but who knows…

  • @karasu Thanks for your help

    I tried to upload a txt file with the output but seems that I do not have permissions. You want me to cp paste all the text from journalctl --since=today here?

    Noticed this part that seems relevant:

    mar 10 09:36:13 JTBIGARCH kernel: NVRM: Your system is not currently configured to drive a VGA console
    mar 10 09:36:13 JTBIGARCH kernel: NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
    mar 10 09:36:13 JTBIGARCH kernel: NVRM: requires the use of a text-mode VGA console. Use of other console
    mar 10 09:36:13 JTBIGARCH kernel: NVRM: drivers including, but not limited to, vesafb, may result in
    mar 10 09:36:13 JTBIGARCH kernel: NVRM: corruption and stability problems, and is not supported.
  • Hi,

    I don’t really know if it’s related or not.

    Anyways, you can use paste2.org (or any similar service) to upload your log and then put here the link for us to see.


  • @Jonnyteronni said in DOOM 2016 - System freeze:

    Noticed this part that seems relevant:

    This is only a warning, and everybody get this on installed nvidia driver…

    [updates once a week] = [90% less problems]
    how to add system logs
    i3 GNOME

  • @joekamprad Ok. I just edited the original post with the journalctl output.

  • Hi,

    You have some errors on that log, but nothing critical.

    Here http://steamcommunity.com/app/379720/discussions/0/152391995402132325/ says that you have to block services.bethesda.net adding it to your /etc/hosts with a loopback ip: (I don’t know if you already did this or if it’s still needed).

    I think you’ll have more luck asking here:
    irc: freenode.net #doom-wine


  • Oh, If you want to get rid of that NVRM error you have to edit
    sudo nano /etc/default/grub

    And change the GRUB_CMDLINE_LINUX_DEFAULT line to

    GRUB_CMDLINE_LINUX_DEFAULT="video=vesa:off vga=normal quiet"

    and then update your grub menu:

    sudo grub-mkconfig -o /boot/grub/grub.cfg


  • @karasu Hi
    It says in the end of the steam post : “with latest wine patches everything should work fine.
    you don’t need my workaround anymore, just get the latest wine-staging and enjoy!”

    I’m using 2.3 staging so it should be fixed right? I will try to get some help on the freenode chat aswell.

gaming5 wine16 doom1 freeze23 Posts 10Views 909
Log in to reply