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-06-19T15:22:21+00:00

    did that as u said memory test i conduct today in the morning were positive. SFC came out clear. Did the Driver Verifier as i rebooted and logged in system crashes lycosa.sys my keyboard driver was the culprit this time . and i am uploading my last BSoD mini dump file after i did driver verify and also the earlier one.

    here is the link

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

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2010-06-19T15:31:17+00:00

    whats rtm.... plus after uninstalling the driver i got the bsod again :S

    Was this answer helpful?

    0 comments
  3. Anonymous
    2010-06-19T15:28:37+00:00

    the driver Lycosa.sys causes the issue (Referencing user handle as KernelMode).

    try to update it.

    1 note, please install all security updates. You still have the RTM.

    "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-19T14:53:13+00:00

    Start here: Can you upload the contents of c:\windows\minidump to your**SkyDrive**and provide a link?

    For dealing with Blue Screens, general guidance follows:

    Consider running chkdsk on all partitions.  Let chkdsk complete on each partition and see if that helps.

    Also consider running SFC /SCANNOW.

    If you boot into safe mode, do you still experience bugchecks? What about if you do a clean boot, or device clean boot?

    Consider testing memory with Windows Memory Diagnostic or memtest86. Note that memory that passes tests is not necessarily  good memory - it just hasn't failed a test.  Consider systematically eliminating RAM from the system - run with a couple of  modules for a while, and see how things go. Then try the other modules.

    Other common suggestions include ensuring drivers are up to date (including video drivers), as well as ensuring that you're  using the latest BIOS.

    It can be helpful to use Driver Verifier.  To enable Driver Verifier... start->verifier.exe->OK->Create standard settings- >Next->select driver names from a list->Next->sort by Provider->select all non-Microsoft drivers->Finish, and OK your way out  of the dialog.

    Then, reboot and use the system as you normally would, and wait for a problem.  In the event that the system does not boot  completely after enabling driver verifier, boot into Safe Mode and run driver verifier, and tell it to delete the changes.

    Wait for a bugcheck to occur after enabling verifier as described, and then upload it to your SkyDrive, and provide a link.

    Was this answer helpful?

    0 comments