Windows 7 BSODs happening at different times - Hal.dll

Hello, all! I've been having some trouble with my custom-built PC lately. I get BSODs every now and then and WhoCrashed tells me the problem is Hal.dll. The crash has happened while streaming video, playing games, and while idling with no programs running. My temps stay pretty low as the room my PC is in is pretty cold because of the weather so I don't think overheating is an issue. I do not think I am overclocking anything (GPu is a GTX780 Superclocked. Factory overclocked?) and I am pretty sure that all my drivers are up to date, too. Uploaded my debug thinger. Hope someone can help!

Whocrashed is correct to a certain extent. It's not an amazing program, there are much better debuggers. hal.dll is the hardware abstraction layer that is implemented in software, it contains a set of routines that translate hardware information for software like device drivers.
You have a bugcheck of 0x124 which indicates a fatal hardware error has occurred.

Please run some stress tests to determine which hardware component is at fault. Follow the instructions from the links below.

RAM - Test with Memtest86+

Hardware - Stress Test With Prime95

Video Card - Stress Test with Furmark

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80097c9028, be000000, 100110a}

Probably caused by : hardware

Followup: MachineOwner

user31 said:

Since nobody helped me I'll be a gent and help you :) ; a Hal.dll BSOD sounds a lot like a video card related problem. HAL means hardware abstraction layer. Try patching the driver and see if that helps. Best of luck.

I have tried to help you but you don't reply then you create multiple threads.
If you need help then not replying to your own thread or creating duplicate threads is the best way for help to come to you.
I go through all the threads that have no replies first so when you keep commenting I already think somebody is with you.
If you require assistance then message people on the BSOD team or reply to your previous thread when people have commented.



I don't mean to sound annoyed or angry it's just don't say people don't try to help when they do. I will be more than happy to help you if you have issues. :)

Ran the GPu test and it passed, I suppose. Temperature stopped at 68°C. Will run the hardware test and memtest shortly.

Edit: Started the hardware test but my CPU cores hit 80°C+ and I freaked out a little. Should they be getting this hot?

They can get this hot yes from stress tests. Just run it but make sure it doesn't go over 90C.

Anybody have any ideas?

hmm, we could try and enable Driver Verifier to see if a driver is at fault. I know it's a 0x124 bugcheck which indicates a fatal hardware error but I personally have encountered situations where 0x124 can be caused by drivers. It's rare but it can happen.
Follow these instructions on how to enable Driver Verifier.

Driver Verifier - Enable and Disable

As soon as I rebooted, I got a new BSOD. IRQL_NOT_LESS_OR_EQUAL. Rebooted again and tried to enter startup repair but I think it disables my USB ports and I can't select to restore or cancel.