Windows 10: BsoD WHEA_UNCORRETABLE_ERROR

Discus and support BsoD WHEA_UNCORRETABLE_ERROR in Windows 10 BSOD Crashes and Debugging to solve the problem; Hey, i've been getting BsoD Whea_uncorretable_error every now and then. It can be once a week or once a day. So far i've ran intel diagnostic tool... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by DaimlerStool, May 22, 2020.

  1. BsoD WHEA_UNCORRETABLE_ERROR


    Hey, i've been getting BsoD Whea_uncorretable_error every now and then. It can be once a week or once a day. So far i've ran intel diagnostic tool couple of times, no errors. Memtest86 for over an hour, no errors. Prime95 for over an hour, no errors. Also done sfc /scannow a couple of times.


    Having Any OC or XMP enabled doesn't seem to have any effect since i've encountered it with and without any OC on. I've also reseted CMOS.


    Somehow i feel it is related to audio drivers since it happens more when i'm playing something and listening to music/stream in the backround and especially when a track changes to another. I also managed to get this when i opened my computer and immedialty started playing music from Spotify when it came to the desktop.


    Here's the latest minidump:


    WHEA_UNCORRECTABLE_ERROR 124

    A fatal hardware error has occurred. Parameter 1 identifies the type of error

    source that reported the error. Parameter 2 holds the address of the

    WHEA_ERROR_RECORD structure that describes the error conditon.

    Arguments:

    Arg1: 0000000000000000, Machine Check Exception

    Arg2: ffffa7816b0de028, Address of the WHEA_ERROR_RECORD structure.

    Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.

    Arg4: 0000000000030005, Low order 32-bits of the MCi_STATUS value.



    Debugging Details:

    ------------------



    fffff8007aa2a3d8: Unable to get Flags value from nt!KdVersionBlock

    fffff8007aa2a3d8: Unable to get Flags value from nt!KdVersionBlock

    fffff8007aa2a3d8: Unable to get Flags value from nt!KdVersionBlock

    fffff8007aa2a3d8: Unable to get Flags value from nt!KdVersionBlock

    fffff8007aa2a3d8: Unable to get Flags value from nt!KdVersionBlock

    fffff8007aa2a3d8: Unable to get Flags value from nt!KdVersionBlock

    fffff8007aa2a3d8: Unable to get Flags value from nt!KdVersionBlock

    fffff8007aa2a3d8: Unable to get Flags value from nt!KdVersionBlock



    KEY_VALUES_STRING: 1



    Key : Analysis.CPU.Sec

    Value: 5



    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on DESKTOP-0HG6M7A



    Key : Analysis.DebugData

    Value: CreateObject



    Key : Analysis.DebugModel

    Value: CreateObject



    Key : Analysis.Elapsed.Sec

    Value: 19



    Key : Analysis.Memory.CommitPeak.Mb

    Value: 70



    Key : Analysis.System

    Value: CreateObject



    BUGCHECK_CODE: 124



    BUGCHECK_P1: 0



    BUGCHECK_P2: ffffa7816b0de028



    BUGCHECK_P3: b2000000



    BUGCHECK_P4: 30005



    BLACKBOXBSD: 1 !blackboxbsd



    BLACKBOXNTFS: 1 !blackboxntfs



    BLACKBOXWINLOGON: 1



    CUSTOMER_CRASH_COUNT: 1



    PROCESS_NAME: Wow.exe



    STACK_TEXT:

    ffffce00`6ff2aad8 fffff800`7b0ff188 : 00000000`00000124 00000000`00000000 ffffa781`6b0de028 00000000`b2000000 : nt!KeBugCheckEx

    ffffce00`6ff2aae0 fffff800`7ef81920 : ffffa781`63b9b4f0 00000000`00000000 ffffa781`6b0de028 00000000`00000000 : hal!HalBugCheckSystem+0xd8

    ffffce00`6ff2ab20 fffff800`7a9410a2 : ffffa781`63b9b4f0 ffffce00`6ff2aba9 00000000`00000000 ffffa781`6b0de028 : PSHED!PshedBugCheckSystem+0x10

    ffffce00`6ff2ab50 fffff800`7b100ae6 : ffffce00`6ff2ac70 00000000`00000001 ffffa781`63b9b540 ffffa781`63b9b4f0 : nt!WheaReportHwError+0x382

    ffffce00`6ff2ac10 fffff800`7b100f7a : 00000000`00000010 ffffa781`63b9b540 ffffce00`6ff2adc8 ffffce00`6ff2b010 : hal!HalpMcaReportError+0x72

    ffffce00`6ff2ad70 fffff800`7b100e54 : ffffa781`638d99c0 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xf2

    ffffce00`6ff2adc0 fffff800`7b1010c0 : 00000000`00000006 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe0

    ffffce00`6ff2ae00 fffff800`7b100168 : 00000000`00000000 ffffce00`6ff2b090 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4

    ffffce00`6ff2ae30 fffff800`7b101347 : ffffa781`638d99c0 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c

    ffffce00`6ff2ae60 fffff800`7a8a4e40 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37

    ffffce00`6ff2ae90 fffff800`7a7d13ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10

    ffffce00`6ff2aec0 fffff800`7a7d106f : 00000000`00000000 00000000`00000000 000002a8`92555448 00000000`00000000 : nt!KxMcheckAbort+0x7a

    ffffce00`6ff2b000 00007ff7`3b378c29 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x26f

    000000cc`52dbe448 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff7`3b378c29



    MODULE_NAME: GenuineIntel



    IMAGE_NAME: GenuineIntel.sys



    STACK_COMMAND: .thread ; .cxr ; kb



    FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE_INTERNAL_PARITY



    OS_VERSION: 10.0.18362.1



    BUILDLAB_STR: 19h1_release



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    FAILURE_ID_HASH: {ad18667d-e4af-4a49-4062-3121e823755f}



    Followup: MachineOwner

    :)
     
    DaimlerStool, May 22, 2020
    #1
  2. ARC
    Arc Win User

    Random BSOD while browsing internet


    BitDefender is nothing special. mwac.sys causes BSODs anywhere.
    A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
    In that very thread, the suggested action apparently worked.

    The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
    As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
    That is why I posted that my suggestion may work, or may not. Let us see where it goes.
     
  3. cplpro Win User
    7 different BSoD

    Hey guys,

    I have a serious problem. I make it as short as possible:

    • system runs 100 % fine with the 10.12
    • updatet to Catalyst 11.1 -> BSoD
    • updatet to 11.1 Hotfix -> BSoD
    • rollback to 10.12 -> BSoD
    • removed ALL AMD files manually, installed 10.12 -> BSoD
    • Temps are fine
    • no sfc /scannow errors
    • no chkdsk errors
    • Prime, Furmark all fine
    • regardless what driver I install -> BSoD
    • I did no hw changes, no OC
    Here are my BSoDs I receive:
    • 0x0000010e
    • 0x1000007e
    • 0x0000007e
    • 0x0000004e
    • 0x0000003b
    • dxgmms1.sys
    • PFN_LIST_CORRUPT
    They all refer to the GPU of course ...

    From now on I receive a BSoD every time I try to play a game (especially BC2 and SC II) even if I completely remove the old driver and make a clean install.
    Apparently the 11.1 damaged my system irreparable.

    Any advice or info would be very much appreciated *Smile BsoD WHEA_UNCORRETABLE_ERROR :)
     
    cplpro, May 22, 2020
    #3
  4. axe0 Win User

    BsoD WHEA_UNCORRETABLE_ERROR

    BAD_POOL_HEADER BSOD, Dump File attached


    Hi Groggubus,

    Welcome to the 10forums BsoD WHEA_UNCORRETABLE_ERROR :)

    Please remove / disable items from the startup in taskmanager
    These programs could interfere with the boot process giving you trouble and increase the boot time.

    Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
    Please remove Daemon Tools and run the SPTD pass through remover.

    1. Uninstall Daemon Tools
    2. Download the SPTD standalone installer and follow these steps:
      • Double click the executable to open it
      • Click on the button shown below

    BsoD WHEA_UNCORRETABLE_ERROR [​IMG]

    If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window

    Please follow this suggestion for the BSOD
    1. Please open BitDefender and go to the modules,
    2. Go to the firewall settings,
    3. Uncheck 'Block port scans in the network',
    4. Reboot your system <-- IMPORTANT
     
Thema:

BsoD WHEA_UNCORRETABLE_ERROR

Loading...
  1. BsoD WHEA_UNCORRETABLE_ERROR - Similar Threads - BsoD WHEA_UNCORRETABLE_ERROR

  2. BSOD Crashing overnight and sometimes on log-in

    in Windows 10 BSOD Crashes and Debugging
    BSOD Crashing overnight and sometimes on log-in: Hello, I started having issues a week or two ago where the computer would restart overnight. At first I thought it was updates but it kept on happening. I looked at Event Viewer system logs and googled some of the errors I saw and most people seemed to have RAM troubles. I...
  3. Attempt to update 1909 to 2004 I have bsod in 85% on 3rd reboot. "page fault in nonpaged"

    in Windows 10 Ask Insider
    Attempt to update 1909 to 2004 I have bsod in 85% on 3rd reboot. "page fault in nonpaged": Update last bios and mother+video drivers, update to last 1909 and sfc/scannow+chkdsk C: /f /r but not help. r5 3600 b450-a pro max 1080ti 16gb setuperr log 2020-05-29 21:01:41, Error CSI 00000001 (F) STATUS_OBJECT_NAME_NOT_FOUND #10# from...
  4. Windows 10 1903 April 2020 update BSOD

    in Windows 10 Installation and Upgrade
    Windows 10 1903 April 2020 update BSOD: I installed the April, 2020 Windows updates for W10 1903 after the installation I am getting BSOD and when I can boot the computer. When I can get into Office 2016 click to run programs, Adobe Acrobat, the Control panel, Acronis True Image, the update uninstall screen, no...
  5. Never ending BSoDs

    in Windows 10 Ask Insider
    Never ending BSoDs: Hi guys, so yesterday morning I went to work on my Surface Pro 3 and I found it dead. No big deal, this happens a lot so I plugged it back in and let it charge up and turn on. When I turned it back on it started to update. I believe the update finished because my lock screen...
  6. Driver Power State Failure BSOD

    in Windows 10 Drivers and Hardware
    Driver Power State Failure BSOD: Hello, two days ago I built a custom computer. I have been having problems with BSOD. It says Driver Power State Failure, they ocurrur randomly and before they start windows starts lagging Mouse shutters and moving windows is lagging. I already have tried resetting Windows...
  7. Upgrading (or even a clean install) to Windows 10 2004 fails with two errors: (BSOD)

    in Windows 10 Ask Insider
    Upgrading (or even a clean install) to Windows 10 2004 fails with two errors: (BSOD): Summary of Issue Upgrading (or even a clean install) to Windows 10 2004 fails with two errors: (BSOD) DRIVER PNP WATCHDOG ERROR (installation continues after it dumps and reboots, but once in the OS the below mentioned problem exists) If I delete the AMD driver 20.5.1 and...
  8. NEW! SAHARA Termination BSOD

    in Windows 10 BSOD Crashes and Debugging
    NEW! SAHARA Termination BSOD: I Discovered A New Stop Code In BSOD Look This [ATTACH] https://answers.microsoft.com/en-us/windows/forum/all/new-sahara-termination-bsod/760a1832-7c9d-41a6-89a7-201293b93cbe
  9. BSOD WIN32K_POWER_WATCHDOG_TIMEOUT

    in Windows 10 BSOD Crashes and Debugging
    BSOD WIN32K_POWER_WATCHDOG_TIMEOUT: Hello, After connecting my laptop to an external monitor via HDMI, I'm faced with the BSOD error code as shown below. Is there something wrong with my driver or is the HDMI cable not suitable for my laptop? I have yet to try other monitor or cable yet. The problem occurs...
  10. I'm having semi regular BSOD and I'm not sure how to narrow down the problem.

    in Windows 10 BSOD Crashes and Debugging
    I'm having semi regular BSOD and I'm not sure how to narrow down the problem.: Firstly, I have 2 computers that are exactly the same and are only <6 months old. At first neither had any problems, nice and smooth as you'd expect but recently I have started to get BSOD's. I could have the computer on all day with nothing running and no crash. But if I...