Constant Blue Screen- WHEA_Uncorrectable_Error

OnlyUseMeFace

Prominent
Jul 8, 2017
24
0
510
My new build is constantly blue screening me, despite having updated my drivers recently. It blue screened both before and after the driver updates, so I assume that is not what caused it. There are days with no blue screen crashes, then days with 4-5 in a row, and I cannot for the life of me determine the cause.

The crashes also seem to only happen when trying to game ( especially League) or watch Youtube Videos and game at the same time, although it's very inconsistent.

BlueScreenView says that the offending drivers in the crashes are Hal.dll and ntoskrnl, but I have no idea what this means. I have attached a link to a minidump file of todays latest crash:
http://
My PC specs are-

MSI H81M-E33 motherboard
Intel i7 processor, 4770 (3.6ghz)
GTX 1060 6gb vram
16gb DDR3 ram
Corsair CS550M psu
1 TB HDD
Cooler Master Hyper 212 Evo cpu cooler
Cooler Master Elite 430 Case
Razer Naga Mouse and Razer BlackWidow Keyboard
 
Solution
basically, this could be overheating, or incorrect voltages to the cpu
you should remove the overclocking driver and retest for failure.

C:\Program Files (x86)\Intel\Intel(R) Extreme Tuning Utility\Drivers\IocDriver\64bit\iocbios2.sys Sun Apr 16 23:21:40 2017


you have memory modules from different vendors, Kingston and Samsung
you should run memtest86 to confirm your memory timings.
Note: some cpus have bugs in the circuits where they handle the modules from different vendors incorrectly. if all else fails pull out one of the vendors modules and see if you get the same problem. often these types of problems will be fixed in microcode patches applied to the BIOS or added by driver patches when the system loads windows. you...

OnlyUseMeFace

Prominent
Jul 8, 2017
24
0
510


1 stick is the 8gb ram that came with my old Lenovo PC that I moved over, and 1 stick is HyperX fury 8gb
 
you need to put the actual files from c:\windows\minidump directory onto a server so they can be looked at with the windows debugger.

otherwise we just see that the cpu called the bugcheck the reason is located at ffffa589`d10fd028 in memory. in the debugger we would issue the command !errrec ffffa589`d10fd028
and it would decode the info.

bugcheck 0x124 parameter 1=0 is most often incorrect voltages being applied to the cpu. it can be overheating, bad BIOS settings, bad overclocking drivers. GPU pulling too much power from the pci/e bus and the motherboard resting the cpu to prevent over current draw on the graphics card.

 

OnlyUseMeFace

Prominent
Jul 8, 2017
24
0
510


how would I go about putting the minidump files on a server? Tried using dropbox and don't have permission to upload them, despite being administrator.

Any of those problems you listed could be the cause, but I don't know how to check each one to see if they are causing it? Especially the power issues and the BIOS settings, I'm new to all this.
 
the system owns the files but you have rights to make a copy. so copy the files to dropbox rather than trying to move them.



 

OnlyUseMeFace

Prominent
Jul 8, 2017
24
0
510
Added a link to a minidump from 17/10(https://www.dropbox.com/s/nqob3133awq7bvg/101717-26953-01.dmp?dl=0) and today (https://www.dropbox.com/s/ghi8dv2jfbwhwv2/101917-28250-01.dmp?dl=0), any ideas would be greatly appreciated
 
basically, this could be overheating, or incorrect voltages to the cpu
you should remove the overclocking driver and retest for failure.

C:\Program Files (x86)\Intel\Intel(R) Extreme Tuning Utility\Drivers\IocDriver\64bit\iocbios2.sys Sun Apr 16 23:21:40 2017


you have memory modules from different vendors, Kingston and Samsung
you should run memtest86 to confirm your memory timings.
Note: some cpus have bugs in the circuits where they handle the modules from different vendors incorrectly. if all else fails pull out one of the vendors modules and see if you get the same problem. often these types of problems will be fixed in microcode patches applied to the BIOS or added by driver patches when the system loads windows. you should look for a bios update and update your intel drivers from the motherboard vendor or directly from intel https://downloadcenter.intel.com/download/24345/Intel-Driver-Update-Utility
you had some old intel drivers as old as 2012

bugcheck 0x124 called by the cpu
Error Type : Micro-Architectural Error
Severity : Fatal

Error : Internal unclassified (Proc 2 Bank 4)
Status : 0xba00000052000402

System Uptime: 0 days 0:33:45.154

----------------
BIOS Version V6.7
BIOS Starting Address Segment f000
BIOS Release Date 04/21/2015

Manufacturer MSI
Product H81M-E33 (MS-7817)
Version 1.0
Manufacturer MSI
Product Name MS-7817

Processor Version Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 3600MHz
 
Solution