locked
Win 7 64-bit bluescreen (bccode "1a") & RAM R/W memory test failed? RRS feed

  • Question

  • I don't really understand what's wrong.. I know it has to do something with RAM because recently my computer has started to  say "RAM R/W memory test failed" on startup and the bluescreen says something about RAM too... I'm clueless.. Thanks for anyone who even reads my problem!

     


    information from Speccy:

    MS Windows 7 Home Premium 64-bit

    MSI MS-7369 (CPU 1)

    AMD Athlon 64 X2 5000+

    512MB GeForce 8600 GT

    997GB Seagate ST31000528AS ATA Device (IDE)

     

    I read from another thread that I should maybe upload my minidump files, so I did.

    (not sure if I used Skydrive right, never used it before..)

     

    https://cid-05bcdaf60496b008.skydrive.live.com/redir.aspx?resid=5BCDAF60496B008!285

    Friday, April 22, 2011 11:13 AM

Answers

  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    CRITICAL_STRUCTURE_CORRUPTION (109)
    This bugcheck is generated when the kernel detects that critical kernel code or
    data have been corrupted. There are generally three causes for a corruption:
    1) A driver has inadvertently or deliberately modified critical kernel code
     or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
    2) A developer attempted to set a normal kernel breakpoint using a kernel
     debugger that was not attached when the system was booted. Normal breakpoints,
     "bp", can only be set if the debugger is attached at boot time. Hardware
     breakpoints, "ba", can be set at any time.
    3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
    Arguments:
    Arg1: a3a039d8976c34f2, Reserved
    Arg2: 0000000000000000, Reserved
    Arg3: 99341a8b184c2a3c, Failure type dependent information
    Arg4: 0000000000000101, Type of corrupted region, can be
     0 : A generic data region
     1 : Modification of a function or .pdata
     2 : A processor IDT
     3 : A processor GDT
     4 : Type 1 process list corruption
     5 : Type 2 process list corruption
     6 : Debug routine modification
     7 : Critical MSR modification

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


    BUGCHECK_STR:  0x109

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80003483740

    STACK_TEXT: 
    fffff880`02fd95d8 00000000`00000000 : 00000000`00000109 a3a039d8`976c34f2 00000000`00000000 99341a8b`184c2a3c : nt!KeBugCheckEx


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt+70740
    fffff800`03483740 48894c2408      mov     qword ptr [rsp+8],rcx

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt+70740

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  4cc791bd

    FAILURE_BUCKET_ID:  X64_0x109_nt+70740

    BUCKET_ID:  X64_0x109_nt+70740

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

    ________________________________________________________________________

    Bug Check Code 0x109: http://msdn.microsoft.com/en-us/library/ff557228(VS.85).aspx

    I am unable to get much informatiom from the dump you uploaded.

    Please configure your Windows to generate a full dump and use Microsoft Skydrive to upload it (Use 7Zip to divide it).

    You can try the following:

    • Update all possible drivers
    • Install latest Windows Update
    • Run memtest86+ to check that there is no problem with your RAM. If a problem was detected, replace the faulty RAM

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    • Marked as answer by Juke Chou Wednesday, April 27, 2011 9:18 AM
    Friday, April 22, 2011 6:55 PM

All replies

  • The share folder is not set for public access. Please change settings.

    If you want to read dump files without my help, use Windbg and refer to this Microsoft article:

    http://support.microsoft.com/kb/315263

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    Friday, April 22, 2011 12:54 PM
  • I think it should now be public... I changed the sharing options from "only me" to "public..

    I'll also try to see the dump files myself when I have time.

    Friday, April 22, 2011 6:40 PM
  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    CRITICAL_STRUCTURE_CORRUPTION (109)
    This bugcheck is generated when the kernel detects that critical kernel code or
    data have been corrupted. There are generally three causes for a corruption:
    1) A driver has inadvertently or deliberately modified critical kernel code
     or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
    2) A developer attempted to set a normal kernel breakpoint using a kernel
     debugger that was not attached when the system was booted. Normal breakpoints,
     "bp", can only be set if the debugger is attached at boot time. Hardware
     breakpoints, "ba", can be set at any time.
    3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
    Arguments:
    Arg1: a3a039d8976c34f2, Reserved
    Arg2: 0000000000000000, Reserved
    Arg3: 99341a8b184c2a3c, Failure type dependent information
    Arg4: 0000000000000101, Type of corrupted region, can be
     0 : A generic data region
     1 : Modification of a function or .pdata
     2 : A processor IDT
     3 : A processor GDT
     4 : Type 1 process list corruption
     5 : Type 2 process list corruption
     6 : Debug routine modification
     7 : Critical MSR modification

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


    BUGCHECK_STR:  0x109

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80003483740

    STACK_TEXT: 
    fffff880`02fd95d8 00000000`00000000 : 00000000`00000109 a3a039d8`976c34f2 00000000`00000000 99341a8b`184c2a3c : nt!KeBugCheckEx


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt+70740
    fffff800`03483740 48894c2408      mov     qword ptr [rsp+8],rcx

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt+70740

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  4cc791bd

    FAILURE_BUCKET_ID:  X64_0x109_nt+70740

    BUCKET_ID:  X64_0x109_nt+70740

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

    ________________________________________________________________________

    Bug Check Code 0x109: http://msdn.microsoft.com/en-us/library/ff557228(VS.85).aspx

    I am unable to get much informatiom from the dump you uploaded.

    Please configure your Windows to generate a full dump and use Microsoft Skydrive to upload it (Use 7Zip to divide it).

    You can try the following:

    • Update all possible drivers
    • Install latest Windows Update
    • Run memtest86+ to check that there is no problem with your RAM. If a problem was detected, replace the faulty RAM

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    • Marked as answer by Juke Chou Wednesday, April 27, 2011 9:18 AM
    Friday, April 22, 2011 6:55 PM