Before the Windows upgrade it was working well. After the clean Windows upgrade and re-installation of the latest Chrome browser this happened.

Please see the task manager processes for chrome browser.

Deleted: Chrome_Taskmanager.jpg 105 KB

	Chrome_Taskmanager.jpg 105 KB View Download

Unable to reproduce the issue upon re-installation and upgrading to latest Stable 62.0.3202.94 and latest Canary 64.0.3269.3 using Windows 10 

+ grt@ for further inputs.

Hi, thank you for your feedback.

After trying out several things found out the chrome is having problem when I switch the program from integrated graphic cards to my Nvidia GPU model GT 540M.
I am using the latest Nvidia driver version 388.31.

So what is the problem then? Chrome or Nvidia driver?

Thank you for providing more feedback. Adding requester "divya.padigela@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

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

By the way, I am able to switch to the Nvidia GPU with no problem when using firefox.

This issue is related to Installers and dual GPU as per comment#6, can anyone from the inhouse team have a look at this issue.

+vmiura@ for triage. 

tiamchuah@: Could you please provide about:gpu using your integrated GPU? Thanks!

sunnyps@ is this the same as we discussed today?

This could be a reported problem with DirectComposition on Win 10 Fall Creators Ed.

Hi, thank you for the follow up.

Basically my machine have 2 graphic adaptors, integrated Intel HD Graphics 3000 and addon Nvidia GPU GT 540M.

After fresh installation of Windows 10 fall creator and updates, I installed the latest Chrome as mentioned and confirmed by our side.

I noticed that by then Windows 10 update already included the Intel and Nvidia adpators' drivers.

Initially, Chrome worked fine on the integrated Intel adaptor. However when I switched Chrome to use the Nvidia GPU for better graphics performance via their Nvidia control panel, Chrome would startup but ended up with the black screen and the cursor just keeping flashing as per my screenshot.

Then I decided to un-installed the Nvidia driver and installed the latest Nvidia driver from Nvidia web site but still the same problem persist.

From the internet information, it seemed that whenever Microsoft Windows 10 changes there are alot of Nvidia GPU operational problems especially with for web browsers.

Firefox and Edge seemed to have no basic problem of switching between the Intel and Nvidia adaptors.


Hope this helps.

As a result, I am now stuck with the default drivers from Windows 10 and Chrome can only operate on the Intel adaptor and cannot switch to use Nvidia adaptor.

Can you post contents of chrome://gpu? Also, can you please try latest Chrome Canary with --disable-direct-composition command line flag?

Hi,

Please see the chrome://gpu information.

I can now switch chrome to use Nvidia GPU via the Nvidia control panel but it is still using the Intel adaptor not the Nvidia adaptor as the Nvidia GPU activity panel does not display chrome using it.

Deleted: Nvidia Display.jpg 14.2 KB

	Nvidia Display.jpg 14.2 KB View Download

Deleted: ChromeGPU.pdf 1.7 MB

ChromeGPU.pdf 1.7 MB Download

Deleted: Nvidia.jpg 149 KB

	Nvidia.jpg 149 KB View Download

There are two workarounds for other problems caused by the Fall Creators Update:
1. Run Chrome Canary with the --disable-direct-composition flag.
2. Run Chrome under Windows 8 compatibility mode.

We're working on blacklisting direct composition for the affected hardware, but can you try these workarounds meanwhile and let us know if they help. Thanks!

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

commit fbbf434ba94f5e150b0dfc1b830f7829f0e4e177
Author: Sunny Sachanandani <sunnyps@chromium.org>
Date: Tue Nov 21 06:02:11 2017

gpu: Blacklist direct composition on older GPUs.

Older Intel and Nvidia GPUs either cause slow presents or black flashes
with direct composition. Blacklist only those devices which have been
reported to have issues.

R=kbr
BUG=775898,785648

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel
Change-Id: I506df99854d7d0d464cea9d0a83336429eeefd4d
Reviewed-on: https://chromium-review.googlesource.com/777854
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518146}
[modify] https://crrev.com/fbbf434ba94f5e150b0dfc1b830f7829f0e4e177/gpu/config/gpu_driver_bug_list.json

Tested the issue on windows 10 with the creators update 1703 using chrome stable  M62 #62.0.3202.94 and chrome reported version M64 #64.0.3269.3 and unable to reproduce the issue.

GPU Driver Info :
NVIDIA Quadro 400 Direct3D11 

@MTV Team -- Could someone from MTV team look into this with the fall creators update and "integrated Intel HD Graphics 3000 and addon Nvidia GPU GT 540M" Drivers.

Thanks!

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

commit 138492abcdb3e0d9369f25868fff4b9dababf915
Author: Bruce Dawson <brucedawson@chromium.org>
Date: Wed Nov 29 00:11:00 2017

Change GPU driver bug list tag from windows to win

Some recent additions to gpu_driver_bug_list.json tagged the workarounds
with os type "windows" when "win" is the correct tag. This fixes that.

I'll investigate adding checks to the script to reject unknown OS types.

Bug: 775898,785648
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I4f9cfb86487385c45fe6a2a8f67c93f711c0f315
Reviewed-on: https://chromium-review.googlesource.com/791850
Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Commit-Queue: Bruce Dawson <brucedawson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519916}
[modify] https://crrev.com/138492abcdb3e0d9369f25868fff4b9dababf915/gpu/config/gpu_driver_bug_list.json

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

commit f0980d12d3c008a78a2a03109e2b63954f60b680
Author: Bruce Dawson <brucedawson@chromium.org>
Date: Wed Nov 29 05:27:33 2017

Add OS type checking to process_json.py

File adding a workaround to a GPU driver bug the os type "win" was
misspelled as "windows". This caused a one-week delay in testing the
workaround. This adds an OS type check to avoid this error in the
future. It was confirmed that this check would have detected and
prevented the recent error, with this error message:

    Exception: Unknown OS type "windows" for entry 248

Bug: 775898,785648
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: Idd1a4266087acbae24cfc6e60ac873f17c7ac7ef
Reviewed-on: https://chromium-review.googlesource.com/791930
Commit-Queue: Bruce Dawson <brucedawson@chromium.org>
Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#520018}
[modify] https://crrev.com/f0980d12d3c008a78a2a03109e2b63954f60b680/gpu/config/process_json.py

I'm experiencing the same issue. I have an ASUS laptop without any fancy video hardware. The chrome window is black with only a white bar at the top. The application seems to think it has loaded correctly as when I move my cursor around on the screen it registers the tab names and the urls of hyperlinks (which I cannot see) as I roll over them. I tried loading Canary and it also does not work for me. (It broke when I did the Windows10 Creators updates.) 

Chrome, Chrome beta and Chrome Canary all gave black window as first post following Windows 10 Fall Creators Update.

Running Intel i7-2720QM with Intel Graphics 3000 and NVidia GT555M. The NVidia driver is 388.59, updated yesterday.

Solved temporarily by setting chrome to run on integrated graphics.  (From installed program folder, right click on chrome.exe, select Run with Graphics Processor, and on the fly-out, select "Change default graphics processor" which launches the NVidia control panel, and select the preferred graphics processor as Integrated Graphics.

Issue was fixed for me by updating my display drivers.

This error occurred only right after the Windows update, but as the error came into the knowledge of Microsoft, they immediately fixes it. View more information here https://www.windowstechnicalsupportnumbers.com/blog/fix-windows-error-0x80071a90/