locked
BSOD and Restarts RRS feed

  • Question

  • Hello,

    My computer has been restarting randomly through the last 2 weeks. Sometimes it will stay on for 2 hours, and sometimes it will boot to the login screen and restart immediately. So far, safe mode has seemed to work. I have just disabled the automatic restart on error so I can see any BSOD screens and codes. This error from the MEMORY.DMP file is the only one I have been able to find so far.

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

    File: MEMORY.DMP

    Crash Time: 1/2/2014 3:49:09 AM

    Bug Check Code: 0x00000124

    Parameter 1: 00000000`00000000

    Parameter 2: fffffa80`08dc8028

    Parameter 3: 00000000`f4800000

    Parameter 4: 00000000`00040e0f

    Processor: x64

    Full Path: C:\Windows\MEMORY.DMP

    Processor Count: 8

    Major Version: 15

    Minor Version: 7601

    Dump File Size: 339,710,570

    Dump File Time: 1/2/2014 3:50:34 AM

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

    My specs are:

    ASUS M5A99FX Pro R2.0

    AMD FX-8350 8-Core 4.00

    8 GB DDR3 Corsair Vengeance

    MSI Radeon HD 7870

    1863GB Seagate ST2000DL003-9VT166

    I have checked the CPU, GPU, RAM, and HDD for errors and found none. I have reset and reseated pretty much everything. I have scanned for malware, reinstalled video drivers, and ran benchmark and stability tests. I have updated the BIOS to the latest version.

    Please Help! I am going to try the power supply while I await your reply. Thank you!

    Friday, January 3, 2014 4:02 PM

