Step 2: Edge crash issue troubleshooting workflowįollow the steps below will help you to rule out most common Edge crash issues. In this case, Citrix and Forcepoint components are loaded. Go to the Process tab and sort the module list by Company, you will easily see how many third-party (non-Microsoft) modules are loaded in Edge. Now Process Monitor only displays the event of the target Edge process: 8956, let's scroll down to the bottom and double click the last event. Now let's target at the most long living Edge process: 8956 in this case which is the main Edge process, right click it and click on Add process to Include filter. Werfault.exe's command line tells that the crashing process ID is 9108 which points to the parent Edge process (the GPU process of Edge in this case) One or more werfault.exe ( Windows Error Reporting process) appear as sub-process(es) of Edge process(es). Now press Ctrl+T to open the Process Tree and you would probably see something like following image shows:
Wait for about 10~15 seconds, if Edge still does not start or just hangs there, let's go back to Process Monitor and press Ctrl+E to stop capturing. Reproduce the crash issue where Edge fails to launch or Edge just hangs after launching. Proceed to next step when you see it generating massive events. Start Process Monitor (requires administrator permission), it will automatically start capturing. Another way is to check the edge://conflicts page, but this requires Edge starting successfully which is not suitable for an Edge crashing at launch issue. I always use Process Monitor to check this. The first thing is to check if Edge loads a third-party module. Step 1: Check if Edge loads a third-party module I am writing this article to summarize the actions to take to rule out an Edge crash issue that is caused by a third-party module. I have only seen one Edge/Chrome crash case which was caused by a bug of Blink (The rendering engine of Chromium).
Some of them happened in both Edge and Chrome, some of them only happened in Edge. Most of them were caused by third-party modules where Edge failed to launch at the beginning. I handled many Edge crash issues in my work.
0 kommentar(er)
