Forum Discussion
MS Edge Beta High CPU consumption and crash
- Aug 31, 2019
*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: 0Problem 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_1bafbe26Analysis symbol:
Rechecking for solution: 0
Report Id: fd3b37ed-b5b4-40e1-af8f-eb2159f9d3f7
Report Status: 4
Hashed bucket:
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.
- Ajni KurtajAug 31, 2019Copper Contributor
*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: 0Problem 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_1bafbe26Analysis symbol:
Rechecking for solution: 0
Report Id: fd3b37ed-b5b4-40e1-af8f-eb2159f9d3f7
Report Status: 4
Hashed bucket:- Thomas_ITSep 08, 2021Copper Contributoryou saved me a lot of time ! thx!! 🙂
- Mica64Feb 06, 2020Copper Contributor
- Ajni KurtajFeb 12, 2020Copper Contributor
Mica64 That's nice to hear 🙂
- Elliot KirkSep 02, 2019Former Employee
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
- Ajni KurtajSep 03, 2019Copper Contributor
Hi Elliot Kirk
the problem is solved, it was a Citrix Hook problem, I posted an update in my last comment