Share via

Event 1001 bugcheck

Ferdianta Tarigan 0 Reputation points
2026-03-26T05:01:20.4133333+00:00

hello everyone. i dont know since when it started but my laptop crashes sometime, when im browsing or doing something it just freeze and the screen change to your pc ran into problem and restarted. when i open the event viewer i see 1 eror cause by bugcheck and 1 critical event 41.

the bug check eror is like this: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000096, 0xfffff802a7c31f28, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\032626-17953-01.dmp. Report Id: b5b6d1cf-430f-4f2f-a808-8d0a297fd5e2

i have 5 file on that mini dump when i check
hope someone can help

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

2 answers

Sort by: Most helpful
  1. Thileep Kumar 4,095 Reputation points Independent Advisor
    2026-03-26T05:36:36.9666667+00:00

    Could you please share the minidump files?

    1. Open File Explorer and navigate to:

    C:\Windows\Minidump

    1. If you find any .dmp files, please zip them.
    2. Upload the zipped file to Google Drive, OneDrive, Dropbox, or any file-sharing site.
    3. Share the link here so I can analyze the files.

    Once I have the minidumps, I'll review them to identify what might be causing the crashes.


  2. Q&A Assist
    2026-03-26T05:01:32.6733333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Event ID 1001 with source WER-SystemErrorReporting and text “The computer has rebooted from a bugcheck” means Windows hit a blue screen (bug check) and then restarted. Event ID 41 Kernel-Power is the corresponding critical event that records the unexpected restart.

    The entry shown:

    The bugcheck was: 0x0000001e (0xffffffffc0000096, 0xfffff802a7c31f28, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\032626-17953-01.dmp.

    confirms that a crash dump was written. To find the cause, the minidump files must be analyzed with the Windows debugger tools (WinDbg or KD). In a debugging session, the .bugcheck command can be used to display the bug check data from the dump, and then !analyze can help identify the failing driver or module.

    Key points and next steps:

    1. Confirm the reboot cause in Event Viewer
      In Event Viewer → Windows Logs → System, filter for:
      • Event ID 1001 (source WER-SystemErrorReporting) – shows the bugcheck code and dump path.
      • Event ID 41 (source Kernel-Power) – indicates the system restarted without a clean shutdown.
    2. Collect the minidumps
      The path in the event (C:\WINDOWS\Minidump\*.dmp) contains the crash data. Copy the latest 3–5 .dmp files to a separate folder for analysis.
    3. Analyze the dumps with WinDbg (high‑level outline)
      • Install the Windows debugging tools (WinDbg).
      • Open WinDbg and load one of the .dmp files.
      • Run:
        • .bugcheck – to display the bug check code and parameters from the dump.
        • !analyze -v – to get a detailed analysis and see if a specific driver or module is blamed.
    4. If a driver is implicated
      Many bugchecks are caused by faulty or incompatible drivers. Once the problematic driver is identified from the dump analysis, update or remove that driver (for example, display, storage, or other third‑party drivers) using the vendor’s latest version.

    If further help is needed, share the output of .bugcheck and !analyze -v from one of the minidumps so that the failing component can be pinpointed more precisely.


    References:

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.