Question Computer freezes at random, Windows 10 (64-bit) still operating but not fully responsive

[jaqqu7]

Recently I've started to experience strange behavior - at random my Windows starts to stop being fully responsive. Sometimes it does not happen for hours, sometimes after 30 minutes other time almost over 2 hours of using the PC before it freeze again. Sound of the YouTube video is still playing, but I cannot open or change bookmark, I can open Windows menu, but I cannot restart or shut down, I can open the Task Manager, but everything inside is completely frozen in time there. Any program I've tried to open instantly freezes itself. The system stays in this state until I press the reset button, or for some reason it restarts itself after a while. Other thing I've noticed is that - the lights (ASUS Aura) on my graphic card and motherboard are not pulsating too. Temperatures seems to be operating in normal ranges.

It's happening without any prior signals that something is wrong: one moment I watch a video, second moment my Windows suddenly refuse to cooperate. This is a computer I just build two weeks ago, and only thing I did during this time is to keep BIOS up-to-date.

• AMD Ryzen 7 7800X3D
• ASUS PRIME X670E-PRO WIFI (BIOS ver. 1413)
• ASUS TUF Gaming GeForce RTX 4070 ti
• RAM: G.Skill Trident Z5 (2 x 16GB)
• Disk: Kingston KC3000 2TB M.2
• Power: Corsair RM850x
• Cooling: ENDORFY Navis F280
• Case: ENDORFY Regnum 400 Air

 

[Colif]

Do you have latest chipset drivers?

https://www.amd.com/en/support/chipsets/amd-socket-am5/x670e

How often is it?
Try a clean boot and see if it changes anything - make sure to read instructions and make sure NOT to disable any microsoft services or windows won't load right - https://support.microsoft.com/en-au/help/929135/how-to-perform-a-clean-boot-in-windows

It doesn’t delete anything, it just stops non Microsoft programs running with start. Easy to reverse.

if clean boot fixes it, it shows its likely a startup program. You should, over a number of startups. restart the programs you stopped to isolate the one that is to blame.

any errors showing in reliability History?