BSOD 0x124 hal.dll

Toggle sidebar Toggle sidebar
D

Diels_Alder

Honorable
Oct 4, 2013
4
0
10,510
All-
I would love to get some assistance with my recent BSOD issues. It can happen anytime, but usually within 5-30 minutes of booting. The system is currently only stable in safe mode. It first started showing up when playing games, but now it appears outside of games. My computer is a custom build, no overclocking, and has been stable since I built it (2 months). I have made no recent hardware or software changes.

MB: AsRock Z77 Extreme 4 LGA1155
CPU: Intel i5 2500k
RAM: GSkills Ripjaw DDR3 1600
GPU: Nvidia GTX 650 Ti

1. Ran Memtest86 for 12 hours, no issues.
2. Ran a torture test, all internal temps never rose above 55C.
3. Downloaded driver utility and updated all drivers.
4. Ran msched, no issues.
5. Updated mobo bios from 2.80 to 2.90, no change. Reverted back to 2.80.
6. I've re-seated all hardware, re-made all connections, and thoroughly cleaned all components.
7. Run SFC /scannow, no issues.
8. Ran a registry cleaner.

Using a bluescreen viewer, the crashes appear to be caused by driver hal.dll (crash address ntoskrnl.exe)

The system is still only stable in Safe mode (with networking).

Thanks for your time!

Thank you!
 
Solution
Kelthar
Re-installing windows is the only thing left to do.

Also, due to the fact that it doesn't crash on safe-mode it rules out hardware issues. This is most likely software-level problems, my best guess would be drivers, but since those are updated then your windows installation is most likely corrupt for some reason.

EDIT: Also, how's the state on OCs? Any overclocking on either GPU or CPU?
Sort by date Sort by votes
Kelthar

Kelthar

Honorable
Mar 27, 2013
640
0
11,360
Re-installing windows is the only thing left to do.

Also, due to the fact that it doesn't crash on safe-mode it rules out hardware issues. This is most likely software-level problems, my best guess would be drivers, but since those are updated then your windows installation is most likely corrupt for some reason.

EDIT: Also, how's the state on OCs? Any overclocking on either GPU or CPU?
 
Upvote 0 Downvote
Solution
E

enemy1g

Honorable
Oct 3, 2013
2,224
1
12,460
Check your voltages to your CPU (as well as the other components). I was getting the same error. Error 124 is usually hardware related, and when I had the issue both hal.dll and ntoskrnl.exe were the cause of the BSODs. It turns out my BIOS defaulted to an adaptive power option, and when I switched it to manual and put 1.2v on the CPU the issue went away.
 
Upvote 0 Downvote
D

Diels_Alder

Honorable
Oct 4, 2013
4
0
10,510
Thank you for the responses.

I've done very little OC'ing of the system. In the course of troubleshooting, I have tried a few of the preset OC profiles without any apparent increase or decrease in BSODs.

I tried changing CPU voltages to fixed values (default is "auto"), such as 1.1 and 1.2v - still no change in stability of the system.

I'll perform a fresh install of Windows 7 and report back.

Thank you for your time!
 
Upvote 0 Downvote
D

Diels_Alder

Honorable
Oct 4, 2013
4
0
10,510
Update:

I got through a fresh install of Windows 7 (Pro, 64 bit), and in the process of installing the essential drivers from the disc supplied with the mobo - I got the BSOD 0x124 again. Ugh. I have not been able to get through a refresh re-install again w/o BSOD. I am now back to believing it to be a hardware issue.

I pulled my GPU (using the onboard adapter for video) and still get the BSOD. I pulled my RAM sticks, moved them over to the other channel(s) - still getting BSOD.

Not sure what to try next, since that only leaves my CD drive, RAM, PSU, and hard drive - and I need all of these to install Windows (right?). I was thinking of pulling everything out of the case on the off chance something is shorting out (even though it POSTs just fine).

All ideas would be greatly appreciated!

Thanks!
 
Upvote 0 Downvote
Kelthar

Kelthar

Honorable
Mar 27, 2013
640
0
11,360
Reseat the RAM: take it out and place it back in, as simple as that.

The fact that it's persisting and happening during installation means it's a hardware issue, for sure.

