Trying To Understand Steam Crash Dump File

[Shanoa Ravendare]

For the last two weeks I've been having issues with Steam itself crashing while I'm playing 7 Days To Die on my friend's multiplayer server. I don't have any issues in single player. I was able to find and open the dump file generated by the steam crash, but I've been out of the coding world for so long that I have no idea what I'm looking at and can't make heads or tails of it.

Any tips on understanding the information it's providing would be greatly appreciated.

[Jack Schitt]

I don't experience game crashes so I don't have any of my own dump files to look at. Please share yours and I'll try to help translate it. Dump files don't always indicate why, exactly, a game crashed. I'm assuming it might be a mod mismatch? Have you insured you have the same exact version of any and all of the mods on the server if there are any? That's usually why these things happen if it's not a connection error.

[Iceira]

Do other Multiplayer server work, maybe your friends server has connection issue or bandwide issue. ( many forget route to other ppl privat server through ISP network is also a issue. ) + congested area or bad packets even + wifi , then you have all the worst case senario with to late with data so you get DC or game crash even.

ps.
forgot the VPN in top of this jump out on other side of the world even

and it dont make it better if both ends use wifi and VPN, thats means double travl distance in packets on both ends. ( as i said worst case senario with all worst possible idea's in top of each other. )

[Shanoa Ravendare]

It's not the game that's crashing, it's Steam. Which is why it's so confusing. I just played for several hours on another friend's multiplayer server and had no issues at all. I'm starting to think it's related to one of the mods he's using, they were originally created for A19 and then upgraded for A20 and might not be as stable as they should be.

[Elucidator]

Usually you don't need to understand code to understand crash dump files.
I don't know what the average crash dump file looks like. There isn't a wiki listing examples of every crash dump. This point being, its likely a case by case thing.

Meaning, so long you don't share anything no one will be able to look or give an answer as to what it could be.

So, is it like... filled with hex or is it filled with assembly or something?
Does it say "error" anywhere, maybe a memory address, pointer, etc.

Considering it crashes while playing online, its probably something with the programming of the game itself. Maybe you want to take the subject to the 7 Days to Die forum (and tell them they screwed up some networking packets somewhere basically).
They will likely also ask for crash logs, etc.

[Shanoa Ravendare]

So this is what I'm getting in the Dump File.

*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4515

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 7758

    Key  : Analysis.Init.CPU.mSec
    Value: 280

    Key  : Analysis.Init.Elapsed.mSec
    Value: 15148

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 232

    Key  : Timeline.Process.Start.DeltaSec
    Value: 4202

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1

    Key  : WER.Process.Version
    Value: 7.0.91.85


FILE_IN_CAB:  crash_steam.exe_20220121225038_1.dmp

COMMENT:  Assert( ***** OUT OF MEMORY! attempted allocation size: 1048576 ****
 ):c:\buildslave\steam_rel_client_win32\build\src\tier0\memstd.cpp:2831


NTGLOBALFLAG:  0

CONTEXT:  (.ecxr)
eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=00000002 edi=00000002
eip=77df2f8c esp=04e0ee10 ebp=04e0efa0 iopl=0         nv up ei pl nz ac po nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00200212
ntdll!NtWaitForMultipleObjects+0xc:
77df2f8c c21400          ret     14h
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00000000
   ExceptionCode: 00000000
  ExceptionFlags: 00000000
NumberParameters: 0

PROCESS_NAME:  steam.exe

STACK_TEXT:  
04e0ee0c 77afb1d3     00000002 04e0efd8 00000001 ntdll!NtWaitForMultipleObjects+0xc
04e0efa0 77afb0b8     00000002 04e0efd8 00000000 KERNELBASE!WaitForMultipleObjectsEx+0x103
04e0efbc 6e5d66cd     00000002 04e0efd8 00000000 KERNELBASE!WaitForMultipleObjects+0x18
WARNING: Stack unwind information not available. Following frames may be wrong.
04e0efe0 6e5d6687     0d586008 6e6127d8 6e5d27f1 crashhandler+0x66cd
04e0f004 6e5d27a3     00000b0c 04e0f7a8 00000000 crashhandler+0x6687
04e0f02c 6e42ec21     094b3dc8 00000000 04e0f7a8 crashhandler+0x27a3
04e0f7c4 6e42f33a     04e0f91c 6e459548 00000b0f tier0_s!CThreadRWLock::UnlockWrite+0x321
04e0f7e0 6e4253e6     04e0f91c 6e459548 00000b0f tier0_s!WriteMiniDump+0x9a
04e0f8f4 6e424a81     04e0f91c 6e459548 00000000 tier0_s!AssertMsgImplementation+0x206
04e0f908 6e42cdaa     6e459548 80000b0f 04e0f91c tier0_s!AssertMsgHelper<1>::AssertFailed+0x11
04e0fa1c 6e429e03     00100000 04e0fb74 09472790 tier0_s!CThreadMutex::Lock+0xd5a
04e0fa34 78628f24     00100000 78ea1d40 00000b6d tier0_s!RealPrintRawCallStack+0x16d3
04e0fac8 7872bd1d     06424780 04e0fb74 04e0fb9c steamclient!hid_write_output_report+0x1036d4
04e0fb18 786b2b23     0000000c 04e0fb9c 7918bb90 steamclient!Steam_ReleaseThreadLocalMemory+0xeb8d
04e0fb38 78722567     00050004 04e0fb74 04e0fb9c steamclient!hid_write_output_report+0x18d2d3
04e0fb54 786b3c37     00050004 04e0fb74 04e0fb9c steamclient!Steam_ReleaseThreadLocalMemory+0x53d7
04e0fbd0 786b45b8     765edfb0 7918bb90 004feb00 steamclient!hid_write_output_report+0x18e3e7
04e0fc4c 786b3cc2     7918bc48 6e432aee 04e0fccc steamclient!hid_write_output_report+0x18ed68
04e0fc60 6e42e686     7918bc48 033feae8 6e42e725 steamclient!hid_write_output_report+0x18e472
04e0fc98 6e42e0a8     04e0fccc 765edfb0 033feae8 tier0_s!CValidator::GetNumSockets+0x396
04e0fcc0 6e42f001     04e0fccc 00000003 6e432ae0 tier0_s!CThread::CalcStackDepth+0x48
04e0fce4 6e432c38     6e432ae0 7918bc48 00000000 tier0_s!CatchAndWriteMiniDumpForVoidPtrFn+0x51
04e0fd1c 765efa29     013feae8 765efa10 04e0fd88 tier0_s!CThread::ThreadProc+0x118
04e0fd2c 77de7a9e     033feae8 1dcbce1c 00000000 kernel32!BaseThreadInitThunk+0x19
04e0fd88 77de7a6e     ffffffff 77e08a42 00000000 ntdll!__RtlUserThreadStart+0x2f
04e0fd98 00000000     6e432b20 033feae8 00000000 ntdll!_RtlUserThreadStart+0x1b


SYMBOL_NAME:  crashhandler+66cd

MODULE_NAME: crashhandler

IMAGE_NAME:  crashhandler.dll

STACK_COMMAND:  ~7s ; .ecxr ; kb

EXCEPTION_CODE_STR:  0

FAILURE_BUCKET_ID:  APPLICATION_FAULT_0_crashhandler.dll!Unknown

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x86

OSNAME:  Windows 10

IMAGE_VERSION:  7.0.91.85

FAILURE_ID_HASH:  {038d2e03-5cb7-55cc-b10e-a83d16e3c61e}

Followup:     MachineOwner

@Elucidator, I posted here because it's STEAM that is crashing not the game itself.

[CZI]

Dump file is usually help to debug at debug environment with original source code.

It would not help you to understand, but it would help to debug and locate issue quicker to developer.

So I'd suggest to file proper bug report to both Steam and Game publisher. If Steam don't fix, publisher may able to push to fix.

Following is simple bug report form.

A) Bug title

