Can someone help me understand why my server crashed?

Anonymous
2023-11-13T20:12:18+00:00

EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007ffe1456deda ExceptionCode: 80131623 ExceptionFlags: 00000001 NumberParameters: 0

PROCESS_NAME:  ntdll.wrong.symbols.dll

WRONG_SYMBOLS_TIMESTAMP: 65175333

WRONG_SYMBOLS_SIZE: 1ad000

FAULTING_MODULE: 00007ffe7cfa0000 ntdll

ADDITIONAL_DEBUG_TEXT:  
You can run '.symfix; .reload' to try to fix the symbol path and load symbols. ; Followup set based on attribute [Is_ChosenCrashFollowupThread] from Frame:[0] on thread:[PSEUDO_THREAD]

STACK_TEXT:  
00000000`00000000 00000000`00000000 WRONG_SYMBOLS!WRONG_SYMBOLS+0x0

STACK_COMMAND:  ** Pseudo Context ** ManagedPseudo ** Value: ffffffff ** ; kb

BUGCHECK_CODE:  65175333

EXCEPTION_CODE_STR:  65175333

EXCEPTION_STR:  WRONG_SYMBOLS

IMAGE_NAME:  ntdll.wrong.symbols.dll

MODULE_NAME: ntdll_wrong_symbols

SYMBOL_NAME:  ntdll_wrong_symbols!651753331AD000

FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X64_6.3.9600.18217_(winblue_ltsb.160124-0053)_TIMESTAMP_230929-224403_65175333_ntdll.wrong.symbols.dll!651753331AD000

OS_VERSION:  6.3.9600.18217

BUILDLAB_STR:  winblue_ltsb

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

FAILURE_ID_HASH:  {ee300239-d39b-c705-6d1b-a5eacacde854}

Followup:     MachineOwner
Windows for business | Windows Server | Performance | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Anonymous
    2023-11-14T02:30:46+00:00

    Hello

    Thank you for posting in Microsoft Community forum.

    It seems like you’re dealing with a crash dump analysis. The error message indicates that the symbols for ntdll.wrong.symbols.dll are incorrect. This can happen if the symbol files (.pdb files) are not correctly loaded or are outdated.

    The debug text suggests a possible solution: You can run .symfix; .reload in your debugger to fix the symbol path and load symbols.

    The exception code 80131623 typically indicates a managed debugging assistant ‘CallbackOnCollectedDelegate’ has detected a problem (a delegate was garbage collected while a callback was still active).

    Please note that this is a general interpretation of the error message. The actual issue might be different based on the specifics of your application and environment. It’s recommended to look into the specific modules and code where the crash is happening for a more accurate diagnosis. If you have the source code, you might want to check the parts of the code that interact with ntdll.wrong.symbols.dll.

    Remember, always make sure your debugging tools and symbol files are up-to-date to avoid such issues.

    Best Regards,

    Wesley Li

    0 comments No comments