Crashes that don't produce crash logs.

[ThatDearGuy]

I wanted to adress something slightly different from what I already reported in:

You see, it's quite unique for me to even have a crash log. I crash semi-frequently, *only* two times in the last hour, but I just have two crash logs in my TLD Steam folder since July.

Seeing as how most of these crashes generally play out the same, I thought I'd chronologue one instead.

Playing on Interloper, two RL hours into a game. Experienced one similar crash maybe 40 minutes ago so far.

1. I'm exiting the Log Sort cabin in Coast Highway. There are wolves very nearby, so I crouch, make my way to the highway and head west, following the road toward Fishing Camp.
2. Once I'm on the road, I resume to walk.
3. Before I pass the first rock outcropping on my left and get a clear view of the ocean, the screen output freezes.
4. I notice the game's environmental sound is still playing. I check to see if my keyboard lights responds to input and it does. Windows hasn't frozen (I know W10 doesn't really do that anymore, but old habits die hard).
5. Upon touching a few more keys I notice the game's sound still responds to my movement and pressing menu keys. I can audibly get into a menu, produce a few random menu sounds return to my game while the screen output is still frozen.
6. I wait a short while. The game doesn't seem to give me any error messages.
7. Not having any visual feedback, I try to alt-F4 to close the game. The game refuses to be shut down.
8. I successfully alt-tab out of the game. I wait a short while again, but the game still does not produce any error messages and still does not react to the alt-F4 interrupt I gave it earlier.
9. As a test, I try to alt-tab back into the game. Windows maximizes one corner of an empty window (that doesn't overlap my desktop), but I'm ultimately not let back inside.
10. I open the task manager and forcibly close the program through it. It still takes seconds to respond still, but it shuts down.
11. I determine no new crash logs have been written.

That's about it. If you know of any diagnostic tools I can run while the game plays, I'll gladly run those.

 

Windows 10 Pro 64-bit COEM edition
Intel(r) Core(TM) i7-4820K CPU 3.60 Ghz
16,0 GB RAM, Kingston, custom timings
Gainward Geforce 770 (2 GB VRAM), driver version 375.86

 

DxDiag.txt

[Sirenesong]

I experience the same crashes. Mine occurs after tops five minutes of gameplay. Once I only got to the title screen. 

I tried to delete the game and reinstall without luck, and I have checked the buffers, and updated my directX. No luck. Should I try to delete all progress ever done saved in my The Long Dark Steam Cloud?

[Support]

When you say crash logs, do you mean the debug log? The game doesn't always crash giving a full crash log, but you should still see a debug log in your tld_data folder - this will be just as useful to us. The crash log only occurs if Unity is able to catch the crash, generally if the issue occurs from outside the game Unity won't produce a crash log. Check for that log file to make sure that's being created as well. If that's not being created we might have a very different issue on hand (one where the game can't write data for some reason.) 

[Sirenesong]

When I open the "tld_data" folder, I first find the log of what I assume, the game starting up:

Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\TheLongDark\tld_Data\Managed\UnityEngine.dll (this message is harmless)
Loading C:\Program Files (x86)\Steam\steamapps\common\TheLongDark\tld_Data\Managed\UnityEngine.dll into Unity Child Domain

However it changes to this after some rounds:

 

<RI> Initializing input.
<RI> Input initialized.
desktop: 1920x1080 60Hz; virtual: 1920x1080 at 0,0
<RI> Initialized touch support.
UnloadTime: 1.366030 ms
Non platform assembly: data-14489008 (this message is harmless)
Fallback handler could not load library C:/Program Files (x86)/Steam/steamapps/common/TheLongDark/tld_Data/Mono/data-14489008.dll
Non platform assembly: data-1450DF60 (this message is harmless)
Fallback handler could not load library C:/Program Files (x86)/Steam/steamapps/common/TheLongDark/tld_Data/Mono/data-1450DF60.dll
Non platform assembly: data-27F9E020 (this message is harmless)
Fallback handler could not load library C:/Program Files (x86)/Steam/steamapps/common/TheLongDark/tld_Data/Mono/data-27F9E020.dll
Rewired: Searching for compatible XInput library...
Rewired: Found Xinput1_3.dll.
Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\TheLongDark\tld_Data\Managed\System.Xml.dll (this message is harmless)
Received stats and achievements from Steam

 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42)

Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\TheLongDark\tld_Data\Managed\Mono.Security.dll (this message is harmless)
Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\TheLongDark\tld_Data\Managed\System.Configuration.dll (this message is harmless)
Unloading 6 Unused Serialized files (Serialized files now loaded: 0)
UnloadTime: 3.876461 ms
-- SystemInfo --
deviceType: Desktop
processorType: Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz
processorCount: 4
systemMemorySize: 8107 Mb
operatingSystem: Windows 10  (10.0.0) 64bit
graphicsDeviceID: 0x412
graphicsDeviceName: Intel(R) HD Graphics 4600
graphicsDeviceType: Direct3D11
graphicsDeviceVendor: Intel
graphicsDeviceVendorID: 0x8086
graphicsDeviceVersion: Direct3D 11.0 [level 11.0]
graphicsMemorySize: 1136 Mb
graphicsShaderLevel: 50
supportsRenderTextures: True
supportsShadows: True
supportsStencil: 1
----
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42)

Unloading 14885 unused Assets to reduce memory usage. Loaded Objects now: 37216.
Total: 83.961662 ms (FindLiveObjects: 2.605369 ms CreateObjectMapping: 3.859141 ms MarkObjects: 73.776253 ms  DeleteObjects: 3.719298 ms)

GAME VERSION: Sandbox Alpha v.388
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42)