Answers

  • The possibility of both memory modules failing at the same time is unlikely, so I'm really curious if you made any BIOS changes or overclocking, that could result into RAM issues, recently.

    I did some analysis of the MEMORY.DMP file you provided, but, as usually with WHEA BSODs, it's very difficult to say what exactly cause the issue. Anyways, there are my findings:

    First, let's run initial automated analysis:

    *******************************************************************************
    *                                                                             *
    *                        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: fffffa8008dc5028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000f4800000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000040e0f, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    Page 220f41 not present in the dump file. Type ".hh dbgerr004" for details
    
    BUGCHECK_STR:  0x124_AuthenticAMD
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  XmppAuth.exe
    CURRENT_IRQL:  f
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    STACK_TEXT:  
    fffff880`01f91b88 fffff800`02226a3b : 00000000`00000124 00000000`00000000 fffffa80`08dc5028 00000000`f4800000 : nt!KeBugCheckEx
    fffff880`01f91b90 fffff800`023e9463 : 00000000`00000001 fffffa80`07cc08f0 00000000`00000000 fffffa80`07cc0940 : hal!HalBugCheckSystem+0x1e3
    fffff880`01f91bd0 fffff800`02226700 : 00000000`00000728 fffffa80`07cc08f0 fffff880`01f91f30 fffff880`01f96000 : nt!WheaReportHwError+0x263
    fffff880`01f91c30 fffff800`02226052 : fffffa80`07cc08f0 fffff880`01f91f30 fffffa80`07cc08f0 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`01f91d80 fffff800`02219e8f : fffffa80`09f564f0 00000000`00000001 fffff880`01f91fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`01f91dc0 fffff800`022d14ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
    fffff880`01f91df0 fffff800`022d1313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`01f91f30 fffff800`02406e02 : 00000000`00000099 00000000`0000afd1 fffffa80`09a09980 00000000`00000000 : nt!KiMcheckAbort+0x153
    fffff880`098f7610 fffff800`022e5f56 : fffffa80`000001a4 00000000`00000018 fffffa80`09ef5ab0 00000000`000007ff : nt!ExAllocatePoolWithTag+0x1f2
    fffff880`098f7700 fffff880`02caee91 : fffffa80`0a7c5340 fffffa80`0a7c54e8 fffff880`098f77c0 fffffa80`09ef5ad0 : nt!ExAllocatePoolWithQuotaTag+0x56
    fffff880`098f7750 fffff880`02cc66dc : fffffa80`09ef5ac0 fffff880`098f77c0 fffffa80`0a7c5340 fffff800`022e39cc : afd!AfdPollGetInfo+0x21
    fffff880`098f7790 fffff880`02cb6d3b : fffffa80`08ea9d00 00000000`00000000 00000000`00000001 00000000`0000001c : afd!AfdPoll32+0xfc
    fffff880`098f78a0 fffff800`025ef3a7 : fffffa80`09e4db70 fffff880`098f7b60 fffffa80`0a7c5530 fffffa80`0a7c5340 : afd! ?? ::GFJBLGFE::`string'+0x17b5
    fffff880`098f78d0 fffff800`025efc06 : fffff880`098f7ab8 00000000`0000029c 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x607
    fffff880`098f7a00 fffff800`022d1e53 : fffff880`098f7b60 fffffa80`09a09c70 fffff880`098f7ab8 00000000`00000001 : nt!NtDeviceIoControlFile+0x56
    fffff880`098f7a70 00000000`74f82e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0097eaf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74f82e09
    
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: AuthenticAMD
    IMAGE_NAME:  AuthenticAMD
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    IMAGE_VERSION:  
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:x64_0x124_authenticamd_processor_bus
    FAILURE_ID_HASH:  {44023482-051f-5b9f-29e6-f81bb1d7cfed}
    Followup: MachineOwner
    ---------

    Get more information about the error:

    ===============================================================================
    Common Platform Error Record @ fffffa8008dc5028
    -------------------------------------------------------------------------------
    Record Id     : 01cf0831abe23c85
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 1/3/2014 4:01:40 (UTC)
    Flags         : 0x00000000
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8008dc50a8
    Section       @ fffffa8008dc5180
    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   : 0x0000000000600f20
    Processor ID  : 0x0000000000000005
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8008dc50f0
    Section       @ fffffa8008dc5240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000005
    CPU Id        : 20 0f 60 00 00 08 08 05 - 0b 32 98 3e 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  @ fffffa8008dc5240
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8008dc5138
    Section       @ fffffa8008dc52c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : BUSLG_GENERIC_ERR_*_NOTIMEOUT_ERR (Proc 5 Bank 5)
      Status      : 0xf480000000040e0f
      Address     : 0x000000000000001c
      Misc.       : 0x0000000000000000
    

    Get the binary representation of the error status:

    Evaluate expression:
      Hex:     f4800000`00040e0f
      Decimal: -828662331435905521
      Octal:   1722000000000001007017
      Binary:  11110100 10000000 00000000 00000000 00000000 00000100 00001110 00001111
      Chars:   ........
      Time:    ***** Invalid FILETIME
      Float:   low 3.72385e-040 high -8.11296e+031
      Double:  -1.46631e+253

    Last 16 bits of the error matches the following BUS error patern:

    0000_1PPT_RRRR_IILL
    
    General bus errors including link and DRAM
    PP = Participation Processor
    T = Timeout
    RRRR = Memory Transaction Type
    II = Memory or IO
    LL = Cache Level

    As you can see, it says it's possible the error is link to RAM. Anyhow, analyzing the error code further doesn't provide more information:

    PP = GEN: Generic
    T = 0
    RRRR = GEN: Generic. Includes scrub errors.
    II = GEN: Generic
    LL = LG: Generic (includes L3 cache)

    Next 5 bits (20-16) represents the extended error code, which translates to the following:

    00100 -> 04h
    IDRF array parity
    A parity error occurred in the immediate displacement register file
    So, if replacing the RAM modules really solves the issues, that's OK. Anyhow, this kind of error can be caused by some other things, like motherboard failure, CMOS battery, overclocking, incorrect BIOS settings etc.




    • Marked as answer by 暁北 Tuesday, January 21, 2014 2:50 AM
    Friday, January 3, 2014 7:36 PM

