Forum Discussion

josh_bodner's avatar
josh_bodner
Former Employee
Jan 08, 2020

Dev channel update to 81.0.381.0 is live

Welcome to the new year!  Today we’re releasing build 81.0.381.0 to the Dev Channel, which as you can see is the first new build from major version 81.  We haven’t been completely asleep during the h...
HotCakeX's avatar
HotCakeX
MVP
Jan 09, 2020
Spoiler
C-los wrote:

I'm also receiving STATUS_ACCESS_VIOLATION. From Event Viewer, I see the following:

 

Faulting application name: msedge.exe, version: 81.0.381.0, time stamp: 0x5e0eac60
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000001d7fe2
Faulting process id: 0x4630
Faulting application start time: 0x01d5c702a60d0ed2
Faulting application path: C:\Program Files (x86)\Microsoft\Edge Dev\Application\msedge.exe
Faulting module path: unknown
Report Id: 001aab9f-8642-4513-a4da-d6e0fcdc29bc
Faulting package full name:
Faulting package-relative application ID:

 

HiC-los 

It could be related to DEP, not 100% sure

https://serverfault.com/questions/130716/if-dep-has-stopped-an-app-is-there-a-possibility-to-see-this-events-in-a-log

 

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc738483(v=ws.10)?redirectedfrom=MSDN

 

You can try turning it off to see if it changes anything

https://www.minitool.com/data-recovery/dep-data-execution-prevention-windows-10.html

 

 

 

David Hurst's avatar
David Hurst
Copper Contributor
Jan 09, 2020

HotCakeX I tried turning off DEP following the instructions in the links you provided.  It did not fix the issues I am seeing.  Thanks for the response and information,