Tested in chrome # 58.0.3029.81 and Stable #58.0.3029.96 and Canary #60.0.3088.0 on win 10.0 and not able to reproduce the issue.
Tested Environment : Win 10.0 and NVIDIA version #8.1.850.0

@Reporter: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 in latest stable and Canary builds and let us know the observations of the issue which would help us to triage the issue further.

Thanks in Advance.

Thanks for looking into it. I know its hard to reproduce and possibly win10 CU and/or hardware related. That is why I took the dumps (i can make full dumps available, I have a bunch from when it took longer than 5 seconds to respond). 

I just had hangs on 58.0.3029.96 (64-bit) (all chrome windows did not update for about 4 seconds, I have a timer open in one tab).

I will retest later today on canary with an empty profile.

Thank you for providing more feedback. Adding requester "rbasuvula@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Unable to reproduce the issue on Win-10 using chrome latest stable #58.0.3029.81 and latest canary #60.0.3090.0.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Opened chrome browser.
2. Typing in the address bar, scrolling the page and clicking did not freeze the window.

mgt576@ - Could you please check this issue on latest canary #60.0.3090.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Thanks...!!

Deleted: 715094.mp4 13.9 MB

	715094.mp4 13.9 MB View Download

I am using canary now and will check whether it hangs in day to day. It is important to note, that the observed issue does not happen right away. Its is not reproducible for me directly but when actually working (like e.g. I am typing in the browser right now) it suddenly hangs (it just did when writing this text too for example). Enabling HW Acceleration makes the problem worse.

Anyway I will switch to canary for the rest of the day and report back (will leave HW acceleration switched on). Should it happen often enough I will take some 'hang' dumps.

To be clear I was not using Canary when typing the comment just now. That was still in the mainstream browser. In Canary I will not log in with my profile etc.

Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

I worked with Canary and without User Profile for the rest of the day and today and could not reproduce it. I will try it on Canary with my user profile now. Sorry for not testing on canary even before opening this ticket, but I did test with the beta which showed the same problem and last time I worked with Canary it was not really stable enough.

Friendly ping!!

mgt576@Could you please check this issue on latest stable-58.0.3029.110 or Canary #60.0.3090.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.
Thank you..!!

Small update: With my default profile on Chrome 60.0.3106.1 it showed strong issues today (last 2 hours). Entire window freezes for short time periods (once even showing unresponsive, i.e more than 4/5 seconds frozen for Windows to detect that). I have switched to incognito mode for the rest of the day and will compare.

Thank you for providing more feedback. Adding requester "jmukthavaram@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Already, after about 12 minutes, I had small hangs that I did not experience in Canary early last week.This is in incognito mode just surfing openai.com, twitter, spiegel.de etc.

I do not experience hangs in any other application, just Chrome since the reinstall of Windows 10 Creators Update. All drivers are supposedly up-to-date, though I do use the nVidia driver from Windows Update and not the newest driver from nVidia (which turned out to be unstable).

Just monitoring like this is unlikely to be productive though. I will try to configure procdump to take snapshots again (from canary this time) should it hang for long enough (which is rare, mostly its less than 2-3 seconds).

I will also try to disable HW acceleration again on Canary, since this proved to be a mitigating factor (much reduced,not totally gone though).

After testing extensively I have to conclude that the issue is/was indeed hardware related. It is basically gone on my PC now.

To recap:

After installation (fresh)of Windows 10 CU I noticed the issues almost right away with Chrome. It was much reduced when disabling H/W Acceleration.

Everything else on the PC worked as fine as ever.

The CPU was not particularly busy when Chrome (the entire window) hang so I assumed it was an IO/driver issue.

After spending some more time with the Canary and some more dumps which did not show a consistent issue I looked into the BIOS settings. Since this is a Multi CPU system (2 CPU, 12 cores physical, 24 with HT) with light overclocking I suspected the issue coming directly from the H/W side of the Mainboard or CPU/Ram.

I set most of the CPU settings (which BTW had not changed for more than a year) back a little, especially the PCI multiplier, and the issue is basically gone. Previous reboots were no help and no Windows updates were installed at the same time.

There are about a dozen BIOS OC settings which I do not have the time to go through to isolate the exact cause, but ever since I rebooted with this slightly changed setup, it was immediately obvious that it had the desired effect. 

Basically no more hangs (unless I load a lot of tabs with large videos/graphics etc very quickly when it could still hang for a very short while).

I would advise to close this issue and declare it a case of user hardware overclocking stupidity. Even though the extreme exactness of the error (only affecting Chrome in such a visible manner, not Electron apps, nor Photoshop etc) is still leaving me curious.

Many thanks for the time invested and I hope this issue can at least be a helpful lead if it ever crops up again.

As per comment #14 closing this issue, Please raise a new issue if you come across the similar one on any of the latest chrome versions.

Thanks!