A clean boot is the best next test because the freezing occurs only while Windows is idle or lightly loaded, which points to a startup service, background application, or driver entering a problematic state.
1. Test Windows in a clean-boot environment
Since Command Prompt repairs and several other fixes have already failed, do not repeat SFC, DISM, or CHKDSK now.
- Sign in with an administrator account.
- Search for msconfig, then open System Configuration.
- Select Services.
- Check Hide all Microsoft services—do not skip this—and select Disable all.
- Select Apply.
- Open Startup → Open Task Manager.
- Under Startup apps, record which entries are enabled, then disable each enabled entry.
- Close Task Manager, select OK, and restart.
- Leave the computer idle long enough that it would normally freeze. Some third-party functionality may be temporarily unavailable during this test. ^1^
If it does not freeze, re-enable half of the disabled non-Microsoft services, restart, and test again. Continue testing halves until one service is isolated. Then repeat that process with Startup apps. Update, uninstall, or leave the identified component disabled.
After testing, restore normal startup:
- Open msconfig.
- On General, select Normal startup.
- Re-enable the services and Startup apps that were not responsible.
- Restart.
If it still freezes during the clean boot, the problem is less likely to be an ordinary startup application or third-party service.
2. Check drivers and collect evidence
Idle-only freezing can involve hardware entering a low-power state, but the exact device cannot be identified without logs or a dump.
- Right-click Start → Device Manager.
- Look for devices displaying a yellow exclamation mark.
- Obtain current chipset, graphics, network, and storage drivers from the PC or motherboard manufacturer. Microsoft also recommends checking Settings → Windows Update → Advanced options → Optional updates for driver updates. ^2^
- After the next freeze and forced restart, open Event Viewer:
- Examine Windows Logs → System
- Examine Windows Logs → Application
- Focus on errors immediately before the freeze—not the later Kernel-Power event caused by holding the power button.
- Press Win+R, run the following, and wait while Windows generates a System Diagnostics report:
perfmon /report
Microsoft’s freeze-troubleshooting guidance specifically recommends reviewing the System and Application logs and generating this report after a physical computer recovers from a freeze. ^3^
If a blue or black stop screen ever appears, record its stop code and any displayed driver/module name. Windows stop errors may identify the hardware device, driver, or software involved. ^4^
3. Repair Windows without immediately downgrading
If the clean boot still freezes and no specific driver is identified, back up important files first, then use:
Settings → System → Recovery → Reinstall now under the option for fixing problems using Windows Update.
On Windows 11 version 22H2 or later, this reinstalls the current Windows version without affecting files, apps, or settings. If that option is unavailable, use the other recovery choices under Settings → System → Recovery, leaving Reset this PC until last because it is more disruptive. ^5^
About returning to Windows 10
If Settings → System → Recovery → Go back is available, rollback generally remains available for only 10 days after upgrading. It keeps personal files but removes apps and drivers installed after the upgrade and reverses subsequent settings changes. ^6^
However, Windows 10 support ended on October 14, 2025, so it no longer receives free security updates through ordinary Windows Update. Prefer isolating the conflicting service/driver or repairing Windows 11 rather than using Windows 10 as the long-term fix.
References