Windows 10: BSOD 0x00000124 and HAL.dll

Discus and support BSOD 0x00000124 and HAL.dll in Windows 10 BSOD Crashes and Debugging to solve the problem; A friend purchased a Dell XPS 8900 just before Christmas and dropped it off to me for some upgrades (PSU, GTX 770, SSD). After installing the new... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by mconway, Jan 9, 2016.

  1. mconway Win User

    BSOD 0x00000124 and HAL.dll


    A friend purchased a Dell XPS 8900 just before Christmas and dropped it off to me for some upgrades (PSU, GTX 770, SSD). After installing the new hardware I did a fresh install of Win10 Home x64 and sent it back. He contacted me recently about lockups he has been having and today was the first chance I've had to look at it. First thing I fired up bluescreenview and had a look. There were 50 BSOD's since Dec 28, all with 0x00000124 and HAL.dll as the culprit. I'm a very experienced system builder and can install/tweak Windows in my sleep but analyzing BSOD's is not my strong suit. I know the video card, hard drives, PSU to be good and am currently testing the RAM. If anybody can have a look at the dump files and offer some advice I'd appreciate it.

    :)
     
    mconway, Jan 9, 2016
    #1
  2. AngDean Win User

    hal.dll+35f1f bsod error in Windows 10

    OT- hal.dll+35f1f bsod

    Hello,

    There was a bsod just now, which is the first time I've experienced it - and should I be worrying about it?

    This is what I got from BlueScreenView:

    071816-24656-01.dmp

    18/7/2016 8:23:23 PM

    0x00000124

    00000000`00000000

    ffffe000`2db12028

    00000000`b2000000

    00000000`00100402

    hal.dll

    hal.dll+35f1f

    x64

    ntoskrnl.exe+142940

    C:\WINDOWS\Minidump\071816-24656-01.dmp

    What caused this? Thanks!
     
    AngDean, Jan 9, 2016
    #2
  3. BSOD w/ a WHEA_UNCORRECTABLE_ERROR after building a new PC with the hard-drive from my old PC.

    The error code is 0x00000124 and it appears to be caused by hal.dll(+3267f) and ntoskrnl.exe(+226800).

    Here's a google drive link to the minidump file: 112317-27734-01.dmp

    Anyone think they could help?
     
    Dragonslayerelf, Jan 9, 2016
    #3
  4. axe0 New Member

    BSOD 0x00000124 and HAL.dll

    This is an interesting one, a PCI-E error.
    Why this is an interesting one is explained below.
    Analyse
    Code: WHEA_UNCORRECTABLE_ERROR (124) 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. Arguments: Arg1: 0000000000000004, PCI Express Error Arg2: ffffe00149c188d8, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000 Arg4: 0000000000000000 1: kd> !errrec ffffe00149c188d8 =============================================================================== Common Platform Error Record @ ffffe00149c188d8 ------------------------------------------------------------------------------- Record Id : 01d14ac7a0212c9e Severity : Fatal (1) Length : 672 Creator : Microsoft Notify Type : PCI Express Error Timestamp : 1/9/2016 11:34:48 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : PCI Express ------------------------------------------------------------------------------- Descriptor @ ffffe00149c18958 Section @ ffffe00149c189e8 Offset : 272 Length : 208 Flags : 0x00000001 Primary Severity : Recoverable Port Type : Root Port Version : 1.1 Command/Status: 0x0810/0x0407 Device Id : VenIdBSOD 0x00000124 and HAL.dll :DevId : 8086:a110 Class code : 030400 Function No : 0x00 Device No : 0x1c Segment : 0x0000 Primary Bus : 0x00 Second. Bus : 0x00 Slot : 0x0000 Dev. Serial # : 0000000000000000 Express Capability Information @ ffffe00149c18a1c Device Caps : 00008001 Role-Based Error Reporting: 1 Device Ctl : 0007 ur FE NF CE Dev Status : 0012 ur fe NF ce Root Ctl : 0008 fs nfs cs AER Information @ ffffe00149c18a58 Uncorrectable Error Status : 00008000 ur ecrc mtlp rof uc CA cto fcp ptlp sd dlp und Uncorrectable Error Mask : 00000000 ur ecrc mtlp rof uc ca cto fcp ptlp sd dlp und Uncorrectable Error Severity : 00060011 ur ecrc MTLP ROF uc ca cto fcp ptlp sd DLP UND Correctable Error Status : 00000000 adv rtto rnro dllp tlp re Correctable Error Mask : 00000000 adv rtto rnro dllp tlp re Caps & Control : 0000000f ecrcchken ecrcchkcap ecrcgenen ecrcgencap FEP Header Log : 00000000 00000000 00000000 00000000 Root Error Command : 00000000 fen nfen cen Root Error Status : 00000000 MSG# 00 fer nfer fuf mur ur mcr cer Correctable Error Source ID : 00,00,00 Correctable Error Source ID : 00,00,00 =============================================================================== Section 1 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffe00149c189a0 Section @ ffffe00149c18ab8 Offset : 480 Length : 192 Flags : 0x00000000 Severity : Informational Proc. Type : x86/x64 Instr. Set : x64 CPU Version : 0x00000000000506e3 Processor ID : 0x0000000000000001[/quote] Looking at the hardware we can see it is the Intel(R) 100 Series/C230 Series Chipset Family PCI Express Root Port #1
    Code: Name: Intel(R) 100 Series/C230 Series Chipset Family PCI Express Root Port #1 - A110 Device ID: PCI\VEN_8086&DEV_A110&SUBSYS_06B81028&REV_F1\3&11583659&0&E0 Driver: n/a[/quote] Update the Intel 100 series chipset drivers and let me know how it goes *Smile
    Product Support | Dell US


    Explanation why the error is interesting
    Normally with a 0x124 we see the parameter MCE (Machine Check Exception) instead of the PCI Express error.
    MCE is another bluescreen, 0x9C(MACHINE_CHECK_EXCEPTION) that was used for older systems, this bluescreen still exists in current systems (Windows 7, 8, 8.1 and 10).
    When we look at the address of the WHEA_ERROR_RECORD structure as also done above, we see a different output with an MCE.
    In this case it shows an internal unclassified error on core 4 cache bank 4 what means the error hasn't been publicly documented, this error usually relates to a faulty CPU. However, an MCE error unfortunately only shows the problem that has been caught by the CPU, this does NOT mean that the CPU is the problem. With an MCE error the dump usually does not reveal enough data to point to something specific as a cause.
    Code: WHEA_UNCORRECTABLE_ERROR (124) 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. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: ffffe001def18028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000ba000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000052000402, Low order 32-bits of the MCi_STATUS value. 4: kd> !errrec ffffe001def18028 =============================================================================== Common Platform Error Record @ ffffe001def18028 ------------------------------------------------------------------------------- Record Id : 01d149b8bf8340f9 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 1/8/2016 2:11:11 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffe001def180a8 Section @ ffffe001def18180 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 : 0x0000000000000004 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffe001def180f0 Section @ ffffe001def18240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000004 CPU Id : c3 06 03 00 00 08 10 04 - ff 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 @ ffffe001def18240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe001def18138 Section @ ffffe001def182c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Internal unclassified (Proc 4 Bank 4) Status : 0xba00000052000402[/quote]
     
    axe0, Jan 9, 2016
    #4
  5. mconway Win User
    Thanks for the prompt reply axe0. Chipset drivers have been updated from the Dell support site specific to the system tag and the computer is back in my friends' hands. I cleared out the minidump folder just in case there are are any errors going forward. Seeing how it was bluescreening multiple times every day, it should not take long to see if the problem is fixed. Will keep you updated.
     
    mconway, Jan 9, 2016
    #5
  6. axe0 New Member
    My apologies for bumping this thread, but I am very curious how things are going now *Smile
     
  7. Hi Axe0,

    I have same problem with my HP Pavilion laptop, this problem come randomly after log on to windows or after 30 minutes play game, i suspect this problem come after windows 10 auto update the build OS version but i dont update the laptop driver, Now i update bios to latest version but BSOD still came. Please help, and check my thread.

    BSOD randomly after booting, error code 0x00000124 - Windows 10 Forums

    Thanks.
     
    adnansukmana, Jul 11, 2016
    #7
  8. axe0 New Member

    BSOD 0x00000124 and HAL.dll

    Please do not post in other threads to give your thread more attention.
     
  9. Oh iam so sorry axe0 for the mistake, iam new member in this forum, actualy i am follow and read in this thread for solve my problem, and i think i can post in new thread for discus with my problem and then i give you new thread with detailed information. Thanks for the correction.
     
    adnansukmana, Apr 5, 2018
    #9
