Please help! WHEA UNCORRECTABLE ERROR

lovehandles

Commendable
May 9, 2016
4
0
1,510
Hi all,
So I just recently upgraded most of my computer and changed to windows 10. I was good for a week or so, but then all of a sudden I have the dreaded BSOD and "WHEA UNCORRECTABLE ERROR".

Unlike some of the others with the same problem, I am getting spikes of high core frequencies (3.7Ghz), however staying at normal temps (27 C) while idle.

It will crash at anytime ie browsing the net, playing games, rendering, etc

I've tried;
Updating drivers
Updating BIOS
Reseting BIOS
REINSTALLING WINDOWS

These are my specs:
CPU: Intel i7 6700 - Not overclocked - Standard heatsink
GPU: GIGABYTE Geforce GTX 960
RAM: 16 GB
MB: GIGABYTE H170-gaming 3
SSD: 750 EVO samsung 250 GB
HDD: 2 TB
OS: Win 10 home
Pwr
Sup: Corsair CS650M

http://i.imgur.com/SqQJvQ9.png?1

This is a picture of my .dmp file, as I can't work out how to upload it (don't have permission - im a noob)

Any advice will be much appreciated! Thanks!
 
you need to copy the dump file into another location and then you can upload it. You just can't do it direct from the minidump folder

IN the short term, can you download and run this: http://www.resplendence.com/whocrashed
it can read the error logs and show us what the whea errors are reporting

copy/paste results in here

WHEA errors can be hardware or software. Your actions seem to point at it being hardware but we shall see what errors say.
 
Thank you so much.

http://s000.tinyupload.com/index.php?file_id=23118947431300312918

here's one of the .dmp files

Below are 2 Crash Dump Analysis', the first being same as the rest (9) except for the second one.

"On Tue 10/05/2016 3:45:43 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051016-4125-02.dmp
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0xCF)
Bugcheck code: 0x124 (0x0, 0xFFFFE0011B925028, 0xF2000000, 0x14)
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."

"On Mon 9/05/2016 11:58:00 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050916-4109-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR"

Ill clean my CPU and heatsink and reapply thermal paste, to see if that's the problem first. Then I'm going to look for an aftermarket heatsink. How would I go about dealing with the third party driver? Would I have to do a full wipe of the hard drives? could that be a virus?

Thanks again for the reply :)
 
for this error, I would be looking at heating or if you were running a game, you would want to confirm that your GPU is getting proper power. (you were running chrome at the time and it will use the 3d hardware)
Also remove the overclocking software until you figure out the cause of the error. If you tweaked values in the BIOS you might want to reset them back to defaults, BIOS overclocking could also produce this error.

the CPU called a bugcheck because of a error reported inside the CPU:
Error Type : TLB error
Severity : Fatal
Error : DTLBL0_ERR (Proc 3 Bank 2) (this is processor 3 cache memory bank 2 reporting a error)

the system was up for 34 minutes, I would suspect overheating or your overclock driver:
remove: C:\Program Files (x86)\Intel\Intel(R) Extreme Tuning Utility\Drivers\IocDriver\64bit\iocbios2.sys Thu May 28 13:42:10 2015

you also have \SystemRoot\System32\drivers\ScpVBus.sys Sun May 05 14:31:26 2013
installed and it tends to cause memory corruption problems but it would never cause this particular bugcheck.

you might want to find out why this file is so out of date:
SystemRoot\system32\drivers\MBfilt64.sys Thu Jul 30 20:40:32 2009
it is listed as a audio driver and may have been installed by mistake. I would go to the motherboard vendor and install the audio drivers and remove this one.
(it should not have actually caused this bugcheck either)

 
Got a watercooled heatsink, it's holding strong atm so fingers crossed.

As for the drivers, I fixed the first and last but can't get rid of "ScpVBus.sys". What program is it linked to?

 


whea errors can be anything, they can be hardware, they can be software, they can even be USB devices. They are the jack of all trades of windows errors, though there are a few of those. They aren't one single thing that causes them all... if only

 
when you get WHEA error 0x124, you want to look at the value of parameter 1.
if it is 0 it means the CPU shutdown the system because of a internal error
if it is 4 it means the system detected a error on the PCI/e bus (gpu, or anything shared on the PCI/e interface (like USB ports)

generally you also want to look at the memory dump and see how long the system has been up. if it is under 15 seconds it means the system rebooted and bugchecked on the reboot after some power related event.



 


Yes I think you are right. my solution worked for about 24 hours and the system wouldn't post again and I ended up RMAing the board, processor and soon as Corsair gets me a number the liquid cooler. Thought it was worth a try.

 
Hey guys, the liquid cooling seemed to fix it for a while, however I installed battle.net and overwatch the other day and now I can't get more then 5 minutes before BSODing. I'll uninstalling battle.net and overwatch to see if that fixes anything. If not, here is a new dmp. file from recently.

http://s000.tinyupload.com/index.php?file_id=75812848007187288869

I feel like it's most likely faulty hardware, but I just wanted to check before taking it back to the shop.

If anyone could check this quickly, it would be much appreciated.