Forum Discussion

Ajni Kurtaj's avatar
Ajni Kurtaj
Copper Contributor
Aug 29, 2019

MS Edge Beta High CPU consumption and crash

Hi Folks

 

I just tried to install MS Edge Beta on one of my RDS 2016 Servers. Right after starting the browser, CPU consumption goes crazy (like 100%) and crashes after a while.

Eventviewer shows following error:

 

Faulting application name: msedge.exe, version: 77.0.235.15, time stamp: 0x5d63324c
Faulting module name: ntdll.dll, version: 10.0.14393.2969, time stamp: 0x5ccd148a
Exception code: 0xc0000005
Fault offset: 0x0000000000065553
Faulting process id: 0x24f0
Faulting application start time: 0x01d55e6c48f02cd5
Faulting application path: C:\Program Files (x86)\Microsoft\Edge Beta\Application\msedge.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: a0a28a07-e398-4682-8df7-528df3ff9044
Faulting package full name:
Faulting package-relative application ID:

The OS is Windows Server 2016 14393.3025

Any ideas?

  • *UPDATE*

    I saw that in the report there were some citrix DLLs, so I excluded MS Edge from Citrix Hook (the environment ist Citrix XenApp). Now it works!!!

     

    HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\CtxHook
    REG_SZ "ExcludedImageNames"
    Value "msedge.exe,nacl64.exe"

     

    Hi Elliot Kirk 

    I got an event entry like yours, but the cab ID is 0

    I could give you this report if you want?

     

    Fault bucket , type 0
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: msedge.exe
    P2: 77.0.235.15
    P3: 5d63324c
    P4: ntdll.dll
    P5: 10.0.14393.2969
    P6: 5ccd148a
    P7: c0000005
    P8: 0000000000065553
    P9:
    P10:

    Attached files:

    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_msedge.exe_393e7f92beac25963aca3073acfdfd8bfb62c8_adb6d895_1bafbe26

    Analysis symbol:
    Rechecking for solution: 0
    Report Id: fd3b37ed-b5b4-40e1-af8f-eb2159f9d3f7
    Report Status: 4
    Hashed bucket:

  • Hi Ajni Kurtaj, we have seen a number of crashes on that build, and the number one issue we are tracking is a bug with the graphics driver.  Would you mind sharing you graphics card model and driver information with us?  If you are running an Nvidia card, and are not running the latest certified driver, could you upgrade you driver and see if that makes the problem go away?  Thanks - Elliot

      • Elliot Kirk's avatar
        Elliot Kirk
        Icon for Microsoft rankMicrosoft

        *Edited* 

        Thanks, Ajni Kurtaj!  That eliminates the top hitting bug.  Do you see any crashes in your event viewer record?

        Here is a similar crash from a VM here:

        Fault bucket 2299843119412377231, type 4

        Event Name: APPCRASH

        Response: Not available

        Cab Id: 1173160400849985183

         

        The Cab ID will allow us to hopefully find the crash data and allow us to debug the failure.

Resources