dwm.exe causing black screening on a clean installation of Windows 10 version 20H2

Blizzerac 1 Reputation point
2020-12-04T03:01:23.8+00:00

I just installed a clean installation of Windows 10 version 20H2 on my new M.2 SSD and had been experiencing moments where my PC would black screen / the screen would turn black as if there was no display input, but there was still audio and I could play and pause using my keyboard and mouse. After attempting to restart, the resolution would be messed up and the computer would quickly freeze. This could only be fixed by using the reset button on my PC. After some investigation this has been a problem for people since version 2004. Is there a fix for this yet or do I need to find out how to install an older version of Windows 10 on a clean installation?

Specs:
i5-6600k
16GB Vengeance LPX RAM
MSI Z170A SLI PLUS
GTX 1070
Seasonic M12II 620W

Solutions I have attempted:

  • Reseating GPU
  • Reseating RAM
  • Monitoring my temps (no effect)
  • Changing thermal paste on CPU
  • Uninstalling 3rd party antivirus
  • Uninstalling OneDrive
  • Using DDU to uninstall my graphics drivers and reinstalling
  • Using sfc /scannow
  • Using DRIM.exe
  • Removing my overclock
  • Turning off XMP

Errors I'm having:
Event ID 465:
Winlogon in session 2 (console) reuqested session stop using GPU, returned status STATUS_SUCCESS, with progress stage of successful

Event ID 1000:
Faulting application name: dwm.exe, version: 10.0.19041.508, time stamp: 0xcd97c98b
Faulting module name: KERNELBASE.dll, version: 10.0.19041.662, time stamp: 0xec58f015
Exception code: 0xe0464645
Fault offset: 0x000000000010bd5c
Faulting process ID: 0x1584
Faulting application start time: 0x01d6c9e3f5584727
Faulting application path: C:\Windows\System32\dwm.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report ID: 537e3ffe-a451-4b8a-988e-61a7d91b2d01
Faulting package full name:
Faulting package-relative application ID:

Event ID 0:
The Desktop Window Manager process has exited. (Process exit code: 0x000000ff, Restart count: 8, Primary display device ID: NVIDIA GeForce GTX 1070)

Event ID 219:
The driver \Driver\WudfRd failed to load for the device ROOT\WindowsHelloFaceSoftwareDriver\0000.

Event ID 642:
Video.UI (12364,D,2) {91CAB9A8-9464-44CB-B0A2-9B7C081B8575}: The database format feature version 9080 (0x2378) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

Event ID 360:
Windows Hello for Business provisioning will not be launched.
Device is AAD joined ( AADJ or DJ++ ): Not Tested
User has logged on with AAD credentials: No
Windows Hello for Business policy is enabled: Not Tested
Windows Hello for Business post-logon provisioning is enabled: Not Tested
Local computer meets Windows hello for business hardware requirements: Not Tested
User is not connected to the machine via Remote Desktop: Yes
User certificate for on premise auth policy is enabled: Not Tested
Machine is governed by none policy.
See https://go.microsoft.com/fwlink/?linkid=832647 for more details.

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
11,594 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Dale Kudusi 3,236 Reputation points
    2020-12-04T09:28:50.967+00:00

    Hi,
    You could try the following troubleshooting method:
    Please try updating the GPU drivers from providers’ official site:
    https://www.nvidia.com/en-us/geforce/drivers/

    Check all the connections to monitors and peripherals.
    Try connecting to different video outputs on the PC. Sometimes a change in driver can cause the video to be sent to a different display adapter or different output (such as from HDMI to DVI, or DisplayPort to VGA).
    If it is a desktop PC, try connecting to a different display adapter. If you are connected to an add-in video card, try connecting to the built-in video from the motherboard.

    If this issue happened right after a clean installation, might need to consider hardware issues,
    You could try boot into Safe Mode to see if the issue persists.

    Please note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information

    Best regards.

    **
    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. S.Sengupta 18,676 Reputation points MVP
    2020-12-04T13:47:57.68+00:00

    Restart computer and choose to Troubleshoot > Advanced options > Command Prompt.

    When Command Prompt opens you need to enter the following:

    cd C:UsersYour Name HereAppDataLocalTemp
    del mdi264.dll

    After deleting the file close Command Prompt and restart your PC.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.