[Bug] Game crashes after a few minutes play with "Display Driver not responding" [31316]

andrewway

Crash at 3:25

Steps to reproduce behaviour on my system:
- start subnautica
- start a new, or load a game
- play for 5-30 minutes

It tends to happen most when I'm moving, and usually when moving quickly (seaslide, seamoth). It seems related to loading graphics/streaming in the content.

You can still hear audio running (bubbles) - not sure if my player would actually run out of air or anything. Pressing Esc brings up the mouse (like the menu would be up) and then clicking "locks" the mouse (presumably trying to take control of my character).

DxDiag, and a recent crash log (not this specific one, because I didn't get the "Ooops" error) are included in this folder.
https://onedrive.live.com/redir?resid=5E8B81B2AFA039F1!10595&authkey=!AFoeZq6baACLUn8&ithint=folder,txt

A copy of my game save that I used to launch at the start of this video is also included. It was a fresh Freedom game started a few days ago (brilliant, because it let me find the seamoth fragments, etc).

This type of crash can occur from 1 minute through to 30 minutes into a session. I save A LOT to protect against this.

It has happened since I started playing the game (around 17 March 2016), including the standard version at that time and then into the experimental version.

Whenever I get the urge I try different things, like the -force-d3d9 parameter, or messing with my nVidia control panel (changing settings against the subnautica.exe application).

As yet I haven't found the "silver bullet" to fix it.

I've tried running everything from "Low" quality settings through to Experimental. I've use all of the game modes - all exhibit the same behaviour at different times. I'm using a computer with 2 screens. The primary screen runs 4K @ 30Hz, although I have even tried running the game AFTER dropping the display resolution to 1080p @ 60 Hz.

I'm getting desperate for a fix - I have an older PC with the exact same video card and I'm even thinking of switching that out to see if it's a factor. This PC I'm using doesn't get a LOT of gaming use, but runs Starcraft II and Homeworld without issue (at 1080p).

[In short, I'm also super keen to see an Xbox One port as this type of "video card just not quite compatible for some weird reason" just doesn't happen - or if it does it affects EVERY Xbox One at the same].

I hope this gives you a better picture of the issue - if you need any more information captured I'm happy to provide that too.

andrewway

I'd noticed that I always seemed to have a HDD hit whenever the crash occurred (just before) - and the textures would seem to take a while to load in (machine would "chug" until the textures loaded with a corresponding frame rate drop).

So...
- uninstalled and reinstalled a fresh copy of the game to my C: drive (128GB SSD, vs my usual 5400 rpm SATA 1TB disk)
- jumped in my Seamoth and headed off to the South East. Ok, so Reapers are bad... m'kay
- reloaded my game and headed East - just started to ascent the sand banks near the front of the Aurora and "poof" Display Driver not responding

So I guess it's not (necessarily) a performance of disk issue/loading textures taking too long (although it's still a possibility)

You see, if I move the Seamoth in "fits and squirts" leaving plenty of time for textures to load in I (seem to) have less crashes.

HTH

Updated to version 31321, by the way.

Coranth

Well... all I can say is send all your logs to the devs, using this guide: steamcommunity.com/sharedfiles/filedetails/?id=403087864; attach them to an email with a brief description of the problem--in fact, send your original post from here as the email, just attach your logs to it.

The more help we can give the devs with bug smashing, the better things will be for all of us.

Apart from that:

1. Update your nVidia Display Driver; there's a more recent one out.
2. See if you can find a more up-to-date Realtek Sound Driver; see if that helps.
3. Run a test on your RAM, using MemTest x86 or Windows Memory Diagnostic, just in case?

Dracobomba

I seem to have a very similar issue. Your game seems to crash the exact same way mine does (albeit, I have a harder time since my crashes are VERY much repeatable, especially around my sea base). If it's anything like my crashes, the game does in fact still run, and you can even save the game in this state. I suggest trying to see if you can save your game while in this crashed state (just remember where the buttons would be) and reloading to see if its linked to where you were at the time of the crash.

My GPU, however, is different, as it is integrated graphics, so I can't find a connection there. I think the problem is with how Subnautica interacts with the computer's graphics processing.

dethovu

Yep, same here. Seems to be the same type of GPU crash that was happening on AMD hardware a little while back before it was fixed. Same symptoms, reproduction, etc.

4GB AMD R9 380X

andrewway

And here's another crash - unfortunately it's pretty unusable/unplayable... ah well, I'm away with the family for 2 weeks... so either (a) we get the Xbox preview or (b) something magical happens with finding and squishing this one...



Files for latest crashes...
https://onedrive.live.com/redir?resid=5E8B81B2AFA039F1!10595&authkey=!AFoeZq6baACLUn8&ithint=folder,txt

Help me Obi Wan Kenobi... you're my only hope
(sorry, haven't looked for updated sound drivers, nor run a memory test - the rig I run gets used for video editing, PhotoShop/Lightroom, plus StarCraft II and Homeworld & a bit of minecraft) - so I'm pretty sure she's stable.

Also - updated Nvidia software to latest available.

andrewway

Ok, so decided to go back and play the (updated) Homeworld on this same PC... and whaddaya know... crash after a few minutes.

So, we have 2 PCs at home, both with near equivalent video cards in them (GTX 650Ti), although I reckon my pc got the slightly later one.

Had time last night to swap the video cards - Homeworld is now fixed and I'm about to test Subnautica, but I expect it to work perfectly.

It turns out the reason the video card fan wasn't running hard when going heavy graphics is because the DUST BUNNIES had clogged it.

So... no software issue. No weird driver issue. Purely a physical "display card full of dust, overheating" issue.

During this week I'm also going to bring one of my cans of compressed air home and spray the guts of this PC out. It is severely blocked up. It's amazing the thing even boots.

:-)