Thanks for the report.  Could you provide your GPU configuration from 'chrome://gpu'?

ericrk@ is investigating.

Sorry, I am out of the office now. I will attach gpu info tomorrow. 
I have tested HD* and GMA* Intel GPUs, all of them are broken.
PS. Don't forget to use the flag —disable-d3d11

This works on my razer blade stealth, FWIW. I imagine the bug's connected to the steps documented at https://cs.chromium.org/chromium/src/ui/views/widget/widget_hwnd_utils.cc?type=cs&q=WS_EX_COMPOSITED+package:%5Echromium$&l=51 that we take to create transparent windows, but I don't know why they'd cause problems.

jbau...@chromium.org
You are right!
I have reverted this hack and bug disappeared.

I attached gpu info.

Deleted: gpu.htm 103 KB

gpu.htm 103 KB View Download

Just to add my data (nothing too useful unfortunately) - I can't repro on my desktop system (NVidia Quadro K2200) or a test laptop (Intel HD Graphics 400 Cherryview) while passing --disable-d3d11

Looking through the reports, these all appear to be on older Intel systems (GMA or early HD Graphics). It sounds like HD4000+ at least is working. Will try to track down a machine.

jbauman@ may have a device that repros. Assigning to him - if not, please assign back and I'll work on tracking one down.

I can repro this on my machine with an Intel HD 4000. --disable-dwm-composition also fixes the problem, so we might need to use that (or something similar) as a workaround on these machines if we can't find a better fix.

I can repro on HD4000 too. My winver is 10.0.15063.
--disable-dwm-composition helps!

To repro this on canary with the "alert(1);" you may need to specify the "--disable-features=AutoDismissingDialogs" command-line flag, or else the dialog could be created in a way that doesn't cause the bug. With that flag I can repro it on both systems I have with Intel graphics cards.

 Issue 710560  has been merged into this issue.

 Issue 710783  has been merged into this issue.

I'm also affected by this, and it started immediately after installing the Windows 10 Creators Update, with the then-current stable Chrome 57, and now on 58.

Specifications of the affected laptop, including switchable graphics, Intel onboard GPU and Radeon HD 7690M: https://support.hp.com/us-en/document/c03144648

Chrome doesn't crash; just dialogs, like from clicking the profile name at the top, or on the "Do you want to leave this site?" dialog, are not visible. I've found that those dialogs (such as in the attached screenshot) can be bypassed by pressing Enter, assuming the default selection is the desired one - in this case, 'Leave'.

Disabling hardware acceleration and restarting Chrome makes those dialogs visible again.

I'm happy to provide any other information that may be helpful.

Deleted: dialog.png 5.7 KB

	dialog.png 5.7 KB View Download

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/fec5a00d881dcf85a1a4334af1369402e183a302

commit fec5a00d881dcf85a1a4334af1369402e183a302
Author: jbauman <jbauman@chromium.org>
Date: Fri Apr 21 01:10:49 2017

Remove use of WS_EX_COMPOSITED for translucent windows.

This style causes windows to display transparent on Windows 10 creators
update with some Intel drivers on D3D9.

