Solved BSOD WHEA_UNCORRECTABLE_ERROR hal.dll+37213

5h1n · Aug 26, 2014

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).

usasma · Aug 27, 2014

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:

[FONT=lucida console]**************************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: [B]9600[/B].17085.amd64fre.winblue_gdr.140330-1035
System Uptime:[B]0 days 0:03:59.027[/B]
Probably caused by :[B]GenuineIntel[/B]
BugCheck [B]124, {0, ffffe0001dd5d028, b2000000, 80005}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x00000124"]WHEA_UNCORRECTABLE_ERROR (124)[/URL]
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: [B]0x124_GenuineIntel_PROCESSOR_MAE[/B]
CPUID:        "Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3400[/B]
  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: [B]9600[/B].17085.amd64fre.winblue_gdr.140330-1035
System Uptime:[B]1 days 4:44:44.210[/B]
Probably caused by :[B]GenuineIntel[/B]
BugCheck [B]124, {0, ffffe001ddd56028, b2000000, 80005}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x00000124"]WHEA_UNCORRECTABLE_ERROR (124)[/URL]
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: [B]0x124_GenuineIntel_PROCESSOR_MAE[/B]
CPUID:        "Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3400[/B]
  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: [B]9600[/B].17085.amd64fre.winblue_gdr.140330-1035
System Uptime:[B]0 days 7:56:40.404[/B]
Probably caused by :[B]GenuineIntel[/B]
BugCheck [B]124, {0, ffffe0012f103028, b2000000, 80005}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x00000124"]WHEA_UNCORRECTABLE_ERROR (124)[/URL]
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: [B]0x124_GenuineIntel_PROCESSOR_MAE[/B]
CPUID:        "Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3400[/B]
  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: [B]9600[/B].17031.amd64fre.winblue_gdr.140221-1952
System Uptime:[B]0 days 1:47:26.211[/B]
Probably caused by :[B]GenuineIntel[/B]
BugCheck [B]124, {0, ffffe00070657028, b2000000, 80005}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x00000124"]WHEA_UNCORRECTABLE_ERROR (124)[/URL]
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: [B]0x124_GenuineIntel_PROCESSOR_MAE[/B]
CPUID:        "Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3400[/B]
  BIOS Version                  F2
  BIOS Release Date             04/28/2014
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  H97-HD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

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:

[FONT=lucida console]**************************Tue Aug 26 17:03:06.338 2014 (UTC - 4:00)**************************
[COLOR=RED][B]danew.sys                   Tue Mar 23 04:37:33 2010 (4BA87DCD)[/B][/COLOR]
[COLOR=RED][B]VKbms.sys                   Thu Sep 30 12:16:33 2010 (4CA4B7E1)[/B][/COLOR]
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)
[/FONT]

5h1n · Aug 27, 2014

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!

usasma · Aug 28, 2014

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

5h1n · Nov 16, 2014

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.

usasma · Nov 17, 2014

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.

5h1n · Nov 17, 2014

usasma said:
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.

usasma · Nov 18, 2014

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!

5h1n · Dec 1, 2014

usasma said:
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).

usasma · Dec 2, 2014

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.

5h1n · Dec 2, 2014

usasma said:
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.

They weren't bent before and for sure not in a way like this: http://i.imgur.com/UBEI8pD.jpg
But they are completely bent since I got it back, while they weren't before I sent it in (I am not THAT blind!). I also have doubts that my PC would have even been booting under these circumstances (the messed up pin on the top is actually bent outside..). I did some google research and asked on a german forum, where everyone knew about which shop I am talking without me even mentioning or hinting towards their name and many other reporting about similar problems. Even if I could bent the pins back (the way they are bent could make this be pretty hard), my mainboard would still have the same issues which caused me opening this thread. They claim they have checked my other hardware parts and they wouldn't have shown anything abnormal though. My question now was if my bluescreens could be caused by pins as messed up those are (remember: my PC was running without issues for 20h+ at times and CPU tests went without any errors). I don't think they could be, and I am also confident they were all ok before I sent them my hardware. But if you think otherwise, tell me =)
I am now trying to argue that I have proof for it not working during the first weeks already and that bluescreens weren't the cause (therefore asking here again), also by pointing on the logs I have posted here. Their first reply via Mail came from their legal department (I messaged their technical support) indirectly threatening me that they will let this go to the court ("we have witnesses for the court that the pins were already bent"). How would you proceed in this situation? I think my best bet would be trying to prove that the issues started in the first week and weren't caused by pins..

