BSOD after logging in - BCCode 124. Frequent Freezing of computer


  1. Posts : 13
    windows 7 home 64bit
       #1

    BSOD after logging in - BCCode 124. Frequent Freezing of computer


    Hi Everyone,

    I am using windows 7 and recently my computer freezes quite frequently, sometimes BSOD gets displayed and after logging in back again, crash dump (.dmp) file is getting created. This freezing happens even if i do nothing after logging in. I do not play games on my machine. I am attaching the dump files here, so that you may review it. I want to understand if the issue is a driver or a hardware issue. :)
      My Computer

  2.   My Computer


  3. Posts : 13
    windows 7 home 64bit
    Thread Starter
       #3

    Sorry and thanks Axe0.

    Here is the attachment, after running the DM log collector.
      My Computer


  4. Posts : 13
    windows 7 home 64bit
    Thread Starter
       #4

    Hi,

    I ran windbg and analyzed one .dmp file.

    Below is the result of the analysis of the debugger. Bug check analysis is pointing issue towards hardware. Need help to understand the issue, if it is a hardware issue, then which is the hardware. I did ran memtestx86, sfc scannow and chkdsk but
    found no issues after running them.

    -----------------------------------------------------------------------------------------------

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

    Use !analyze -v to get detailed debugging information.

    BugCheck 124, {0, fffffa80088ad8f8, 0, 0}

    Probably caused by : hardware

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

    3: 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: 0000000000000000, Machine Check Exception
    Arg2: fffffa80088ad8f8, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


    BUGCHECK_STR: 0x124_GenuineIntel

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    STACK_TEXT:
    fffff880`033af6f0 fffff800`036ddc59 : fffffa80`088ad8d0 fffffa80`05a73b60 00000000`00000007 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`033afc10 fffff800`035bdfa7 : fffffa80`088ad8d0 fffff800`036382b8 fffffa80`05a73b60 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`033afc40 fffff800`035255c5 : fffff800`03699ac0 00000000`00000001 fffffa80`088f1860 fffffa80`05a73b60 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`033afc80 fffff800`034a5021 : fffff880`014fce00 fffff800`035255a0 fffffa80`05a73b00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`033afcb0 fffff800`0373732e : 00000000`00000000 fffffa80`05a73b60 00000000`00000080 fffffa80`05a5c5f0 : nt!ExpWorkerThread+0x111
    fffff880`033afd40 fffff800`0348c666 : fffff880`031d5180 fffffa80`05a73b60 fffff880`031dffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`033afd80 00000000`00000000 : fffff880`033b0000 fffff880`033aa000 fffff880`033af6a0 00000000`00000000 : nt!KiStartSystemThread+0x16


    STACK_COMMAND: kb

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME: hardware

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

    BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

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

    3: kd> lmvm hardware
    start end module name
    Mini Kernel Dump does not contain unloaded driver list
      My Computer


  5. Posts : 7,050
    Windows 10 Pro
       #5

    Yes, 0x124 means that an unknown hardware problem has occured. This may, however, be caused by
    - hardware
    - drivers
    - BIOS
    - and even software, mainly motherboard/laptop manufacturer software.

    Please make sure that Windows is fully up to date.
    Code:
    Hotfix(s):                 7 Hotfix(s) Installed.
      My Computer


  6. Posts : 13
    windows 7 home 64bit
    Thread Starter
       #6

    Thanks Axe0 for replying.

    I will update windows, been a quite time i updated it.
    I also suspect the wifi card/driver to be a source of issue, because currently i do not see the driver/device located under Network Adapters in device manager and my machine has not hanged for more than around 2 hours.
      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 17:33.
Find Us