12 comments :

Lai Jiang said...

Crashes on Windows 10 64bit...

Nyte said...

Same issue here. Crash on Win 10 (64).

EdoFlo said...

Same, Windows 10 64-bit

Jacob Groß said...

Start Chrome with "--no-experiments",
Go to: chrome://flags/#enable-service-worker-servicification and disable it. Worked for me.

Torsin2000 said...

So, after the update every-time I opened chrome it would crash (ended all procs and restarting didn't fix it). Adding the --no-experiments flag did not fix it either. I started wondering why it would load up, load the new-tab start page and then die. I checked the event log and found a standard 1000 error mentioning ntdll.dll, when I looked at some of the previous instances of chrome crashing off of ntdll.dll they mentioned specific websites. Well all I was doing was loading the new-tab start page, so why should it not work, anyway I decided to right-click the shortcut on the taskbar and have it load up a recent website...and it loaded up without issue. This led me to believe the new-tab page was broken in some way, so off to settings and reset to default theme (was using 'Unknown Space'). What's interesting is that the background image has been not loading properly for a little while now, it would load down to half-way then white the rest of the screen. Anyway hope this helps, error for what it is worth:

Log Name: Application
Source: Application Error
Date: 3/10/2018 1:31:59 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Atium
Description:
Faulting application name: chrome.exe, version: 66.0.3359.22, time stamp: 0x5aa214ed
Faulting module name: ntdll.dll, version: 10.0.16299.248, time stamp: 0xeffc9126
Exception code: 0xc0000374
Fault offset: 0x00000000000f87bb
Faulting process id: 0x2f64
Faulting application start time: 0x01d3b852a28f4739
Faulting application path: C:\Program Files (x86)\Google\Chrome Dev\Application\chrome.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 29753615-0bd3-4442-bdcb-1237f25e38f8
Faulting package full name:
Faulting package-relative application ID:



And the WER event:

Log Name: Application
Source: Windows Error Reporting
Date: 3/10/2018 1:32:01 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Atium
Description:
Fault bucket 1600184315365293349, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: chrome.exe
P2: 66.0.3359.22
P3: 5aa214ed
P4: StackHash_e942
P5: 10.0.16299.248
P6: effc9126
P7: c0000374
P8: PCH_04_FROM_ntdll+0x00000000000A09D4
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBFA3.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC283.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC291.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC2A1.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_chrome.exe_6d8edbd948a5a411691e7ee8c353a654f7d4a0_6792fe9b_08f4c83e

Analysis symbol:
Rechecking for solution: 0
Report Id: 29753615-0bd3-4442-bdcb-1237f25e38f8
Report Status: 268435456
Hashed bucket: be4e4d5a2205a84c2634ff281c7ffd25

Ram said...

"--no-experiments" worked once, then wouldn't open again. Also tried opening a website from a desktop shortcut as mentioned by Torsin and it still crashes.

gilmour said...

Same problem here with crashing on win10 64bit

I can get it to work everytime by setting compatibility mode to run as windows 7.
Unfortunately I have to set compatibility mode each time I restart chrome as the setting doesn't hold.

Mark T. Kennedy said...

numerous bug reports about it already. one reported that launching it in windows 7 coampatibility mode works. it does. seems a tad slower, though.

Asger Nørgaard said...

Having the same crashes on startup of Chrome. Windows 10 64bit. Setting to Windows 7 compatibility mode resolves the issue.

Mark T. Kennedy said...

windows 7 or windows 8 compatibility mode on windows 10 (64 bit) is *painfully* slow. i had to install a prod chrome release. over the last decade(?), the dev channel has been one of the most stable channels i've used. it's gone off the deep end lately.

Chris Murphy said...

Chrome 65 is forcing all sites to use https, even internal sites. This is unacceptable. What do I need to do to fix this?

Bin Zhao said...
This comment has been removed by the author.