locked
Windows 7 64bit Blue Screen of Death RRS feed

  • Question

  • I just installed a new window 7 on my new pc.I get blue screen of death randomly.I think when I am multitasking but not sure.I dont think its ram because i switch my ram with another ram from my other pc which runs fine and once i put it in my pc,the same issue occured.After restartig from error my pc says this about the error.

     

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.1
    Locale ID: 4105

    Additional information about the problem:
    BCCode: 124
    BCP1: 0000000000000000
    BCP2: FFFFFA8002B5B028
    BCP3: 00000000F6000000
    BCP4: 0000000000010015
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\072610-19546-01.dmp
    C:\Users\CTE\AppData\Local\Temp\WER-37019-0.sysdata.xml

    Read our privacy statement online:
    http://go.microsoft.com/fwlink/?link...8&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt

     

    Please help,and thanks

    Monday, July 26, 2010 3:54 PM

Answers

  • Hi Andrew,

    you have a TLB [1] issue with the L1 Cache of your CPU:

    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 7/28/2010 0:01:42
    Flags         : 0x00000000

    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8002c6c0a8
    Section       @ fffffa8002c6c180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal

    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : TLB error
    Flags         : 0x00
    Level         : 1
    CPU Version   : 0x0000000000100f22
    Processor ID  : 0x0000000000000002

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

    Local APIC Id : 0x0000000000000002
    CPU Id        : 22 0f 10 00 00 08 04 02 - 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  @ fffffa8002c6c240

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

    Error         : DTLBL1_ERR (Proc 2 Bank 0)
      Status      : 0xb600000000010015
      Address     : 0x0000000018be0000
      Misc.       : 0x0000000000000000

    Replace the CPU, because it's damaged. Check if you bought a Boxed CPU, in this case you mostly got 3 years warranty.

    best regards
    André

    [1] http://en.wikipedia.org/wiki/Translation_lookaside_buffer


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Proposed as answer by Andre.Ziegler Tuesday, July 27, 2010 10:55 PM
    • Marked as answer by Dale Qiao Monday, August 2, 2010 1:04 AM
    Tuesday, July 27, 2010 10:55 PM

