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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2012-04-03T13:06:16+00:00
    1. Locate and then click following registry subkey:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\WMI\Autologger\DiagLog 2. Locate the MaximumBuffers registry value.

    If the registry value is not present, follow these steps to create it: 

    a. Select the registry subkey that is listed in step 2. 

    b. On the Edit menu, point to New, and then click DWORD Value.

    c. Type MaximumBuffers, and then press ENTER. 3. Set the DWORD value to 0x100 in hexadecimal (which is 256 in decimal). To do this, click Modify on the Edit menu, and in the Value data box, type 100, make sure Hexadecimal is selected under Base, and then click OK. 4. Exit Registry Editor, and then restart the computer.

    Start Registry Editor. To do this, click Start, click Run, type Regedit , and then press ENTER. 

    I have mb - evga classified sr-2, nvidia quadro 4000, two x5660, 48gb ram (corsair), and coolermaster 1000w PSU.

    Win 7 x64 and getting those same blue screen. Blue screen viewer tells this. hal.dll+12903, ntoskrnl.exe+186513 and pci.sys+9aff. I have done what you wrote and we will see if problem goes away. If it does I thank you soo much, and is it possible to bit explain what we did with this registry edit and what it fixed. Thnx a lot (fingers crossed that it helped)

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-01-17T15:36:08+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

    follow these steps and check if this fixes the problem

    1. Start Registry Editor. To do this, click Start, click Run, type Regedit , and then press ENTER.
    2. Locate and then click following registry subkey:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\WMI\Autologger\DiagLog 3. Locate the MaximumBuffers registry value.

    If the registry value is not present, follow these steps to create it: 

    a. Select the registry subkey that is listed in step 2. 

    b. On the Edit menu, point to New, and then click DWORD Value.

    c. Type MaximumBuffers, and then press ENTER. 4. Set the DWORD value to 0x100 in hexadecimal (which is 256 in decimal). To do this, click Modify on the Edit menu, and in the Value data box, type 100, make sure Hexadecimal is selected under Base, and then click OK. 5. Exit Registry Editor, and then restart the computer.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2010-08-28T06:48:49+00:00

    im glad that your problem got solved,its good that one stupid theory prooved right,when you overclock your sistem dont touch the memory speed and then you are able to do anything with the processor,my old allendale and an old asrock 775i65g r2.0 are dancing at fsb 1200mhz but the memory stays at ddr400

    Was this answer helpful?

    0 comments
  4. Anonymous
    2010-08-27T20:33:36+00:00

    hi guys back again... sorry took a pretty long time was waiting for my processors and rams... got them changed tested them and my system is running fine ... thanx for ur support

    Was this answer helpful?

    0 comments