Windows 10: DRIVER_POWER_STATE_FAILURE and VIDEO_DXGKRNL_FATAL_ERROR after 2004-OS Build 19041.662 and...

I don't have much information but it started happening after the last windows update 2004-OS Build 19041.662 and 20H2-OS Build 19042.662.

Here is the link to the dump file.

Please look into it.

:)

 

windows build 2004 version not showing in system information page

I have download and install new feature windows 10 version 2004 and now windows 10 version 2004 is up to date but i have see system information build is 19041.

My query is that why not show build 2004. it is showing build 19041

 

computer forced an update 2 days ago to version 2004 OS Build 19041/450

The computer prompted me that I needed to install the latest version o Windows 10 2 days ago. It took several hours. When I was able to access my computer, I still had Office but needed to connect my One Drive and other apps. Then I had to set up my Chrome
browser. Today it prompted me that there was another update. I am not sure if this is connected by later in the day I had to troubleshoot my speaker because I wasn't able to get any sound from my speaker. The troubleshooter fixed this issue.

When my computer restarted, I had to reinstall these same apps. I have 2 questions, one is how many more times will I need to set up my computer due to more updates and second should I warn my husband that this will be happening to his computer soon.

Currently, I am running Version 2004 OS Build 19041/450

 

Version 2004, OS build 19041.207

I was having problems: open programs and OS freezing, errors when updating W 10 Pro ver 1909. While trying to solve those concerns, I stumbled into upgrading to Version 2004 build 19041.264. I followed Eiji T's example with clean boot using msconfig.
After hiding Microsoft services, I disabled half the listed programs. The freezing continued. I reversed the active programs. The problem seemed resolved at first. Before I could add programs back within msconfig, the freezing returned. I have no doubt my
problem lies deep in Windows 10. ....Ver. 2004 is not to blame.