The style itself is unnecessary, becasue based on its documentation it
doesn't affect top-level window rendering, but affects only how child
unredirected windows (which aren't used in Aura) render on top of their
parents.

BUG= 712196 

Review-Url: https://codereview.chromium.org/2826343002
Cr-Commit-Position: refs/heads/master@{#466207}

[modify] https://crrev.com/fec5a00d881dcf85a1a4334af1369402e183a302/content/browser/compositor/software_output_device_win.cc
[modify] https://crrev.com/fec5a00d881dcf85a1a4334af1369402e183a302/ui/base/win/internal_constants.cc
[modify] https://crrev.com/fec5a00d881dcf85a1a4334af1369402e183a302/ui/base/win/internal_constants.h
[modify] https://crrev.com/fec5a00d881dcf85a1a4334af1369402e183a302/ui/views/widget/desktop_aura/desktop_window_tree_host_win.cc
[modify] https://crrev.com/fec5a00d881dcf85a1a4334af1369402e183a302/ui/views/widget/widget_hwnd_utils.cc
[modify] https://crrev.com/fec5a00d881dcf85a1a4334af1369402e183a302/ui/views/win/hwnd_message_handler.cc
[modify] https://crrev.com/fec5a00d881dcf85a1a4334af1369402e183a302/ui/views/win/hwnd_message_handler.h

Do you plan to commit it in 59? (or may be 58?)

Yeah, though we'll need to wait a few days for it to bake in canary.

Newest Canary seems to have the fix. Running on post-Creators build 16179.

A decision was made a while back to disable D3D11 on these AMD switchable systems. Is it time to revisit that? Drivers have gotten better since then.

There's no way to force enable D3D11 with either GPU, even if you rename the Chrome executable and run it on the AMD GPU.

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

@erapple.. try using --ignore-gpu-blacklist; this works with my AMD setup.

Your change meets the bar and is auto-approved for M59. Please go ahead and merge the CL to branch 3071 manually. Please contact milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), gkihumba@(ChromeOS), Abdul Syed@(Desktop)

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

@reupload The flag doesn't help. Stuck at DX9 with both GPUs. At least with these newest builds I can run in HW accel mode again. It was months.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/bfacd1e5e1f1db344364c6c7f56f89ce773b722a

commit bfacd1e5e1f1db344364c6c7f56f89ce773b722a
Author: John Bauman <jbauman@chromium.org>
Date: Tue Apr 25 20:12:59 2017

Remove use of WS_EX_COMPOSITED for translucent windows.

This style causes windows to display transparent on Windows 10 creators
update with some Intel drivers on D3D9.

The style itself is unnecessary, becasue based on its documentation it
doesn't affect top-level window rendering, but affects only how child
unredirected windows (which aren't used in Aura) render on top of their
parents.

BUG= 712196 

Review-Url: https://codereview.chromium.org/2826343002
Cr-Commit-Position: refs/heads/master@{#466207}
(cherry picked from commit fec5a00d881dcf85a1a4334af1369402e183a302)

Review-Url: https://codereview.chromium.org/2842853002 .
Cr-Commit-Position: refs/branch-heads/3071@{#202}
Cr-Branched-From: a106f0abbf69dad349d4aaf4bcc4f5d376dd2377-refs/heads/master@{#464641}

[modify] https://crrev.com/bfacd1e5e1f1db344364c6c7f56f89ce773b722a/content/browser/compositor/software_output_device_win.cc
[modify] https://crrev.com/bfacd1e5e1f1db344364c6c7f56f89ce773b722a/ui/base/win/internal_constants.cc
[modify] https://crrev.com/bfacd1e5e1f1db344364c6c7f56f89ce773b722a/ui/base/win/internal_constants.h
[modify] https://crrev.com/bfacd1e5e1f1db344364c6c7f56f89ce773b722a/ui/views/widget/desktop_aura/desktop_window_tree_host_win.cc
[modify] https://crrev.com/bfacd1e5e1f1db344364c6c7f56f89ce773b722a/ui/views/widget/widget_hwnd_utils.cc
[modify] https://crrev.com/bfacd1e5e1f1db344364c6c7f56f89ce773b722a/ui/views/win/hwnd_message_handler.cc
[modify] https://crrev.com/bfacd1e5e1f1db344364c6c7f56f89ce773b722a/ui/views/win/hwnd_message_handler.h

I tried on two machines where I wasn't able to reproduce the issue without the fix in comment#26, hence we are going ahead with M59 Beta launch.

As Creators update rolls out more this will hit more people, so we should consider merging to M58.

Ok, seems like this isn't quite critical enough for M58.

I also hate how my Intel gpu is limited because I have AMD switchable. The drivers don't let Chrome run on the AMD chip had Chrome reverts the Intel to software cause it sees the AMD end brute/blanket disables everything regardless. 

Still happening here after updating to W10 creators:

Google Chrome: 58.0.3029.110 (64 bits)
Revision: 691bdb490962d4e6ae7f25c6ab1fdd0faaf19cd0-refs/branch-heads/3029@{#830}
SO: Windows

How is this not 'critical'? This bug hasn't been fixed yet as of version 58.0.3029.110 (64-bit), and is directly affecting user experience. Most of my popup windows are still missing, and only render after randomly guessing where the buttons should be (such as the translation popup).