[Crash] Currently unable to play the game - Subnautica crashes/freezes after one minute

ScanianMoose

Heya,

I am currently unable to play Subnautica, as it crashes or freezes one minute into the game.
Sometimes, it crashes, sometimes, it crashes the computer, sometimes, it only freezes the graphics, while the game and sound keep going.
I used to have this problem for a couple of weeks now, although the "playable" period was one-two minutes longer when I still had Windows 7.

My computer is Win10 64bit and should have more than enough power to run Subnautica (comparable games don't crash).
Drivers etc. are up-to-date, reinstalling Subnautica or validating the cache did not yield any results.

Logs:
http://pastebin.com/ANNtaVSa (normal crash)
http://pastebin.com/45ewq2gs (computer crash)
(For some reason, these logs say I have Windows 8.1, which is not the case)

Dxdiag:
http://pastebin.com/qDS6Jyz7

Hope I can get some feedback on what else I could try to fix the game.
Cheers!

DC_Darkling

Where to start.....

dxdiag shows many many windows errors. Starts with 'AutoKMS.exe', which a short google shows pretty much only shows up on cracked windows stuff.
Cracks can give all sorts of weird problems. Personally (and im speaking only for me), id say support ends there.

Windows Error Reporting:
+++ WER0 +++:
Fehlerbucket -234640452, Typ 5

Ereignisname: CLR20r3

Antwort: Nicht verfügbar

CAB-Datei-ID: 0



Problemsignatur:

P1: AutoKMS.exe

P2: 2.5.0.0

P3: 52aef33f

P4: AutoKMS

P5: 2.5.0.0

P6: 52aef33f

P7: 3d

P8: a8

P9: System.ApplicationException

P10:



Angefügte Dateien:

C:\Windows\Temp\WER9612.tmp.appcompat.txt

C:\Windows\Temp\WER96A0.tmp.WERInternalMetadata.xml

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_AutoKMS.exe_32d853038dfbd4f32b5da376def74dcfa6aeba_9fcfe276_cab_50f096dc\memory.hdmp

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_AutoKMS.exe_32d853038dfbd4f32b5da376def74dcfa6aeba_9fcfe276_cab_50f096dc\triagedump.dmp



Diese Dateien befinden sich möglicherweise hier:

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_AutoKMS.exe_32d853038dfbd4f32b5da376def74dcfa6aeba_9fcfe276_3f0ca9a9



Analysesymbol:

Es wird erneut nach einer Lösung gesucht: 0

Berichts-ID: 4b126e07-8e86-4ba3-a9bd-c8b7ab94f7ef

Berichtstatus: 0

Bucket mit Hash: fb05c6e968ab237a76ceff5f200042d7

Im also not convinced of the vid cards graphics power. R9 200 doesn't exist according to gpuboss, which makes me wonder which submodel yours is. If it does exist and isnt even on a site like gpuboss, its probably puny.


Some shader errors and steam running errors. I do not know if shader errors matter, but the steam one seems weird.

WARNING: Shader Unsupported: 'Marmoset/Mobile/Specular IBL' - All passes removed
WARNING: Shader Unsupported: 'Marmoset/Mobile/Self-Illumin/Specular IBL' - All passes removed
WARNING: Shader Unsupported: 'Marmoset/Mobile/Self-Illumin/Bumped Specular IBL' - All passes removed
WARNING: Shader Unsupported: 'Marmoset/Mobile/Self-Illumin/Specular IBL' - All passes removed
WARNING: Shader Unsupported: 'Marmoset/Mobile/Specular IBL' - All passes removed
WARNING: Shader Unsupported: 'Marmoset/Mobile/Self-Illumin/Bumped Specular IBL' - All passes removed
Steamworks: SteamAPI_Init() failed. Is Steam running? If you are inside the editor, this is probably ok, but Steamworks integrations will not function.

Also many dx errors:

d3d11: failed to create index buffer of size 240 [0x887A0005]
d3d11: failed to create vertex buffer of size 240 [0x887A0005]
d3d11: failed to create index buffer of size 12 [0x887A0005]

Your system and game install both do not seem healthy to me.

x1Alpha2014

I have Lag problems, I think its because my Base is as Big like a Town, im in experimental mode.

ScanianMoose

dxdiag shows many many windows errors. Starts with 'AutoKMS.exe', which a short google shows pretty much only shows up on cracked windows stuff.
Cracks can give all sorts of weird problems. Personally (and im speaking only for me), id say support ends there.

Uh, neither my Windows, nor my game are cracked. I bought the game months ago (and I am also one of the Wiki admins).

Im also not convinced of the vid cards graphics power. R9 200 doesn't exist according to gpuboss, which makes me wonder which submodel yours is. If it does exist and isnt even on a site like gpuboss, its probably puny.

I think that's because the drivers for these graphics cards are just a general 200 series driver. IIRC, my graphics card is a R9 290 or 280.

DC_Darkling

Still the original comment of windows errors stands. IF it is officially shipped with your version of windows, it should still not crash that often.

I took the liberty of looking at my own output log. I do not have the directx and shader errors yours has. So you should still follow up on all 3 of those points.


>edit, also as you can see by me responding im still considering all options, even the ones which atm seem unlikely. Nonetheless noone should ever troubleshoot a application if the system under it is not in optimal shape.)

