Random Freeze and Unresponsiveness [Windows 10 20H2]

I keep hoping someone figures this out, I have tried everything listed in thread and still freezes in about 20 minutes. System was smilie until windows 10 upgrade 20h2. I am so tired of trying to fix laptop I finally bought an IPad, at least now I can work. Microsoft needs to fix this.

Thank you. The information in the upper part using msconfig resolved the problem for me. Now I have to find out which service or program was causing the desktop freeze every few seconds after W21H1 update.

Ya if you figure out the specific service that caused it, that would potentially be quite helpful as other folks could then compare their services to see if there is a commonality.

Thank you. The information in the upper part using msconfig resolved the problem for me. Now I have to find out which service or program was causing the desktop freeze every few seconds after W21H1 update.

Has anyone with the issue tried this update by chance (or made sure it's installed?)? https://www.bleepingcomputer.com/news/microsoft/windows-10-kb5000842-cumulative-update-fixes-freezing-issues/

I had the freezing problem when I had moved forward from 2004 to 20H2 and then I rolled back to 2004 and the problem went away - I'm still on 2004 and I won't install a new version until 21H2 later this year, but I am continuing to monitor this thread as this is a very concerning problem. Hoping an actual solution is found at some point since some people who have now tried 21H1 are still having some issues as well.

EDIT - Also has anyone tried disabling "Hardware Accelerated GPU scheduling"? I saw one post on reddit where someone had mentioned that resolving system freezes for them. So just something to try. Since I am not currently having the issue with v2004 I can't test any of this stuff.

Honestly, i wont try nothing else anymore. Im just tired about this, so many hours focus on that problem.

Anyway, i had the same problem as 2004, 20h2 and 21h1, so i think atleast for me its something about 2004 update that it's not solved yet on the next updates. I don't know what to do right now cause windows 2004 and next's makes my shooter games more fluid about fps than the windows 10 1909, but can't have cause system crash so..

Has anyone with the issue tried this update by chance (or made sure it's installed?)? https://www.bleepingcomputer.com/news/microsoft/windows-10-kb5000842-cumulative-update-fixes-freezing-issues/

I had the freezing problem when I had moved forward from 2004 to 20H2 and then I rolled back to 2004 and the problem went away - I'm still on 2004 and I won't install a new version until 21H2 later this year, but I am continuing to monitor this thread as this is a very concerning problem. Hoping an actual solution is found at some point since some people who have now tried 21H1 are still having some issues as well.

EDIT - Also has anyone tried disabling "Hardware Accelerated GPU scheduling"? I saw one post on reddit where someone had mentioned that resolving system freezes for them. So just something to try. Since I am not currently having the issue with v2004 I can't test any of this stuff.

I've just checked and I did install that update and currently running the latest 21H1 version of Windows and I had 6 lock-ups just from yesterday.

I disabled the Hardware Accelerated GPU Scheduling since version 1909 and didn't have a luck with it.

Good thing that you don't experience any issue after you rolled back because I read on another thread that someone rolled back to version 2004 and the problem didn't go away. Rumors has it that the next major update would come out at the end of July this year and I am not sure if it's going to fix this issue. Hopefully it will because I can't trust my laptop with any important work at all because of the freezing issue.

Ya this is a really irritating problem. My rig is rock solid stable, and with 20H2 it started hard-locking (freezing) on an almost daily basis immediately after installation - the issue would occur when it was idle, though, never when I was using it actively, usually overnight and I'd walk in the next morning and it would be completely frozen - nothing in the logs to indicate what had happened. I ended up rolling back to 2004 and the problem has completely disappeared - that was back in February, haven't had the system lock up since then, almost 4 months ago. For me, it's definitely an issue that was introduced in 20H2 and I'm avoiding 21H1 because I don't trust that it's fixed based on all the info people are supplying in this thread.