Frequent Dreamseeker Crashed

ID:2969788
 
Apr 14, 4:55 pm
I'm crashing very frequently and its hard to pinpoint why or when. This is an event log from one of them. These have taken place across different ss13 servers.

Faulting application name: dreamseeker.exe, version: 5.0.516.1659, time stamp: 0x67d87b16
Faulting module name: byondwin.dll, version: 5.0.516.1659, time stamp: 0x67d87afe
Exception code: 0xc0000005
Fault offset: 0x0010b4ef
Faulting process id: 0x0x638C
Faulting application start time: 0x0x1DBAD953EB8A7B1
Faulting application path: C:\Program Files (x86)\BYOND\bin\dreamseeker.exe
Faulting module path: C:\Program Files (x86)\BYOND\bin\byondwin.dll
Report Id: 2c5f4fcb-dbc1-4a62-8a07-ccfdae3d96ac
Faulting package full name:
Faulting package-relative application ID:

Other crashes, except for the report Id, are identical. Can someone help me figure out what's up? BYOND is updated
Apr 14, 6:06 pm
This is a client-side crash, and it's happening because either a hashtable has been corrupted or there's been an out-of-memory situation, so I'd need more data to drill down to the exact cause. A minidump with a stack trace might help.

There's also a newer BYOND build as of earlier today, although it won't have an impact on your issue.
Apr 14, 9:48 pm
0:000> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4375

Key : Analysis.Elapsed.mSec
Value: 15232

Key : Analysis.IO.Other.Mb
Value: 22

Key : Analysis.IO.Read.Mb
Value: 1

Key : Analysis.IO.Write.Mb
Value: 125

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.27793.1000

Key : Analysis.Version.Description
Value: 10.2410.02.02 amd64fre

Key : Analysis.Version.Ext
Value: 1.2410.2.2

Key : Failure.Bucket
Value: BREAKPOINT_80000003_wow64cpu.dll!CpupSyscallStub

Key : Failure.Exception.Code
Value: 0xffffffff80000003

Key : Failure.Hash
Value: {289a12fb-10fd-bb5b-3edc-4567046643a5}

Key : Faulting.IP.Type
Value: Null

Key : ProblemClass.Collapse.After.BUCKET_ID
Value: BREAKPOINT

Key : ProblemClass.Collapse.After.DEFAULT_BUCKET_ID
Value: BREAKPOINT

Key : ProblemClass.Collapse.After.PRIMARY_PROBLEM_CLASS
Value: BREAKPOINT

Key : ProblemClass.Collapse.Before.BUCKET_ID
Value: APPLICATION_FAULT

Key : ProblemClass.Collapse.Before.DEFAULT_BUCKET_ID
Value: APPLICATION_FAULT

Key : ProblemClass.Collapse.Before.PRIMARY_PROBLEM_CLASS
Value: APPLICATION_FAULT

Key : Timeline.OS.Boot.DeltaSec
Value: 104

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

Key : WER.OS.Branch
Value: ni_release

Key : WER.OS.Version
Value: 10.0.22621.1

Key : WER.Process.Version
Value: 5.0.516.1660


FILE_IN_CAB: dreamseeker.DMP

NTGLOBALFLAG: 0

APPLICATION_VERIFIER_FLAGS: 0

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 0000000000000000
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 0

FAULTING_THREAD: 3430

PROCESS_NAME: dreamseeker.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.

EXCEPTION_CODE_STR: 80000003

STACK_TEXT:
00000000`0065e838 00000000`77801b56 : 00000023`7571593c 00007ff8`ca5a0023 00000000`00000000 00000000`0085c3dc : wow64cpu!CpupSyscallStub+0x13
00000000`0065e840 00000000`77801d75 : 00000000`0085f674 00007ff8`ca5acb78 00000000`00000000 00007ff8`ca5aec97 : wow64cpu!Thunk0ArgReloadState+0x5
00000000`0065e8f0 00007ff8`ca5aea8d : 00000000`005d7000 00000000`0065f330 00000000`00000000 00000000`0065f330 : wow64cpu!BTCpuSimulate+0xbb5
00000000`0065e930 00007ff8`ca5ae18d : 00000000`00000000 00000000`00a85cf0 00000000`00000000 00000000`00000000 : wow64!RunCpuSimulation+0xd
00000000`0065e960 00007ff8`ca7ae82b : 00000000`00ae0118 00007ff8`ca80b760 00000000`005d6000 00007ff8`ca807b28 : wow64!Wow64LdrpInitialize+0x12d
00000000`0065ec10 00007ff8`ca79ab16 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : ntdll!LdrpInitializeProcess+0x174b
00000000`0065efe0 00007ff8`ca744523 : 00000000`0065f330 00007ff8`ca6d0000 00000000`005d6050 00000000`005d97ee : ntdll!_LdrpInitialize+0x565ba
00000000`0065f060 00007ff8`ca74444e : 00000000`0065f330 00000000`00000000 00000000`0065f330 00000000`00000000 : ntdll!LdrpInitializeInternal+0x6b
00000000`0065f2e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrInitializeThunk+0xe


SYMBOL_NAME: wow64cpu!CpupSyscallStub+13

MODULE_NAME: wow64cpu

IMAGE_NAME: wow64cpu.dll

STACK_COMMAND: dt ntdll!LdrpLastDllInitializer BaseDllName ; dt ntdll!LdrpFailureData ; ~0s; .ecxr ; kb

FAILURE_BUCKET_ID: BREAKPOINT_80000003_wow64cpu.dll!CpupSyscallStub

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 10.0.22621.2506

FAILURE_ID_HASH: {289a12fb-10fd-bb5b-3edc-4567046643a5}

Followup: MachineOwner
Apr 14, 9:51 pm
Above are results from a manual DMP file ran and analyzed through WinDbg. I'm not especially computer literate so I'm hoping that it's the data that would be helpful in realizing the problem.
I am under the impression that it is a memory problem, but unsure how to solve it regardless if I'm correct or not.
Apr 16, 7:27 pm
I would need the .dmp file itself, assuming it's not ginormous.

Login to reply.