BSOD 0x124


  1. Posts : 4
    Windows Ultimate 32 Bit
       #1

    Random BSOD 0x124 Occurs Frequently


    I have a HP Probook 4310 S, 4Gb RAM, Windows Ultimate 32 bit.
    Am experiencing BSOD 0x124 very frequently and randomly for the past 2 months.
    Also experiencing several other BSOD codes as well.
    I did a Hard Disk test from HP Diagnostics Tool.
    And it mentioned failed.
    Memory Test was successfull.

    After boot, BSOD 0x124 occurs at any time 5 mins, 1 hour ,2 hrs.
    But BSOD never occured while in safe mode. able to use safe mode for several hours.
    Am worried if it is only the hard disk that has failed or the processor or the motherboard.

    Also warranty expired last month and it is quite expensive to extend it.

    I have reinstalled Windows 7 2 times in the past week.

    I have attached recent minidumps. Please let me know.
    Thanks a lot in advance.
      My Computer


  2. Posts : 1,454
    Windows 7 ultimate x64
       #2

    hi

    I did a Hard Disk test from HP Diagnostics Tool.
    And it mentioned failed
    I think you have answered half of your question..... Try doing a Disk Check as well as Post the SMART Value of the HDD here to confirm (post a snapshot)


    Second all the BSOD point to like you said a Bugcheck 0x124 error...... this is a hardware errors specifically related to the processor. Since overclocking can be ruled out as the laptop doesn't have that feature.... then the only other possibility is heating ....if you check your logs you can see

    ACPI thermal zone ACPI\ThermalZone\CPUZ has been enumerated.
    _PSV = 378K
    _TC1 = 1
    _TC2 = 2
    _TSP = 30000ms
    _AC0 = 357K
    _AC1 = 340K
    _AC2 = 330K
    _AC3 = 320K
    _AC4 = 313K
    _AC5 = 303K
    _AC6 = 0K
    _AC7 = 0K
    _AC8 = 0K
    _AC9 = 0K
    _CRT = 381K
    _HOT = 0K
    _PSL - see event data.
    The temps are above 84 deg C ..... at that point of time.....which is high..... check your temps using coretemp or speedfan... Are the air vent dusty ???

    Let me know....
      My Computer


  3. Posts : 4
    Windows Ultimate 32 Bit
    Thread Starter
       #3

    Hi , Thank u so much for ur reply.
    i have attached the screeenshots of hard disk check and crystal disk info.

    The air vent is not dusty.
    So, pl let me know if it is a processor or a hard disk problem or anything else.
    Thanks a lot for your info.

    Also, will install speedfan and core temp and let u know the results.
      My Computer


  4. Posts : 1,454
    Windows 7 ultimate x64
       #4

    The check disk did find problems with you MFT $BITMAP attribute which is actually NTFS file system corruption. You HDD smart values look good with no bad sectors

    Run chkdsk C: /F to remove the above error.

    Again... you wont actually find it dusty outside... it might be dusty inside the fins and maybe the air is not able to vent out properly... try using a vaccum to suck it out... let me know the temps

    Also update windows 7 to SP1.

    do these and let me know
      My Computer


  5. Posts : 4
    Windows Ultimate 32 Bit
    Thread Starter
       #5

    I have attached the speedfan results. Seems like my CPU is hot at the moment.
    Also will check the air vent properly. Will update to SP1 also.

    Also all the attributes in S.M.A.R.T tab in speedfan for Hard Disk are O.K.
    Will buying a coolerpad be helpful?
      My Computer


  6. Posts : 4
    Windows Ultimate 32 Bit
    Thread Starter
       #6

    Hi centaur,

    I got two BSODs with different codes,
    both were during the boot up.

    Also noticed that went I went from balanced to power saver in options,
    and going from 1366*768 to 1280*768, there was no BSOD for more than 8 hours.

    I have updated to SP1 and have installed other Windows updates.
    Also attached System Info and Minidumps in the attachment.
    Pl have a look and help me.
    Thanks a lot.

    P.S. will clean air vents during the weekend.
      My Computer


  7. Posts : 1,454
    Windows 7 ultimate x64
       #7

    Hi

    The last two BSOD are

    Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
    and

    Bugcheck 0x124. This bug check indicates that a fatal hardware error has occurred.
    And below is the analysis for 082412-25833-01.dmp

    ....
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 124, {0, 8653e024, b2000040, 800}

    Probably caused by : GenuineIntel

    Followup: MachineOwner
    ---------

    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    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: 00000000, Machine Check Exception
    Arg2: 8653e024, Address of the WHEA_ERROR_RECORD structure.
    Arg3: b2000040, High order 32-bits of the MCi_STATUS value.
    Arg4: 00000800, Low order 32-bits of the MCi_STATUS value.

    Debugging Details:
    ------------------


    BUGCHECK_STR: 0x124_GenuineIntel

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: 1f

    STACK_TEXT:
    82b33d0c 82e2ffcd 00000124 00000000 8653e024 nt!KeBugCheckEx+0x1e
    82b33d48 82ae0a6c 864d4b89 8653e024 82a872d0 hal!HalBugCheckSystem+0xab
    82b33d78 82e3027f 864d49e0 82e3de40 00000000 nt!WheaReportHwError+0x230
    82b33e8c 82e30371 864d49e0 864d4a30 00000002 hal!HalpMcaReportError+0x3b
    82b33eb0 82e3048d 00000000 864d4a30 00000000 hal!HalpMceHandler+0x8b
    82b33ed0 82e305d6 00000000 864d49e0 82b33ff0 hal!HalpMceHandlerWithRendezvous+0x4b
    82b33ee0 82e265f5 00000000 00000000 00000000 hal!HalpHandleMachineCheck+0x34
    82b33ff0 82e23261 00000002 801de000 00000000 hal!HalpMcaExceptionHandler+0x87
    82b33ff0 00000000 00000002 801de000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x89


    STACK_COMMAND: kb

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: GenuineIntel

    IMAGE_NAME: GenuineIntel

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_BUS

    BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_BUS

    Followup: MachineOwner
    ---------

    0: kd> !errrec 8653e024
    ===============================================================================
    Common Platform Error Record @ 8653e024
    -------------------------------------------------------------------------------
    Record Id : 01cd81d9a5f98563
    Severity : Fatal (1)
    Length : 928
    Creator : Microsoft
    Notify Type : Machine Check Exception
    Timestamp : 8/24/2012 9:20:24 (UTC)
    Flags : 0x00000000

    ===============================================================================
    Section 0 : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor @ 8653e0a4
    Section @ 8653e17c
    Offset : 344
    Length : 192
    Flags : 0x00000001 Primary
    Severity : Fatal

    Proc. Type : x86/x64
    Instr. Set : x86
    Error Type : BUS error
    Operation : Generic
    Flags : 0x00
    Level : 0
    CPU Version : 0x000000000001067a
    Processor ID : 0x0000000000000000

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

    Local APIC Id : 0x0000000000000000
    CPU Id : 7a 06 01 00 00 08 02 00 - fd e3 08 0c 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 @ 8653e23c

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

    Error : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)
    Status : 0xb200004000000800
    Thats the L1 cache thats at fault... probably damaged by heating....

    Sorry to say this... i would suggest you get the processor check or replaced...
      My Computer


 

  Related Discussions
Our Sites
Site Links
About 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 07:10.
Find Us