BSOD on new pc build!?

SadistikLazarus

Reputable
Aug 2, 2015
8
0
4,510
So I have just built a new pc, here are the specs
Intel Core i7-4790K 4.0GHz Quad-Core Processor
Corsair H55 57.0 CFM Liquid CPU Cooler
Gigabyte GA-Z97X-Gaming 5 ATX LGA1150 Motherboard
Kingston HyperX Fury Black 16GB (2 x 8GB) DDR3-1866 Memory
Samsung 850 EVO-Series 250GB 2.5" Solid State Drive
Seagate Barracuda 1TB 3.5" 7200RPM Internal Hard Drive
MSI GeForce GTX 970 4GB Twin Frozr V Video Card
Corsair Graphite Series 230T Orange ATX Mid Tower Case
EVGA 850W 80+ Gold Certified Fully-Modular ATX Power Supply
Microsoft Windows 7 Home Premium SP1 OEM (64-bit)

The computer works perfectly well but at night I will watch a movie/tv on the internet and I will get a crash that says there is uncorrectable hardware... the bluescreen reader comes up with these:
Hal.dll+12a3b and ntoskrnl.exe+18dc33.

I am not overclocking anything and all the settings are on the BIOS default, the temperatures are all perfectly fine and I can't see anything explicitly wrong with the pc - I have also tried resitting the hardware but to no avail. I have never experienced (yet) a BSOD crash during gaming or working, only whilst watching videos online..
All drivers are up to date and I am losing my mind trying to find an answer. Any help is much appreciated :)
 
if you have a bugcheck 0x124 and a new low power Intel Core i7-4790K CPU the first thing you want to check is the date and version of the BIOS.
Make sure the BIOS is updated and is dated well after the release date of the processor (after july 1 2014)

old BIOS versions will apply too high of voltage to the CPU for the given clock frequency and your CPU will act like it is poorly overclocked.

beyond that, it would be helpful to see a memory dump
 
Thank you for help; it is much appreciated. Here are the minidump files -

==================================================
Dump File : 080315-12558-01.dmp
Crash Time : 8/3/2015 12:19:45 AM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`0e140028
Parameter 3 : 00000000`bf800000
Parameter 4 : 00000000`00200401
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+748c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\080315-12558-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 348,208
Dump File Time : 8/3/2015 12:20:44 AM
==================================================


==================================================
Filename : ntoskrnl.exe
Address In Stack : ntoskrnl.exe+18dc33
From Address : fffff800`0305f000
To Address : fffff800`0364b000
Size : 0x005ec000
Time Stamp : 0x556356e8
Time String : 5/25/2015 10:07:52 AM
Product Name : Microsoft® Windows® Operating System
File Description : NT Kernel & System
File Version : 6.1.7601.18869 (win7sp1_gdr.150525-0603)
Company : Microsoft Corporation
Full Path : C:\Windows\system32\ntoskrnl.exe
==================================================

On a side note.. I am using gigabyte z97x-gaming 5 with f5 Bios and everytime I try to update to F6 (latest version) I get told that I need a 64bit version of the download, even though the gigabyte website says that the download is for a 64bit w7.
 
Just a quick update: I was able to download the new BIOS (installed it through the BIOS), but if that has solved the problem.. I dunno - I won't know until some time has passed and I don't get another BSOD; but just letting you all know of the progress.
 
yes put the actual binary up on a server and post a link
the memory dumps are stored at c:\windows\minidump by default.
you can use a public server like microsoft onedrive or mediafire, just make sure you give the files public access.

The file size is not very big as it only contains the list of drivers, bios info and the current running stack data.
(well not big by today's standards)

 
Ok guys so I have the situation sorted now. After a few futile attempts at fixing it, I decided to re-install windows and bingo problem hasn't reappeared since. I believe that what might of been causing it in the first place might of been caused by a driver issue. Many thanks for all your help though guys!