Would you provide a more concrete repro step?

Please attach the crash id from chrome://crashes as well for further debugging.

Giving the output of chrome://conflicts/ from the crashing machine will be very helpful too.

Hello Guys,

At the following link you will find the requested information in a zip file. All Crash IDs are also located there. 

Unfortunately for the repro steps thats all there is to it. Chrome is crashing on start up. 

https://drive.google.com/open?id=0B9BQIK7d0CYNZ0pLRWs5RHptcDA

I still suspect one of the many extensions causing the problem. While in safe mode you can disable all extensions and verify whether the problem persists.

The problem does not persist in safe mode. The browser has been run with extensions disabled but problem persists.

When Chrome is run with extensions disabled, are the DLLs still loaded in to the main browser process ? 

Any advice on further identifying the offending extension.

Extensions are not loaded if disabled. If disabling them doesn't help. We should assume they are not the culprit. Next please navigate to chrome://plugins and disable everything there.

It appears that the crash can be eliminated by setting the compatibility mode on the executable to Windows 8.

Once you do that although the crashes stop the performance of chrome is very slow. 

Could this be related to the camera driver issue reported in this group discussion? https://productforums.google.com/forum/#!msg/chrome/YBIJiBn7X-E/3Bp1f7AjBgAJ.

CAMERA_NVM ERROR: NVM: EEPROM parser will not parse entire NVM but get vcminfo only!

"My guess, for those of you that don't use WebEx but are getting crashes, is that Chrome is trying to access the device camera. Until Dell releases a patch (and I have a case open with them), you might try disabling your camera in device manager to see if that stops the crashing."

We have tested with the plugins disabled it crashes. Dell provided a new bios version on last week and the crashing went away. Almost four days without the crashing. Since the Chrome update that came out today or yesterday the crashing is back. 

I have tried disabling the video camera - still crashes .. (Comment 11)
How do I get more focus on this issue ?  I am spending too much time with chrome crashing all the time..

What was changed in the last version that was released ?

Hi all,

All recommendations have been tried already, and Chrome debug logs were captured in different stages, I've attached new Chrome Debug logs in the Drive folder (Google-restricted) in the link below:

https://drive.google.com/open?id=0Bxg-rTzA58PeVHZRb2dfcXRPYnc

Details:

* chrome_debug1.log contains log information while Chrome was running with extensions. We see a couple of errors there.
* chrome_debug2.log it crashed right after opening the browser, and it registered an error while moving cache information from one folder to another.
* chrome_debug3.log contains logging info without extensions. Only extensions that are found in the log are the Google default ones that belong to the chrome://net-internals/#modules list. This log contains USB peripherals issues, which are not seen in the other log files.
* msinfo32.txt. This file contains information about the computer hardware.


All these log files were captured running v51.0.2704.106. 

Thanks.

Seems like we are losing our focus here so let's go back to the original issue. Try:

- Remove or disable all Chrome extensions
- Disable all plugins in chrome://plugins

If the issue still persists, please provide a fresh Crash ID from chrome://crashes. Chances are we will see a different stack trace, which may or may not be a different root cause.

Hi,

This has been tried before and the results are the same, that why I was providing new logs for each scenario. The only scenario where logs weren't captured is without plugins, but they were disabled and still, the browser crashed. Nevertheless, we'll get fresh crashes IDs maybe you can extract more info from there.

Thanks!

@pastarmovj,

Customer has provided windows dump files to analyze the exceptions (PII protected):
https://drive.google.com/a/google.com/folderview?id=0B6fESMmJITTNa0dvcHZsNkQ3MU0&usp=sharing


I went ahead and de-symbolized the dump files and listed the exceptions below for convenience:

---------------------------------

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007fff2de6b199 (AcLayers!NS_FaultTolerantHeap::FthReportCriticalFailure+0x0000000000000051)
   ExceptionCode: c0000374
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000000
DEFAULT_BUCKET_ID:  STATUS_HEAP_CORRUPTION
PROCESS_NAME:  chrome.exe
ERROR_CODE: (NTSTATUS) 0xc0000374 - A heap has been corrupted.
EXCEPTION_CODE: (NTSTATUS) 0xc0000374 - A heap has been corrupted.
EXCEPTION_CODE_STR:  c0000374
EXCEPTION_PARAMETER1:  0000000000000000
BUGCHECK_STR:  STATUS_HEAP_CORRUPTION
---------------------------------

