Depois de instalar o Windows 10 versão 1803 (atualização de abril de 2018), a tela congela

Question

Eu tenho uma situação estranha. Eu tinha recente instalação recente do Windows 10 versão 1803 e também tentei atualizar alguns dos meus drivers com novos lançamentos do site oficial. Eu sempre desabilito a Atualização Automática e nunca as uso.

Eu estou percebendo uma questão estranha desde então. Enquanto trabalha em algum momento em alta carga, a tela pára de funcionar. Eu posso mover meu mouse (o movimento é visível), eu posso continuar falando com outra pessoa no Skype, mas a tela não muda nada. Eu posso até abrir aplicativos usando o atalho de teclado. Eles estão abertos mas não são mostrados na tela

Eu tenho o botão de energia física mapeado para o Hibernate. Isso também funciona. Quando eu restauro do modo de hibernação, a tela começa a funcionar normalmente.

Não consigo diagnosticar o problema corretamente. Ativar / desativar o monitor não corrige, mas o modo de hibernação funciona.

Eu tentei teste de estresse na CPU, GPU, ambos os discos e nada acontece. Mas em algum momento do nada, ele congela mesmo se eu abrir uma aba.

Como faço para diagnosticar o problema e encontrar o culpado? Eu realmente não quero instalar o Windows mais uma vez.

    

Answer 1

Muitas pessoas que instalaram o Windows 10 versão 1803 de forma proativa relataram problemas semelhantes. A Microsoft está lançando uma correção na atualização Patch Tuesday amanhã (8 de maio de 2018):

Yesterday, we reported that several users were experiencing Windows 10 intermittently freezing after installing the April 2018 Update while using certain software such as Google Chrome. While an official fix is not yet available, it now appears that Microsoft is aware of the problem and will be releasing a solution on May 8.

The issue in question randomly popped up during normal workflow when using Chrome, causing Windows 10 to "freeze" and not respond to any keystrokes or mouse clicks. The only workarounds, that myself and other people experiencing the problem found, were to either close the machine's lid and reopen it, or attempt the Windows key sequence (Windows + Ctrl + Shift + B) to wake the screen. While some also reported that turning off hardware acceleration in Chrome seemed to solve the problem, the workaround did not work for me.

Now, Microsoft has officially acknowledged the issue, saying that Windows 10 does indeed freeze for some users while using software such as Cortana and Chrome. The company has posted the same workarounds already discovered by users, but has also noted that it is developing a fix "with the goal of including it in the next regular monthly update".

The next regular monthly update refers to May 8, which is the Patch Tuesday for the current month. While the exact scope and root cause of the problem is still unknown, it's good to know that Microsoft is actively working on a fix.

Fonte: A Microsoft está trabalhando em uma correção para o problema de congelamento do Windows 10 que afeta o Chrome

Atualização 1

As notas oficiais da Microsoft sobre este patch são as seguintes:

Improvements and fixes

---

This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:

• Addresses an issue with the April 2018 Windows Servicing update that causes App-V Scripts (User Scripts) to stop working.
• Addresses an issue that may cause some devices to stop responding or working when using applications, such as Cortana or Chrome, after installing the Windows 10 April 2018 Update.
• Addresses an issue that prevents certain VPN apps from working on builds of Windows 10, version 1803. These apps were developed using an SDK version that precedes Windows 10, version 1803, and use the public RasSetEntryProperties API.
• Addresses additional issues with updated time zone information.
• Addresses an issue that may cause an error when connecting to a Remote Desktop server. For more information, see CredSSP updates for CVE-2018-0886.
• Security updates to Windows Server, Microsoft Edge, Internet Explorer, Microsoft scripting engine, Windows app platform and frameworks, Windows kernel, Microsoft Graphics Component, Windows storage and filesystems, HTML help, and Windows Hyper-V.

If you installed earlier updates, only the new fixes in this package will be downloaded and installed on your device.

