Repeating BSOD x000000124 Hardware

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by jhendricks85, Mar 12, 2013.

  1. jhendricks85

    jhendricks85 New Member

    Joined:
    Mar 12, 2013
    Messages:
    4
    Likes Received:
    0

    Attached Files:

  2. usasma

    usasma Fantastic Member
    Microsoft Community Contributor

    Joined:
    Mar 22, 2010
    Messages:
    3,048
    Likes Received:
    83
    Your BIOS dates from 2009. Please check at the manufacturer's website to see if there are any BIOS updates available for your system. Also check the readme file to see if they apply to the problems that you are having. Please be advised that flashing the BIOS is a very unforgiving process - and one mistake can physically damage your motherboard.

    No Windows Updates installed. Most systems have 140 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

    No entries in the WER section of MSINFO32. Have you tweaked the system settings to stop Error Reporting?

    Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
    If you're overclocking, please stop the overclock while we're troubleshooting. Feel free to resume the overclock once the system has been stabilized.

    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

    lmimirr.sys Tue Apr 10 18:32:45 2007 (461C108D)
    RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver
    http://www.carrona.org/drivers/driver.php?id=lmimirr.sys

    RaInfo.sys Fri Jan 4 13:57:14 2008 (477E818A)
    LogMeIn/RemotelyAnywhere Kernel Information Provider
    http://www.carrona.org/drivers/driver.php?id=RaInfo.sys

    LMIRfsDriver.sys Mon Jul 14 12:26:56 2008 (487B7E50)
    RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver
    http://www.carrona.org/drivers/driver.php?id=LMIRfsDriver.sys

    Rt64win7.sys Thu Feb 26 04:04:13 2009 (49A65B0D)
    Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
    http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys

    If all of this doesn't stop the BSOD's, please run these free hardware diagnostics: Hardware Diagnostics. Let us know the results and we can move on from there.




    Analysis:
    The following is for informational purposes only.
    Code:
    [font=lucida console]**************************Tue Mar 12 02:07:13.917 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031213-24960-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
    System Uptime:[B]0 days 2:17:35.618[/B]
    Probably caused by :[B]AuthenticAMD[/B]
    BugCheck [B]124, {0, fffffa8007b5f028, b666a000, eb000135}[/B]
    BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000124]WHEA_UNCORRECTABLE_ERROR (124)[/url]
    Arguments: 
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa8007b5f028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b666a000, High order 32-bits of the MCi_STATUS value.
    Arg4: 00000000eb000135, Low order 32-bits of the MCi_STATUS value.
    BUGCHECK_STR:  0x124_AuthenticAMD
    PROCESS_NAME:  hl2.exe
    FAILURE_BUCKET_ID: [B]X64_0x124_AuthenticAMD_PROCESSOR_CACHE[/B]
      BIOS Version                  F4
      BIOS Release Date             04/21/2009
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  GA-MA790X-UD4P
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Mon Mar 11 23:48:45.852 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031113-42915-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
    System Uptime:[B]0 days 0:12:08.553[/B]
    Probably caused by :[B]AuthenticAMD[/B]
    BugCheck [B]124, {0, fffffa80082e1028, b6004000, 68000135}[/B]
    BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000124]WHEA_UNCORRECTABLE_ERROR (124)[/url]
    Arguments: 
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa80082e1028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b6004000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000068000135, Low order 32-bits of the MCi_STATUS value.
    BUGCHECK_STR:  0x124_AuthenticAMD
    PROCESS_NAME:  dirt3_game.exe
    FAILURE_BUCKET_ID: [B]X64_0x124_AuthenticAMD_PROCESSOR_CACHE[/B]
      BIOS Version                  F4
      BIOS Release Date             04/21/2009
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  GA-MA790X-UD4P
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    [/font]
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    [font=lucida console]**************************Tue Mar 12 02:07:13.917 2013 (UTC - 4:00)**************************
    [COLOR=RED][B]lmimirr.sys        Tue Apr 10 18:32:45 2007 (461C108D)[/B][/COLOR]
    [COLOR=RED][B]RaInfo.sys         Fri Jan  4 13:57:14 2008 (477E818A)[/B][/COLOR]
    [COLOR=RED][B]LMIRfsDriver.sys   Mon Jul 14 12:26:56 2008 (487B7E50)[/B][/COLOR]
    [COLOR=RED][B]Rt64win7.sys       Thu Feb 26 04:04:13 2009 (49A65B0D)[/B][/COLOR]
    amdxata.sys        Fri Mar 19 12:18:18 2010 (4BA3A3CA)
    pbfilter.sys       Sat Nov  6 22:23:54 2010 (4CD60DBA)
    speedfan.sys       Fri Mar 18 12:08:46 2011 (4D83838E)
    SbieDrv.sys        Wed Oct 12 10:10:34 2011 (4E959FDA)
    [COLOR=RED][B]dtsoftbus01.sys    Fri Jan 13 08:45:46 2012 (4F10358A)[/B][/COLOR]
    MpFilter.sys       Wed Oct 31 18:43:06 2012 (5091A97A)
    AtihdW76.sys       Tue Nov  6 16:41:51 2012 (5099841F)
    HWiNFO64A.SYS      Wed Nov 14 06:15:59 2012 (50A37D6F)
    atikmpag.sys       Sat Feb  2 14:40:11 2013 (510D6B9B)
    atikmdag.sys       Sat Feb  2 15:51:55 2013 (510D7C6B)
    [/font]
    http://www.carrona.org/drivers/driver.php?id=lmimirr.sys
    http://www.carrona.org/drivers/driver.php?id=RaInfo.sys
    http://www.carrona.org/drivers/driver.php?id=LMIRfsDriver.sys
    http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
    http://www.carrona.org/drivers/driver.php?id=amdxata.sys
    http://www.carrona.org/drivers/driver.php?id=pbfilter.sys
    http://www.carrona.org/drivers/driver.php?id=speedfan.sys
    http://www.carrona.org/drivers/driver.php?id=SbieDrv.sys
    http://www.carrona.org/drivers/driver.php?id=dtsoftbus01.sys
    http://www.carrona.org/drivers/driver.php?id=MpFilter.sys
    http://www.carrona.org/drivers/driver.php?id=AtihdW76.sys
    http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
     
  3. Vir Gnarus

    Vir Gnarus Active Member

    Joined:
    Jan 8, 2013
    Messages:
    199
    Likes Received:
    9
    The three WHEA crashes were all identical in that bank 0 of the L1 cache for the CPU has failed during a data read. Commonly this is caused by hardware issues like an internal CPU failure, a bad power supply, or overclocked settings or high temps that are creating instability.

    As John mentioned, make sure to reset motherboard to non-overclocked default settings. You may need to set it to safe defaults, since sometimes normal preset settings on some motherboards are actually overclocked. Also what temps are you getting now at high load for the CPU?

    I've seen these WHEA crashes also be caused by unscrupulous motherboard software. If you have any software that came with your motherboard, uninstall it. You may need to remove it using something like Driver Fusion or CCleaner (both free) as even their uninstallers sometimes can leave trace items behind. Also make sure to update that BIOS as John also spoke of, since that can be related as well.

    I must ask, have you been suffering crashes from temps issues previously before you installed the new cooling? If so, the temps may have caused irreparable damage to the CPU, which might mean you chucking it out and replacing it with a new one.

    I recommend running through some hardware tests, starting with two runs of Prime95 on Torture Test. The first run should be using Blend settings, then the second one - regardless of the results of the first - should run with Large FFTs. Each test should be an overnight run so first test for 30 minutes using HwInfo to gauge temps to make sure things are ok before letting it run unsupervised for several hours. Post any new crashdumps that may occur during either run and mention to us the results of each test. Also, do a several pass Memtest86+ for good measure.

    Analysts:

    All three crashdumps are the same as below, save one which reported it occurred with Proc 2 activity and not Proc 3:

    Code:
    3: kd> !errrec fffffa80082e1028
    ===============================================================================
    Common Platform Error Record @ fffffa80082e1028
    -------------------------------------------------------------------------------
    Record Id     : 01ce1ed2cde40004
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 3/12/2013 3:48:45 (UTC)
    Flags         : 0x00000000
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa80082e10a8
    Section       @ fffffa80082e1180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    [COLOR=#ff0000]Error Type    : Cache error
    Operation     : Data Read[/COLOR]
    Flags         : 0x00
    Level         : 1
    CPU Version   : 0x0000000000100f42
    Processor ID  : 0x0000000000000003
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa80082e10f0
    Section       @ fffffa80082e1240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000003
    CPU Id        : 42 0f 10 00 00 08 04 03 - 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  @ fffffa80082e1240
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa80082e1138
    Section       @ fffffa80082e12c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    [COLOR=#ff0000]Error         : DCACHEL1_DRD_ERR (Proc 3 Bank 0)[/COLOR]
      Status      : 0xb600400068000135
      Address     : 0x00000001144cb580
      Misc.       : 0x0000000000000000
     
  4. jhendricks85

    jhendricks85 New Member

    Joined:
    Mar 12, 2013
    Messages:
    4
    Likes Received:
    0
    View attachment 031213-39109-01.dmp

    I have updated the bios, that has worked well. I have also updated the drivers mentioned, or got rid of them.

    Got another error just now, x0000001E while playing dirt 3. I haven't seen this error before on this system.
     

Share This Page

Loading...