usasma · Dec 2, 2014

Aren't there consumer protection agencies in Germany? Can you file a complaint against them - and also cite the forums where others support your claims?

As for going to court - they've got an army of lawyers. Can you afford to fight them? On a strictly economic viewpoint, you'll spend more on a lawyer than you will on a new motherboard. They will testify to support the person who made the observation about the pins, with a whole army of people saying "Yes, it was received from the owner with the pins bent already."

I can't say for certain if it's the pins or not. I see more motherboard failures than I see CPU failures. But it's a fine line as the two are directly connected together. The tests that we have only test certain parts of the system - and they're only software tests (they don't actually look inside the parts).

There are no 100% certain motherboard tests. The tests would be more expensive than the motherboard - and the manufacturer's wouldn't be able to make any money. An exact diagnosis of this problem is likely to cost you thousands of Euro's - much, much more than a new motherboard would cost.

Say, for example, that the upper pin that is bent is only used during certain operations. If your system only does those certain operations every 20+ hours, then it'll only have a problem every 20+ hours (and that presumes that the bent pin is not functioning at all - but what if it's only partially broken?).

5h1n · Dec 2, 2014

usasma said:
Aren't there consumer protection agencies in Germany? Can you file a complaint against them - and also cite the forums where others support your claims?

There are, gotta look into it and if that would help in some way. Ther are also laws that you can send anything back without having to explain why for the first 14days and during the first 6 months (it is 3months for me now) the seller has to prove that they didn't damage it. In the letter that came with my hardware, where it states what they tested/replaced, normally at least, they already mentioned some court rulings that would decide against me under these circumstances. With circumstances, so they explained further, it was meant that I didn't report such an obvious defect immediately, as I should have. Of course I didn't do this, because it wasn't the case before I sent it back. That's why I will just try to prove that it never was working as intended.

usasma said:
As for going to court - they've got an army of lawyers. Can you afford to fight them? On a strictly economic viewpoint, you'll spend more on a lawyer than you will on a new motherboard. They will testify to support the person who made the observation about the pins, with a whole army of people saying "Yes, it was received from the owner with the pins bent already."

Just how much work it is and that it seems to be regular thing for them makes me not want to do this for "just" a mainboard. The court thingy wasn't anything I mentioned either, but them, attempting to scare me away, I assume.

usasma said:
There are no 100% certain motherboard tests. The tests would be more expensive than the motherboard - and the manufacturer's wouldn't be able to make any money. An exact diagnosis of this problem is likely to cost you thousands of Euro's - much, much more than a new motherboard would cost.

Say, for example, that the upper pin that is bent is only used during certain operations. If your system only does those certain operations every 20+ hours, then it'll only have a problem every 20+ hours (and that presumes that the bent pin is not functioning at all - but what if it's only partially broken?).

But doesn't the CPU need to be connected to all the pins on the motherboard? With one being bent outside it would be hard to even place the CPU properly too. There are roughly 800 pins, 4 being broken right now (they didn't seem to be in a state where they could still work, but maybe they still can? I asked some co-workers (people who studied IT) and they also thought so), which makes 0,5% of the pins not being active at all. I always thought you could not even boot under these circumstances.
Anyway, thanks a lot for your help again! I will see how far I get with proving that it never did work, since them claiming that you have bent the pins yourself seems to be a regular thing (maybe even a strategy as some people on the forums say) and arguing about this won't get me far. They seem to be really confident in this case as long as you haven't taken pictures before and after. Kinda sucks, because I am now running 6 years old hardware and can't use anything of my new one :x Will tell you if a miracle happened and I somehow made them decide that they will offer customer service from now on!

usasma · Dec 3, 2014

They win either way.
If you do decide to fight, they get a bunch of people to say it's your fault - so they don't lose then.
If you decide not to fight, it doesn't cost them anything.

I haven't experimented with broken pins, so I don't know if it could work or not.
I would question it myself, but I can easily afford a new motherboard - I don't know your situation, nor do I presume to tell you how to spend your money.

Good luck to you whatever you may decide.
Should the problems continue, feel free to post back.

5h1n · Dec 12, 2014

