Tested in chrome #68.0.3432.3 and Canary #68.0.3436.0 on win 10.0 and not able to reproduce the issue.Please find the screen shots for your reference.

@karaziox: Could you please let me know if i have missed anything and if possible,Please create new profile without extensions and apps.Re-check once and let us know the observations of the issue which would help us to triage the issue further.

Thanks in Advance!

Deleted: 844893.PNG 105 KB

	844893.PNG 105 KB View Download

Issue happened again 2-3 times after the report. This time it was with only Google Music open. I've disabled all extensions and will check if it happen again today. This doesn't seem related with the tabs open or any kind of interaction. Sometime it crashed when I was interacting with the browser, sometime it crashed after it had been minutes since my last interaction.

I'll keep you posted if it happen again

Thanks

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I haven't had a crash yet after disabling all extensions. I'm gradually enabling them back in the hope I'll narrow down which one is the cause. Its taking some time as I need a couple hours to be sure its stable. I assume you will want the details as I don't think an extension is supposed to be able to cause a whole-browser crash?

Also, do we know why the crash reporter wasn't picking these up? It would have made narrowing it down easier.

Thanks

Similar issue. I don't have crash dumps but this has happened twice over the last few days. I'd leave by computer and come back and Chrome has exited.

Windows event viewer logs:

Faulting application name: chrome.exe, version: 68.0.3432.3, time stamp: 0x5afcfe82
Faulting module name: ntdll.dll, version: 10.0.17134.1, time stamp: 0x207580e2
Exception code: 0xc0000374
Fault offset: 0x00000000000f4eeb
Faulting process id: 0x3064
Faulting application start time: 0x01d3f242ecc9a53f
Faulting application path: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 45b32735-03ad-4212-8ecc-c59b5f54f5d9
Faulting package full name: 
Faulting package-relative application ID: 



Faulting application name: chrome.exe, version: 68.0.3432.3, time stamp: 0x5afcfe82
Faulting module name: ntdll.dll, version: 10.0.17134.1, time stamp: 0x207580e2
Exception code: 0xc0000374
Fault offset: 0x00000000000f4eeb
Faulting process id: 0x898
Faulting application start time: 0x01d3f1fcc2521c0c
Faulting application path: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: d9ab5833-4e59-4c53-bb73-ed2b5636b9d8
Faulting package full name: 
Faulting package-relative application ID: 

@Reporter: Can you please check the same in latest canary #68.0.3439.0 and update the behavior here?

Thanks!!

Possibly related?

https://bugs.chromium.org/p/chromium/issues/detail?id=844004

As noted there, I have a few of these in my local Windows event log in recent days.

Faulting application name: chrome.exe, version: 68.0.3436.0, time stamp: 0x5b00f6b9
Faulting module name: ntdll.dll, version: 10.0.17134.1, time stamp: 0x207580e2
Exception code: 0xc0000374
Fault offset: 0x00000000000f4eeb
Faulting process id: 0x554
Faulting application start time: 0x01d3f0269459915c
Faulting application path: C:\Users\RobRich\AppData\Local\Chromium\Application\chrome.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: c92e65ad-9685-4c08-a0c1-5bca4f32c76a
Faulting package full name: 
Faulting package-relative application ID: 

I did not dig too deep, but I could not determine a basic reproducer.

I have not (yet?) seen it with my latest local v68.0.3440.0 build today.

Hi guys, just had the crash again while I was gradually reenabling extensions. This happened after I reenabled "goo.gl URL Shortener (Unofficial)" and "Tampermonkey". My bet is currently either on random luck or Tampermonkey. I've disabled the goo.gl one for now to see if it happen again. I'll try running Canary on that same config also, to see if 3439 reproduces it too. Currently I'm still on 68.0.3438.3

The Tampermonkey is a fresh install, no userscripts.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Requesting someone from Internals>CrashReporting team to take a look at this issue, since this issue isn't reproducible from TE end.

I've not had any crash since the previous report, either on dev or canary. Both of them had been running continuously since the last report. I've updated them today and will continue to monitor this in case I see it again. I'll let you decide what to do with the bug, as we can't seem to find a trigger or reproduce it with any consistency.

Thanks

As per comment #10 adding TE-NeedsTriageHelp label

If this involves an HP Spectre or Lenovo Yoga, see  issue 806977  which is causing similar hard crashes with no crash report for certain commerce sites.

That problem has been traced to the Windows 1803 monthly updates & bad USB3 drivers.

I was on 1803 indeed, but this is a custom built computer so not an HP or Lenovo brand. It might indeed have been related to commerce sites, although I didn't notice it. I've visited the websites from the issue you linked without reproducing the crash, but I also haven't had any crashes since my last report on May 25. Also, I am now on 69.0.3452.0.

On the hardware side I'm using an Intel i7 8700k on an Asus z370 motherboard. I'm using the Windows Update drivers and I'm on insider slow lane. The hardware/windows version/symptoms might be close enough to be a match on the issue so... I'm not sure.

karaz@ - What's the status on tampermonkey?  Was this the culprit?

When you were crashing earlier did you test from incognito?

If it crashes again, inspect the USB 3 eXtensible host controller and 
root hub 3.0 driver dates and compare them to healthy (now) state - like 
10.0.17134.1 and 10.0.17134.112 respectively.

I haven't had a crash yet, tried a few other combinations of extensions but nothing conclusive. I've fallen back to thinking it was probably more random luck than extension related.

I've checked the issue and forum ticket you linked. I am indeed on versions 10.0.17134.1 and 10.0.17134.112 and I've checked the windows update history. I've had the KB4284835 you mentioned since June 12, but I noticed I also had an insider build update (or was it the release version for 1803? UI is not quite clear, it's listed under Feature Updates) on May 26, which is just after the last crash. It seems that feature update might have brought the updated drivers and fixed my problem. Or I just avoided the websites triggering the issue until the KB4284835 hit.

At this point the issue feel similar enough to the one you linked that I'm ok closing this one as duplicate. Especially since I haven't been able to reproduce in close to a month now.