BSOD: Bug Check Code: 0x00000124


  1. Posts : 1
    Windows 7 home premium 64-bit Sp1
       #1

    BSOD: Bug Check Code: 0x00000124


    Hello,
    I am experiencing random system crashes and restarts.
    More information:
    Dump File : 070213-16411-01.dmp
    Crash Time : 7/2/2013 3:28:08 AM
    Bug Check String :
    Bug Check Code : 0x00000124
    Parameter 1 : 00000000`00000000
    Parameter 2 : fffffa80`0ac1b038
    Parameter 3 : 00000000`00000000
    Parameter 4 : 00000000`00000000
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+4ade0c
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows®
    Operating System Company : Microsoft Corporation
    File Version : 6.1.7601.18113 (win7sp1_gdr.130318-1533)
    Processor : x64
    Crash Address : ntoskrnl.exe+4ade0c
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\070213-16411-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 262,144
    Dump File Time : 7/2/2013 3:28:11 AM
      My Computer

  2.    #2

    Welcome to the forums HdogXero,

    Code:
    BugCheck 124, {0, fffffa800aa1d8f8, 0, 0}
    
    Probably caused by : AuthenticAMD
    Code:
    Hardware, Incompatibility, May be driver corruption
    Code:
    3: kd> !errrec fffffa800aa1d8f8
    ===============================================================================
    Common Platform Error Record @ fffffa800aa1d8f8
    -------------------------------------------------------------------------------
    Record Id     : 01ce76b594bca441
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 7/1/2013 23:49:22 (UTC)
    Flags         : 0x00000002 PreviousError
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa800aa1d978
    Section       @ fffffa800aa1da50
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : BUS error
    Operation     : Generic
    Flags         : 0x00
    Level         : 3
    CPU Version   : 0x0000000000100f43
    Processor ID  : 0x0000000000000000
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa800aa1d9c0
    Section       @ fffffa800aa1db10
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000000
    CPU Id        : 43 0f 10 00 00 08 04 00 - 09 20 80 00 ff fb 8b 17
                    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  @ fffffa800aa1db10
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa800aa1da08
    Section       @ fffffa800aa1db90
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
      Status      : 0xfa00000000070f0f
    The first parameter or argument has the value of 0x0, which is a Machine Check Exception, which means the CPU has detected a hardware problem and the address points to a processor error because the CPU has found one, so it could be a different form of hardware which is causing the issue. This is supported with shown error from the !errrec output, a request has timed out, but where the timeout occurred is unknown.

    In such a situation, it is best to use these steps:

    Enable "Round off checking" before the test (see first post below tutorial).

    All the hardware seeming to be running stable and tests reporting no errors, could mean a bad motherboard.
      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 00:41.
Find Us