ScanianMoose

I have done all I could find for [0x887A0005] - like forcing -noborder in Steam, having Windows find and repair corrupted system files, and adding a hkey that should give the graphics card 10 instead of 2 seconds to catch up. No success. I get a windows event that the AMD driver has crashed every time SN crashes, but I have no idea how to fix that, as reinstalling the drivers obviously does not help at all.

Nobody but Unity developers seem to have these shader problems. I have nothing to go on there.

DC_Darkling

First things first.. before you dive into any subnautica errors, you have to make sure your system itself is not flawed. But it is.

Application crash:
AutoKMS.exe

Problem with this one is that I dont know the app. (which if its shipped by windows would be rare for me to not know.)
I can find no documentation on this one. The only links I can find all link to virus & hacks, as described earlier.
Though a 'mere' application, the above does raise its severity factor quite a bit.
As documentation is sparse and my system does not have this file, I can not say how to troubleshoot it precisely. Id need access to the system in question for that.


Then you also have kernel errors in your log:
Live Kernel Event

Your log shows not much additional info I can directly use on the matter, but kernel events are usually a big problem.
It made you a dmp file: C: \ Windows \ Live Kernel Reports \ WATCHDOG \ WD 20150810-0522.dmp
Im willing to run it through the windows debugger if you can upload it somewhere, but I guarantee nothing.


Another appcrash:
Subnautica this time, I dont truly think subnautica is to blame with the few info in its subsection.

More info:
These files may be here:

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Subnautica.exe_5ef3e05a29773769cc5d8f31727c16b2dcaae3f4_b2356449_


Now kernel events may be due to drivers, but without more info its all guesswork.
Obviously after you have looked into all of the above I would suggest a full cleanup of your video card drivers and reinstalling them.

ScanianMoose

Kernel report:
http://www26.zippyshare.com/v/VRU90Qt0/file.html
App crash report:
http://www26.zippyshare.com/v/S61NJ2F3/file.html

DC_Darkling

Its the ati driver which crashed your kernel.

