Windows locks up after varying hours of usage

Question

Windows locks up after varying hours of usage

Someone999 0

Hello!

I've been facing an issue where after some time, my computer will begin to lock up and become unresponsive. My mouse will work fine and it seems the OS is okay, but all other software, including file explorer will freeze and is unable to be recovered. The only exception is web browsers, which seems to work fine while this is happening.

I also documented some stuff coming out of event viewer:

An error listing the following...

The server {00000000-0000-0000-0000-000000000000} did not register with DCOM within the required timeout.

And a repeated warning listing...

The application-specific permissions settings do not grant Local Activation permission for the COM Server application with CLSID
{00000000-0000-0000-0000-000000000000}
 and APPID
{8BC3F05E-D86B-11D0-A075-00C04FB68820}
 to the user DESKTOP-XXXXXXX\XXXXXXX SID (XXXXXXXXXXXX) from address LocalHost (Using LRPC) running in he application container Unavailable SID (XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX). This security permission can be modified using the Component Services administrative tool.

If anyone knows how to resolve this issue, please let me know! And thank you in advance for the help!

0 comments

2 answers

Your answer

Answer 1

Thomas4-N 22,395 Microsoft External Staff Moderator

Hello Someone999,

The DCOM warning may simply have been recorded during the freeze rather than causing it, so I would not change its permissions yet.

Could you provide:

Your Windows version and OS build
PC model and hardware specifications
Any recent updates, drivers, or software changes
Whether the issue also occurs in Safe Mode
Any critical events shown in Reliability Monitor at the freeze time

These details should help narrow down whether this involves a driver, background software, storage, or Windows itself before moving to advanced dump collection.

Thomas4-N 22,395 Reputation points Microsoft External Staff Moderator

2026-09-03T10:55:28.2+00:00

Hello Someone999,

Just check in to see how things are going. Let me know if you need anything.

Someone999 0

Hi @Thomas4-N ,

sorry for the wait, life got a little crazy on my end and I had to take care of some things, but I do have some answers for you.

Version 35H2 Build 26200.9445
PC:
		Intel Core i9-12900KF - Core i9 12th Gen Alder Lake 16-Core
		ASUS TUF GAMING Z790-PLUS WIFI LGA 1700 ATX Gaming Motherboard
		CORSAIR Vengeance RGB 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Desktop Memory Model CMH32GX5M2E6000Z36
		GIGABYTE GeForce RTX 4060 EAGLE OC 8G Graphics Card, 3x WINDFORCE Fans, 8GB 128-bit GDDR6, GV-N4060EAGLE OC-8GD Graphics Card
		ASUS TUF Gaming GT301 Mid-Tower Compact Case for ATX Motherboards with Honeycomb Front Panel
		CORSAIR RMe Series RM1200e ATX Power Supply – Fully Modular – ATX 3.1 – 80 PLUS Gold – Cybenetics Platinum – Low-Noise – 1200 Watts
		SAMSUNG 990 PRO SSD 1TB PCIe 4.0 M.2 2280 Internal Solid State Hard Drive, Seq. Read Speeds Up 	to 7,450 MB/s, MZ-V9P1T0B/AM
		Cooler Master Hyper 212 Halo Black CPU Air Cooler, MF120 Halo² Fan, Dual Loop ARGB, Aluminum Top Cover, 4 Copper Heat Pipes, 154mm (H) for AMD Ryzen AM5/AM4, Intel LGA 1851 1700/1200 (RR-S4KK-20PA-R1)
No updates prior to new problems
Issue not happening in safe mode (to my knowledge)
No critical events in reliability monitor

Thomas4-N 22,395 Reputation points Microsoft External Staff Moderator

2026-09-14T13:24:16.19+00:00

Hello Someone999,

The fact that the freezing does not occur in Safe Mode is useful and makes the DCOM warnings less useful as a starting point.

I would test a clean boot next to narrow down whether a background service or startup program is involved. If the PC remains stable during a clean boot, re-enable the disabled services/startup items gradually until the freezing returns.

If it still freezes even after that isolation, then collecting diagnostic data during a freeze would be the next step rather than changing DCOM permissions.
Thomas4-N 22,395 Reputation points Microsoft External Staff Moderator

2026-09-17T06:51:58.1166667+00:00

Hello Someone999,

Just check in to see how things are going. Let me know if you need anything.
Someone999 0 Reputation points

2026-09-21T14:04:24.3+00:00

Hello @Thomas4-N ,

Looks like it's still freezing when running in a clean boot, I'll update you when I have some diagnostic data back.

Edit:

I found some leads with a reoccuring yet varying thing that pops up as "Microsoft.Windows.Kernel.PnP.AggregateSetDevNodeProblem" and "Microsoft.Windows.Kernel.PnP.AggregateClearDevNodeProblem" if that says anything. Other than that, everything else looks like its windows processes when freezing.

Would you like me to toss over the export data or any of the full reports?
Thomas4-N 22,395 Reputation points Microsoft External Staff Moderator

2026-09-23T06:55:38.12+00:00

Hello Someone999,

Thanks for testing the clean boot. Since the system still freezes there, I think it makes sense to move on to collecting diagnostic data rather than trying more startup changes.

The Kernel-PnP entries are worth noting, but I wouldn’t treat them alone as proof of the cause yet.

If you’re willing, please share the diagnostic information from around the time of the next freeze. I would take a closer look at what Windows recorded.

Answer 2

For this kind of partial freeze, the supported next step is to collect diagnostic data during the hang rather than treat the DCOM entries as the root cause by themselves.

First identify the pattern of the freeze:
- Whether it happens on one PC only
- What operation was happening when it froze
- How often it occurs
- Whether it happens at a predictable time
Configure Windows to capture a complete memory dump:
- Press Win + R, run Sysdm.cpl
- Go to Advanced > Performance > Settings > Advanced > Change and verify the paging file
- Go back to System Properties > Advanced > Startup and Recovery > Settings
- In Write debugging information, select Complete memory dump
- Enable Overwrite any existing file
- Make sure pagefile.sys is on the system drive and is at least 100 MB larger than installed RAM
- Make sure the system drive has more free space than the amount of physical RAM
Enable keyboard-triggered crash dump collection. Warning: Registry changes can cause serious problems if done incorrectly. Back up the registry first. In Registry Editor, create CrashOnCtrlScroll as REG_DWORD with value 1 in both keys:
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\kbdhid\Parameters
Then restart the PC.
When the system enters the frozen state:
- Hold the right Ctrl key
- Press Scroll Lock twice
This generates a memory dump. By default, the dump file is saved at %SystemRoot%\MEMORY.DMP.
Validate the dump file:
- Use Dumpchk.exe to verify the dump was created correctly and is not corrupted
Collect performance data as well:
- Run Performance Monitor logging during normal operation and around the time the freeze occurs
- Performance Monitor logs are stored in C:\PERFLOGS

The DCOM timeout and COM permission warnings shown in Event Viewer can appear during broader system hangs, so the most reliable way to find the actual cause is the dump and performance data collection path above.