THREAD_SHA1_HASH_MOD_FUNC:  7abded50ac4fb468b4969b4df6b088826329a8d9
THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  86a439de4ce2eaaf6719c3b40dafe6586c6a95d3
THREAD_SHA1_HASH_MOD:  c6fc51edba88dec14cd92f654a214a8f18bae36b
FOLLOWUP_IP: 
chrome_7fff2acd0000!GetHandleVerifier+2b77e5
00007fff`2afeddd5 488bcf          mov     rcx,rdi
FAULT_INSTR_CODE:  e8cf8b48
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  chrome_7fff2acd0000!GetHandleVerifier+2b77e5
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: chrome_7fff2acd0000
IMAGE_NAME:  chrome.dll
DEBUG_FLR_IMAGE_TIMESTAMP:  576b48d7
STACK_COMMAND:  .ecxr ; kb
FAILURE_BUCKET_ID:  STATUS_HEAP_CORRUPTION_c0000374_chrome.dll!GetHandleVerifier
BUCKET_ID:  STATUS_HEAP_CORRUPTION_chrome_7fff2acd0000!GetHandleVerifier+2b77e5
PRIMARY_PROBLEM_CLASS:  STATUS_HEAP_CORRUPTION_chrome_7fff2acd0000!GetHandleVerifier+2b77e5
BUCKET_ID_OFFSET:  2b77e5
BUCKET_ID_MODULE_STR:  chrome_7fff2acd0000
BUCKET_ID_MODTIMEDATESTAMP:  576b48d7
BUCKET_ID_MODCHECKSUM:  30f999a
BUCKET_ID_MODVER_STR:  51.0.2704.106
BUCKET_ID_PREFIX_STR:  STATUS_HEAP_CORRUPTION_
FAILURE_PROBLEM_CLASS:  STATUS_HEAP_CORRUPTION
FAILURE_EXCEPTION_CODE:  c0000374
FAILURE_IMAGE_NAME:  chrome.dll
FAILURE_FUNCTION_NAME:  GetHandleVerifier
BUCKET_ID_FUNCTION_STR:  GetHandleVerifier
FAILURE_SYMBOL_NAME:  chrome.dll!GetHandleVerifier
WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/chrome.exe/51.0.2704.106/576b490d/AcLayers.dll/6.2.10586.0/5632d6fb/c0000374/0000b199.htm?Retriage=1
TARGET_TIME:  2016-07-08T15:55:31.000Z
OSBUILD:  10586
OSSERVICEPACK:  0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
OSPLATFORM_TYPE:  x64
OSNAME:  Windows 10
OSEDITION:  Windows 10 WinNt SingleUserTS
USER_LCID:  0
OSBUILD_TIMESTAMP:  2015-10-29 22:27:54
BUILDDATESTAMP_STR:  151029-1700
BUILDLAB_STR:  th2_release
BUILDOSVER_STR:  10.0.10586.0
ANALYSIS_SESSION_ELAPSED_TIME: 85c
ANALYSIS_SOURCE:  UM
FAILURE_ID_HASH_STRING:  um:status_heap_corruption_c0000374_chrome.dll!gethandleverifier
FAILURE_ID_HASH:  {a858025f-fd75-aeaa-3b7c-abd91cfe1968}

-------------------------


We also have Chrome crash ID's:
Crash ID eb3f48ba00000000 ﴾2562bf44‐4793‐4fc0‐8d1a‐911d379ce010﴿
Crash ID 06d1fe8600000000 ﴾40dbf42a‐04f8‐4d94‐831c‐276b45984c1e﴿
Crash ID 79512b5a00000000 ﴾fde5cab0‐24ca‐497b‐ab8b‐61a2f866e348﴿
Crash ID 3e339e5a00000000 ﴾6d997648‐e4af‐4f39‐bafb‐063dca098b80﴿
Crash ID 4d760eaa00000000 ﴾6b4a0ba4‐ed82‐4771‐8c1e‐a9d133fce050﴿

We have crash id's, dump files, and chrome debug logs from the customer.
Do we need anything else for this investigation to move forward?

Ping.  Any update here?

Justin, Will, can this be a result of the heap corruption prevention not coping with a buggy driver or some other injected module?

I can try to take a look myself too but I will be OOO for the following 3 weeks.

Some sort of third party interaction here. Looks like intel camera drivers to me. If you don't need to use the webcam, just uninstall it.

please let the customer know.

Associated support case is closed. I am closing this bug too.