Outstanding system instability and BSOD events

For both Windows 11 devices, the supported next steps are to focus on drivers, recent hardware or system changes, system logs, and memory diagnostics rather than repeating OS reinstall or general stress tests.

1. Check for recent driver or system-service changes Stop errors are most commonly caused by third-party driver code. Remove or update any recently added device drivers or system services, and identify any recent configuration changes that line up with when the BSODs began.
2. Review Device Manager on both devices Right-click Start > Device Manager. Look for any device marked with an exclamation point (!). For any affected device:
   • Select Update driver.
   • If that does not help, try Disable device or Uninstall device. This is especially relevant since the systems pass synthetic stress tests but still fail during real client usage, which is consistent with device or driver-triggered stop errors.
3. Check Event Viewer around each crash window In Event Viewer, review the System log for critical or error events that occurred in the same time frame as each BSOD. Look for entries that help identify the faulting device or driver. If a specific driver name appears on screen or in logs, disable that driver or obtain an updated version from the manufacturer.
4. Run Windows Memory Diagnostics even if third-party RAM tests passed In Control Panel, search for Memory, then select Diagnose your computer's memory problems. After the test completes, open Event Viewer and check the System log for MemoryDiagnostics-Results. This is worth doing because Microsoft’s stop-code guidance explicitly calls for this workflow.
5. Temporarily remove or replace recently added hardware If either device had hardware changes near the start of the issue, remove or replace that hardware and retest. Also confirm compatibility of installed hardware with the current Windows version.
6. Check free disk space Ensure each system has roughly 10% to 15% free disk space available. Windows and applications need free space for swap files and related operations.
7. Install the latest Windows 11 updates Go to Start > Settings > Windows Update > Check for updates. Since updates were already applied, this step is mainly to confirm both systems are fully current after the reinstall and repair cycles.
8. Use Safe Mode for isolation If crashes are frequent, start the PC in Safe Mode and test there. If stability improves in Safe Mode, that strongly points to a driver, service, or related software loaded during normal startup.
9. If basic steps do not resolve it, use recovery options Use a system restore point or another option under Recovery options in Windows 11. This carries some risk of rollback or app removal depending on the recovery method chosen.
10. For device2’s “hung thread” pattern, prioritize driver and power-state investigation Microsoft guidance for stop errors specifically calls out driver-related failures and recommends checking Event Viewer, Device Manager, and recently added drivers/services. If the issue occurs around sleep, resume, or power transitions, temporarily disable power saving in Control Panel > Power Options to isolate power-state driver issues.
11. For device1 where newer dumps are not being generated The supported guidance in the provided material is to continue using Event Viewer system logs and Device Manager to identify the faulting device or driver when dump data is unavailable.
12. If a recent driver update appears in logs, roll it back or remove it Example event-log guidance shows that a recently installed service or driver can indicate the trigger. If the crash timing matches a recent driver update, remove or roll back that update and retest.

Given the history provided, the strongest supported conclusion is that these recurring BSODs should be treated first as driver, device, or hardware-compatibility issues, not as proof of a Windows update defect. Microsoft’s troubleshooting data states that most stop errors are caused by third-party drivers, with hardware issues also being a significant cause.

• Troubleshooting Windows unexpected restarts and stop code errors
• Advanced troubleshooting for stop code errors
• Bug checks (stop code errors)
• Stop errors and unexpected restart troubleshooting guidance
• Troubleshoot unexpected reboots using system event logs