Forum Discussion
Edge Beta crashing as of Jan 20, 2023 after update i guess
Edge Beta is crashing after 5 to 10 minutes of opening. Started Jan 20, 2023 late. Disabled the Edge WinView2 or whatever that is but didn't help. I have Edge standard open and there are no issues. Firefox isn't crashing either. I have searched high and low but don't see anything out there. I will just use another browser for now and wait to see if things change in a couple of days.
I guess this is more of an FYI
I got this lovely message in WinDbg
seems to be a bug with old Microsoft's telemetry client accessing memory it shouldn't be hmmm.
STACK_COMMAND: ~9s; .ecxr ; kb SYMBOL_NAME: msedge+1990790 MODULE_NAME: msedge IMAGE_NAME: msedge.dll FAILURE_BUCKET_ID: NULL_POINTER_WRITE_c0000005_msedge.dll!Unknown OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 IMAGE_VERSION: 110.0.1587.17 FAILURE_ID_HASH: {c171bb6a-7522-ae2f-5ecb-19c1b53d3623} Followup: MachineOwner --------- 0:009> ExceptionAddress: 00007ff9125e2ca0 (msedge!telemetry_client::IDataFieldVisitor::IDataFieldVisitor+0x0000000001990790) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000001 Parameter[1]: 0000000000000000 Attempt to write to address 0000000000000000
126 Replies
- Goldfinger007Copper Contributor
Same here. Just started this morning. Worked fine yesterday. Microsoft Edge works fine. Problem just with Microsoft Edge Beta. Version 110.0.1587.17 (Official build) beta (64-bit). Running on Windows 11. Does not matter what tabs I am viewing or if just have home screen open. Just shuts down. Restarts fine but shuts down again. Have removed & reinstalled beta, problem is still there. Glad to see it is not just me. Thought I was having a computer problem.
Anyone know a way to go back to previous build??
Same problem on 2 different computers. My laptop & my desktop.
- Unreal4LifeCopper Contributor
Goldfinger007 I've found this website with older versions of edge beta.
https://microsoft-edge-beta.en.uptodown.com/windows/versions
But it is useless, cant get this working. The .exe autodownloads last version of edge and cant get older versions installed. Tried to disable edge autoupdate aswell but nothing to do, it continues installing last version, this is crazy.
- Unreal4LifeCopper ContributorSame FAILURE_ID_HASH: {c171bb6a-7522-ae2f-5ecb-19c1b53d3623} here.
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullPtr
Key : AV.Fault
Value: Write
Key : Analysis.CPU.mSec
Value: 984
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 10763
Key : Analysis.IO.Other.Mb
Value: 20
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 76
Key : Analysis.Init.CPU.mSec
Value: 734
Key : Analysis.Init.Elapsed.mSec
Value: 31239
Key : Analysis.Memory.CommitPeak.Mb
Value: 540
Key : Timeline.Process.Start.DeltaSec
Value: 607
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
Key : WER.Process.Version
Value: 110.0.1587.17
FILE_IN_CAB: f431fade-42d8-4895-85c0-adbf04b2f858.dmp
NTGLOBALFLAG: 0
PROCESS_BAM_CURRENT_THROTTLED: 0
PROCESS_BAM_PREVIOUS_THROTTLED: 0
APPLICATION_VERIFIER_FLAGS: 0
CONTEXT: (.ecxr)
rax=00007ffe84562ca0 rbx=0000000000000016 rcx=0000000000000016
rdx=00007ffe813002d0 rsi=00007ffe84562ca0 rdi=00007ffe8ad27d58
rip=00007ffe84562ca0 rsp=000000d47d9fe7a8 rbp=0000000000000002
r8=000000d47d9fe820 r9=000000d47d9fe828 r10=00000fffd08ac594
r11=0000000000100000 r12=0000000000000910 r13=0000000000000000
r14=000000d47d9fe801 r15=000000d47d9fe894
iopl=0 nv up ei pl zr na po cy
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010247
msedge!telemetry_client::IDataFieldVisitor::IDataFieldVisitor+0x1990790:
00007ffe`84562ca0 c704250000000037130000 mov dword ptr [0],1337h ds:00000000`00000000=????????
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffe84562ca0 (msedge!telemetry_client::IDataFieldVisitor::IDataFieldVisitor+0x0000000001990790)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000
PROCESS_NAME: msedge.exe
WRITE_ADDRESS: 0000000000000000
ERROR_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%p hace referencia a la memoria en 0x%p. La memoria no se pudo %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 0000000000000000
STACK_TEXT:
000000d4`7d9fe7a8 00007ffe`812dde3f : 000000d4`7d9fe828 00007ffe`812ddf93 00000000`00000016 00007ffe`84562ca0 : msedge!telemetry_client::IDataFieldVisitor::IDataFieldVisitor+0x1990790
000000d4`7d9fe7b0 00007ffe`812a7828 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000035 : msedge!GetHandleVerifier+0x164a3f
000000d4`7d9fe820 00007ffe`81694b08 : 00000000`00000035 000000d4`7d9fe8a0 aaaaaaaa`aaaaaaaa 00007fff`20b5c730 : msedge!GetHandleVerifier+0x12e428
000000d4`7d9fe850 00007ffe`816adb91 : 000000d4`7d9ff4d8 00007ffe`7d3def43 0000415c`048964c0 000000d4`7d9ff501 : msedge!telemetry_client::IDataFieldVisitor::operator=+0x2a138
000000d4`7d9ff4a0 00007ffe`81638069 : 000000d4`7d9ff620 0000008a`0ef5d24c 0000a722`5f641ba9 000000d4`7d9ff710 : msedge!telemetry_client::IDataFieldVisitor::operator=+0x431c1
000000d4`7d9ff4d0 00007ffe`7fbefafe : aaaaaaaa`aaaaaaaa 000000d4`7d9ff560 aaaaaaaa`00c600c4 000000d4`7d9ff620 : msedge!GetHandleVerifier+0x4bec69
000000d4`7d9ff500 00007ffe`805513a4 : 0000415c`0e519240 00000000`00000101 80000000`00000110 aaaaaaaa`aaaaaaaa : msedge!ChromeMain+0xa39dae
000000d4`7d9ff6f0 00007ffe`7dc81f08 : 00000000`0000000f 00007ffe`8ad92e00 0000415c`0f303200 00000000`0000000e : msedge!RelaunchChromeBrowserWithNewCommandLineIfNeeded+0x7a174
000000d4`7d9ff770 00007ffe`7dc7f76c : 00003c18`00255000 0000415c`18f3a630 00000000`00000000 00007ffe`7e8ff416 : msedge+0xd11f08
000000d4`7d9ff9d0 00007ffe`7dc7e41a : 000000d4`7d9ffde0 00007ffe`7e6e3b65 00000000`00000000 00000000`00000000 : msedge+0xd0f76c
000000d4`7d9ffcf0 00007ffe`7edae458 : 00003c18`002f75e0 00007ffe`7edae321 00003c18`002f75e0 00003c18`002943c0 : msedge+0xd0e41a
000000d4`7d9ffe60 00007ffe`7e6e30ee : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : msedge+0x1e3e458
000000d4`7d9ffea0 00007fff`1ec27614 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : msedge+0x17730ee
000000d4`7d9fff30 00007fff`20b226a1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
000000d4`7d9fff60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21
SYMBOL_NAME: msedge+1990790
MODULE_NAME: msedge
IMAGE_NAME: msedge.dll
STACK_COMMAND: ~11s; .ecxr ; kb
FAILURE_BUCKET_ID: NULL_POINTER_WRITE_c0000005_msedge.dll!Unknown
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 110.0.1587.17
FAILURE_ID_HASH: {c171bb6a-7522-ae2f-5ecb-19c1b53d3623}
Followup: MachineOwner
---------
0:011> .exr -1
ExceptionAddress: 00007ffe84562ca0 (msedge!telemetry_client::IDataFieldVisitor::IDataFieldVisitor+0x0000000001990790)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000 - Keelo252Copper ContributorSame problem here on the (now cursed) beta build 110.0.1587.17. I guess I'll need to switch to the stable build until this gets fixed, hopefully.
- Legion-MicrosoftCopper Contributor
I don't know what else to do. The Microsoft Edge Beta automatically crashes and closes after about 3 minutes.
No warning. No signs, nothing.
I can't work anymore. I can't surf anymore. A repair does nothing. I'm desperate.Edit: Microsoft Edge Version 110.0.1587.17 (Official build) beta (64-bit)
- Legion-MicrosoftCopper ContributorOh, and the Stabile Channel version of Microsoft Edge (replacement Beta) works fine (what else). Hope our dear MS Team fixes the bug quickly and we can all continue testing the Beta/Dev.
- ZemmicCopper ContributorBoth Edge Beta and Dev just started (jan 21) constantly crashing after a few minutes on macOS.
- vlastawCopper Contributor
I confirm. Repeated crashing on 110.0.1587.17 Beta @ Windows 11 22621.1105, Windows Feature Experience Pack 1000.22638.1000.0
- jmolleringCopper ContributorAfter I updated to Version 110.0.1587.17 (Official build) beta (64-bit), my Edge keeps crashing/closing every 10mins or so. Very annoying. Not sure what to do.
Edition Windows 11 Enterprise
Version 21H2
Installed on 11/18/2022
OS build 22000.1455
Experience Windows Feature Experience Pack 1000.22000.1455.0 - DaminousPurityCopper Contributor
Glad to now know it isn't just me that is having this problem.
Wasted 9 1/2 hours doing a full check disk, uninstalling, reinstalling, repair of the browser etc and everything online it tells you to try on every forum and now back on it is still the same.
Seems to be exactly at the 10 minute mark now.
Version 110.0.1587.17 (Official build) beta (64-bit) and I even installed all the windows updates last night and still everything crashes.
Seems to be something is unstable in the browser matrix, as if I sign out completely and just use the browser as normal, there is no crash, it's only when everything is signed in, fully syncing to the cloud or whatever Microsoft is doing. Normal Microsoft Edge is working without problems.
It's almost as if the browser isn't closed from the other side as regardless of what site I was on the "Performance" heart symbol was having a fit. I've sent all the feedback logs, even screen shots via the feedback tab, so fingers crossed someone looks at this as it's unusable at this point. - vincedu56Copper ContributorBonjour, même chose pour moi Edge Beta Windows 10.
- PhildiditCopper Contributor
Dave_Gleason_DGNorCal Same here - about ten minutes too. Is it going to be fixed?
- Shubham996633Copper Contributor
Having same from yesterday just crashing after 10 mins Dave_Gleason_DGNorCal