Thema:

BSOD 0x00000124 and HAL.dll

Loading...
  1. BSOD 0x00000124 and HAL.dll - Similar Threads - BSOD 0x00000124 HAL

  2. BSOD 0x00000124

    in Windows 10 BSOD Crashes and Debugging
    BSOD 0x00000124: Please help me figure this one out! It happens ~30 minutes into playing any video games... GPU issue? Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available. Symbol search path is: srv*...
  3. BSOD: No bluescreen but dump is there. 0x00000124

    in Windows 10 BSOD Crashes and Debugging
    BSOD: No bluescreen but dump is there. 0x00000124: Hello, I have attached the minidump. This has been going on for a few months now, sometimes it doesnt crash for few days and sometimes multiple times a day. I have tried everything. Memtest each ram and each slot. CPU temps are below 30 idle and around 40 while using...
  4. BSOD: No bluescreen but dump is there. 0x00000124

    in Windows 10 BSOD Crashes and Debugging
    BSOD: No bluescreen but dump is there. 0x00000124: Hello, I have attached the minidump. This has been going on for a few months now, sometimes it doesnt crash for few days and sometimes multiple times a day. I have tried everything. Memtest each ram and each slot. CPU temps are below 30 idle and around 40 while using...
  5. Bluescreen / BSOD 0x00000124

    in Windows 10 BSOD Crashes and Debugging
    Bluescreen / BSOD 0x00000124: I Got BDOD 0x00000124 with Caused By Driver hal.dll . Caused By Address hal.dll+477e7 , hal.dll+47803 I Used Windows 10 Pro . System : Amd A6-6400k Apu with Radeon(tm) HD Graphic 3.92 GHz Ram: 4GB System Type: 64bit Operating System,x64 Based Processor I Provide...
  6. BSOD caused by 0x00000124

    in Windows 10 BSOD Crashes and Debugging
    BSOD caused by 0x00000124: I've been getting a BSOD under this error for about a year now, I've done a system reset and nothing's fixed it. https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/bsod-caused-by-0x00000124/ee169a5b-f007-4e73-b880-a59298a408f8
  7. BSOD error 0x00000124

    in Windows 10 BSOD Crashes and Debugging
    BSOD error 0x00000124: Attachment 114444 Hello, I got 2 consecutive crashes while playing rainbow 6 siege. The first time it simply freeze. The second time I got BSOD. Can anyone help me pinpoint the problem? Zip file attached Thank 73089
  8. Random BSOD 0x00000124

    in Windows 10 BSOD Crashes and Debugging
    Random BSOD 0x00000124: It tends to happen when I'm doing anything CPU intensive (mostly gaming or video editing). As I understand it x124 is usually a hardware error and I have ruled out bad RAM and bad drives. This didn't start until I upgraded my cpu/mb so I'm fairly sure it's one of the two...
  9. BSOD hal.dll 0x00000124

    in Windows 10 BSOD Crashes and Debugging
    BSOD hal.dll 0x00000124: So I'm new to this forum and checked out the instructions about posting but still I apologize if I do something wrong. For a few weeks my PC has been suddenly stopping and displaying the blue screen and saying WHEA UNCORRECTABLE ERROR. I searched for what this could mean...
  10. BSOD - *** STOP: 0x00000124

    in Windows 10 BSOD Crashes and Debugging
    BSOD - *** STOP: 0x00000124: I have been receiving BSOD's since i replaced several hardware items two weeks ago (and I copied my C drive from my old SSD to my new one). They have been occuring regularly, however sometimes i have also been able to use my PC for several hours without any issues. It...