Fix Windows 11 PCs That Freeze Briefly Every 30 Seconds

Quick fix: A clockwork 30-second freeze on Windows 11 is almost always the SMB browser election on a workgroup, the Group Policy refresh on a domain-joined PC, or a failing SSD with retry timeouts. Disable Function Discovery Resource Publication, run chkdsk /scan, and check Event Viewer at the freeze timestamps.

The pattern matters. A random freeze that happens once an hour points to one thing; a freeze that recurs every 30 seconds — clock-perfect — points to a scheduled task. The interval is too regular to be hardware noise. Something on the system is running on a 30-second loop and blocking the foreground long enough to glitch audio, stall the cursor, and pause whatever app you’re using.

What causes this

The 30-second cadence is unusual and narrows the suspect list down to a handful of services. The SMB browser elects a master browser every 12 seconds during contention but settles into a 30-second heartbeat once stable. Group Policy on a slow domain controller can stall at the standard refresh interval. A failing SSD with rotating bad blocks retries reads with a 5-second timeout that — combined with queued I/O — can cluster at 30 seconds. Bluetooth scanning, USB enumeration, and Windows Update probes all have rhythms that fall in this range.

The fastest way to identify which one is at fault is correlation: capture the timestamps of three or four freezes, then look at Event Viewer for matching entries within a one-second window. Most causes leave a trace, even if it’s a warning rather than an error.

Method 1: Disable SMB browser and Function Discovery on a home network

SMB master browser election is a common cause on workgroup machines with mixed Windows versions. If your PC is on a home or coffee-shop network, you don’t need either service.

1. Press Win + R, type services.msc, press Enter.
2. Find Function Discovery Provider Host (fdPHost) and Function Discovery Resource Publication (FDResPub).
3. For each, set Startup type to Manual (don’t disable; some printing flows need them).
4. Find Computer Browser if it exists (legacy Windows 11 builds) and set it to Disabled.
5. Open Control Panel → Programs and Features → Turn Windows features on or off and uncheck SMB 1.0/CIFS File Sharing Support if it’s on. SMB1 ships disabled by default but enterprise images sometimes turn it back on.
6. Reboot and observe for an hour.

If the freezes stop, SMB browsing was the cause. Re-enable services individually if you find specific network shares or printers that broke.

Method 2: Check Event Viewer for time-correlated entries

If Method 1 didn’t help, capture exact freeze times and match them in logs.

1. Open Task Manager (Ctrl + Shift + Esc) and note three consecutive freeze times to the second. The clock in the upper-right of the taskbar is enough.
2. Press Win + X and open Event Viewer.
3. Navigate to Windows Logs → System. Click Filter Current Log in the right pane.
4. In Logged, choose Custom range and narrow to your freeze window. Filter event level to Critical, Error, Warning.
5. Look for repeating entries: Kernel-Power at the freeze interval points to USB or power management; disk source with The IO operation at logical block address ... was retried means failing storage; Service Control Manager entries point to a service stalling.

The matched event source tells you what to fix. Disk retries are an SSD warning. Kernel-Power entries usually mean USB enumeration storms — unplug suspect USB devices one at a time.

Method 3: Run chkdsk and a quick SMART check on the system drive

If Event Viewer pointed to disk retries or you want to rule out hardware before deeper steps:

1. Open an elevated PowerShell or Command Prompt.
2. Run chkdsk C: /scan — the read-only scan finishes in a few minutes on a healthy SSD without requiring a reboot.
3. Run Get-PhysicalDisk | Get-StorageReliabilityCounter in PowerShell. Look at ReadErrorsCorrected and Wear. Read errors above zero or wear over 90% are a flag.
4. If the drive is NVMe, install CrystalDiskInfo (free, portable) and check the Health Status. Anything other than Good warrants imaging the drive to a replacement.
5. If chkdsk reports bad sectors, run chkdsk C: /f /r on the next reboot and let it complete (can take hours).

A failing SSD with retry storms is the most common cause that survives Method 1. Don’t wait for it to fully fail — clone the drive while you still can.

How to verify the fix worked

• Open Resource Monitor (resmon), watch the CPU and Disk graphs for ten minutes. No periodic spikes at the previous 30-second cadence.
• Run an audio test track in the background — no glitches over a sustained period.
• Check Event Viewer System log filtered to the last hour. No repeating Warning/Error entries at the old interval.

If none of these work

If freezes persist with SMB disabled, no disk errors, and Event Viewer empty at the freeze times, the cause is likely a driver-level operation that doesn’t log. Run the Windows Performance Recorder (part of the Windows ADK) with the Audio glitches and CPU usage profiles for two minutes, then open the resulting .etl file in Windows Performance Analyzer and look for DPC spikes at the freeze interval. The top function in the call stack will name the driver. For most users, the culprit ends up being a Bluetooth, Wi-Fi, or NIC driver — update through Device Manager or the manufacturer’s site. If the freezes also happen in Safe Mode, the cause is in the kernel or hardware, not user-mode software.

Bottom line: A 30-second freeze is a scheduled event, not random hardware noise. Start with SMB browsing, then disk retries, then Event Viewer correlation. One of those three resolves the vast majority of cases on Windows 11.