Do you have any Linux Live-CD (or live USB installation)? If so, boot it up with the HDD unplugged (just the SATA cable unplugged is enough, you can leave the power cable). This, to see if the HDD might be the problem.

I assume you have another computer otherwise you wouldn't be able to write here, so as long as it has a USB port and you have a flash drive, install a simple linux distribution to it, whichever it is, just so that the computer can boot up.

Linux doesn't throw out blue screens, so in place of one the screen will either freeze, the computer will restart or shutdown, or a message saying the kernel panicked or something will be shown.

Also, please remove all CPU OCs, put it on stock settings.
 
Upvote 0 Downvote
D

Diels_Alder

Honorable
Oct 4, 2013
4
0
10,510
Thanks for your great response Kelthar.

I re-seated the RAM, still getting BSOD.
I haven't OC'd this system, but I verified that all BIOS settings are default.

As suggested, I created a Ubuntu boot flash drive. Prior to booting into Ubuntu, I disconnected by CD drive and HDD. I was able to boot into Ubuntu w/o issue (obviously no BSOD, but no freezing or weird restarts/shutdowns). I then re-connected my HDD and was able to successfully perform a full install of Ubuntu w/o issue. I then re-connected my CD drive and was able to boot w/o issue.

I threw my Windows 7 disc into the CD drive and then tried to boot from it and got an instant BSOD.

I then tried to boot back into Ubuntu and it froze at the Ubuntu splash screen. Disconnecting my CD drive got things going again. This phenomenon has been repeatable (OK w/o CD drive, not so great with it). So it's the CD drive? Or was I just getting lucky prior to re-connecting the CD drive? I was unable to run any real stress tests in Ubuntu (besides memtest) b/c I'm so unfamiliar with that OS, so I can't be sure. Is it that the hardware issue is still there and that it's just not being "recognized" by Ubuntu uniformly?

I am in the process of generating a Windows 7 USB bootable to try all this over again. (I'm having trouble generating a "valid" ISO (according to the Microsoft tool)from my Windows 7 disc, any suggestions?)

Also, after doing some more research, a lot of folks seem to think the BSOD 0x124 is generally due to a vcore issue - and that increasing or decreasing it may be the solution.

Any guidance as to how to proceed from here would be greatly appreciated!

Thanks again!

Update: Here's some more detail from one of my dump files. Maybe it is the CPU voltage?!?!

----
BugCheck 124, {0, fffffa8007b25028, b2000000, 30005}

Probably caused by : GenuineIntel
----

1: kd> !errrec fffffa8007b25028
===============================================================================
Common Platform Error Record @ fffffa8007b25028
-------------------------------------------------------------------------------
Record Id : 01cec0983c1341a2
Severity : Fatal (1)
Length : 864
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 10/4/2013 0:36:21 (UTC)
Flags : 0x00000000

===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ fffffa8007b250a8
Section @ fffffa8007b25180
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal

Proc. Type : x86/x64
Instr. Set : x64
Error Type : Micro-Architectural Error
Flags : 0x00
CPU Version : 0x00000000000206a7
Processor ID : 0x0000000000000002

===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ fffffa8007b250f0
Section @ fffffa8007b25240
Offset : 536
Length : 64
Flags : 0x00000000
Severity : Fatal

Local APIC Id : 0x0000000000000002
CPU Id : a7 06 02 00 00 08 10 02 - bf e3 9a 1f ff fb eb bf
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa8007b25138
Section @ fffffa8007b25280
Offset : 600
Length : 264
Flags : 0x00000000
Severity : Fatal

Error : Unknown (Proc 1 Bank 0) <-- Possibly not publicly documented by Intel
Status : 0xb200000000030005
 
Upvote 0 Downvote
Kelthar

Kelthar

Honorable
Mar 27, 2013
640
0
11,360
You should change voltage to Auto if it wasn't already, by the way. The motherboard can handle voltages just fine on its own when on stock.

The CD/DVD reader causing BSODs is weird. Plug it in after changing voltages to auto, run until you get a BSOD or a kernel panic. Once you get one, unplug, and try it out.

Use the computer normally without the CD/DVD, if it crashes you can be certain it's not it (just a coincidence).

NOTE: It's not it IF you assume there aren't multiple components failing at the same time, which would be one hell of a bad luck.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom