Issues with Microsoft Edge crashing for 4-5 users Version 123.0.2420.81 (Official build) (64-bit) - msedge_elf.dll missing.

Question

Hi Everyone,

A few members of our team have been experiencing intermittent Edge crashes on their PC. It started happening around March 24th. We performed quite few troubleshooting steps to try to narrow down the issue:

1. Ensure the users Windows, Dell updates (Dell laptop), and any other relevant updates are complete..
2. Checked our antivirus dashboard to see if any Edge services are getting blocked (checked msedge_elf.dll as we saw this is in the dump files, but I'll go into this later).
3. Cleared the browser cache and reset back to factory defaults.
4. Repaired the Edge browser in Programs and Features.
5. Performed an SFC /scannow and DISM health check to see if any OS issues - none.
6. Internet tests - good
7. There has been high memory usage on most of the machine averaging above 75% (mostly from browsers and Teams) - 16 GM of RAM.
8. Ran the MS Malicious tool to see if it detects any issues - none.

Doing all this, some users are still running issues, so I have checked the dump log's location and find that a lot of these users are getting dump files at the same time the browser is crashing. I had the users test out Chrome to isolate the issue, but they are experiencing the same crashes in Chrome as well with similar dump files indicating the msedge_elf.dll is missing (chrome_elf.dll for Chrome). However, when I go to the applications folder, I can see the msedge_elf.dll file so why is Windows complaining that it does not exist or there is an issue with that file? Has anyone else experienced this issue?

Location: C:\Users<username>\AppData\Local\Microsoft\Edge\User Data\Crashpad\reports

Dump file below:

0:036> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************


KEY_VALUES_STRING: 1

    Key  : Analysis.Elapsed.mSec
    Value: 1557

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

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

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

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

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

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

    Key  : Failure.Bucket
    Value: APPLICATION_FAULT_517a7ed_msedge_elf.dll!crash_reporter::DumpWithoutCrashing

    Key  : Failure.Hash
    Value: {6d8d74dd-b055-2a68-3b16-135f8b24a2d2}

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

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

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1

    Key  : WER.Process.Version
    Value: 123.0.2420.81


FILE_IN_CAB:  5f357bf2-7792-46ca-97ae-e089f186ae48.dmp

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

CONTEXT:  (.ecxr)
rax=0000003f66bff820 rbx=aaaaaaaaaaaaaaaa rcx=0000003f66bff820
rdx=00000000000000ca rsi=0000003f66bff820 rdi=0000003f66bffd70
rip=00007ffdcb956267 rsp=0000003f66bff800 rbp=0000000000000000
 r8=00000000000000b0  r9=00000000000000c0 r10=00007ffdcb670000
r11=00007ffdcb86cd9b r12=0000000000000000 r13=0000000000000000
r14=0000003f66bffe10 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000202
msedge_elf!crash_reporter::DumpWithoutCrashing+0x37:
00007ffd`cb956267 4889f1          mov     rcx,rsi
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ffdcb956267 (msedge_elf!crash_reporter::DumpWithoutCrashing+0x0000000000000037)
   ExceptionCode: 0517a7ed
  ExceptionFlags: 00000000
NumberParameters: 0

PROCESS_NAME:  msedge.exe

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

EXCEPTION_CODE_STR:  517a7ed

STACK_TEXT:  
0000003f`66bff800 00007ffd`cb955b83     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : msedge_elf!crash_reporter::DumpWithoutCrashing+0x37
0000003f`66bffd10 00007ffe`3cc0257d     : 00000000`00000030 0000003f`66bffdd0 00000000`00000030 00000000`00000000 : msedge_elf!crash_reporter::internal::DumpProcessForHungInputThread+0x133
0000003f`66bffdc0 00007ff7`8fe98d72     : 00000000`00000000 00007ffd`cb955a50 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x1d
0000003f`66bffdf0 00007ffe`3e84aa58     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : msedge_exe!TargetBaseThreadInitThunk+0x40
0000003f`66bffe80 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x28


SYMBOL_NAME:  msedge_elf!crash_reporter::DumpWithoutCrashing+37

MODULE_NAME: msedge_elf

IMAGE_NAME:  msedge_elf.dll

STACK_COMMAND:  ~36s; .ecxr ; kb

FAILURE_BUCKET_ID:  APPLICATION_FAULT_517a7ed_msedge_elf.dll!crash_reporter::DumpWithoutCrashing

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  123.0.2420.81

FAILURE_ID_HASH:  {6d8d74dd-b055-2a68-3b16-135f8b24a2d2}

Followup:     MachineOwner
---------

Thanks for your help!

Answer 1

Open Command Prompt as administrator:

Type the following command and press Enter: sfc /scannow

If the SFC scan doesn't fix the issue, you can try a DISM :

Open Command Prompt as administrator:

Type the following command and press Enter: DISM /Online /Cleanup-Image /RestoreHealth

Uninstall and reinstall Edge:

https://www.microsoft.com/en-us/edge

Answer 2

Hi @Shayn Bennett,

Based on your previous description and the latest description, I suspect that Edge may be taking up too much memory, which may cause system resources to be exhausted, causing the browser to become unresponsive or crash. But you have tried some basic fix Troubleshooting but that didn't fix the issue either. So, I suggest you use Windows Event Viewer and Process Monitor to capture relevant logs to more accurately locate the problem on your device, which will take more time, we recommend that you open a ticket to continue tracking this problem. You can click this link: https://developer.microsoft.com/en-us/microsoft-edge/support/?form=MA13LH and select "Support for business" to open a ticket.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Best regards,

Jinxin Wang