Windows 8 and 8.1 Forums


BSOD WHEA_UNCORRECTABLE_ERROR hal.dll+37213

  1. #1


    Posts : 14
    Win 8.1

    BSOD WHEA_UNCORRECTABLE_ERROR hal.dll+37213


    Good evening!

    I build a new computer a bit less than a week ago. Everything runs fine, as it should, heat doesn't go over 50░C on the CPU and didn't reach 50░C on the video card yet. Overall this all seems fine.
    But, occassionally, there are blue screens. There have been 4 or 5 so far over the past week. Today there were 2 within 5 minutes, after 3 days without.
    According the bluescreenviewer it is having problems with the hal.dll, the BSOD itself only tells me that there is an uncorrectable error (so negative!) without further information. I am running Windows 8.1 Pro (I guess).

      My System SpecsSystem Spec

  2. #2


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Inconsiderate BSOD! Hmmph!
    Seriously, the hal.dll issue and the uncorrectable errors are symptoms of a STOP 0x124 BSOD error code.
    This error is most often related to hardware, but can also be due to low-level driver issues or incompatibilities with software/drivers in the system.

    So, here's how we get started......

    Only 46 Windows Updates installed. Most systems have 70 to 90 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

    Don't worry about the specific number, it's just important that you have checked and installed any updates that were available (and didn't experience any errors).

    Ensure that you have the latest firmware for your Crucial SSD

    The drivers for this device aren't installed:
    SM-Bus-Controller PCI\VEN_8086&DEV_8CA2&SUBSYS_50011458&REV_00\3&11583659&0&FB Die Treiber f№r dieses Gerфt wurden nicht installiert.
    This is most likely a component of your chipset drivers. Please visit the Gigabyte website for your model and download/install the latest, Win8.1 compatible chipset drivers.

    The drivers for your Razer Death Adder (danew.sys and VKbms.sys) date from 2010 and they aren't compatible w/Win8.1 (and they are known to cause BSOD's). Please uninstall them and see if that helps. You should still be able to use the mouse without the Razer drivers installed.
    Once we have the system stabilized, feel free to visit the Razer website and download/install the latest, Win8.1 compatible drivers available for your device.

    Check to see if these programs/drivers are compatible w/Win8.1 (from the manufacturer's website):
    NetGroup Packet Filter Driver, part of the WinPcap packet capture library (npf.sys)
    C-Media USB Audio Driver WDM (PLTGC.sys)
    Realtek PCI/PCIe Network Adapters (Rt630x64.sys)
    If they're not compatible, or if you're not sure - update them to the latest version that you know is compatible w/Win8.1

    Beyond this, I have these 3 suggestions:
    1. Get ALL available Windows Updates. It may take several trips to get them all
    2. Start with these free hardware diagnostics: Hardware Diagnostics
    3. If all of the hardware tests pass, then run Driver Verifier according to these instructions: Driver Verifier Settings



    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Tue Aug 26 17:03:06.338 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-5250-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:03:59.027
    Probably caused by :GenuineIntel
    BugCheck 124, {0, ffffe0001dd5d028, b2000000, 80005}
    BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
    Arguments: 
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffe0001dd5d028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000080005, Low order 32-bits of the MCi_STATUS value.
    BUGCHECK_STR:  0x124_GenuineIntel
    PROCESS_NAME:  chrome.exe
    FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE
    CPUID:        "Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3400
      BIOS Version                  F2
      BIOS Release Date             04/28/2014
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  H97-HD3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 16:58:45.518 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-7625-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:1 days 4:44:44.210
    Probably caused by :GenuineIntel
    BugCheck 124, {0, ffffe001ddd56028, b2000000, 80005}
    BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
    Arguments: 
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffe001ddd56028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000080005, Low order 32-bits of the MCi_STATUS value.
    BUGCHECK_STR:  0x124_GenuineIntel
    PROCESS_NAME:  chrome.exe
    FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE
    CPUID:        "Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3400
      BIOS Version                  F2
      BIOS Release Date             04/28/2014
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  H97-HD3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Aug 23 13:35:28.712 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082314-5703-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 7:56:40.404
    Probably caused by :GenuineIntel
    BugCheck 124, {0, ffffe0012f103028, b2000000, 80005}
    BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
    Arguments: 
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffe0012f103028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000080005, Low order 32-bits of the MCi_STATUS value.
    BUGCHECK_STR:  0x124_GenuineIntel
    PROCESS_NAME:  chrome.exe
    FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE
    CPUID:        "Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3400
      BIOS Version                  F2
      BIOS Release Date             04/28/2014
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  H97-HD3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Aug 21 18:28:39.521 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082214-4578-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17031.amd64fre.winblue_gdr.140221-1952
    System Uptime:0 days 1:47:26.211
    Probably caused by :GenuineIntel
    BugCheck 124, {0, ffffe00070657028, b2000000, 80005}
    BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
    Arguments: 
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffe00070657028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000080005, Low order 32-bits of the MCi_STATUS value.
    BUGCHECK_STR:  0x124_GenuineIntel
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE
    CPUID:        "Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3400
      BIOS Version                  F2
      BIOS Release Date             04/28/2014
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  H97-HD3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Tue Aug 26 17:03:06.338 2014 (UTC - 4:00)**************************
    danew.sys                   Tue Mar 23 04:37:33 2010 (4BA87DCD)
    VKbms.sys                   Thu Sep 30 12:16:33 2010 (4CA4B7E1)
    npf.sys                     Thu Feb 28 20:31:24 2013 (513004EC)
    PLTGC.sys                   Fri Apr 12 04:45:13 2013 (5167C999)
    Rt630x64.sys                Fri May 10 05:59:08 2013 (518CC4EC)
    intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
    dump_storahci.sys           Thu Aug 22 07:40:39 2013 (5215F8B7)
    nvhda64v.sys                Thu Nov 28 08:38:09 2013 (52974741)
    TeeDriverx64.sys            Thu Mar 13 14:21:52 2014 (5321F740)
    nvvad64v.sys                Fri Mar 28 09:32:06 2014 (533579D6)
    tap0901.sys                 Tue Apr  8 09:33:45 2014 (5343FAB9)
    ptun0901.sys                Thu Apr 24 14:44:45 2014 (53595B9D)
    rzudd.sys                   Mon May 19 02:43:44 2014 (5379A820)
    RTKVHD64.sys                Wed May 28 08:17:12 2014 (5385D3C8)
    nvlddmkm.sys                Wed Jul  2 13:42:02 2014 (53B4446A)
    NvStreamKms.sys             Fri Jul 25 07:35:56 2014 (53D2411C)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Aug 21 18:28:39.521 2014 (UTC - 4:00)**************************
    cpuz137_x64.sys             Mon Feb 17 09:22:16 2014 (53021B18)
    
    http://www.carrona.org/drivers/driver.php?id=danew.sys
    http://www.carrona.org/drivers/driver.php?id=VKbms.sys
    http://www.carrona.org/drivers/driver.php?id=npf.sys
    http://www.carrona.org/drivers/driver.php?id=PLTGC.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
    http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
    http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
    http://www.carrona.org/drivers/driver.php?id=tap0901.sys
    ptun0901.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=rzudd.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
    cpuz137_x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
      My System SpecsSystem Spec

  3. #3


    Posts : 14
    Win 8.1


    I installed all available windows updates now (there was even one for my mouse suggested by windows).
    I uninstalled the old DeathAdder Driver and what was shipped with it and replaced it with the newer software by Razer, which I wanted to avoid due to many useless features (it is a left handed mouse and just switching the buttons over windows is not supported by some software =/ )
    I got all the drivers Gigabyte offers for my mainboard.

    But I can't find any firmware updates/downloads for the Crucial MX100.

    For now I will go to get some rest and will continue following the steps suggested by you (hardware tests) as soon as another BSOD shows up!
    Thanks a lot for your help and all the work you do here overall!
      My System SpecsSystem Spec

  4. #4


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Don't worry overmuch about the firmware update for the Crucial at this point.
    Should it be needed, we'll research it later on.
      My System SpecsSystem Spec

  5. #5


    Posts : 14
    Win 8.1


    Gotta post here again, unfortunately. My problem persists and has never been solved. I tried everything from your initial post during the past weeks, including completely whiping my SSD and installing Windows 7 instead of 8. Still the same. Still the same errors, even under Windows 7. Should I ask here for help again, because I have now switched to 7 but am having a problem that doesn't seem to be limited to any OS.
    Last edited by 5h1n; 16 Nov 2014 at 19:10.
      My System SpecsSystem Spec

  6. #6


    Posts : 5,139
    Win8.1Pro - Finally!!!


    In most cases this is a symptom of a hardware problem (but can be low-level drivers or compatibility issues).
    Start with these free hardware diagnostics: Hardware Diagnostics
    Then have a look at this procedure to help rule out hardware: Hardware Stripdown Troubleshooting

    Edit: Make sure to get all available updates from the Gigabyte website.
    Also, Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system. Also check the readme file to see if they apply to the problems that you are having. Please be advised that flashing the UEFI/BIOS is a very unforgiving process - and one mistake can physically damage your motherboard. If possible, use the "inside Windows" flash mechanism (if your OEM provides one) - that is much more forgiving than the traditional (floppy drive) flash method.
      My System SpecsSystem Spec

  7. #7


    Posts : 14
    Win 8.1


    Quote Originally Posted by usasma View Post
    In most cases this is a symptom of a hardware problem (but can be low-level drivers or compatibility issues).
    Start with these free hardware diagnostics: Hardware Diagnostics
    Then have a look at this procedure to help rule out hardware: Hardware Stripdown Troubleshooting

    Edit: Make sure to get all available updates from the Gigabyte website.
    Also, Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system. Also check the readme file to see if they apply to the problems that you are having. Please be advised that flashing the UEFI/BIOS is a very unforgiving process - and one mistake can physically damage your motherboard. If possible, use the "inside Windows" flash mechanism (if your OEM provides one) - that is much more forgiving than the traditional (floppy drive) flash method.
    The mainboard offers a flash method itself via USB Stick etc. I did this, with sadly no success in terms of solving my bsod problem. All drivers for the mainboard are installed. No drivers installed besides those that are completely necessary. That's why I formatted everything and installed a clean OS that wasn't the same as I used before.

    I will probably send my hardware back tomorrow and see if they can figure something out. Since the bluescreens give no information and aren't reproducable due to their random nature, I have little hope there though.
      My System SpecsSystem Spec

  8. #8


    Posts : 5,139
    Win8.1Pro - Finally!!!


    At work, once we run the hardware diagnostics and do the stripdown procedure - that's when we give up.
    We send it to the service center with a detailed statement of all that we've done - and they usually end up replacing the motherboard.

    Good luck!
      My System SpecsSystem Spec

  9. #9


    Posts : 14
    Win 8.1


    Quote Originally Posted by usasma View Post
    At work, once we run the hardware diagnostics and do the stripdown procedure - that's when we give up.
    We send it to the service center with a detailed statement of all that we've done - and they usually end up replacing the motherboard.

    Good luck!
    I got my hardware sent back without anything being done. The shop now claims I would have bent the pins of the mainboard. There was nothing like this when I sent the board back, but after their "checks" I suddenly have some obviously bent pins (you know, to the point they don't even seem to be golden anymore). They also claim it was me damaging the board and therefore I would have no right for a replacement (it's funny, because their support asked me about bent pins before sending it in). That I won't order anything there again is obvious, but do you have any idea if those bluescreens could be caused by completely screwed up pins, or if it would be even possible to have a PC running for 20h, stable, under these circumstances. Maybe I will be able to prove that this wasn't causing the bluescreens (I am 100% sure that it wasn't in this state before).
      My System SpecsSystem Spec

  10. #10


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Which pins on the mainboard were bent - and what were their condition?
    I'd suspect that bent pins could cause this problem under a couple of circumstances:
    - if the pins are touching one another (could result in a short circuit)
    - if the pins aren't letting a device seat in that slot (or only partially seat)
    Just plain bent pins (without any underlying damage) probably won't cause problems.

    As you have the board back, can you straighten the pins yourself (it's a very delicate job!).
    I use a credit card/stiff piece of plastic and a magnifying glass to gently push them back into place (try not to overbend them).
    On a CPU it's easy to tell if they're straight by looking down the rows of pins.

    My son had a CPU with bent pins that we sent back to NewEgg for a replacement - and they didn't argue with us about who bent them. We discussed keeping the CPU and using it (I would have straightened the pins first) and he chose to send it back. I truly can't recall if they came that way or not - but I do know what a ZIF socket is and I didn't use any force to put the CPU on the mobo.
      My System SpecsSystem Spec

Page 1 of 3 123 LastLast
BSOD WHEA_UNCORRECTABLE_ERROR hal.dll+37213
Related Threads
Solved Bsod whea_uncorrectable_error in BSOD Crashes and Debugging
Hey guys, After updating every driver I can find and doing a fresh install of windows 8.1 Pro, I am still having problems with WHEA_UNCORRECTABLE ERROR. I have also updated my BIOS and ran sfc scan, memtest, stress tested my CPU and GPU and ran chkdsk. Can anyone take a look at my crash...
As the title states I'm getting a whea_uncorrectable_error bsod. According to BlueScreenViewer it's these: hal.dll+37213 ntoskrnl.exe+1c6699 I have found the hal.dll error on the forums but not even google show a result for the ntoskrnl.exe error. I have recently upgraded my computer...
BSOD whea_uncorrectable_error in BSOD Crashes and Debugging
Hello When i play any HTML5 videos on Google Chrome, the BSOD whea_uncorrectable_error happen. I had updated my motherboard to the latest version and i had formatted my SSD and install Windows 8.1 Pro again but it is still happen when i play any HTML5 videos on Google Chrome. Dump file +...
BSOD hal.dll+37213 in BSOD Crashes and Debugging
Hi forum!, First post and love how you guys help out! I am getting a BSOD when running "guild wars 2" in the background and doing web browsing, I have run bluescreen view as well as who crashed and it seems hal.dll+37213 is the issue, as per the sticky i have run the SF tool which collected...
Hello, I run a custom built computer and this mainly happens when playing games or rendering video files. I have no idea what is causing it and I tried many different ways of fixing it. New video card drives, Memory tests, Chkdsks. Nothing worked. I'm going to post my zip file. Could anyone take a...
BSOD - whea_uncorrectable_error in BSOD Crashes and Debugging
Hello everyone :D Im new to Windows 8. My computer crash while surfing on news sites with video or in computer games after 10 sek in there. The computer is brand new! See my attachment please
Eight Forums Android App Eight Forums IOS App Follow us on Facebook