Solved Whea_uncorrectable_error

[prfella]

I am having random BSODs. WhoCrash is reporting back this:

This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8005453028, 0xB66E4000, 0x9B000175)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

If anyone can help, it would be greatly appreciated. Attached is the SF Diagnostic Tool Folder.

 

[Pauly]

Hello prfella, Welcome to SF

All your dumps are pointing at a hardware error and stating the problem originated in the level 1 cache of your cpu as a first step i recommend you check the temperatures on your machine, install some monitoring software on your machine and check your idle temps then run a stress test on your cpu http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html i recommend you dont leave your machine unattended while doing this (at least not for a while at the start) and see how temps rise while loading up the processor and report back. If temps go to high quit the test

 

[prfella]

Hi, Pauly! Thank you for the quick response!


My CPU is a AMD Phenom II X4 970 BE

My MB is a ASUS M4A87TD/USB3

For Hardware Monitoring I use CPUID Hardware Monitor

My CPU Temps Idle are 52 degrees Celsius. Under Load I've seen it go up to 62 Degrees Celsius

The temps for the individual cores are 59 degrees Celsius and I've seen them go up as high as 72 degrees Celcius.

I have heard the the max operating temp for this CPU is 72 degrees Celsius, however I have not seen it go that high (unless it reaches it right when before the PC BSODs, in which case I have no way of knowing it).

 

[Pauly]

Try the prime95 test with the temp software showing on your screen and see what it goes up to, if it shoots up then BSOD you know what the problem is if it raises then levels out then thats something ruled out, remember it could be the processor going south but more often than not its something else and the cpu is the component that gets upset first and reports the crash, if it turns out ok then try running through some hardware tests to prove other components

 

[Britton30]

Since this is a hardware issue...
To better help us to help you would you please add your systems specs? Here's the correct way to do it. :SystemInfo See Your System Specs Under System Manufacturer/Model Number add whether it is a desktop or laptop and whether self built. Very important

Log in to Seven Forums and you will be able to transfer the info directly to the specs page in your profile from within the System Info app.

After doing this your specs will be available in each of your posts.
Click on My system Specs in the lower left of this post to see how it should look.
Full instructions are in the tutorial.

Along with Pauly's suggestions....
Some hardware tests to run.

Graphics card:
Video Card Stress Test with Furmark ​

Hard drive(s):

Pick one for your HDD brand or use Seatools.
7 Free Hard Drive Testing Software Tools​

RAM (memory):

This will require memtest on a bootable CD or USB stick.
RAM - Test with Memtest86+​

 

[prfella]

Excellent, thank you guys, I will try these tests and report the results back as soon as they are done.


EDIT: I have also added my system specs.

 

[prfella]

Ok I am currently running Prime95 test (Small FFTs) and its on its 10th test currently and the CPU temp has not gone past 69 degrees Celsius and the Core Temps have not gone past 83 degrees Celcius. No BSODs currently and the temps are holding steady. Should I try any of the other Prime95 tests?

 

[Britton30]

No, the default setting are OK, allow it to run a few hours to see if the temp stay in that range. This tests a lot of RAM along with CPU.Each Prime pass is 19-22 tests and they become more intensive.

 

[prfella]

Ok so I stop the current test (Small FFT) and run Blend test? The reason I chose Small FFT is because a couple of weeks ago when I started getting BSODs I did a quick preliminary search and came up with that memory is usually the culprit. I ran memtest86+ and within 9 minutes I got back errors.

So I took out one stick and ran memtest86+ again and it completed an entire pass without any errors. So I thought it was the memory. After a few hours though, the PC BSOD'ed again.

So I chose the Small FFT test in Prime95 to really test out only the CPU. The Blend test seems to test both CPU and RAM, and if an error came back , I wouldnt be able to tell where it came from, am I correct in assuming this?

 

[Britton30]

OK, since memtest got errors, did you run through the process of testing each stick in each slot? You may also try to set your BIOS to default settings for the time being. Just set your boot priorities and proper RAM timings, voltage, and timings. Improper setting can give memtest errors too.

 

[prfella]

