BSOD help, hal.dll

[PC n00b]

Sorry if this is in wrong category!

I have just gotten my first BSOD on my newly built PC, using bluescreen view it says hal.dll is the issue but I have read some forums saying this isn't likely the issue. Anyway this is the minidump file I have taken from blue screen viewer, not sure how to directly insert files into the forum so this is the best I can do now.

My system components are: i5 4690k, Gigabyte Z97x Gaming 7, Samsung OEM 128gb SSD, Evga 850 G2

==================================================
Dump File : 012515-3322-01.dmp
Crash Time : 1/25/2015 12:24:28 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`08728028
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+76e80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012515-3322-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 281,936
Dump File Time : 1/25/2015 12:25:21 PM
==================================================

 

[johnbl]

hal.dll is just the windows hardware abstraction layer. it talks to the hardware, a failure indicates a problem with your hardware configuration.

the bughceck 0x124 is called directly by the CPU, most often because of a error detected by the internal CPU cache controller. The most common cause of this would be incorrect overclocking of the CPU.

to fix you would remove any overclocking of the CPU and GPU
confirm the CPU is not overheating, blow dust out of fans, and make sure the fans are working

you would also make sure your power supply is working correctly and not overheating
- if this happens while you run a graphics card in 3d mode (game or browser with hardware acceleration) check for proper power to your graphics card and do not overclock the GPU.

I would also boot into BIOS and either update it or reset it to defaults and reconfigure. This will rebuild the database of hardware settings that the BIOS sends to windows. incorrect settings sent to windows will also cause hal.dll to bugcheck. This is very common when people upgrade the GPU to new version from the same graphics vendor. for example, I upgrade one AMD card to a better AMD card. The BIOS may not detect the change and provide bad info to windows then windows bugchecks because it thinks you have a hardware failure.

 

[PC n00b]

hal.dll is just the windows hardware abstraction layer. it talks to the hardware, a failure indicates a problem with your hardware configuration.

the bughceck 0x124 is called directly by the CPU, most often because of a error detected by the internal CPU cache controller. The most common cause of this would be incorrect overclocking of the CPU.

to fix you would remove any overclocking of the CPU and GPU
confirm the CPU is not overheating, blow dust out of fans, and make sure the fans are working

you would also make sure your power supply is working correctly and not overheating
- if this happens while you run a graphics card in 3d mode (game or browser with hardware acceleration) check for proper power to your graphics card and do not overclock the GPU.

I would also boot into BIOS and either update it or reset it to defaults and reconfigure. This will rebuild the database of hardware settings that the BIOS sends to windows. incorrect settings sent to windows will also cause hal.dll to bugcheck. This is very common when people upgrade the GPU to new version from the same graphics vendor. for example, I upgrade one AMD card to a better AMD card. The BIOS may not detect the change and provide bad info to windows then windows bugchecks because it thinks you have a hardware failure.

Thank you for the very detailed reply, I currently have no graphics card so its not because of the BIOs not detecting hardware. If you have said it may be bad overclocking its could be due to using XMP profiles, I have heard that when using it, it can also unintentionally run your CPU at turbo boost speeds with high voltage. When the crash occurred the computer was at idle with no programs running, I just happened to glace and see the BSOD.

 

[johnbl]

well, bugcheck 0x124 with param 1 = 0
would be caused by incorrect clock and voltage to the CPU. It should not be caused by external memory. If your fan and temps are good for your CPU, I would reset the BIOS to defaults or upgrade the BIOS and retest for failure.

if you put a memory dump on a cloud server I can check the speed that the CPU was running at the time of the memory dump and also dump reason that the CPU told windows to shutdown.

 

[PC n00b]

well, bugcheck 0x124 with param 1 = 0
would be caused by incorrect clock and voltage to the CPU. It should not be caused by external memory. If your fan and temps are good for your CPU, I would reset the BIOS to defaults or upgrade the BIOS and retest for failure.

if you put a memory dump on a cloud server I can check the speed that the CPU was running at the time of the memory dump and also dump reason that the CPU told windows to shutdown.

from what I understand some motherboards when XMP is enabled can overvolt your CPU when at boost frequencies though at the time of BSOD, my system was idling so maybe the CPU was undervolted wrong and that caused it

 

[johnbl]

just make sure you have a BIOS with updated microcode for your CPU. that is a BIOS released after the release date of the new CPU. The older BIOS will have incorrect specs for voltages and frequencies for the newer CPU.

 

[PC n00b]

My CPU should be compatible with the motherboard, According to
gigabyte the i5 4690k is supported out the box.
Only strange thing I have noticed is that when not using XMP my CPU base clock is @ 99.xx (can't remember exact number but it was definetly below 100 and no less than 99) but when I was using XMP it was @ 100 not sure if this is bad but system seems stable so far, ran some Prime95 for a good 45 mins, had fine temps no issues. Gonna run it over night just to be sure.