ValveSoftware / Dota-2-Vulkan

Tracker for issues specific to the Vulkan version of Dota 2 on Windows, Linux, and macOS
101 stars 17 forks source link

Vulkan Crashes my Entire Machine #187

Open hntd187 opened 7 years ago

hntd187 commented 7 years ago

Normally I start up with "-phased_window_create -high -threads 12 -gl" but vulkan crashes my machine no matter what. Even running it with just "-vulkan" alone. The title screen will begin to show up, like the first half a second of it and then just freeze. Sound continues to play on the computer, but I am not able to do anything input wise. I am not even able to get a dump from the error or see what is going on around my machine as my machine completely locks up and requires a restart. I can't even get to an alternate tty via control+alt+F2 I've attached my glxinfo and my vulkaninfo maybe that sheds some light on it.

vulkan.txt glx.txt

Computer Information:
    Manufacturer:  Unknown
    Model:  Unknown
    Form Factor: Desktop
    No Touch Input Detected

Processor Information:
    CPU Vendor:  GenuineIntel
    CPU Brand:  Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz
    CPU Family:  0x6
    CPU Model:  0x4f
    CPU Stepping:  0x1
    CPU Type:  0x0
    Speed:  4200 Mhz
    12 logical processors
    6 physical processors
    HyperThreading:  Supported
    FCMOV:  Supported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Unsupported
    SSE41:  Supported
    SSE42:  Supported
    AES:  Supported
    AVX:  Supported
    CMPXCHG16B:  Supported
    LAHF/SAHF:  Supported
    PrefetchW:  Unsupported

Network Information:
    Network Speed:  

Operating System Version:
    Ubuntu 16.04.1 LTS (64 bit)
    Kernel Name:  Linux
    Kernel Version:  4.4.0-57-generic
    X Server Vendor:  The X.Org Foundation
    X Server Release:  11804000
    X Window Manager:  Metacity (Marco)
    Steam Runtime Version:  steam-runtime-beta-release_2016-09-02

