BSOD caused by hal.dll

CaRuJa · 11 May 2015

Hi there,

I've been frustrated by multiple and repeated blue screens over the past 24 hours which range from anywhere between every hour to every 2minutes. I haven't done anything new so these do appear to have just come out of nowhere.

I have done what seemed the usual sensible stuff: system restore to the end of last month, used SlimDrivers to check all of my system drivers are up to date, checked Windows Update. I can usually trouble shoot PC issues myself with the help of Google but I'm just out of my depth and this is driving me crazy.

Although the PC has crashed countless times it has only left three dmp files behind. I have since changed Windows Error Reporting Service to automatically start as it was set to manual and disabled for some reason (not sure if this is the default setting). I also have verifier.exe running in the background, for what has been around 20hours so far.

Any guidance or advice or help from ANYONE would be so gladly appreciated, this is driving me crazy and I don't know what to do.

Thanks so much to anyone who takes the time to help

Cheers
Russ

EDIT: I updated my system info to my profile when registering, but will gladly repost it in this thread if it will help. Sorry if that should have been done in the first place!

SGT Oddball · 11 May 2015

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa800f80c028, be200000, 11152}
Probably caused by : GenuineIntel
Followup: MachineOwner
---------

All your dumps are 124's these are typically related to a hardware issue and can only be isolated by stress testing the major components.
If overclocking, reset all overclocks back to their default settings and then follow these:
RAM - run for a minimum of 8 consecutive passes
RAM - Test with Memtest86+
CPU - run the HIGH test
CPU - Stress Test Using IntelBurnTest
Video - run the FURMARK test for 20mins
Graphics Card Problems - Diagnose
Video Card - Stress Test with Furmark
Storage - run the SHORT test using the DOS version
SeaTools for DOS and Windows - How to Use

CaRuJa · 11 May 2015

Thank you so much for the amazingly quick reply!

I'm fairly sure my CPU is overclocked, as the PC was a custom build from overclockers.co.uk. I don't really know how to change it to default though - is it through a menu before the PC boots?

Also my GPU isn't the standard issue. As far as I'm aware it is the one in this link Review: ASUS GeForce GTX 680 DirectCU II TOP - Graphics - HEXUS.net

How do I check if this is overclocked and how do I reset it to it's normal parameters?

Sorry to be such a nuisance and thank you again!

TVeblen · 11 May 2015

"How do I remove Overclocking and reset normal parameters?"

You set the BIOS to optimized default settings on the Exit Tab. It will say "Load Optimized Defaults" or "Set Defaults" or similar.
Save changes and exit, let the PC reboot.

Note all your current BIOS settings before performing the procedure. If you must set the SATA Controller to AHCI Mode then you should boot directly back into BIOS Settings and change that before trying to start up Windows.

Arc · 12 May 2015

CaRuJa said:

I'm fairly sure my CPU is overclocked, as the PC was a custom build from overclockers.co.uk. I don't really know how to change it to default though - is it through a menu before the PC boots?

Overclocking is a very common cause of a stop 0x124 BSOD.

As TVeblen said, you need to reset the BIOS to defaults. Clearing CMOS will do it. There are three known ways to do it. See the link below:

How To Clear CMOS (Reset BIOS)