How to find out what caused BSOD?


  1. Posts : 241
    Windows 10 Pro
       #1

    How to find out what caused BSOD?


    I got a BSOD with the message "WHEA uncorrectable error" and nothing else specified
    Then it booted into BIOS repeatedly until I turned off the PC and turned on back again

    Is there a way to check now what caused this?

    Thanks
      My Computer


  2. Posts : 18,045
    Win 10 Pro 64-bit v1909 - Build 18363 Custom ISO Install
       #2

    Hello @mibaup,

    mibaup said:
    I got a BSOD with the message "WHEA uncorrectable error" and nothing else specified
    Then it booted into BIOS repeatedly until I turned off the PC and turned on back again

    Is there a way to check now what caused this?

    As part of the initial BSOD data collection for diagnostics, please perform the following . . .

     BSOD - Initial Data Collection

    [1] Please click the BSOD - Posting Instructions link below.

    • IMPORTANT: Read and follow the Instructions.

    [2] Download and Run the V2 & DM Log Collectors.

    • The log collectors scan necessary files and produce information that will allow us to help you with your issue.

    > BSOD - Posting Instructions

    I am sure that somebody [ @zbook ] will be able to help analyse the output data.

    Thanks.
      My Computer


  3. Posts : 241
    Windows 10 Pro
    Thread Starter
       #3

    Thank you, Chrome blocks the DM logger so I just copied a few Critical and Error logs I see from the same time of the BSOD:

    1) Critical error (There are 4 of them, I guess because of 4 total BSODs so far):

    Log Name: SystemSource: Microsoft-Windows-Kernel-PowerDate: 27/02/2021Event ID: 41Task Category: (63)Level: CriticalKeywords: (70368744177664),(2)User: SYSTEMComputer: DESKTOP-Z3THE3VDescription:The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{321c3b3x-2015-44c2-bc5e-77220c326b4}" /> <EventID>41</EventID> <Version>8</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2021-02-27T10:49:19.7972293Z" /> <EventRecordID>2211</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>DESKTOP-Z3THE3V</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">292</Data> <Data Name="BugcheckParameter1">0x10</Data> <Data Name="BugcheckParameter2">0x0</Data> <Data Name="BugcheckParameter3">0x0</Data> <Data Name="BugcheckParameter4">0x0</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">0</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> <Data Name="BugcheckInfoFromEFI">true</Data> <Data Name="CheckpointStatus">0</Data> <Data Name="CsEntryScenarioInstanceIdV2">0</Data> <Data Name="LongPowerButtonPressDetected">false</Data> </EventData></Event>

    Also, 1400(yes, thousand+) disk errors in the time before the Critical BSOD happened (like 4 of these identical errors per second)

    Log Name: SystemSource: diskDate: 27/02/2021Event ID: 7Task Category: NoneLevel: ErrorKeywords: ClassicUser: N/AComputer: DESKTOP-Z3THE3VDescription:The device, \Device\Harddisk0\DR0, has a bad block.Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="disk" /> <EventID Qualifiers="49156">7</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2021-02-27T20:00:49.5384342Z" /> <EventRecordID>1830</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="9948" /> <Channel>System</Channel> <Computer>DESKTOP-Z3THE3V</Computer> <Security /> </System> <EventData> <Data>\Device\Harddisk0\DR0</Data> <Binary>030080000100000000000000070004C0000100009C0000C000000000000000000000DE33400000004D9902000000 0000FFFFFFFF01000000580000840200000049200AFF42072040001000000A0000000000000000000000302AF0998E9AFFFF 0000000000000000204A5E9A8E9AFFFF0000000000000000000000000000000028002019EF0000000800000000000000F000 03000000000A00000000110000000000000000000000</Binary> </EventData></Event>
    Could it be that my NVME is faulty? Or it still can't be determined what's causing the disk to throw errors?
      My Computer


  4. Posts : 18,045
    Win 10 Pro 64-bit v1909 - Build 18363 Custom ISO Install
       #4

    Hello @mibaup,

    You could check the integrity of the Disk . . .

     Hard Disk Sentinel

    First, check your HDD using the Hard Disk Sentinel Portable Trial Version.

    About HardDiskSentinel:

    HardDiskSentinel is a computer Hard Disk Drive monitoring software for Windows, Linux and DOS operating systems.

    Hard Disk Sentinel [ HDSentinel ] is a multi-OS SSD and HDD monitoring and analysis software. Its goal is to find, test, diagnose and repair hard disk drive problems, report and display SSD and HDD health, performance degradations and failures. Hard Disk Sentinel gives complete textual description, tips and displays/reports the most comprehensive information about the hard disks and Solid State Disks inside the computer and in external enclosures [ USB hard disks / e-SATA hard disks ].

    You can run it directly from a USB, and in my opinion, this gives the best instant report available compared to other software of the same type.

    > Website => Hard Disk Sentinel
    > Download Page => Download Hard Disk Sentinel - Portable

    I hope this helps.
      My Computer


  5. Posts : 241
    Windows 10 Pro
    Thread Starter
       #5

    It's a new Samsung 970 Evo NVME 500GB, does this tool work with NVMEs?

    *Edit: Just saw that it does, will give it a try

    - - - Updated - - -

    Update: Sentinel says my disk is "Perfect"...
    But, still I get those random BSODs and reboot loops into BIOS. And after each BSOD the BIOS does not recognize the NVME. Until a few reboots later it recognizes it again. Is it motherboard hardware issue? BIOS version issue? SSD issue?
      My Computer


  6. Posts : 18,045
    Win 10 Pro 64-bit v1909 - Build 18363 Custom ISO Install
       #6

    Hello @mibaup,

    mibaup said:
    I got a BSOD with the message "WHEA uncorrectable error" and nothing else specified
    Then it booted into BIOS repeatedly until I turned off the PC and turned on back again

    Is there a way to check now what caused this?

    That message does point to some sort of Hardware issue.

    Can you physically check that the RAM is correctly seated. Also, please perform the following . . .

     MemTest86+ - Test RAM

    About MemTest86+:

    MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:
    • RAM will accept and keep random patterns of data sent to it.
    • There are no errors when different parts of memory try to interact.
    • There are no conflicts between memory addresses.

    Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    > MemTest86+ - Test RAM With

    I hope this helps.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 09:04.
Find Us




Windows 10 Forums