All replies

  • Hello,

    Please download and run Sysnative jcgriff2 BSOD File Collection app. Once done, upload ZIP file the app created to SkyDrive and share the link here.  Additionally, please compress and upload C:\WINDOWS\MEMORY.DMP file as well.

    Friday, January 3, 2014 4:06 PM
  • Mistabla07

    The error code 124 is a hardware issue.

    Stop 0x124 is a hardware error
    If you are overclocking try resetting your processor to standard settings and see if that helps.
    If you continue to get BSODs here are some more things you may want to consider.
    This is usually heat related, defective hardware, memory or even processor though it is"possible" that it is driver related (rare).

    Stop 0x124 - what it means and what to try

    Synopsis:
    A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.
    Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.


     Generic "Stop 0x124" Troubleshooting Strategy:

    1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.
    2) Ensure that the machine is adequately cooled.
     If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.
    3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
    It is good practice to run the latest drivers anyway.
    4) Update the motherboard BIOS according to the manufacturer's instructions and clear the CMOS.
    Their website should provide detailed instructions as to the brand and model-specific procedure.
    5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
    At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.
    6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
    The most obvious examples are the RAM and HDD(s).
    For the RAM, use the 3rd-party memtest86 utility to run many hours worth of testing. (6-8 passes to stress the ram out)
    For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
    Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is free from defects - only that none were encountered during the test passes.
    7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
    Should that fail to mitigate the 0x124 problem, jump to the next steps.
    If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine is still free from 0x124 crashes.
    Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
    If stop 0x124 errors persist despite the steps above, and the hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
    Be aware that attempting the subsequent hardware troubleshooting steps may, in some cases, void your warranty:
    8) Clean and carefully remove any dust from the inside of the machine.
    Reseat all connectors and memory modules.
    Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.
    9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
    Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.

    Should you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.

    More advanced reading can be found here from a MS MVP IT PRO


    Wanikiya and Dyami--Team Zigzag

    Friday, January 3, 2014 4:21 PM
  • The MEMORY.DMP was taking forever to upload, so I got the Minidump file, along with yours, instead. Since I can't post links yet,

    here you go: http://sdrv.ms/1f0EhCu

    Friday, January 3, 2014 4:35 PM
  • The MEMORY.DMP was taking forever to upload, so I got the Minidump file, along with yours, instead. Since I can't post links yet,

    here you go: http://sdrv.ms/1f0EhCu

    Unfortunately, minidumps are not enough for troubleshooting 124 bugchecks (WHEA_UNCORRECTABLE_ERROR), that's why I asked for MEMORY.DMP file.

    In addition, please follow the steps provided in the Team Zigzag post above.

    Friday, January 3, 2014 4:40 PM
  • Sorry about that. The MEMORY.DMP finally uploaded.

    If you would like to look at it,

    here are all 3 files together: http://sdrv.ms/KotCmS

    I will follow the Team Zigzag steps as well. Thank you.

    Friday, January 3, 2014 4:53 PM
  • Starting to think it's the memory. I had tested the memory a few weeks ago, and it all checked out. But, today I have tried to test both of my sticks individually and the computer restarts no matter which stick I use or which port they're in. I used one of my spare sticks and it passed all the way through, first try.
    Friday, January 3, 2014 5:18 PM
  • The possibility of both memory modules failing at the same time is unlikely, so I'm really curious if you made any BIOS changes or overclocking, that could result into RAM issues, recently.

    I did some analysis of the MEMORY.DMP file you provided, but, as usually with WHEA BSODs, it's very difficult to say what exactly cause the issue. Anyways, there are my findings:

    First, let's run initial automated analysis:

    *******************************************************************************
    *                                                                             *
    *                        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: fffffa8008dc5028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000f4800000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000040e0f, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    Page 220f41 not present in the dump file. Type ".hh dbgerr004" for details
    
    BUGCHECK_STR:  0x124_AuthenticAMD
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  XmppAuth.exe
    CURRENT_IRQL:  f
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    STACK_TEXT:  
    fffff880`01f91b88 fffff800`02226a3b : 00000000`00000124 00000000`00000000 fffffa80`08dc5028 00000000`f4800000 : nt!KeBugCheckEx
    fffff880`01f91b90 fffff800`023e9463 : 00000000`00000001 fffffa80`07cc08f0 00000000`00000000 fffffa80`07cc0940 : hal!HalBugCheckSystem+0x1e3
    fffff880`01f91bd0 fffff800`02226700 : 00000000`00000728 fffffa80`07cc08f0 fffff880`01f91f30 fffff880`01f96000 : nt!WheaReportHwError+0x263
    fffff880`01f91c30 fffff800`02226052 : fffffa80`07cc08f0 fffff880`01f91f30 fffffa80`07cc08f0 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`01f91d80 fffff800`02219e8f : fffffa80`09f564f0 00000000`00000001 fffff880`01f91fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`01f91dc0 fffff800`022d14ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
    fffff880`01f91df0 fffff800`022d1313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`01f91f30 fffff800`02406e02 : 00000000`00000099 00000000`0000afd1 fffffa80`09a09980 00000000`00000000 : nt!KiMcheckAbort+0x153
    fffff880`098f7610 fffff800`022e5f56 : fffffa80`000001a4 00000000`00000018 fffffa80`09ef5ab0 00000000`000007ff : nt!ExAllocatePoolWithTag+0x1f2
    fffff880`098f7700 fffff880`02caee91 : fffffa80`0a7c5340 fffffa80`0a7c54e8 fffff880`098f77c0 fffffa80`09ef5ad0 : nt!ExAllocatePoolWithQuotaTag+0x56
    fffff880`098f7750 fffff880`02cc66dc : fffffa80`09ef5ac0 fffff880`098f77c0 fffffa80`0a7c5340 fffff800`022e39cc : afd!AfdPollGetInfo+0x21
    fffff880`098f7790 fffff880`02cb6d3b : fffffa80`08ea9d00 00000000`00000000 00000000`00000001 00000000`0000001c : afd!AfdPoll32+0xfc
    fffff880`098f78a0 fffff800`025ef3a7 : fffffa80`09e4db70 fffff880`098f7b60 fffffa80`0a7c5530 fffffa80`0a7c5340 : afd! ?? ::GFJBLGFE::`string'+0x17b5
    fffff880`098f78d0 fffff800`025efc06 : fffff880`098f7ab8 00000000`0000029c 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x607
    fffff880`098f7a00 fffff800`022d1e53 : fffff880`098f7b60 fffffa80`09a09c70 fffff880`098f7ab8 00000000`00000001 : nt!NtDeviceIoControlFile+0x56
    fffff880`098f7a70 00000000`74f82e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0097eaf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74f82e09
    
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: AuthenticAMD
    IMAGE_NAME:  AuthenticAMD
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    IMAGE_VERSION:  
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:x64_0x124_authenticamd_processor_bus
    FAILURE_ID_HASH:  {44023482-051f-5b9f-29e6-f81bb1d7cfed}
    Followup: MachineOwner
    ---------

    Get more information about the error:

    ===============================================================================
    Common Platform Error Record @ fffffa8008dc5028
    -------------------------------------------------------------------------------
    Record Id     : 01cf0831abe23c85
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 1/3/2014 4:01:40 (UTC)
    Flags         : 0x00000000
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8008dc50a8
    Section       @ fffffa8008dc5180
    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   : 0x0000000000600f20
    Processor ID  : 0x0000000000000005
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8008dc50f0
    Section       @ fffffa8008dc5240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000005
    CPU Id        : 20 0f 60 00 00 08 08 05 - 0b 32 98 3e 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  @ fffffa8008dc5240
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8008dc5138
    Section       @ fffffa8008dc52c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : BUSLG_GENERIC_ERR_*_NOTIMEOUT_ERR (Proc 5 Bank 5)
      Status      : 0xf480000000040e0f
      Address     : 0x000000000000001c
      Misc.       : 0x0000000000000000
    

    Get the binary representation of the error status:

    Evaluate expression:
      Hex:     f4800000`00040e0f
      Decimal: -828662331435905521
      Octal:   1722000000000001007017
      Binary:  11110100 10000000 00000000 00000000 00000000 00000100 00001110 00001111
      Chars:   ........
      Time:    ***** Invalid FILETIME
      Float:   low 3.72385e-040 high -8.11296e+031
      Double:  -1.46631e+253

    Last 16 bits of the error matches the following BUS error patern:

    0000_1PPT_RRRR_IILL
    
    General bus errors including link and DRAM
    PP = Participation Processor
    T = Timeout
    RRRR = Memory Transaction Type
    II = Memory or IO
    LL = Cache Level

    As you can see, it says it's possible the error is link to RAM. Anyhow, analyzing the error code further doesn't provide more information:

    PP = GEN: Generic
    T = 0
    RRRR = GEN: Generic. Includes scrub errors.
    II = GEN: Generic
    LL = LG: Generic (includes L3 cache)

    Next 5 bits (20-16) represents the extended error code, which translates to the following:

    00100 -> 04h
    IDRF array parity
    A parity error occurred in the immediate displacement register file
    So, if replacing the RAM modules really solves the issues, that's OK. Anyhow, this kind of error can be caused by some other things, like motherboard failure, CMOS battery, overclocking, incorrect BIOS settings etc.




    • Marked as answer by 暁北 Tuesday, January 21, 2014 2:50 AM
    Friday, January 3, 2014 7:36 PM