Home

MS Edge Beta High CPU consumption and crash

%3CLINGO-SUB%20id%3D%22lingo-sub-829066%22%20slang%3D%22en-US%22%3EMS%20Edge%20Beta%20High%20CPU%20consumption%20and%20crash%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-829066%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Folks%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20just%20tried%20to%20install%20MS%20Edge%20Beta%20on%20one%20of%20my%20RDS%202016%20Servers.%20Right%20after%20starting%20the%20browser%2C%20CPU%20consumption%20goes%20crazy%20(like%20100%25)%20and%20crashes%20after%20a%20while.%3C%2FP%3E%3CP%3EEventviewer%20shows%20following%20error%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFaulting%20application%20name%3A%20msedge.exe%2C%20version%3A%2077.0.235.15%2C%20time%20stamp%3A%200x5d63324c%3CBR%20%2F%3EFaulting%20module%20name%3A%20ntdll.dll%2C%20version%3A%2010.0.14393.2969%2C%20time%20stamp%3A%200x5ccd148a%3CBR%20%2F%3EException%20code%3A%200xc0000005%3CBR%20%2F%3EFault%20offset%3A%200x0000000000065553%3CBR%20%2F%3EFaulting%20process%20id%3A%200x24f0%3CBR%20%2F%3EFaulting%20application%20start%20time%3A%200x01d55e6c48f02cd5%3CBR%20%2F%3EFaulting%20application%20path%3A%20C%3A%5CProgram%20Files%20(x86)%5CMicrosoft%5CEdge%20Beta%5CApplication%5Cmsedge.exe%3CBR%20%2F%3EFaulting%20module%20path%3A%20C%3A%5CWindows%5CSYSTEM32%5Cntdll.dll%3CBR%20%2F%3EReport%20Id%3A%20a0a28a07-e398-4682-8df7-528df3ff9044%3CBR%20%2F%3EFaulting%20package%20full%20name%3A%3CBR%20%2F%3EFaulting%20package-relative%20application%20ID%3A%3C%2FP%3E%3CP%3EThe%20OS%20is%20Windows%20Server%202016%2014393.3025%3C%2FP%3E%3CP%3EAny%20ideas%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-831979%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Edge%20Beta%20High%20CPU%20consumption%20and%20crash%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-831979%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F119592%22%20target%3D%22_blank%22%3E%40Ajni%20Kurtaj%3C%2FA%3E%2C%20we%20have%20seen%20a%20number%20of%20crashes%20on%20that%20build%2C%20and%20the%20number%20one%20issue%20we%20are%20tracking%20is%20a%20bug%20with%20the%20graphics%20driver.%26nbsp%3B%20Would%20you%20mind%20sharing%20you%20graphics%20card%20model%20and%20driver%20information%20with%20us%3F%26nbsp%3B%20If%20you%20are%20running%20an%20Nvidia%20card%2C%20and%20are%20not%20running%20the%20latest%20certified%20driver%2C%20could%20you%20upgrade%20you%20driver%20and%20see%20if%20that%20makes%20the%20problem%20go%20away%3F%26nbsp%3B%20Thanks%20-%20Elliot%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-831980%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Edge%20Beta%20High%20CPU%20consumption%20and%20crash%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-831980%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F239638%22%20target%3D%22_blank%22%3E%40Elliot%20Kirk%3C%2FA%3E%26nbsp%3BThe%20machine%20is%20a%20virtual%20Windows%20Server%202016%20without%20a%20graphic%20card%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-831982%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Edge%20Beta%20High%20CPU%20consumption%20and%20crash%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-831982%22%20slang%3D%22en-US%22%3E%3CP%3E*Edited*%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F119592%22%20target%3D%22_blank%22%3E%40Ajni%20Kurtaj%3C%2FA%3E!%26nbsp%3B%20That%20eliminates%20the%20top%20hitting%20bug.%26nbsp%3B%20Do%20you%20see%20any%20crashes%20in%20your%20event%20viewer%20record%3F%3C%2FP%3E%0A%3CP%3EHere%20is%20a%20similar%20crash%20from%20a%20VM%20here%3A%3C%2FP%3E%0A%3CP%3EFault%20bucket%202299843119412377231%2C%20type%204%3C%2FP%3E%0A%3CP%3EEvent%20Name%3A%20APPCRASH%3C%2FP%3E%0A%3CP%3EResponse%3A%20Not%20available%3C%2FP%3E%0A%3CP%3ECab%20Id%3A%201173160400849985183%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20Cab%20ID%20will%20allow%20us%20to%20hopefully%20find%20the%20crash%20data%20and%20allow%20us%20to%20debug%20the%20failure.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-832590%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Edge%20Beta%20High%20CPU%20consumption%20and%20crash%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-832590%22%20slang%3D%22en-US%22%3E%3CP%3E*UPDATE*%3C%2FP%3E%3CP%3EI%20saw%20that%20in%20the%20report%20there%20were%20some%20citrix%20DLLs%2C%20so%20I%20excluded%20MS%20Edge%20from%20Citrix%20Hook%20(the%20environment%20ist%20Citrix%20XenApp).%20Now%20it%20works!!!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHKEY_LOCAL_MACHINE%5CSOFTWARE%5CCitrix%5CCtxHook%3CBR%20%2F%3EREG_SZ%20%22ExcludedImageNames%22%3CBR%20%2F%3EValue%20%22msedge.exe%2Cnacl64.exe%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F239638%22%20target%3D%22_blank%22%3E%40Elliot%20Kirk%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20got%20an%20event%20entry%20like%20yours%2C%20but%20the%20cab%20ID%20is%200%3C%2FP%3E%3CP%3EI%20could%20give%20you%20this%20report%20if%20you%20want%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFault%20bucket%20%2C%20type%200%3CBR%20%2F%3EEvent%20Name%3A%20APPCRASH%3CBR%20%2F%3EResponse%3A%20Not%20available%3CBR%20%2F%3ECab%20Id%3A%200%3C%2FP%3E%3CP%3EProblem%20signature%3A%3CBR%20%2F%3EP1%3A%20msedge.exe%3CBR%20%2F%3EP2%3A%2077.0.235.15%3CBR%20%2F%3EP3%3A%205d63324c%3CBR%20%2F%3EP4%3A%20ntdll.dll%3CBR%20%2F%3EP5%3A%2010.0.14393.2969%3CBR%20%2F%3EP6%3A%205ccd148a%3CBR%20%2F%3EP7%3A%20c0000005%3CBR%20%2F%3EP8%3A%200000000000065553%3CBR%20%2F%3EP9%3A%3CBR%20%2F%3EP10%3A%3C%2FP%3E%3CP%3EAttached%20files%3A%3C%2FP%3E%3CP%3EThese%20files%20may%20be%20available%20here%3A%3CBR%20%2F%3EC%3A%5CProgramData%5CMicrosoft%5CWindows%5CWER%5CReportQueue%5CAppCrash_msedge.exe_393e7f92beac25963aca3073acfdfd8bfb62c8_adb6d895_1bafbe26%3C%2FP%3E%3CP%3EAnalysis%20symbol%3A%3CBR%20%2F%3ERechecking%20for%20solution%3A%200%3CBR%20%2F%3EReport%20Id%3A%20fd3b37ed-b5b4-40e1-af8f-eb2159f9d3f7%3CBR%20%2F%3EReport%20Status%3A%204%3CBR%20%2F%3EHashed%20bucket%3A%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-833608%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Edge%20Beta%20High%20CPU%20consumption%20and%20crash%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-833608%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F119592%22%20target%3D%22_blank%22%3E%40Ajni%20Kurtaj%3C%2FA%3E%2C%20I%20will%20talk%20with%20our%20reliability%20team%20tomorrow%2C%20when%20I%20get%20back%20to%20work%2C%20but%20I%20am%20worried%20that%20ID%200%20means%20that%20the%20crash%20dump%20was%20not%20uploaded%20to%20our%20servers%2C%20and%20therefore%20we%20may%20be%20stuck.%26nbsp%3B%20I%20will%20follow%20up%20with%20you%20tomorrow%20afternoon.%26nbsp%3B%20Thanks%20-%20Elliot%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-833701%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Edge%20Beta%20High%20CPU%20consumption%20and%20crash%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-833701%22%20slang%3D%22en-US%22%3E%3CP%3ELike%20many%20more%2C%20also%20experiencing%20crashes%2C%20I%20have%20not%20kept%20close%20tabs%20on%20CPU%20usage%20tho.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERunning%20NVIDIA%20drivers%20but%20not%20the%20latest%20which%20in%20a%20way%20does%20not%20matter%20since%20the%20drive%20of%20the%20card%20itself%20is%20never%20updated%20being%20it's%20a%20GT640%20thus%20running%20current%20or%20not%20current%20drivers%20should%20not%20affect%20Windows%2FEdge%2FGraphic%20but%20I%20may%20update%20the%20drivers.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20crash%20itself%20will%20eventually%20happen%20during%20usage%20and%20usually%20at%20the%20very%20instant%20I%20do%20a%20click%20on%20a%20link%20or%20open%20a%20new%20tab%20via%20middle%20click%20but%20no%20matter%20what%20the%20crashes%20happens%20at%20clicking%20time.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20crashes%20are%20also%20problematic%20as%20they%20are%20not%20causing%20a%20simple%20failure%20of%20Edge%2C%20the%20screen%20goes%20dark%20but%20does%20not%20close%2C%20impossible%20to%20ever%20see%20the%20desktop%20again%20which%20results%20a%20force%20reboot%20of%20the%20computer%20to%20get%20out%20of%20this%20mode%20which%20is%20very%20annoying%20on%20my%20old%20system%20(long%20reboots).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-833725%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Edge%20Beta%20High%20CPU%20consumption%20and%20crash%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-833725%22%20slang%3D%22en-US%22%3ETo%20completely%20rule%20out%20possible%20graphic%20card%20or%20its%20driver%20incompatibility%20try%3A%3CBR%20%2F%3E1.%20remove%20discrete%20Nvidia%20card%20and%20run%20Edge%20for%20few%20days%20on%20on-board%20GPU%20or%20IGPU.%20(assuming%20your%20CPU%20got%20one).%3CBR%20%2F%3E2.%20turn%20off%20hardware%20acceleration%20from%20the%20Edge%20insider%20browser%20settings.%3CBR%20%2F%3E%3CBR%20%2F%3Ebtw%20what's%20your%20OS%20and%20version%3F%201%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-834528%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Edge%20Beta%20High%20CPU%20consumption%20and%20crash%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-834528%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F239638%22%20target%3D%22_blank%22%3E%40Elliot%20Kirk%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethe%20problem%20is%20solved%2C%20it%20was%20a%20Citrix%20Hook%20problem%2C%20I%20posted%20an%20update%20in%20my%20last%20comment%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-835337%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Edge%20Beta%20High%20CPU%20consumption%20and%20crash%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-835337%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F119592%22%20target%3D%22_blank%22%3E%40Ajni%20Kurtaj%3C%2FA%3E%2C%20glad%20you%20were%20able%20to%20solve%20this%20issue.%26nbsp%3B%20Thank%20you%20for%20taking%20the%20time%20to%20report%20it.%26nbsp%3B%20-%20Elliot%3C%2FP%3E%3C%2FLINGO-BODY%3E
Ajni Kurtaj
Occasional Contributor

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?

