Outstanding system instability and BSOD events

User 0 Reputation points
2026-09-14T23:24:50.3533333+00:00

Hi,

We have multiple devices with outstanding operating system related issues which require technical attention.

Two devices named device1 and device2 are custom built, and are owned and used by one of our client as their CAD computers.

  • device2 Windows 11 PRO

This device has been experiencing long-term issues resulting in frequent BSOD events.  

  • What we have found  

Event Viewer logs characteristic of BSOD BugCheck events

Event Viewer logs indicating corrupt file system (likely caused by forceful shutdowns due to BSOD events)  

BugCheck memory dump logs indicate CPU hung thread forcefully stopped while handling a core system process by the kernel watchdog program.  

Bitdefender antivirus scans reporting clean

  • What we have tried  

Windows11OS updates  

Re-installation of Windows11OS  

BIOS update to latest version

 > sfc, dism, chkdsk  

Installation of new CPU  

Installation of new RAM  

RAM health diagnostics with MemTest64  

DSK health diagnostics with CrystalDiskInfo  

Hardware stress testing with CineBench, FurMark, CrystalDiskMark

  • device1  Windows 11 PRO

This device has been experiencing long-term issues resulting in frequent BSOD events, however less significant then the other device.

  • What we have found  

Event Viewer logs characteristic of BSOD BugCheck events  

Event Viewer logs indicating corrupt file system (likely caused by forceful shutdowns due to BSOD events)  

BugCheck memory dump logs indicate CPU hung thread forcefully stopped while handling a core system process by the kernel watchdog program.  

Latest memory dump logs consistently fail to generate and we cannot actually find out what exactly is causing the issue anymore  

Bitdefender antivirus scans reporting clean

  • What we have tried  

Windows11OS updates  

Re-installation of Windows11OS  

BIOS update to latest version  

sfc, dism, chkdsk  

RAM health diagnostics with MemTest64  

DSK health diagnostics with CrystalDiskInfo  

Hardware stress testing with CineBench, FurMark, CrystalDiskMark  

  • Other
  • Notes  

We find that the devices always pass our stress tests  

We find that the devices always persist with their issues after the client uses them  

We have kept the devices up to date with the latest Windows and manufacturer firmware/patches/updates  

We have already contacted the company whom built the PCs for our client and they have not found a solution  

we have not been able to link the issues with any particular pieces of software

device2 - We have investigated the errors and have connected  CPU hanging with bad Windows update impacting Intel CPUs causing hung threads and failure  

device1 - Recently a bad Windows update (Windows 11 KB5094126) caused the device to be unbootable which as resolved by re-installing Windows11OS after repair and recovery attempts were made.

I am compiling the hardware and crash reports for both devices now, and will provide these soon.

Any assistance will be greatly appreciated.

Windows for home | Windows 11 | Performance and system failures
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Alex-L 12,570 Reputation points Microsoft External Staff Moderator
    2026-09-17T09:42:07.62+00:00

    Hi User

    Thanks for the detailed information. Based on the troubleshooting already performed, the next most useful step is likely the collection and analysis of the crash artifacts you mentioned (minidumps, MEMORY.DMP, and hardware reports). At this stage, repeated OS reinstalls and generic diagnostics are unlikely to provide additional insight.

    A few observations:

    • The fact that both systems pass synthetic stress tests but become unstable during normal CAD workloads may point to a driver, firmware, storage, or workload-specific interaction rather than a simple CPU or RAM fault.
    • The file system corruption events may be a consequence of the BSODs rather than the root cause.
    • For device1, it would be useful to investigate why dump generation is failing, as the absence of current dumps makes root-cause analysis much more difficult.
    • Once the dump files and hardware reports are available, please share them so the stop codes, faulting modules, and stack traces can be reviewed in more detail.

    Also, while you mentioned suspected Windows update involvement, it would be difficult to attribute the crashes to a specific update without dump analysis showing a consistent pattern or a known issue affecting the hardware involved.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-09-14T23:25:14.1833333+00:00

    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.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.