Hal.dll causing BSOD

Fingerzz · 26 Nov 2013

Hi, this is my first time posting but i thought id give it a go.

A few months ago i did a complete rebuild of my computer, fresh windows install, the works.
At first i had some problems with the odd blue screen but i thought i had the problem fixed after i did a complete re-install of some graphics drivers.

However after having no major problem for a couple of months i found that when sitting down at my computer it was once again sitting at the login screen, after logging in i was surprised to find that it had once again blue screened.

And so i have come to the seven forums in the hope of finding what is causing this happen as i'm completly stumped as to what is causing this to happen.

Thanks for an assistance
Fingerzz

Edit:
Forgot to hit upload on the required dump information, is now added

Arc · 28 Nov 2013

Hi Fingerzz.

hal.dll is hardware abstruction layer; and stop 0x124 means hardware failure.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Also do some hardware tests:

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results.
______________________________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800a93e028, bf800000, 200401}

Probably caused by : GenuineIntel

Followup: MachineOwner
---------