![]() After updating Edge to the latest version, a crash may still be observed on the first Edge launch, but not subsequent ones. If Edge still crashes, please ensure Edge is updated to the latest version and Windows is also up-to-date. If it does, please check Edge crashes because of confliction between Symantec DLP and Windows Defender Exploit Protection feature section for details. Launch Edge with -no-sandbox flag: msedge.exe -no-sandbox to see if it mitigates the issue. If you do find such event, please see Third-party module fails with Code Integrity checking section for resolution. Go to Event Viewer → Applications and Services Logs → Microsoft → Windows → Code Integrity → Operational and check if there was always an Error event matching the time when user failed to launch Edge browser and the error message is likely to be:Ĭode Integrity determined that a process (\Device\HarddiskVolumeX\Programe Files (x86)\Microsoft\Edge\Application\msedge.exe) attempted to load \Device\HarddiskVolumeX\AnyPathToAThirdPartyModule\ThirdPartyModule.dll that did not meet the Microsoft signing level requirements. 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 steps to take in order to eliminate the possibility that an Edge crash issue is caused by a third-party module. There was only one case where the crash was caused by a bug in Blink (The rendering engine of Chromium) and affected both Edge and Chrome. Some of these crashes occurred in both Edge and Chrome, while others only happened in Edge. Most of them were caused by third-party modules, resulting in Edge failing to launch. I have dealt with many Edge crash issues in my work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |