Blue Screen 0x124 - WHEA_UNCORRECTABLE_ERROR

Anonymous
2010-06-19T14:51:54+00:00

Original Title: "Getting BSoD ... I am using Intel S5520sc MB and dual xeon e5620 processor"

I am continuiously getting BSoD. I am using Intel S5520sc MB and dual xeon e5620 processors, Nvidia Quadro Fx 4800. I have updated intel bios and reinstalled windows 7. But i am still getting BSoD. I am looking forward for your solution to help me out of this problems. It will be kind of you ppl if help me sorting the problem as soon as possible.

Almost forgot i checked the mini dump file from BlueScreenView what i got wasa hal.dll+12903 and ntoskrnl.exe+186513

Regards

Jibran Hanif

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2010-06-19T15:52:48+00:00

Verifier picked on Lycosa.sys, as Andre mentioned.

The other dump showed a  0x124 - that's WHEA_UNCORRECTABLE_ERROR - "This bug check indicates that a fatal hardware error has occurred."  This can indicate that you have  some faulty hardware, unfortunately, probably the processor or perhaps the motherboard. Additional things you can try, though, just to see... Ensure that the system has adequate cooling and ventilation. Test RAM, reseat RAM and the processor if you can.  If the BIOS is the latest, consider reverting to a previous version and see if that helps.  If not, upgrade to the newest BIOS available.  Also double-check BIOS settings; perhaps, note current settings, reset the BIOS defaults, and then adjust those settings you know are necessary to adjust.  Double-check voltage, etc. and ensure/verify CPU compatibility with the motherboard.  If you're overclocking, stop.

The specific details about the hardware error you encountered indicate a fatal machine check exception due to Micro-Architectural Error (X64_0x124_GenuineIntel_PROCESSOR_MAE).  The specific reason is difficult to assess - it is characterized as "Internal unclassified".  

You do have a few stale drivers that you could remove or update to check the issue, but if that doesn't have an effect, focus on the referenced hardware.

mcdbus.sys 2/24/2009

e1q60x64.sys 4/3/2009

Was this answer helpful?

2 people found this answer helpful.
0 comments

81 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2010-07-04T12:34:11+00:00

    Please start a new topic and don't hijack this topic. Also provide a link to the dump files.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

    Was this answer helpful?

    0 comments
  2. Anonymous
    2010-07-04T09:32:29+00:00

    Here is my memory dump:

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

    *                                                                             *

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

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

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

    Debugging Details:

    BUGCHECK_STR:  0x124_GenuineIntel

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  f

    STACK_TEXT:  

    fffff880009b9b58 fffff80003a09903 : 0000000000000124 0000000000000000 fffffa8007047028 00000000fa000000 : nt!KeBugCheckEx

    fffff880009b9b60 fffff800035a14d3 : 0000000000000001 fffffa8006fceea0 0000000000000000 fffffa8006fceef0 : hal!HalBugCheckSystem+0x1e3

    fffff880009b9ba0 fffff80003a095c8 : 0000000000000728 fffffa8006fceea0 fffff880009b9f30 fffff880009b9f00 : nt!WheaReportHwError+0x263

    fffff880009b9c00 fffff80003a08f1a : fffffa8006fceea0 fffff880009b9f30 fffffa8006fceea0 0000000000000000 : hal!HalpMcaReportError+0x4c

    fffff880009b9d50 fffff80003a08dd5 : 0000000000000008 0000000000000001 fffff880009b9fb0 0000000000000000 : hal!HalpMceHandler+0x9e

    fffff880009b9d90 fffff800039fce88 : fffffa8005f2fca0 fffff800035c9380 0000000000000000 0000000000000000 : hal!HalpMceHandlerWithRendezvous+0x55

    fffff880009b9dc0 fffff80003489eac : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : hal!HalHandleMcheck+0x40

    fffff880009b9df0 fffff80003489d13 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KxMcheckAbort+0x6c

    fffff880009b9f30 fffff800034e07ea : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x153

    fffff88002cc8ba8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt! ?? ::FNODOBFM::`string'+0x324d

    STACK_COMMAND:  kb

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME:  hardware

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

    Followup: MachineOwner

    Here is another I get:

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

    *                                                                             *

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

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

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

    Debugging Details:

    BUGCHECK_STR:  0x124_GenuineIntel

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  WerFault.exe

    CURRENT_IRQL:  f

    STACK_TEXT:

    fffff88001e64b58 fffff80002820903 : 0000000000000124 0000000000000000 fffffa8003b6c028 00000000fa000000 : nt!KeBugCheckEx

    fffff88001e64b60 fffff800029dd4d3 : 0000000000000001 fffffa8003b6fa60 0000000000000000 fffffa8003b6fab0 : hal!HalBugCheckSystem+0x1e3

    fffff88001e64ba0 fffff800028205c8 : 0000000000000728 fffffa8003b6fa60 fffff88001e64f30 fffff88001e64f00 : nt!WheaReportHwError+0x263

    fffff88001e64c00 fffff8000281ff1a : fffffa8003b6fa60 fffff88001e64f30 fffffa8003b6fa60 0000000000000000 : hal!HalpMcaReportError+0x4c

    fffff88001e64d50 fffff8000281fdd5 : 0000000000000008 0000000000000001 fffff88001e64fb0 0000000000000000 : hal!HalpMceHandler+0x9e

    fffff88001e64d90 fffff80002813e88 : 0000000001ac0000 fffffa8003b81550 0000000000000000 0000000000000000 : hal!HalpMceHandlerWithRendezvous+0x55

    fffff88001e64dc0 fffff800028c5eac : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : hal!HalHandleMcheck+0x40

    fffff88001e64df0 fffff800028c5d13 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KxMcheckAbort+0x6c

    fffff88001e64f30 fffff800028faebe : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x153

    fffff880040709f0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!MiRemoveMappedView+0x2ce

    STACK_COMMAND:  kb

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME:  hardware

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

    Followup: MachineOwner

    But Werfault.exe so process for error reporting. My box is running fine now, after I did a disk check with a bart PE disk then removed most programs on start up. I saw this forum with very similar problems and thought I join in and hopfeully help out to get the bottom of this.

    Any more information of things to try let me know. Thanks

    Was this answer helpful?

    0 comments
  3. Anonymous
    2010-07-04T07:06:29+00:00

    yeah am also hopping it ends the issues :S

    Was this answer helpful?

    0 comments
  4. Anonymous
    2010-07-03T19:18:16+00:00

    yes but in some cases as you said it could be the psu ex:you can buy a psu that meets power requirement on your sistem but not amperage necesary output(my case)and wakeup ending with hw error or in your case ram issues with bios by applying bad settings to it and resulting the same;data are passed inacured and its detected by cpuwich has one simpe and safer solution,reboot and dump eronated data before they are written causing data losts or even bad sectors to hdd or even worst,hope the ram subject will put an end to your issues once and for all

    Was this answer helpful?

    0 comments