All replies

  • Hi,
     
    Based on what is in the error,
     
    # for decimal 124 / hex 0x7c :
      BUGCODE_NDIS_DRIVER                                       bugcodes.h
     
    This appears that it may be due to a network driver or hardware, but
    since device drivers have access to the entire OS and protected memory,
    this may not be the exact cause.
     
     
    Can you post the .dmp file to skydrive,
    http://windowslive.com/online/skydrive and then post a link to the file
    back to the thread? Someone with the debugging tools for Windows can
    probably shed more light on the exact cause of the error.
     
     

    -- Mike Burr
    Monday, July 26, 2010 8:35 PM
  • Ok I believe I did it correct, here is the link: https://cid-920683c379124e27.office.live.com/self.aspx/.Documents/072710-52119-01.dmp

     

    and Thanks for replying Mike :)

    Tuesday, July 27, 2010 2:40 PM
  • I was unable to get to it, I just created a file with directions to
    upload to the Public folder here,
     
     Upload a file with SkyDrive
     
    Log in to skydrive.live.com
     
    Click the "Public" folder under documents
     
    Click "Add files"
     
    Click "select documents from your computer"
     
    click the "Continue" button
     
    Click "Share" Menu -> Embed,
     
    Copy link
     <iframe title ="Preview" scrolling="no" marginheight="0" marginwidth="0"
    frameborder="0"
    style="width:98px;height:115px;padding:0;background-color:#fcfcfc;"
     
    get the inside of the .src attribute,
     
     

    -- Mike Burr
    Tuesday, July 27, 2010 10:08 PM
  • Got it,
     From the first look, it appears to be a problem in the TLB cache for
    the processor. Does this error only occur when you are running the
    Fallout process? Are you using a multi-cpu or multicore system? the only
    processor I could find after a quick search that matches is the
     
    AMD Phenom 9100e Quad-Core Processor
     
    I'd recommend ensuring that all of the drivers, BIOS and any firmware
    are up to date. If the error persists, then you might want to try
    replacing the CPU. This is the CPU that caused the issue,
     
    2: kd> !cpuinfo
    CP  F/M/S Manufacturer  MHz PRCB Signature    MSR 8B Signature Features
     2 16,2,2 AuthenticAMD 1807 0000000000000000                   203b7dfe
     
    but without more detailed info on the hardware, it is hard to know
    whether which processor the CP value above refers to.
     *******************************************************************************
    *
          *
    *                        Bugcheck Analysis
          *
    *
          *
    *******************************************************************************
     
    Use !analyze -v to get detailed debugging information.
     
    BugCheck 124, {0, fffffa8002c6c028, b6000000, 10015}
     
    Probably caused by : hardware
     
    Followup: MachineOwner
    ---------
     
    2: kd> !analyze -v
    ERROR: FindPlugIns 80070005
    *******************************************************************************
    *
          *
    *                        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: fffffa8002c6c028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b6000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000010015, Low order 32-bits of the MCi_STATUS value.
     
    Debugging Details:
    ------------------
     BUGCHECK_STR:  0x124_AuthenticAMD
     
    CUSTOMER_CRASH_COUNT:  1
     
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
     
    PROCESS_NAME:  Fallout3.exe
     
    CURRENT_IRQL:  f
     
    STACK_TEXT:
    fffff880`02f6ba88 fffff800`02829903 : 00000000`00000124
    00000000`00000000 fffffa80`02c6c028 00000000`b6000000 : nt!KeBugCheckEx
    fffff880`02f6ba90 fffff800`029e64d3 : 00000000`00000001
    fffffa80`02cafea0 00000000`00000000 fffffa80`02cafef0 :
    hal!HalBugCheckSystem+0x1e3
    fffff880`02f6bad0 fffff800`028295c8 : 00000000`00000728
    fffffa80`02cafea0 fffff880`02f6be30 00000000`18be0000 :
    nt!WheaReportHwError+0x263
    fffff880`02f6bb30 fffff800`02828f1a : fffffa80`02cafea0
    fffff880`02f6be30 fffffa80`02cafea0 00000000`00000000 :
    hal!HalpMcaReportError+0x4c
    fffff880`02f6bc80 fffff800`0281ce8f : 00000000`20a4c458
    00000000`00000001 fffff880`02f6beb0 00000000`00000000 :
    hal!HalpMceHandler+0x9e
    fffff880`02f6bcc0 fffff800`028ceeac : 00000000`00000000
    00000000`00000000 00000000`00000000 00000000`00000000 :
    hal!HalHandleMcheck+0x47
    fffff880`02f6bcf0 fffff800`028ced13 : 00000000`00000000
    00000000`00000000 00000000`00000000 00000000`00000000 :
    nt!KxMcheckAbort+0x6c
    fffff880`02f6be30 00000000`703ea2a2 : 00000000`00000000
    00000000`00000000 00000000`00000000 00000000`00000000 :
    nt!KiMcheckAbort+0x153
    00000000`248ffa18 00000000`00000000 : 00000000`00000000
    00000000`00000000 00000000`00000000 00000000`00000000 : 0x703ea2a2
     STACK_COMMAND:  kb
     
    FOLLOWUP_NAME:  MachineOwner
     
    MODULE_NAME: hardware
     
    IMAGE_NAME:  hardware
     
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
     
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB
     
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB
     
    Followup: MachineOwner
    ---------
     

    -- Mike Burr
    • Proposed as answer by Mike Burr Wednesday, July 28, 2010 1:54 AM
    Tuesday, July 27, 2010 10:36 PM
  • The fallout process if fallout 3 the game,and it doesnt only happen on the fallout process.I do have a multi processor,it is as you said,Amd Phenom 9100e

    I updated all my drivers and stuff except I dont know how to update my BIOS.

     

     

    Tuesday, July 27, 2010 10:55 PM
  • Hi Andrew,

    you have a TLB [1] issue with the L1 Cache of your CPU:

    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 7/28/2010 0:01:42
    Flags         : 0x00000000

    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8002c6c0a8
    Section       @ fffffa8002c6c180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal

    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : TLB error
    Flags         : 0x00
    Level         : 1
    CPU Version   : 0x0000000000100f22
    Processor ID  : 0x0000000000000002

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

    Local APIC Id : 0x0000000000000002
    CPU Id        : 22 0f 10 00 00 08 04 02 - 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  @ fffffa8002c6c240

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

    Error         : DTLBL1_ERR (Proc 2 Bank 0)
      Status      : 0xb600000000010015
      Address     : 0x0000000018be0000
      Misc.       : 0x0000000000000000

    Replace the CPU, because it's damaged. Check if you bought a Boxed CPU, in this case you mostly got 3 years warranty.

    best regards
    André

    [1] http://en.wikipedia.org/wiki/Translation_lookaside_buffer


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Proposed as answer by Andre.Ziegler Tuesday, July 27, 2010 10:55 PM
    • Marked as answer by Dale Qiao Monday, August 2, 2010 1:04 AM
    Tuesday, July 27, 2010 10:55 PM
  • is there anyway to fix it Andre?
    Tuesday, July 27, 2010 10:56 PM
  • No, TLB is a hardware component inside the CPU. Some AMD CPU had TLB bugs which can be solved by updating the BIOS.

    Try to update the BIOS. If this doesn't solve, get a new CPU.


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Tuesday, July 27, 2010 11:04 PM
  • Do you know what motherboard you have installed or the make/model of your system (if a Vendor built it)? I might be able to help you locate an updated BIOS.
    -- Mike Burr
    Wednesday, July 28, 2010 1:57 AM
  • I have the Asus M4A785-M motherboard.
    Wednesday, July 28, 2010 2:53 AM
  • The Download tab of this page,
     
     
    The most recent version of the BIOS appears to be from 4/22/2010
     

    -- Mike Burr
    Wednesday, July 28, 2010 3:51 PM
  • It didnt work,but its alright.Ill just return it.Thanks everyone for help.

    This forum is great because of you guys.

    Wednesday, July 28, 2010 6:21 PM
  • the only chance is to update to BIOS Version 0906. 

    http://support.asus.com.tw/download/download.aspx?model=M4A785-M&SLanguage=en-us

    Those are the data from the dump:

      BIOS Version                  0506   

      BIOS Release Date             11/24/2009

      Manufacturer                  ASUSTeK Computer INC.
      Product                       M4A785-M
      Version                       Rev X.0x

      Processor Version             AMD Phenom(tm) 9100e Quad-Core Processor            
      Processor Voltage             8fh - 1.5V
      External Clock                200MHz
      Max Speed                     1800MHz
      Current Speed                 1800MHz

     

    So ,the CPU is not overclocked.

     


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Tuesday, August 3, 2010 12:54 PM
  • I read this too. But I never seen that a driver could cause this. I had a 0x124 crash on my older AMD and the L2 was damaged. running a stress test crashed it everytime and reading the data was a L2 cache issue.
    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Tuesday, August 3, 2010 12:56 PM
  • oh.  i had regular persistent WHEA fatal machine checks with my AMD cpu on Vista RTM.  reduced to Event Viewer warnings with SP1.  went away completely with SP2.  not a peep ever since.  see how different life experiences are?

     

    so anyway, are you going to share your secret of how to get WinDbg to generate that printout?

     

    type !errrec <address of the Error> in WinDbg

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Tuesday, August 3, 2010 10:03 PM