Question Windows 11 - Apps/Windows freezing, and taking long time to wake up....

[Tonio777]

I am seeing some very odd freezing of windows. It tends to be associated with a specific monitor usually,(I am currently running monitors), and say if I go to click on the top of a chrome window, over on a monitor i haven't done anything recently on, it freezes and doesn't come up immediatelly. I can't click anywhere on the entire monitor, screen, including often explorer. But if i move my mouse over to say monitor 2, and click a window it responds immediately, like nothing is lagging, etc. And yet if I go back to that first monitor, it is still frozen, then after anywhere from 10 seconds, to over a minute, it will suddenly start to work again.

I only experienced this in the last month, maybe a bit longer, or maybe a bit less, but around that kind of time frame, and i am using a new machine I built just after this past Christmas.

I am using the following hardware:
ASUS PRIME X870-P Wi-Fi 7 AM5 DDR5 Motherboard
AMD Ryzen 5 7600X 6-Core 4.7GHz AM5 Processor
Nvidia 3080 GPU
Lexar NQ790 SSD 1TB, M.2 2280 PCIe Gen4x4 NVMe 1.4 Internal Solid State Drive

I am not using any power saving settings, infact I've turned them off trying to figure out what this might be.

I am a bit out of ideas, most stuff I've read seem to say it's my video card, power savings settings, or overheating... but nothing I've seen seems to point to any of these...
Well, at leats any overheating of the CPU or the GPU, as it all reads pretty normal. I have a really decent cpu dual fan liquid cooler, that keeps it usually in the 30C degrees, never going above 54C. And the GPU is unclocked, and i've tried just neutral default settings as well. Nothing seems to make a difference. I've tried GPU drives as well.

I am at a bit of a loss, and it's getting to the point that I am really not able to use my machine without frustating pauses... it's gotten tiny bit better than it was 2 weeks ago. But not something I can really live with..

Any ideas where I should look, any microsoft pages, or things i should try. I've looked at the error events, but nothing seems to be happening as often as what I am experience...
I did see something called DistributedCOM 10010 which does seem to happen with some regularity, but nothing i read online made it clear that what that might point to????

Thanks,

 

[Ralston18]

PSU: make, model, wattage, age, condition (original to build, new, used, refurbished)?

Disk drive(s): make, model, capacity, how full, how connected?

Other attached peripherals?

= = = =

Look in Reliability Monitor - much more end user friendly than Event Viewer and the timeline format may reveal a pattern.

Check Update History for any failed or problem updates.

Use Task Manager, Resource Monitor, and Process Explorer (Microsoft, free) to observe system performance.

Use all three tools but only one tool at a time.

Leave the tool window open and viewable as you work, game, etc. Watch for what changes when the freezes occur.

= = = =

Perhaps some buggy or corrupted files.

Try running "dism" and "sfc /scannow".

 

[SteJBorchard]

So that post above and also how much RAM does this laptop have?

I'd say for now set page file to static, 2048 MB amount, disable all start up programs you don't need or use and have a good whole happy time on the remove programs part of your control panel.

Edit: also until you get it resolved. Control Panel > System > Advanced System Settings > Advanced > under Performance .. Settings > Change to Adjust for best Performance. Until you figure it out.

for starters.

 

[johnbl]

I would confirm what bios update you are on.
looks like they have issues and updates to agesa interface in bios.
also have a firmware update for the usb 4 device.
note: bios update requires chipset update. check out the other driver updates.

https://www.asus.com/motherboards-c...0-p/helpdesk_download?model2Name=PRIME-X870-P

if your system bios and drivers are up to date:
you might consider turning off all unused audio devices.
make sure the gpu drivers are up to date.

after that I would force a kernel memory dump, then look at the internal logs inside the dump using windbg.
generally, if the gpu takes over 2 seconds to respond windows will call a watchdog timeout.