tdesktop icon indicating copy to clipboard operation
tdesktop copied to clipboard

BSOD Dump Windows 11 x64

Open rugabunda opened this issue 3 years ago • 1 comments

Steps to reproduce

Run Telegram for days and wait until it crashes

Expected behaviour

No crash

Actual behaviour

Crash dump Telegram.exe.10196.7z.zip h

` Microsoft (R) Windows Debugger Version 10.0.22000.194 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users**\AppData\Local\CrashDumps\backup\Telegram.exe.10196.dmp] User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: srv* Executable search path is: Windows 10 Version 22000 MP (12 procs) Free x64 Product: WinNt, suite: SingleUserTS Edition build lab: 22000.1.amd64fre.co_release.210604-1628 Machine Name: Debug session time: Tue Feb 1 15:51:15.000 2022 (UTC - 7:00) System Uptime: not available Process Uptime: not available ...................... Loading unloaded module list . This dump file has an exception of interest stored in it. The stored exception information can be accessed via .ecxr. (27d4.2a48): Unknown exception - code c06d007e (first/second chance not available) For analysis of this file, run !analyze -v ntdll!NtWaitForMultipleObjects+0x14: 00007ffc`fe5242a4 c3 ret 0:000> !analyze -v


  •                                                                         *
    
  •                    Exception Analysis                                   *
    
  •                                                                         *
    

*** WARNING: Unable to verify timestamp for Telegram.exe

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 1374

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 2321

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

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

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

Key  : WER.OS.Branch
Value: co_release

Key  : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z

Key  : WER.OS.Version
Value: 10.0.22000.1

Key  : WER.Process.Version
Value: 3.5.0.0

NTGLOBALFLAG: 0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS: 0

APPLICATION_VERIFIER_LOADED: 1

CONTEXT: (.ecxr) rax=0000007a000003ff rbx=0000000000000000 rcx=000000000000345f rdx=0000019e9bdc99e0 rsi=0000000000000001 rdi=0000000000000000 rip=00007ffcfb98478c rsp=0000007a2210fc30 rbp=0000007a2210fd80 r8=0000007a0000000a r9=00000080000003ff r10=000000000000345f r11=0000b6a3252cba11 r12=00007ff6f66b1cd0 r13=00007ff6f502eeb8 r14=00007ff6f502b4b0 r15=00007ff6f69491c0 iopl=0 nv up ei pl nz na pe nc cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202 kernelbase!RaiseException+0x6c: 00007ffc`fb98478c 0f1f440000 nop dword ptr [rax+rax] Resetting default scope

EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007ffcfb98478c (kernelbase!RaiseException+0x000000000000006c) ExceptionCode: c06d007e ExceptionFlags: 00000080 NumberParameters: 1 Parameter[0]: 0000007a2210fd30

PROCESS_NAME: Telegram.exe

ERROR_CODE: (NTSTATUS) 0xc06d007e - <Unable to get error code text>

EXCEPTION_CODE_STR: c06d007e

EXCEPTION_PARAMETER1: 0000007a2210fd30

STACK_TEXT:
0000007a2210fc30 00007ff6f335cf00 : 0000000000000000 000055f000000000 0000000000000002 0000000000000000 : kernelbase!RaiseException+0x6c 0000007a2210fd10 0000000000000000 : 000055f000000000 0000000000000002 0000000000000000 00007ff600000048 : Telegram+0x31ccf00

SYMBOL_NAME: kernelbase!RaiseException+6c

MODULE_NAME: kernelbase

IMAGE_NAME: kernelbase.dll

STACK_COMMAND: ~0s ; .ecxr ; kb

FAILURE_BUCKET_ID: APPLICATION_FAULT_AVRF_c06d007e_kernelbase.dll!RaiseException

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 10.0.22000.434

FAILURE_ID_HASH: {3365e51e-3075-1e7e-2b61-b489eb04e185}

Followup: MachineOwner

`

Operating system

Windows 11 x64

Version of Telegram Desktop

3.5.0

Installation source

Static binary from official website

Logs

No response

rugabunda avatar Feb 05 '22 03:02 rugabunda

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

stale[bot] avatar Aug 10 '22 03:08 stale[bot]