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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2010-06-23T05:58:14+00:00

    fans are working fine managed to fix them here is the link for dmp file

    http://cid-b6373b556feed6d9.office.live.com/browse.aspx/.Public

    and download 062210-20779-01

    Was this answer helpful?

    0 comments
  2. Anonymous
    2010-06-23T09:19:36+00:00

    Here is the mini dump debug log

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

    *                                                                             *

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

    Arg3: 00000000ba000000, 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

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  3dsmax.exe

    CURRENT_IRQL:  f

    STACK_TEXT: 

    fffff88002fead58 fffff80003005903 : 0000000000000124 0000000000000000 fffffa8007e52028 00000000ba000000 : nt!KeBugCheckEx

    fffff88002fead60 fffff80002b9d4d3 : 0000000000000001 fffffa8007e212b0 0000000000000000 fffffa8007e21300 : hal!HalBugCheckSystem+0x1e3

    fffff88002feada0 fffff800030055c8 : 0000000000000728 fffffa8007e212b0 fffff88002feb130 fffff88002feb100 : nt!WheaReportHwError+0x263

    fffff88002feae00 fffff80003004f1a : fffffa8007e212b0 fffff88002feb130 fffffa8007e212b0 0000000000000000 : hal!HalpMcaReportError+0x4c

    fffff88002feaf50 fffff80003004dd5 : 0000000000000010 0000000000000001 fffff88002feb1b0 0000000000000000 : hal!HalpMceHandler+0x9e

    fffff88002feaf90 fffff80002ff8e88 : 0000000000000000 000000009333a800 0000000000000000 0000000000000000 : hal!HalpMceHandlerWithRendezvous+0x55

    fffff88002feafc0 fffff80002a85eac : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : hal!HalHandleMcheck+0x40

    fffff88002feaff0 fffff80002a85d13 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KxMcheckAbort+0x6c

    fffff88002feb130 000000003e2e8845 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x153

    000000008cacc7e8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x3e2e8845

    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

    Was this answer helpful?

    0 comments
  3. Anonymous
    2010-06-23T10:25:11+00:00

    You still get the same error:

    Record Id     : 01cb11f67b3be165

    Severity      : Fatal (1)

    Length        : 928

    Creator       : Microsoft

    Notify Type   : Machine Check Exception

    Timestamp     : 6/22/2010 10:52:48

    Flags         : 0x00000000

    ===============================================================================

    Section 0     : Processor Generic

    Descriptor    @ fffffa8007e520a8

    Section       @ fffffa8007e52180

    Offset        : 344

    Length        : 192

    Flags         : 0x00000001 Primary

    Severity      : Fatal

    Proc. Type    : x86/x64

    Instr. Set    : x64

    Error Type    : Micro-Architectural Error

    Flags         : 0x00

    CPU Version   : 0x00000000000206c2

    Processor ID  : 0x0000000000000003

    ===============================================================================

    Section 1     : x86/x64 Processor Specific

    Descriptor    @ fffffa8007e520f0

    Section       @ fffffa8007e52240

    Offset        : 536

    Length        : 128

    Flags         : 0x00000000

    Severity      : Fatal

    Local APIC Id : 0x0000000000000003

    CPU Id        : c2 06 02 00 00 08 20 03 - fd e3 9e 00 ff fb eb bf

                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

    Proc. Info 0  @ fffffa8007e52240

    ===============================================================================

    Section 2     : x86/x64 MCA

    Descriptor    @ fffffa8007e52138

    Section       @ fffffa8007e522c0

    Offset        : 664

    Length        : 264

    Flags         : 0x00000000

    Severity      : Fatal

    Error         : Internal unclassified (Proc 3 Bank 5)

      Status      : 0xba00000000400405

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

    Was this answer helpful?

    0 comments
  4. Anonymous
    2010-06-23T10:27:58+00:00

    okie now what shall i doo :S how can i fix it :S

    Was this answer helpful?

    0 comments