Forum Discussion
Dev channel update to 81.0.389.2 is live
Having issue with opening web pages. Every time I open a web page I it just clocks for a minute then I get the "This page is having a problem" with an error code STATUS_ACCESS_VIOLATION. I noticed this issue being reported in the previous release discussion thread but was hoping it was going to be fixed in this thread.
Did a little more testing and found that any site I have that tries to open in IE11 will actually open in Edge Dev. I also looked at my event logs and found some errors. They all appear to be similar, so I proved the information below. I hope you find this information helpful.
Event Viewer Log:
Faulting application name: msedge.exe, version: 81.0.389.2, time stamp: 0x5e1cf243
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000201b02
Faulting process id: 0x360a4
Faulting application start time: 0x01d5ce31cb53ce32
Faulting application path: C:\Program Files (x86)\Microsoft\Edge Dev\Application\msedge.exe
Faulting module path: unknown
Report Id: 640f9920-822b-4ee8-8b70-afa3d3602947
Faulting package full name:
Faulting package-relative application ID:
cc: Steven Sanders
Jeffrey Thorpe it seems to be a sort of incompatibility with Forcepoint One Endpoint software. I have the same issue and in fact my organization is using it. Stopping FP services doesn't help, as it didn't help other people having the same issue. However, the problem may be related to QIP.sys driver (which is part of Forcepoint): if you manage to stop it, Edge will eventually work again. In alternative, for me running Edge with parameter "--no-sandbox" fixes it.
Cc: josh_bodner
samuele2 , thanks for the tip. I added the no sandbox parameter to my shortcut and it Edge Dev is working again. I do get a little warning about the unsupported command line flag but I can live with that until there is a fix for the root cause.
- Also you can find the conflicting drivers in Edge in here: edge://conflicts/
- Are you using Forcepoint/Websense in the organization?
- Thanks for the quick reply. I know we did at one time and I used to see "report spam to spam@forcepoint" in our external emails but I don't see that any more. I will need ask out IT Security to see if it is currently being used unless there is any way for me to tell.
I take it that this is a known issue with Forcepoint/Websense that started with 831. If so, is it going to be resolved in the next release?- I'm not really sure, that's something josh_bodner would need to answer 🙂