I have not tested each stick in each slot. I currently have one stick in the system that passed one entire pass without any errors, but I still received a BSOD. I did, however have the 2 sticks in the blue slots (dual Channel) and when I started getting BSODs, I switched them to the black slots (Non-Dual Channel). Still receive BSODs.


I have these sticks:CORSAIR Vengeance 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model CMZ8GX3M2A1600C9B - Newegg.com

and they are currently at the default timings.

 

[Pauly]

Be aware that memtest needs to run multiple passes, ideally 7-8 minimum, we generally suggest running overnight

 

[prfella]

Ok I will run it overnight.


I have a question. If I have errors on a secondary HDD but I am not using it to boot from, just strictly for storage, would it still cause a WHEA UNCORRECTABLE ERROR?

 

[Pauly]

An error on any drive can cause problems depending on the type of error, ie a bad sector on a secondary drive shouldnt cause a system crash but its always safest to remove it for testing purposes

 

[prfella]

OK so I remembered I had a HDD error on one of my drives that I was only using for storage, so I disconnected it to see if that was the cause for the BSODS. I went a full 48 hours without any BSODS, but then I got hit with one.

Since then here are the tests I ran:

Ran Memtest 86+ on the known good stick of RAM, 9 hours, 9 passes. No errors.


Ran Prime95. two seperate tests, Small FFT and Blend test, both over an hour. Temps stood at one temp, and no BSODS occured.


Ran Furmark on GPU. Only Ran it for 15 minutes as the GPU got up to 101 degrees Celsius, however there were no artifacts, and no BSODS occurred.


Ran CHKDSK from the Command Prompt on my main drive. No errors were found.


I looked up online and a few people suggested to running " sfc / scannow" from the command prompt, as a corrupt OS file could also be the cause. I ran that and it in fact did find a corrupt file, CBS I believe. It stated that it fixed the file and I rebooted. I ran the computer a few hours after that (about 2-3 hours) and no BSODS have occurred...YET.


as I stated earlier, I ran Prime95 on my CPU and it got temps up to 68 degrees Celsius, and everything was stable and no BSODS occurred, however I am looking at other computer retailer websites and they list this specific CPU as the max operating temp to be between 55 degrees Celsius and 62 degrees Celsius. My CPU idle right is 59 degrees Celsius and under load goes up to the mid 60's.

Maybe my CPU is running too hot even though Prime95 did not return any errors?

 

[Pauly]

Ran Furmark on GPU. Only Ran it for 15 minutes as the GPU got up to 101 degrees Celsius, however there were no artifacts, and no BSODS occurred.

Doesnt this concern you ?? should not be overheating if cooling is sufficient

Run another sfc scan to verify all clear, it should say no integrity violations found, cbs is the name of the log file that records your scans

Check the max spec temps for your cpu that idle temp sounds too high IMO, again if cooling is sufficient temps shouldnt be a problem
May be time to break out the hoover and do a bit of spring cleaning

 

[prfella]

Heck yea it concerns me, lol. That's why I asked that maybe my CPU is running too hot despite nothing bad happening under Prime95.

Yea that idle temp seems too high to me as well. I've seen on some sites that max temp for this CPU is 62 degrees Celsius and others that say max is 72 degrees Celsius. I've seen a few people speak of having idle temps as low as 37 degrees Celsius and about 48 degrees Celsius under load for this CPU....with air cooling!!! I mean dang, I should be able to get something like that.

I will run another sfc scan again like you suggest, Pauly, and then I'm going to go inside and clean out all the fans and whatnot. I'll post back the results as soon as I get them.

 

[prfella]

So it has been 4 days since I did a sfc scan and it fixed the CBS file. I ran a quick sfc scan after that and it says no integrity violations found.

I have literally done NOTHING else and after 4 days since that sfc scan.....0 BSODS.

It couldn't have been that one single file, could it?

 

[Pauly]

Anythings possible, monitor the situation if no more BSODs in several days mark the thread solved or any more probs post the new info

 

[prfella]

Well it has been a little over a week and not a single BSOD. Amazing. Apparently it was that one single file.

I am so relieved that I didnt have to replace any of my parts, lol. I can confidently say that this issue seems to be resolved!

Thank you, Pauly!!, and thank you, Britton30!!