For more information about the resolved security vulnerabilities, see the Security Update Guide.

Known issues in this update

---

Microsoft is not currently aware of any issues with this update.

How to get this update

---

This update will be downloaded and installed automatically from Windows Update. To get the standalone package for this update, go to the Microsoft Update Catalog website.

Fonte: 8 de maio de 2018 — KB4103721 (edição de sistema operacional 17134.48)

Atualização 2

A Microsoft acaba de lançar outra atualização cumulativa para o Windows 10 versão 1803 que corrige esse problema novamente, e as notas oficiais da versão são as seguintes:

Improvements and fixes

---

This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:

• Addresses an issue that causes the Video Settings HDR streaming calibration slider to stop working. This is caused by a conflict with the panel brightness intensity settings configured by certain OEMs.
• Addresses streaming compatibility issues with certain live TV streaming content providers.
• Addresses an issue where media content previously generated by Media Center doesn't play after installing the Windows 10 April 2018 update.
• Addresses an issue in which SmartHeap didn't work with UCRT.
• Addresses performance regression in App-V, which slows many actions in Windows 10.
• Addresses an issue that causes Appmonitor to stop working at logoff if the Settingstoragepath is set incorrectly.
• Addresses an issue that causes Appmonitor to stop working at logoff, and user settings are not saved.
• Addresses an issue where client applications running in a container image don't conform to the dynamic port range.
• Addresses an issue where the DNS server might stop working when using DNS Query Resolution Policies with a "Not Equal" (NE) condition.
• Addresses an issue with T1 and T2 custom values after configuring DHCP failover.
• Addresses an issue that causes the latest versions of Google Chrome (67.0.3396.79+) to stop working on some devices.
• Addresses issues with the Remote Desktop client in which pop-up windows and drop-down menus don't appear and right-clicking doesn't work properly. These issues occur when using remote applications.
• Addresses an issue that causes a connection failure when a Remote Desktop connection doesn’t read the bypass list for a proxy that has multiple entries.
• Addresses an issue that may cause Microsoft Edge to stop working when it initializes the download of a font from a malformed (not RFC compliant) URL.
• Addresses an issue where some users may receive an error when accessing files or running programs from a shared folder using the SMBv1 protocol. The error is "An invalid argument was supplied".
• Addresses an issue that causes Task Scheduler tasks configured with an S4U logon to fail with the error "ERROR_NO_SUCH_LOGON_SESSION/STATUS_NO_TRUST_SAM_ACCOUNT".
• Addresses a performance issue with Windows Mixed Reality on some laptops with hybrid graphics adapters, such as Surface Book 2.

If you installed earlier updates, only the new fixes in this package will be downloaded and installed on your device.

Known issues in this update

---

Microsoft is not currently aware of any issues with this update.

How to get this update

---

This update will be downloaded and installed automatically from Windows Update. To get the standalone package for this update, go to the Microsoft Update Catalog website.

Fonte: 26 de junho de 2018 — KB4284848 (Compilação do SO 17134.137)

    

Answer 2

Também há relatos de que o Win10 não definiu corretamente as configurações de hibernação por meio da interface do usuário. Você pode tentar o seguinte:

 powercfg /h ON
 powercfg /X hibernate-timeout-ac 15
 powercfg /X hibernate-timeout-dc 15

Fonte: link

    

Answer 3

Eu enfrentei o mesmo problema, mesmo que eu tenha tentado a combinação Windows + Ctrl + Shift + B que faz com que o sistema fique completamente travado.

No entanto, encontrei uma solução temporária para esse problema para salvar seus dados, ou seja, conectar-se ao seu sistema por meio do RDP (Área de Trabalho Remota), fechar o Chrome e Desconectar.

Mais uma vez, faça login diretamente e não abra o Chrome até que o problema seja resolvido pela Microsoft ou pelo Google.

Atualizações

Para corrigir este problema, instale esta atualização.

link