Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Bugcheck 124 - Hal.dll - Need a read on what is failing

06 Mar 2016   #1
FuzzyDice

Windows 7 Home Premium 64bit
 
 
Bugcheck 124 - Hal.dll - Need a read on what is failing

I know this is a hardware failure based on a little research. This machine used to be stable but crashes about every 6 - 48 hours.

I have replaced a PSU (the fan seemed to be going anyway), updated the Bios, added a case fan and reset my bios so that over clocking is off (I think it got turned on during a previous bios flash).

I unfortuantely don't have the time to read up on reading bluescreen data - Thanks for the help.

I'm hoping something indicates a processor failure as my hunch is the now reset OC setting may have baked the stock fan thermal compound but I really don't want to waste time and money at it on a bad hunch,




Attached Files
File Type: zip MEDIA_002-Sun_03_06_2016__00739_23.zip (1.78 MB, 2 views)
My System SpecsSystem Spec
.
06 Mar 2016   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Code:
BugCheck 124, {0, fffffa800fdd1028, be000000, 800400}

Probably caused by : GenuineIntel

Followup:     MachineOwner
---------
0x124 is WHEA_UNCORRECTABLE_ERROR. WHEA means Windows Hardware Error Architecture. It elaborates as ....
Quote:
A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon.
So it is a hardware level failure. When the parameter 1 is zero, it means ....
Arg1: 0000000000000000, Machine Check Exception
It means that the Processor reported a hardware error. And the source of occurrence of the issue is un-traced. It may be anything and everything within the computer's environment.
And following the second parameter becomes meaningless here. It just gives a hint of the processor core where the error was traced. As in your case ....
Code:
===============================================================================
Common Platform Error Record @ fffffa800fdd1028
-------------------------------------------------------------------------------
Record Id     : 01d176258e7ce3c5
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 3/5/2016 6:37:20 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800fdd10a8
Section       @ fffffa800fdd1180
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   : 0x00000000000306c3
Processor ID  : 0x0000000000000006

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa800fdd10f0
Section       @ fffffa800fdd1240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000006
CPU Id        : c3 06 03 00 00 08 10 06 - bf fb fa 7f 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

Proc. Info 0  @ fffffa800fdd1240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800fdd1138
Section       @ fffffa800fdd12c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal timer (Proc 6 Bank 4)
  Status      : 0xbe00000000800400
  Address     : 0x0000000057785b4b
  Misc.       : 0x0000000057785b4b
It will look like the processor itself is causing the issue. But that will be a very misleading information. It is not a processor failure, it is a failure reported by the processor (which may be a processor failure, or any other hardware related issue as well.)

The best way to troubleshoot this issue is to follow Stop 0x124 - what it means and what to try. It is lengthy and time consuming process, but it will narrow down the issue.
My System SpecsSystem Spec
Reply

 Bugcheck 124 - Hal.dll - Need a read on what is failing




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
DVD drive failing to read DVD-RW's but reads other disks
Recently my DVD drive has been doing something weird. When i insert a CD of any type, it works fine, when i insert a DVD which is not an RW, it works fine, but when i insert a DVD-RW, it does its normal loading sound, some cracking and then does a very weird noise, and i hear some spinning, and the...
Hardware & Devices
Eventid 24620 error 0x80000010 at boot failing to read W8 partition
I have W7 Pro 64bit in a dual boot with W8.1 Pro 64 bit on a Dell Inspiron laptop. I purchased and installed a Crucial SSD and used Acronis True Image 2014 to backup and restore to the new SSD. All the backup and restore went without an error. Each system boots and is functional. When W7 is...
Hardware & Devices
BSOD on start, Startup Repair: Unknown Bugcheck: Bugcheck 3d
We've been getting a BSOD on one of our computers on startup recently. The exact message the BSOD gives varies but often mentions atapi.sys. Having done extensive research we've come to the conclusion that it could be a rootkit or it could be the fact that we have Daemon Tools installed on the...
BSOD Help and Support
Check disk failing, disk read errors, blue screen, computer going slow
As of late my PC has been going very slow, stuttering, freezing for a minute occasionally, and sometimes when I restart I get a disk read error that requires me to turn the PC off and on again. I ran check disk using command prompt, it got to 12% before it said it had found corrupt files, now it...
General Discussion
Unknown Bugcheck : Bugcheck c00002e3 - System is randomly Shutting OFF
T61 4GB Kingston T61 specific Ram 2.5GHz 6459CTO T9300 (965 Chipset) Fresh, Full licensed copy of Win 7 Ultimate loaded onto system, without issues. All device drivers from the Lenovo site have been loaded successfully without incident. Device Manager showing Zero issues.
BSOD Help and Support
Explorer failing to read my computer & No icons
I've got a problem that came up recently and I think it might have something to do with one of the latest Windows 7 updates. Most of the time when I open up My Computer, it scans for a really long time and shows nothing(ie.no HDDs, Optical Drives or Network Locations) and in certain folders the...
General Discussion


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 23:41.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App