9 Replies

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

Hi @Elliot Kirk The machine is a virtual Windows Server 2016 without a graphic card

*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.

*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, I will talk with our reliability team tomorrow, when I get back to work, but I am worried that ID 0 means that the crash dump was not uploaded to our servers, and therefore we may be stuck.  I will follow up with you tomorrow afternoon.  Thanks - Elliot

Like many more, also experiencing crashes, I have not kept close tabs on CPU usage tho.

 

Running NVIDIA drivers but not the latest which in a way does not matter since the drive of the card itself is never updated being it's a GT640 thus running current or not current drivers should not affect Windows/Edge/Graphic but I may update the drivers.

 

The crash itself will eventually happen during usage and usually at the very instant I do a click on a link or open a new tab via middle click but no matter what the crashes happens at clicking time.

 

The crashes are also problematic as they are not causing a simple failure of Edge, the screen goes dark but does not close, impossible to ever see the desktop again which results a force reboot of the computer to get out of this mode which is very annoying on my old system (long reboots).

To completely rule out possible graphic card or its driver incompatibility try:
1. remove discrete Nvidia card and run Edge for few days on on-board GPU or IGPU. (assuming your CPU got one).
2. turn off hardware acceleration from the Edge insider browser settings.

btw what's your OS and version? 1

Hi @Elliot Kirk 

the problem is solved, it was a Citrix Hook problem, I posted an update in my last comment

Hi @Ajni Kurtaj, glad you were able to solve this issue.  Thank you for taking the time to report it.  - Elliot

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
46 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
29 Replies