In response to Lummox JR
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1093

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 5317

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

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

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

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

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

Key : WER.OS.Branch
Value: winblue_ltsb_escrow

Key : WER.OS.Timestamp
Value: 2021-10-29T17:00:00Z

Key : WER.OS.Version
Value: 8.1.9600.20173

Key : WER.Process.Version
Value: 5.0.514.1571


NTGLOBALFLAG: 0

APPLICATION_VERIFIER_FLAGS: 0

CONTEXT: (.ecxr)
eax=fef70000 ebx=00000000 ecx=77110ce0 edx=77110ce0 esi=77110ce0 edi=77110ce0
eip=77086b20 esp=3139f970 ebp=3139f99c iopl=0 nv up ei pl zr na pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000244
ntdll!DbgBreakPoint:
77086b20 cc int 3
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 77086b20 (ntdll!DbgBreakPoint)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 1
Parameter[0]: 00000000

PROCESS_NAME: dreamdaemon.exe

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

EXCEPTION_CODE_STR: 80000003

EXCEPTION_PARAMETER1: 00000000

STACK_TEXT:
3139f96c 77110d19 cbd63f71 77110ce0 77110ce0 ntdll!DbgBreakPoint
3139f99c 74e36a14 00000000 74e369f0 c8322cab ntdll!DbgUiRemoteBreakin+0x39
WARNING: Stack unwind information not available. Following frames may be wrong.
3139f9b0 770ba9ef 00000000 cbd63f15 00000000 kernel32!BaseThreadInitThunk+0x24
3139f9f8 770ba9ba ffffffff 7709fde1 00000000 ntdll!__RtlUserThreadStart+0x2f
3139fa08 00000000 77110ce0 00000000 00000000 ntdll!_RtlUserThreadStart+0x1b


SYMBOL_NAME: ntdll!DbgBreakPoint+0

MODULE_NAME: ntdll

IMAGE_NAME: ntdll.dll

STACK_COMMAND: ~6s ; .ecxr ; kb

FAILURE_BUCKET_ID: BREAKPOINT_80000003_ntdll.dll!DbgBreakPoint

OS_VERSION: 8.1.9600.20173

BUILDLAB_STR: winblue_ltsb_escrow

OSPLATFORM_TYPE: x86

OSNAME: Windows 8.1

IMAGE_VERSION: 6.3.9600.20144

FAILURE_ID_HASH: {1d20f983-583a-5d58-a854-5c812a87c587}

Followup: MachineOwner
---------
As you can see from the info you pasted, that's showing that you broke into the process with a debugger, but there's no stack trace for me to look at without a minidump file.

[Edit]
It appears I was given some incorrect info about how to create minidumps and passed that on to you. The command to do a minidump isn't ".dump /ma" but is actually just ".dump /m".
In response to Lummox JR
hello sorry for late answer server only crashed 2 times and i forgot to take dump.
https://drive.google.com/file/d/ 1Ls3TPGf_LjwXYtxHGUyXZL1t_338xt0g/view
In response to LeserZ
That file doesn't appear to be a .dmp or a zip or anything.
In response to Lummox JR
i know but if you try to open it will work. I did what you say and it give me this file.
In response to LeserZ
Which BYOND version was this for? I mean which build specifically?

[edit]
Never mind; it doesn't matter. This minidump caught nothing except the debugger breaking into the program. It isn't usable for debugging purposes.
In response to Lummox JR
So is that all ? Actually the only problem when this problem occur server is kick everyone and dont let them in again. The weird thing one times server is kicked like 10 player but people was able to join again. But server was lagging. Im telling you these things because this may give you idea about problem.
In response to LeserZ
What you described suggests that it's possible there's an infinite loop in your code. I would look to see if loop_checks appears anywhere in your code, and if so if it was set to 0. If that's the case, remove that line; you should never turn off loop_checks except temporarily.
i'll send you a last things in server console when this problem occur
[04:52:52] Runtime in stack_trace.dm,3: addtimer called with a callback assigned to a qdeleted object. In the future such timers will not be supported and may refuse to run or run with a 0 wait
usr: Alesdor/(Default Cyborg-381)
usr.loc: (Central Primary Hallway (122,112,4))


//

[04:51:05] Runtime in atoms.dm,1667: Cannot execute null.log message().
usr: Sipsaknecmi/(Commander Beep O'sky)
usr.loc: (Starboard Primary Hallway (136,128,4))


//


Runtime in map_popups.dm,63: bad index
proc name: clear map (/client/proc/clear_map)
usr: Eslin[DC]/(Eslin)
usr.loc: (start area (8,174,1))
Just wanted to add a note that I believe id:2771136 might have been this bug exactly. It happened specifically with Cyrillic text.
Hi Lummox! I changed windows language long time ago but that didnt change anything. The problem is still happening but we doesnt care much anymore because it happen one time on a week. Its because of player count we was like 90 avg in day but now we like 40
FWIW, we had this issue regularly on -startup- at CM13 until a bit over a year ago

It eventually stopped as we sprayed over several issues, but from memory the most likely related timewise were:

a. extools which we were running in production, and turned out to be causing more problem than it was worth. might want to doublecheck

b. horrible deletes and bad shutdown shenanigans resulting in a soft-reboot and sometimes OOMs, or even ending up with soft-rebooted and re-launched "hard-rebooted" instances side by side
In response to Firartix
im using tg codebase and this is not happening in other servers. So you mean if i fix the console errors is that gonna get fix?if is that work then it also will be suck because that mean we cant update tg anymore. Only thing that i care about here when this problem occur kick people and dont let them join server again. So if is there any way to let people join again that would be great.
Page: 1 2