FAULTING_IP:
atikmpag+cc9c
fffff801`e63acc9c ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_ENGINE_TIMEOUT

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


BUGCHECK_STR: 0x141

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
ffffd000`2074e490 fffff801`e5f42641 : ffffe000`85fee4c0 ffffd000`2074e630 ffffe000`85661000 ffffe000`86def010 : watchdog!WdDbgReportRecreate+0x104
ffffd000`2074e4e0 fffff801`e6609e5c : 00000000`00000000 00000000`00000000 ffffe000`8565d000 ffffe000`8565d000 : dxgkrnl!TdrUpdateDbgReport+0xe1
ffffd000`2074e530 fffff801`e6666e3c : ffffe000`8565d000 00000000`00000000 00000000`00000001 00000000`00000001 : dxgmms2!VidSchiResetEngine+0x63c
ffffd000`2074e810 fffff801`e666a0f4 : 00000000`00000000 ffffd000`2074e920 00000000`00000001 00000000`00000000 : dxgmms2!VidSchiResetEngines+0x84
ffffd000`2074e850 fffff801`e66679fe : ffffe000`8565d000 ffffd000`00000102 ffffd000`2074eb00 00000000`00000004 : dxgmms2!VidSchWaitForCompletionEvent+0x3d4
ffffd000`2074e8e0 fffff801`e6605f87 : ffffe000`85661000 00000000`00000000 ffffe000`85661790 ffffe000`8565d9a0 : dxgmms2!VidSchiWaitForCompletePreemption+0x7e
ffffd000`2074e9d0 fffff801`e65fcbc7 : ffffe000`85661000 ffffe000`85661000 00000000`00000004 ffffe000`832e1c40 : dxgmms2!VidSchiCompletePreemption+0x13
ffffd000`2074ea00 fffff801`e6633363 : ffffe000`85661000 ffffd000`2074ebc8 ffffe000`86117c40 ffffe000`00000000 : dxgmms2!VidSchiScheduleCommandToRun+0x72c7
ffffd000`2074eb90 fffff801`e6633340 : ffffe000`85661000 6372305a`00000000 ffffe000`8025a840 ffffe000`8025a800 : dxgmms2!VidSchiRun_PriorityTable+0x1f
ffffd000`2074ebc0 fffff801`7b173698 : ffffe000`8025a840 ffffd000`2074ec90 ffffd001`6da80180 fffff801`7b1e0230 : dxgmms2!VidSchiWorkerThread+0x80
ffffd000`2074ec00 fffff801`7b1e0306 : ffffd001`6da80180 ffffe000`85662840 ffffd001`6da8ccc0 38477957`586d6252 : nt!PspSystemThreadStartup+0x58
ffffd000`2074ec60 00000000`00000000 : ffffd000`2074f000 ffffd000`20749000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+cc9c
fffff801`e63acc9c ?? ???

SYMBOL_NAME: atikmpag+cc9c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 55a70536

FAILURE_BUCKET_ID: 0x141_IMAGE_atikmpag.sys

BUCKET_ID: 0x141_IMAGE_atikmpag.sys

Followup: MachineOwner

So the only error we have not explained yet is the AutoKMS.exe one. And I once again do urge you to look into this a bit more. (where is it stored, is it signed, scanned for virusses etc.)

As for the amd driver.. cleanup your drivers, reinstall them by downloading a new copy from amd. If the problem persists go check hardware itself.

ScanianMoose

Hello, thought I might update this thread so that future viewers who encounter the same problems may be able to solve it.

The problem was overclocking, in particular my overclocked AMD Radeon R9 290x. I never overclocked it myself, but it seems that it is shipped overclocked by default.

The problem can be solved by reducing the graphic card's clocking to the native value using the AMD Catalyst Control Center.

1) Open the AMD Catalyst Control Center
2) Go to the "Performance" tab
3) Open the "AMD Overdrive" tab
4) Look up your graphic card's native clock rate on the manufacturer's website
5) Check the box for "Enable Graphics OverDrive"
6) Enter the native clock rate value into the "GPU clock settings" field
7) Click on "apply"

This has fixed all issues I had with Subnautica crashing, as well as all instances of the DXGI_ERROR_DEVICE_HUNG I used to get in Battlefield 4 from time to time.

Obraxis

Thanks for letting us know!