d3d11: failed to create index buffer of size 1224 [0x887A0005]
d3d11: failed to create index buffer of size 1272 [0x887A0005]
d3d11: failed to create index buffer of size 1224 [0x887A0005]
d3d11: failed to create vertex buffer of size 2688 [0x887A0005]
d3d11: failed to create index buffer of size 336 [0x887A0005]
d3d11: failed to create vertex buffer of size 2688 [0x887A0005]
d3d11: failed to create vertex buffer of size 2688 [0x887A0005]
d3d11: failed to create vertex buffer of size 2688 [0x887A0005]
d3d11: failed to create vertex buffer of size 2688 [0x887A0005]
d3d11: failed to create vertex buffer of size 2688 [0x887A0005]
d3d11: failed to create vertex buffer of size 2688 [0x887A0005]
d3d11: failed to create vertex buffer of size 2688 [0x887A0005]
d3d11: failed to create vertex buffer of size 2688 [0x887A0005]
d3d11: failed to create vertex buffer of size 2688 [0x887A0005]
d3d11: failed to create vertex buffer of size 2688 [0x887A0005]
d3d11: failed to create vertex buffer of size 2688 [0x887A0005]
d3d11: failed to create vertex buffer of size 2688 [0x887A0005]
d3d11: failed to create vertex buffer of size 2688 [0x887A0005]
d3d11: failed to create vertex buffer of size 2688 [0x887A0005]
d3d11: failed to create vertex buffer of size 2688 [0x887A0005]
d3d11: failed to create vertex buffer of size 2688 [0x887A0005]
d3d11: failed to create vertex buffer of size 2688 [0x887A0005]
d3d11: failed to create vertex buffer of size 2688 [0x887A0005]
d3d11: failed to create vertex buffer of size 2688 [0x887A0005]
d3d11: failed to create vertex buffer of size 2688 [0x887A0005]

After that, the numbers after "of size..." changes as the row keeps on going. In the end it says
Fallback handler could not load library C:/Program Files (x86)/Steam/steamapps/common/TheLongDark/tld_Data/Mono/libc
Setting up 1 worker threads for Enlighten.
  Thread -> id: fec -> priority: 1 


I have no idea what is going on. I have eperienced this for several months, except for the "Four days of Night" event. After it ended, it went back to crashing. I was hoping the next major update would fix it, but it's just gotten worse. 

 

 

 

[Support]

Could you try running the game in DX9 mode? Those errors are saying that your video card failed during a certain DX11 draw call. 

[Sirenesong]

I tried now, by only allowing Windows XP in compatibility mode.

And now I could actually play for half an hour! But, it crashed in the end.