B) Descriptions

C) Steps to reproduce
1)
2)
3)

D) Expected result

E) Actual result

F) Workaround (if available)

G) System info, misc note, etc

then attach your error dump.

In some case, Event Viewer's crash event info would help too.

[Iceira]

How can you run out of memory, disk full issue or something like that, and alot of apps running you dont need or know run things on pc.

have cancer cure app run as hide or something like that.

do note i only focus on out of memory. disk spce free on every system disk and total size, and i doubt you have turn swapfile off.

[Elucidator]

Originally posted by Shanoa Ravendare:

So this is what I'm getting in the Dump File.
@Elucidator, I posted here because it's STEAM that is crashing not the game itself.

So, the top of the file, with the key stuff and such is apparently metadata about the crash file itself.

I am guessing from your descriptions that you were actively playing and then suddenly Steam crashes, but the game keeps running?
hm... very odd.

The crash log indicates the summary of the events in the Comment section, saying it ran out of memory.
this, all in total suggests something has a memory leak. (which means over time memory keeps building up till your RAM is full (or a specific reserved space in RAM is completely in use and it tries to build up beyond this), and then Steam crashes because it realized something was wrong) (It can also be windows that crashed it if it is your whole RAM filling.) (small edit: it wasn't windows)


Anyway no wonder you don't understand what it means. Its a vague report. Even the record value is 0. The stacktrace only tells me it got stuck at wait for multiple objects, but not indicating which. Sorry, I think Valve themselves may know more.

Its possible it is still 7 days to die if it uses Steam for reasons like networking (connecting to people using Steam Friends and Chat for example).
That said, it could be Steam itself alone, but then I expect similar crashes to happen without the game running.

Edit: I'm just saying, just because Steam crashed doesn't mean its caused by Steam and that it is Steam that needs to fix it. Perhaps this is just a safety feature implemented by Steam's dev team, and it is working as it should. (that meaning; if a developer screwed something up and caused this nonsense, to prevent the operating system from crashing, steam itself would crash instead)
That said, it can indeed be steam too, as there is no indication of a link anywhere (not even to Steam's own dlls, so idk.)

When windows crashes, usually the blame doesn't go to windows. Just to name an example. In this case, I think it may still be the game or a mod in a similar way I suppose.

Edit: (see lower post below)

[Iceira]

"memory leak" RAM block issue require testing , even seen reinsert them and problem goes away
Overclocking, or lack or refresh mem table in time.
and even missing Bios update to what board support already know and have fixed.

thats area is filled with other possibilities and could be seen as require a tech person, to even ID or google and update such. you need to be skilled but yeah normal people can do it, but it can be very complicate to talk RAM or how it works, not sure steam places is the right places for that , but any gl with it test ram to all the other things you need to do here.

[ReBoot]

Send this dump to Steam support. This crash dump handler, from the looks of it, is gathering information or whatnot, that'll be help for devs to fix this crash.

[Elucidator]

I think the number in memory size it is trying to allocate is in KB, meaning it tried to reserve 1GB of memory. Steam probably crashed the application, because it found it way too much.

[Shanoa Ravendare]

So it sounds like something in the mods my friend is running on the server is causing a memory leak and that's why Steam crashes when I play with him and not other people. Thanks for all the help! This gives me somewhere to start tracking things down.

[Iceira]

Originally posted by Shanoa Ravendare:

So it sounds like something in the mods my friend is running on the server is causing a memory leak and that's why Steam crashes when I play with him and not other people. Thanks for all the help! This gives me somewhere to start tracking things down.

No what if that mod work on hes pc and yours is not, this is still your pc that doing it.

ps.
steam might tell you contact own board support or Brand pc, because steam dont make Driver or fix other Brands issue, steam sell games and only support own brand steam releated things.

and we can say what if this is a system issue even, you can "Try SFC/scannow" google it.
and safe boot mode but its still require no memleak or whats cause this.

ps.
do note we assume or hope you dont have a hardware issue and its glitch or software releated.