Continuous Crashing with no apparent vause

Shaurya Gupta 20 Reputation points
2026-10-14T17:56:59.3866667+00:00

My PC has just started hanging/crashing out of the blue today. I could be on a call and it'd still run fine however any function would not work such as clicking, and every program would go unresponsive. I have updated my graphics driver and it didnt fix the issue. I get the message that Microsoft Windows has stopped working and i get the option to end process if required. I saw nothing in the reliability monitor and I sent my event logs into an AI which could not find anything major apart of Bugcheck:0 (No logs made), I have attempted to open logs and diagnose the problem however I am unable to do so, even with an AI or IDE they have been unable to diagnose the issue.

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

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ian-T 14,220 Reputation points Microsoft External Staff Moderator
    2026-10-15T04:42:18.54+00:00

    Hi @Shaurya Gupta

    First, please feel free to check out the AI answer

    Since the call audio continues while the Windows interface and applications stop responding, this sounds more like a system hang than a normal blue-screen crash. Bugcheck: 0 does not identify the cause by itself, so I would avoid assuming that the graphics driver is responsible.

    As the next test, perform a clean boot to temporarily disable non-Microsoft services and startup applications. Use the PC normally afterward and check whether the freezing returns. If it remains stable, re-enable the disabled items gradually until the conflicting software is identified.

    You can also press Win + R, enter: perfmon /report

    Let the System Diagnostics report complete, then check whether it identifies resource exhaustion, disk delays, or a repeatedly failing process.

    If the PC still freezes during a clean boot, restart in Safe Mode and test there. A freeze that also occurs in Safe Mode would make a hardware, storage, firmware, or core Windows issue more likely. If it does not occur, the cause is more likely a third-party service, driver, or startup application.

    Also, when the next freeze happens, try Ctrl + Alt + Delete. Please mention whether that screen appears and whether the Caps Lock light still responds, as this helps distinguish a full hardware-level hang from an Explorer or application-level freeze.

    I hope this helps, feel free to let me know if you need any further assistance

    Was this answer helpful?

  2. AI answer

    2026-10-14T17:57:18.8+00:00

    Bugcheck: 0 with no dump/logs often means Windows could not write the crash information. A common reason is a dump configuration problem, especially pagefile configuration. If Event ID 41 shows all zeros, check whether volmgr Event ID 46 is also present: Crash dump initialization failed! That indicates the system may have started without a configured dump file, and the default dump file is the pagefile.

    Use this troubleshooting path:

    1. Open Event Viewer and check Windows Logs > System around the time of the freeze/restart.
      • Look for critical errors in the same time window.
      • If Event ID 41 is present with zero values, also check for volmgr Event ID 46.
    2. Check whether crash dump creation is failing because of pagefile settings.
      • If Event ID 46 is present, review the pagefile configuration.
      • If Windows cannot write a dump, the system can still bugcheck, but the bugcheck type may not appear in Event ID 41 and no memory dump may be generated.
    3. Since the system becomes unresponsive rather than always showing a blue screen, treat hardware as a primary suspect.
      • Disable overclocking and test again.
      • Check memory health and configuration. Make sure memory modules are running at the same speed and are configured correctly.
      • Run Windows Memory Diagnostics: in Control Panel, search for Memory, then select Diagnose your computer's memory problems. After the test, review Event Viewer for MemoryDiagnostics-Results in the System log.
      • Check the power supply. If hardware was added recently, the PSU may not be supplying enough power consistently.
      • Check for overheating.
    4. Check for recent driver, service, or hardware changes.
      • Remove or update any recently added device drivers or system services.
      • If any new hardware was added, remove or replace it temporarily to test.
      • Open Device Manager and look for devices marked with !. Review the device properties and related events for a faulting driver.
    5. Run system integrity and malware checks.
      • Run System File Checker: 
             SFC /scannow
      • Run a virus detection program, including a check of the Master Boot Record.
    6. If the issue continues, collect a dump for analysis.
      • Dump analysis is the next step when the cause is not obvious.
      • If a dump can be generated, tools such as DumpChk and the Windows SDK debugging tools can be used to inspect it.

    Most stop errors are caused by third-party drivers or hardware issues, so the highest-value checks are: pagefile/dump configuration, memory test, Device Manager driver review, recent hardware/driver changes, PSU, and overheating.

    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.