New Mainboard, same old problem. Not just Bluescreens, but the exact same cause and address again. Before I used a Gigabyte H97-HD3, now it is a H87-HD3, which is pretty much the same. I am still running the same OS, but I don't feel like reinstalling it (again) will solve this bluescreen. I am only running 1x4GB RAM atm to decrease the chance of failure on that side. I also did another RAM test over night: http://puu.sh/droaR/1550f3b438.JPG (1 ERROR on the stick I am not using), http://puu.sh/drobD/39d2faacb4.JPG (0 ERRORS on the stick I am currently using). They claim they tested all the other hardware when I sent it back.. but well..
I will do some additional extended hardware tests later today while also contacting the shop again. This also means that my suddenly broken mainboard was fine at the start.

usasma · Dec 12, 2014

In my shop, if we rule out everything else, then we blame the motherboard.
We are rarely wrong because we test each component thoroughly (and the service center charges us if we send in one with a bad diagnosis).
It's unfortunate, but there are no 100% accurate motherboard tests. Developing such a test is more expensive (for the manufacturer) than replacing the motherboard after ruling out everything else.

I can't recall if I provided this link before: Hardware Stripdown Troubleshooting
It's a stripdown procedure for attempting to locate failing hardware.
Good luck!

5h1n · Dec 12, 2014

usasma said:
In my shop, if we rule out everything else, then we blame the motherboard.
We are rarely wrong because we test each component thoroughly (and the service center charges us if we send in one with a bad diagnosis).
It's unfortunate, but there are no 100% accurate motherboard tests. Developing such a test is more expensive (for the manufacturer) than replacing the motherboard after ruling out everything else.

I can't recall if I provided this link before: Hardware Stripdown Troubleshooting
It's a stripdown procedure for attempting to locate failing hardware.
Good luck!

I am borrowing another Hard drive today and try out if it changes anything. I will also use another power supply and then see if it helps. Don't you think it won't be the mainboard? As I said, it is a new one now, and I am still getting the same BSOD.
I will post an update here about the results I get..

usasma · Dec 12, 2014

When troubleshooting by replacing parts, you have to assume that the replacement part is good.
You can also test the part by trying it in another system that's known to be good.
Only after trying/testing each and every part should you wonder about a replacement being bad.

FWIW - we replace parts at work all the time, and it's a rare event that one is bad out of the box.
But, when it does happen, it is incredibly frustrating.

Keep a list of things that you've replaced.
You never know which part it is.

For example, my house got hit by lightning years ago.
Although I had surge protectors, I didn't have surge protection on the cable for the internet.
The lightning came in, went though the modem and router, through the network and into my son's computer. It fried the telephone modem on my son's computer.
This device wasn't being used and wasn't connected to the telephone line. The only connection that it had was being plugged into the motherboard.
It took me weeks of troubleshooting to finally determine that it was the problem!

5h1n · Dec 12, 2014

usasma said:
When troubleshooting by replacing parts, you have to assume that the replacement part is good.
You can also test the part by trying it in another system that's known to be good.
Only after trying/testing each and every part should you wonder about a replacement being bad.

FWIW - we replace parts at work all the time, and it's a rare event that one is bad out of the box.
But, when it does happen, it is incredibly frustrating.

Keep a list of things that you've replaced.
You never know which part it is.

For example, my house got hit by lightning years ago.
Although I had surge protectors, I didn't have surge protection on the cable for the internet.
The lightning came in, went though the modem and router, through the network and into my son's computer. It fried the telephone modem on my son's computer.
This device wasn't being used and wasn't connected to the telephone line. The only connection that it had was being plugged into the motherboard.
It took me weeks of troubleshooting to finally determine that it was the problem!

I would replace my Power supply and my video card (if necessary) with the one I have been using for the past weeks since they are still reliable (both a couple of years old). I am also getting another HDD from work that is working for sure. I also have an older i3 CPU left but I am not sure here if this one is working (either CPU or mainboard died).
I hope I can at least find the cause of this. After 4 months I would really like to be able to use a PC again, especially since holidays are close.

5h1n · Dec 15, 2014

So far:
All kinds of stress tests: Nothing.
New mainboard: Same error.
Different power supply: Same bluescreen
Different video card: Same bluescreen
Only one RAM Stick (the one that passed 12 times in Memtest86+): Same bluescreen
Unplugging second HDD: Same bluescreen
Using a different HDD and installing Windows again: Same bluescreen
=/

Solved BSOD WHEA_UNCORRECTABLE_ERROR hal.dll+37213

New Member

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

New Member

My Computer