Windows 10: WHEA_UNCORRECTABLE_ERROR most probably caused by genuine intel sys

Discus and support WHEA_UNCORRECTABLE_ERROR most probably caused by genuine intel sys in Windows 10 Ask Insider to solve the problem; Hi. Just got a BSOD while gaming. Please help me find what caused the error and what could i do to fix it. Here's the bugcheck: Microsoft (R) Windows... Discussion in 'Windows 10 Ask Insider' started by /u/_space_pilgrim_, Mar 12, 2021.

  1. /U/_SPACE_PILGRIM_
    /u/_space_pilgrim_ Win User

    WHEA_UNCORRECTABLE_ERROR most probably caused by genuine intel sys


    Hi. Just got a BSOD while gaming. Please help me find what caused the error and what could i do to fix it. Here's the bugcheck:

    Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Users\georg\Desktop\031221-9906-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available



    Symbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 19041 MP (8 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Built by: 19041.1.amd64fre.vb_release.191206-1406

    Machine Name:

    Kernel base = 0xfffff802`4ce00000 PsLoadedModuleList = 0xfffff802`4da2a490

    Debug session time: Fri Mar 12 23:05:48.343 2021 (UTC + 2:00)

    System Uptime: 1 days 10:22:07.814

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ................................................................

    ....................

    Loading User Symbols

    Loading unloaded module list

    ..................................................

    For analysis of this file, run !analyze -v

    2: kd> !analyze -v

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************



    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: ffffce82121ac028, Address of the WHEA_ERROR_RECORD structure.

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

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



    Debugging Details:

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



    fffff8024da0f330: Unable to get Flags value from nt!KdVersionBlock

    fffff8024da0f330: Unable to get Flags value from nt!KdVersionBlock

    *************************************************************************

    *** ***

    *** ***

    *** Either you specified an unqualified symbol, or your debugger ***

    *** doesn't have full symbol information. Unqualified symbol ***

    *** resolution is turned off by default. Please either specify a ***

    *** fully qualified symbol module!symbolname, or enable resolution ***

    *** of unqualified symbols by typing ".symopt- 100". Note that ***

    *** enabling unqualified symbol resolution with network symbol ***

    *** server shares in the symbol path may cause the debugger to ***

    *** appear to hang for long periods of time when an incorrect ***

    *** symbol name is typed or the network symbol server is down. ***

    *** ***

    *** For some commands to work properly, your symbol path ***

    *** must point to .pdb files that have full type information. ***

    *** ***

    *** Certain .pdb files (such as the public OS symbols) do not ***

    *** contain the required information. Contact the group that ***

    *** provided you with these symbols if you need this command to ***

    *** work. ***

    *** ***

    *** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***

    *** ***

    *************************************************************************

    fffff8024da0f330: Unable to get Flags value from nt!KdVersionBlock

    *************************************************************************

    *** ***

    *** ***

    *** Either you specified an unqualified symbol, or your debugger ***

    *** doesn't have full symbol information. Unqualified symbol ***

    *** resolution is turned off by default. Please either specify a ***

    *** fully qualified symbol module!symbolname, or enable resolution ***

    *** of unqualified symbols by typing ".symopt- 100". Note that ***

    *** enabling unqualified symbol resolution with network symbol ***

    *** server shares in the symbol path may cause the debugger to ***

    *** appear to hang for long periods of time when an incorrect ***

    *** symbol name is typed or the network symbol server is down. ***

    *** ***

    *** For some commands to work properly, your symbol path ***

    *** must point to .pdb files that have full type information. ***

    *** ***

    *** Certain .pdb files (such as the public OS symbols) do not ***

    *** contain the required information. Contact the group that ***

    *** provided you with these symbols if you need this command to ***

    *** work. ***

    *** ***

    *** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***

    *** ***

    *************************************************************************



    KEY_VALUES_STRING: 1



    Key : Analysis.CPU.Sec

    Value: 5



    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on DESKTOP-CAUECJ8



    Key : Analysis.DebugData

    Value: CreateObject



    Key : Analysis.DebugModel

    Value: CreateObject



    Key : Analysis.Elapsed.Sec

    Value: 33



    Key : Analysis.Memory.CommitPeak.Mb

    Value: 82



    Key : Analysis.System

    Value: CreateObject





    BUGCHECK_CODE: 124



    BUGCHECK_P1: 0



    BUGCHECK_P2: ffffce82121ac028



    BUGCHECK_P3: be000000



    BUGCHECK_P4: 800400



    CUSTOMER_CRASH_COUNT: 1



    PROCESS_NAME: FIFA21.exe



    STACK_TEXT:

    ffffa380`d3f798e8 fffff802`4d2b3a6a : 00000000`00000124 00000000`00000000 ffffce82`121ac028 00000000`be000000 : nt!KeBugCheckEx

    ffffa380`d3f798f0 fffff802`4a1b15b0 : 00000000`00000000 ffffce82`121ac028 ffffce82`09bdcc90 ffffce82`121ac028 : nt!HalBugCheckSystem+0xca

    ffffa380`d3f79930 fffff802`4d3b55fe : 00000000`00000000 ffffa380`d3f799d9 ffffce82`121ac028 ffffce82`09bdcc90 : PSHED!PshedBugCheckSystem+0x10

    ffffa380`d3f79960 fffff802`4d2b5391 : ffffce82`1203e4c0 ffffce82`1203e4c0 ffffce82`09bdcce0 ffffce82`09bdcc90 : nt!WheaReportHwError+0x46e

    ffffa380`d3f79a40 fffff802`4d2b5703 : 00000000`00000002 ffffce82`09bdcce0 ffffce82`09bdcc90 00000000`00000002 : nt!HalpMcaReportError+0xb1

    ffffa380`d3f79bb0 fffff802`4d2b55e0 : ffffce82`09af8660 0001a8c4`00000001 00000000`00000000 ccccc35d`5b5e5f5c : nt!HalpMceHandlerCore+0xef

    ffffa380`d3f79c00 fffff802`4d2b5831 : 00000000`00000008 00000000`00000001 00000000`00000000 41bf7589`4cfe8b45 : nt!HalpMceHandler+0xe0

    ffffa380`d3f79c40 fffff802`4d2b4a9b : 00000000`00000000 00000000`00000000 ffffa380`d3f79ed0 c98548cb`758944df : nt!HalpMceHandlerWithRendezvous+0xc9

    ffffa380`d3f79c70 fffff802`4d2b72e5 : ffffce82`09af8660 000b9a84`0fc08548 30894d28`39836600 0538bf0a`74318945 : nt!HalpHandleMachineCheck+0x5f

    ffffa380`d3f79ca0 fffff802`4d30ca29 : 000002bd`41ffaaa5 b70ffd03`490beb00 c085ffaa`a51ae80f cd75223f`8366f175 : nt!HalHandleMcheck+0x35

    ffffa380`d3f79cd0 fffff802`4d204cfa : 491574c9`85661a74 72c63b01`468ddd03 0216bfe1`ebf08b04 22f98366`7aeb0000 : nt!KiHandleMcheck+0x9

    ffffa380`d3f79d00 fffff802`4d2049b7 : ffffa380`00000000 fffff802`4d2048ec 00000001`00000036 00000000`00000000 : nt!KxMcheckAbort+0x7a

    ffffa380`d3f79e40 fffff802`4d0de1af : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277

    ffffdf81`bb1bf9c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiUpdateStibpPairing+0x28f





    MODULE_NAME: GenuineIntel



    IMAGE_NAME: GenuineIntel.sys



    STACK_COMMAND: .thread ; .cxr ; kb



    FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR__UNKNOWN



    OS_VERSION: 10.0.19041.1



    BUILDLAB_STR: vb_release



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    FAILURE_ID_HASH: {86f02343-3a24-6d22-b341-ad6c04114faf}



    Followup: MachineOwner

    ---------

    submitted by /u/_space_pilgrim_
    [link] [comments]

    :)
     
    /u/_space_pilgrim_, Mar 12, 2021
    #1
  2. HORUS-3-ECHO
    Horus-3-Echo Win User

    QCAMAIN1.SYS CAUSING BSOD

    This was probably caused by the following module:
    qcamain1.sys (Qcamain10x64+0x108678)

    Bugcheck code: 0x1D3 (0x333, 0x0, 0x0, 0x0)

    Error: CUSTOM_ERROR

    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: qcamain1.sys .

    Google query: qcamain1.sys CUSTOM_ERROR

    Using WhoCrashed I found this thread: QCAMAIN1.SYS CAUSING BSOD (Code 37 Error) however without
    solution, locked.

    I did get BSOD almost everytime I moved the laptop.

    This worked for me:

    unscrew wifi module, push a little into the socket. Screw in. DONE
     
    Horus-3-Echo, Mar 12, 2021
    #2
  3. VIJAY_VERMA
    Vijay_Verma Win User
    Lot of WHEA_UNCORRECTABLE_ERROR (124) on intel nuc NUC7i3BN and 1809 17763.104

    Analysis

    File Name: 092018-6718-01.dmp

    BugCheck 124

    Probably caused by : GenuineIntel

    File Name: 092018-9953-01.dmp

    BugCheck 1A

    Probably caused by : memory_corruption

    File Name: 092218-11843-01.dmp

    BugCheck EF

    Probably caused by : ntkrnlmp.exe

    File Name: 100518-9062-01.dmp

    BugCheck 9F

    Probably caused by : Unknown_Image

    File Name: 100918-10265-01.dmp

    BugCheck 124

    Probably caused by : GenuineIntel

    *** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys

    File Name: 101718-15312-01.dmp

    BugCheck 124

    Probably caused by : GenuineIntel

    *** ERROR: Module load completed but symbols could not be loaded for zam64.sys

    *** ERROR: Module load completed but symbols could not be loaded for ehdrv.sys

    File Name: 101818-7734-01.dmp

    BugCheck 124

    Probably caused by : GenuineIntel

    *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys

    *** ERROR: Module load completed but symbols could not be loaded for eamonm.sys

    File Name: 102818-9390-01.dmp

    BugCheck 124

    Probably caused by : GenuineIntel

    DRIVERS

    Driver Name: iaStorA.sys - Intel RST (Rapid Storage Technology) driver

    Driver Date: 12-Oct-2017

    Driver Name: zam64.sys - Zemana ZAM AntiMalware driver

    Driver Date: 17-Aug-2016

    Driver Name: ehdrv.sys - ESET

    Driver Date: 7-Aug-2018

    Driver Name: igdkmd64.sys - Intel Graphics driver

    Driver Date: 15-Aug-2018

    Driver Name: eamonm.sys - ESET Amon driver

    Driver Date: 16-Aug-2018

    Recommendations

    1. Create a system restore point so that if something wrong happens you can revert.

    2. Uninstall ZAM AntiMaware (or try to update if you have a version beyond date given in zam64.sys)

    3. Uninstall ESET (or try to update if you have a version beyond date given in ehdrv.sys and eamonm.sys)

    4. Update your Intel Graphics driver

    4. Download latest driver Intel RST driver from and install
    https://downloadcenter.intel.com/download/27984...

    You need to download f6flpy-x64.zip (64-bit Operating System) / f6flpy-x86.zip (32bit Operating System)

    5. Run Memtest for at least 8 passes (Do it overnight before going to bed)

    https://www.tenforums.com/tutorials/14201-memte...
     
    Vijay_Verma, Mar 12, 2021
    #3
  4. AXE0
    axe0 Win User

    WHEA_UNCORRECTABLE_ERROR most probably caused by genuine intel sys

    System_Thread_Exception_Not_Handled dxgmms2.sys


    Hi Asellia,

    Welcome to the 10forums.


    What driver versions have you tried currently for your graphics?
    If it is the newest version, 361.43, try rolling back the drivers.
    Driver Rollback | NVIDIA
    Code:
    Code:
    Probably caused by : dxgmms2.sys ( dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+3a )  7: kd> lmvm nvlddmkmstart             end                 module name fffff800`cf870000 fffff800`d048b000   nvlddmkm   (deferred)                  Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys     Image name: nvlddmkm.sys     Timestamp:        Wed Dec 16 15:03:30 2015 (56716F32)     CheckSum:         00BE13AE     ImageSize:        00C1B000     Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    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

    WHEA_UNCORRECTABLE_ERROR most probably caused by genuine intel sys [​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
     
    axe0, Mar 12, 2021
    #4
Thema:

WHEA_UNCORRECTABLE_ERROR most probably caused by genuine intel sys

Loading...

  1. WHEA_UNCORRECTABLE_ERROR most probably caused by genuine intel sys - Similar Threads - WHEA_UNCORRECTABLE_ERROR probably caused

  2. Probable cause of "CRITICAL_STRUCTURE_CORRUPTION" BSOD

    in Windows 10 Gaming
    Probable cause of "CRITICAL_STRUCTURE_CORRUPTION" BSOD: This is my first experience with this specific BSOD. I have not manually updated any drivers recently so I'm not quite sure of the issue, although it could be related to the NVIDIA display drivers I installed approx 1 month ago.Microsoft R Windows Debugger Version...

  3. Probable cause of "CRITICAL_STRUCTURE_CORRUPTION" BSOD

    in Windows 10 Software and Apps
    Probable cause of "CRITICAL_STRUCTURE_CORRUPTION" BSOD: This is my first experience with this specific BSOD. I have not manually updated any drivers recently so I'm not quite sure of the issue, although it could be related to the NVIDIA display drivers I installed approx 1 month ago.Microsoft R Windows Debugger Version...

  4. WHEA_UNCORRECTABLE_ERROR BSOD related to Genuine Intel, PSHED.dll and NTOSKRNL.exe.

    in Windows 10 Gaming
    WHEA_UNCORRECTABLE_ERROR BSOD related to Genuine Intel, PSHED.dll and NTOSKRNL.exe.: Hello, I have been getting WHEA_UNCORRECTABLE_ERROR BSOD's for over 2 months on my Windows 11 desktop. I am not good with computers at all.After gaming for more than 30 minutes, I get the blue screen followed by a loud continuous buzzing sound. At first, I used bluescreen...

  5. WHEA_UNCORRECTABLE_ERROR BSOD related to Genuine Intel, PSHED.dll and NTOSKRNL.exe.

    in Windows 10 Software and Apps
    WHEA_UNCORRECTABLE_ERROR BSOD related to Genuine Intel, PSHED.dll and NTOSKRNL.exe.: Hello, I have been getting WHEA_UNCORRECTABLE_ERROR BSOD's for over 2 months on my Windows 11 desktop. I am not good with computers at all.After gaming for more than 30 minutes, I get the blue screen followed by a loud continuous buzzing sound. At first, I used bluescreen...

  6. What is causing this WHEA_UNCORRECTABLE_ERROR

    in Windows 10 BSOD Crashes and Debugging
    What is causing this WHEA_UNCORRECTABLE_ERROR: About two weeks ago, my system started getting random BSODs with different error messages. They increased in frequency until i couldn't boot into windows any more. So, I cleaned the SSD and installed a new windows10. after about a day a BSOD with the...

  7. WHEA_UNCORRECTABLE_ERROR caused by hal.dll

    in Windows 10 BSOD Crashes and Debugging
    WHEA_UNCORRECTABLE_ERROR caused by hal.dll: So I just built a new pc a few months ago, and lately it's been crashing quite often and the error message is WHEA_UNCORRECTABLE_ERROR so I tried to diagnose what the problem is and here is what I got On Sat 2020-07-18 22:59:32 your computer crashed or a problem was...

  8. Frequent BSOD - WHEA_Uncorrectable_Error with either the hal.dll OR rt64.sys

    in Windows 10 BSOD Crashes and Debugging
    Frequent BSOD - WHEA_Uncorrectable_Error with either the hal.dll OR rt64.sys: Hi all, I've tried a lot of solutions on my own / researched in order to fix this problem and I can't seem to figure it out. The error occurs often when I am streaming games or using zoom. I can't explain what the catalyst is for the issue but it will occur anywhere...

  9. WHEA_Uncorrectable_Error // hal.dll AND rt64.sys

    in Windows 10 BSOD Crashes and Debugging
    WHEA_Uncorrectable_Error // hal.dll AND rt64.sys: Hi all, I've tried a lot of solutions on my own / researched in order to fix this problem and I can't seem to figure it out. The error occurs often when I am streaming games or using zoom. I can't explain what the catalyst is for the issue but it will occur anywhere...

  10. hal.dll causing BSOD WHEA_UNCORRECTABLE_ERROR

    in Windows 10 BSOD Crashes and Debugging
    hal.dll causing BSOD WHEA_UNCORRECTABLE_ERROR: Hello all! Yesterday I was playing some videogames in my Acer Nitro 5 AN515-52 and suddenly I had this BSOD crash in my computer. At first I thought it was just a one time thing but when the PC restarted it appeared again and again after some time. I've found it could be...

Users found this page by searching for:

  1. genuineintel.sys bsod

    ,

  2. genuineintel.sys