Video Card:
    Driver:  NVIDIA Corporation GeForce GTX TITAN X/PCIe/SSE2

    Driver Version:  4.5.0 NVIDIA 375.26
    OpenGL Version: 4.5
    Desktop Color Depth: 24 bits per pixel
    Monitor Refresh Rate: 144 Hz
    VendorID:  0x10de
    DeviceID:  0x17c2
    Revision Not Detected
    Number of Monitors:  2
    Number of Logical Video Cards:  2
    Primary Display Resolution:  2560 x 1440
    Desktop Resolution: 5120 x 1440
    Primary Display Size: 23.54" x 13.23"  (26.97" diag)
                                            59.8cm x 33.6cm  (68.5cm diag)
    Primary Bus: PCI Express 16x
    Primary VRAM: 12288 MB
    Supported MSAA Modes:  2x 4x 8x 16x 

Sound card:
    Audio device: Realtek ALC1150

Memory:
    RAM:  32085 Mb

Miscellaneous:
    UI Language:  English
    LANG:  en_US.UTF-8
    Microphone:  Not set
    Steam Controller Cable and Base:  Not set
    Total Hard Disk Space Available:  94087 Mb
    Largest Free Hard Disk Block:  53450 Mb
    VR Headset: None detected

Recent Failure Reports:
danginsburg commented 7 years ago

You have a very high end system that should be fine to run it obviously, it's hard to say based on the report what might be going on. Some suggestions: could you run with -con_logfile and post game/dota/console.log, there may be something useful there. Usually when you get a hang like that you might still be able to ssh in and kill the process. Also, can you try running with -threads 0 and see if it makes any difference?

hntd187 commented 7 years ago

@danginsburg Do you mean SSH in from another machine? I can't get another tty, no keyboard input seems to be working when this occurs.

Also could it be with the vulkan api version? I have vulkan dev libs on my machine inside my LD_LIBRARY_PATH, and those are 1.0.33, does that matter?

I'll try the other options a bit later to see if I can get something. Also, I suppose while I'm asking questions, does Dota2 support Gsync or SLI on linux at this time?

danginsburg commented 7 years ago

Also could it be with the vulkan api version? I have vulkan dev libs on my machine inside my LD_LIBRARY_PATH, and those are 1.0.33, does that matter?

If you are running it directly from Steam then it should be using the Vulkan loader inside the steam-runtime and not the one on your system.

I'll try the other options a bit later to see if I can get something. Also, I suppose while I'm asking questions, does Dota2 support Gsync or SLI on linux at this time?

No, not yet.

hntd187 commented 7 years ago

Okay so @danginsburg running this with the options you specified above, the game still locks up. I am not able to SSH from another machine, the connection just times out. The console log you specified from the run generated a 1.7gb file before I killed the machine. That's some pretty nice disk IO right there.

The nice thing about the file is that regardless of how large the file is it's basically the same file for literally a couple million lines. Attempting to purge m_fencedResourceList.Count() = 6, m_pendingFencedResourceQueue.Count() = 0, nCurrentCmdBuffersAvailable = 0, nAllocatedCommandBuffers = 1500

Here is the first 1000 lines of the log file, after that it's just this line forever.

logs.txt

kisak-valve commented 7 years ago

Hello @hntd187, the log is saying you are using -phased_window_create with -vulkan. These two launch options have been reported incompatible with a log that ends with almost the same recurring line at https://github.com/ValveSoftware/Dota-2/issues/962#issuecomment-267395864. Please retest without -phased_window_create

hntd187 commented 7 years ago

@kisak-valve Removing -phased_window_create does not change anything with the output.

loggylog.txt

This also generated a 1.3gb log file before I killed it.

danginsburg commented 7 years ago

The log file is indicating a GPU hang which has stalled progress on the renderthread. The main thread gets 2 frames ahead (max) and then starts to purge resources, but the fences never retire because the GPU is hung.

hntd187 commented 7 years ago

Okay so @danginsburg What can I do now to investigate further or resolve?

lovesmall commented 7 years ago
hntd187 commented 7 years ago

@lovesmall This isn't about windows, this is about Linux, so it probably doens't apply to you.

lovesmall commented 7 years ago

@hntd187 My Dota2 would crash like every game before I uncheck the Vulkan. After I unchecked it, it's good for 3 consecutive games so far. Maybe it's a cross platform issue ? I'll keep monitoring.

kisak-valve commented 7 years ago

Hello @lovesmall, please follow the steps earlier in the issue report to collect a console log so we can see how closely the symptoms match.

Ace5040 commented 7 years ago

same issue here but whole operating system become unresponsible right after alt-tab. if not alt-tabing can play as long as I want

OS: Archlinux Desktop env.: lxqt nvidia 1060 3gb msi - driver 387.22

log: console.log

with -gl all works just fine

lovesmall commented 7 years ago

Hi, I think issue for me is my video card. 1070 seems unstable after 1 year of use. It's ok after I replaced it.

hntd187 commented 7 years ago

Although I have no proof of this I figured that the issue had something to do with my SLI setup at the time. I've since moved to a 1080Ti and that plays vulkan dota2 totally fine, which is the closest thing I have to any proof of my theory. But I also understand that linux dota2 doesn't use SLI, so that probably isn't it either.

Ace5040 commented 7 years ago

I have found combination of resolution/mode wich works. I mean alt-tab doesn't lead to crash.

works fine: 1600x900 - window/borderless window all others crashes on alt-tab: 1920x1280 - fullscreen 1920x1280 - window/borderless window 1600x900 - fullscreen

Nemoder commented 6 years ago

After a system update (and upgrade to nvidia's 390.25) I am also randomly getting these complete freezes when restoring dota2 -vulkan from being minimized. However I am able to ssh in remotely and 'killall dota2 -9' to recover the desktop. console.log

evantandersen commented 6 years ago

Also suffering from this issue. Ubuntu 16.04 with nvidia driver 384.111 on a GTX 970.

Disabling vulkan fixes the issue.

Squall-Leonhart commented 5 years ago

These system are crashing because 16.04 doesn't include the HT Flaw microcode fix and the users have not updated the bios to include the microcode either.