After monitor sleep awake, everything is frozen

Hello all,
recently I'm experiencing this problem in my Windows 10: When I wake up my PC from monitor screen (which is set for 3 minutes), everything is frozen - I type, it doesn't type, I move my mouse, nothing moves and then later after few seconds, minutes or too much clicking it goes back to normal and shows that what I was typing actually got typed. So basically it seems like computer screen freezes after monitor sleep wake up. I didn't have this problem before, it must be from recent updates probably. Anyone else having the same problem? This is my current build:

Edition Windows 10 ProVersion 20H2Installed on ‎2020-‎06-‎12OS build 19042.782Experience Windows Feature Experience Pack 120.2212.551.0

P.S. I was browsing Windows 10 feedback and I saw this very offensive post there. I know it doesn't have to do with my problem, but holy cow, how this is allowed there?

Have you installed the latest version of graphic card driver from graphic card manufacturer website?

You should perform clean boot state to found out any one of the third-party startup services or applications causing the problem.

Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

FreeBooter said:

Have you installed the latest version of graphic card driver from graphic card manufacturer website?

You should perform clean boot state to found out any one of the third-party startup services or applications causing the problem.

Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

Yes, got update from Nvidia and I installed it. Checked start too and don't have anything unusual there. But to be honest, I don't think it's graphics card driver. In fact, I know for sure that it's not it, because today my wife told me that her computer also started acting exactly like that. That computer doesn't even have a graphics card. The only thing that comes into my mind are Windows updates. We always keep our Windows up to date. So maybe latest update is causing this. Is anyone else experiencing such problem after recent updates?

I have latest updates installed i have no problems.

NO... i absolutely refuse to create MORE threads about this same exact issue.

I am seeing everywhere the same issue under different circumstances, "Turning off monitors" or "Putting the computer to sleep." It all boils down to the system freezing after waking up the monitors. REGARDLESS of drivers, or "recent" updates. I have had this issue for as long as i've had Windows 10.

It is specifically the monitors waking up that freezes something specific to peripherals and display output. Like a USB Filter Driver or something completely neglected by Microsoft's QOL department.

ALSO, this issue is far older than February of this year, in fact, this has been something i've been trying to fix for my entire time on Windows 10. Something to do with antiquated power management? maybe it's an antiquated handshake while waking up new drivers and devices?

All i know is there is a consistent relation between everyone having this problem, and everyone else thinking it's either: GPU drivers, faulty GPU, failing RAM, BIOS, or PSU (so far i haven't seen anything suggesting a faulty PSU, just a PSU in general... what?) I've seen people try COMPLETELY fresh installing Windows, complete isolation installations, fresh GPU driver installs, NEW GPU's, and one story even had the person buying a whole new computer (which did the same thing)...

This is no longer an END USER issue.
Especially when the majority of issues are reported from business use cases, and the minority being gamer use. Thus eliminating the usual "It's just Origin F'ing up Windows again" or "Steam Overlay at it again"

I hope this issue is pinned indefinitely until a fix is found.

FINALLY
My problems have been answered: My PC keeps turning off... - YouTube
My C-STATE setting is now disabled and i no longer freeze/hang after wake up.

Update: STILL freezes after monitors are turned off and back on again via power setting. Confirming it is with Windows, not hardware.

This is such an old thread that I don't even remember what fixed it or what was causing it, but definitely don't have this problem anymore.