locked
BSOD constantly now after win7 upgrade and Ram upgrade RRS feed

  • Question

  • Upgraded from vista 32 to Win7 64 last week and also went from 3 GB to 8 GB in Ram and been getting a lot of BSODs lately.  Done a lot of tests on the RAM and my actual hard drive and found no problems yet.  It's a Gateway Intel q6600 2.4 ghz almost 4 years old.  I will copy and paste a link to a skydrive folder where i put a winrar zip of the dump files there.  I'm not sure if that is what is needed to check this.  If it does not work please let me know here.  Thank you.

     

    https://skydrive.live.com/redir.aspx?cid=b66a16f6bd48774b&resid=B66A16F6BD48774B!102


    Saturday, October 1, 2011 1:20 AM

Answers

  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80002ef4f00, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception
    Debugging Details:
    ------------------
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    FAULTING_IP: 
    nt!MiReplenishPageSlist+c0
    fffff800`02ef4f00 f00fba6b1000    lock bts dword ptr [rbx+10h],0
    EXCEPTION_PARAMETER1:  0000000000000000
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003101100
     ffffffffffffffff 
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    BUGCHECK_STR:  0x1E_c0000005
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  chrome.exe
    CURRENT_IRQL:  2
    LAST_CONTROL_TRANSFER:  from fffff80002f1a588 to fffff80002ecec40
    STACK_TEXT:  
    fffff880`08740e28 fffff800`02f1a588 : 00000000`0000001e ffffffff`c0000005 fffff800`02ef4f00 00000000`00000000 : nt!KeBugCheckEx
    fffff880`08740e30 fffff800`02ece2c2 : fffff880`08741608 17fffa80`005463c0 fffff880`087416b0 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x4977d
    fffff880`087414d0 fffff800`02eccbca : fffff880`08741708 00000000`00000000 fffffa80`00553da0 fffff800`02ed18a4 : nt!KiExceptionDispatch+0xc2
    fffff880`087416b0 fffff800`02ef4f00 : 00000000`00007000 fffff800`02f1a85c fffffa80`0b67a920 fffff800`02f38c45 : nt!KiGeneralProtectionFault+0x10a
    fffff880`08741840 fffff800`02ef36bf : fffffa80`06540320 00000000`00000014 fffffa80`04f9fbc0 00000000`00000014 : nt!MiReplenishPageSlist+0xc0
    fffff880`087418b0 fffff800`02edf84f : 00000000`00000002 fffff880`00000002 fffffa80`0b669ec8 00000000`00000002 : nt!MiRemoveAnyPage+0x24f
    fffff880`087419d0 fffff800`02edc19e : 00000000`00000001 00000000`0088e000 fffff880`08741c20 fffff680`00004470 : nt!MiResolveDemandZeroFault+0x54f
    fffff880`08741ac0 fffff800`02eccd6e : 00000000`00000001 00000000`0088e000 00000000`0018df01 00000000`00000226 : nt!MmAccessFault+0x5de
    fffff880`08741c20 00000000`6ff5dd2a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    00000000`0035f118 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6ff5dd2a
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt!MiReplenishPageSlist+c0
    fffff800`02ef4f00 f00fba6b1000    lock bts dword ptr [rbx+10h],0
    SYMBOL_STACK_INDEX:  4
    SYMBOL_NAME:  nt!MiReplenishPageSlist+c0
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
    IMAGE_NAME:  memory_corruption
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!MiReplenishPageSlist+c0
    BUCKET_ID:  X64_0x1E_c0000005_nt!MiReplenishPageSlist+c0
    Followup: MachineOwner
    ---------
    -----------------------------------------------------
    Please use Microsoft Skydrive to upload MEMORY.DMP file after zipping it.
    Please also run memtest86+ to check that all is okay with your RAM. If an error was detected then replace the faulty RAM or contact your manufacturer Technical Support.

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

    Microsoft Student Partner 2010 / 2011
    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
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer 

    • Marked as answer by Cloud_TS Wednesday, October 19, 2011 3:54 AM
    Monday, October 3, 2011 9:46 PM

All replies

  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80002ef4f00, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception
    Debugging Details:
    ------------------
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    FAULTING_IP: 
    nt!MiReplenishPageSlist+c0
    fffff800`02ef4f00 f00fba6b1000    lock bts dword ptr [rbx+10h],0
    EXCEPTION_PARAMETER1:  0000000000000000
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003101100
     ffffffffffffffff 
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    BUGCHECK_STR:  0x1E_c0000005
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  chrome.exe
    CURRENT_IRQL:  2
    LAST_CONTROL_TRANSFER:  from fffff80002f1a588 to fffff80002ecec40
    STACK_TEXT:  
    fffff880`08740e28 fffff800`02f1a588 : 00000000`0000001e ffffffff`c0000005 fffff800`02ef4f00 00000000`00000000 : nt!KeBugCheckEx
    fffff880`08740e30 fffff800`02ece2c2 : fffff880`08741608 17fffa80`005463c0 fffff880`087416b0 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x4977d
    fffff880`087414d0 fffff800`02eccbca : fffff880`08741708 00000000`00000000 fffffa80`00553da0 fffff800`02ed18a4 : nt!KiExceptionDispatch+0xc2
    fffff880`087416b0 fffff800`02ef4f00 : 00000000`00007000 fffff800`02f1a85c fffffa80`0b67a920 fffff800`02f38c45 : nt!KiGeneralProtectionFault+0x10a
    fffff880`08741840 fffff800`02ef36bf : fffffa80`06540320 00000000`00000014 fffffa80`04f9fbc0 00000000`00000014 : nt!MiReplenishPageSlist+0xc0
    fffff880`087418b0 fffff800`02edf84f : 00000000`00000002 fffff880`00000002 fffffa80`0b669ec8 00000000`00000002 : nt!MiRemoveAnyPage+0x24f
    fffff880`087419d0 fffff800`02edc19e : 00000000`00000001 00000000`0088e000 fffff880`08741c20 fffff680`00004470 : nt!MiResolveDemandZeroFault+0x54f
    fffff880`08741ac0 fffff800`02eccd6e : 00000000`00000001 00000000`0088e000 00000000`0018df01 00000000`00000226 : nt!MmAccessFault+0x5de
    fffff880`08741c20 00000000`6ff5dd2a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    00000000`0035f118 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6ff5dd2a
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt!MiReplenishPageSlist+c0
    fffff800`02ef4f00 f00fba6b1000    lock bts dword ptr [rbx+10h],0
    SYMBOL_STACK_INDEX:  4
    SYMBOL_NAME:  nt!MiReplenishPageSlist+c0
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
    IMAGE_NAME:  memory_corruption
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!MiReplenishPageSlist+c0
    BUCKET_ID:  X64_0x1E_c0000005_nt!MiReplenishPageSlist+c0
    Followup: MachineOwner
    ---------
    -----------------------------------------------------
    Please use Microsoft Skydrive to upload MEMORY.DMP file after zipping it.
    Please also run memtest86+ to check that all is okay with your RAM. If an error was detected then replace the faulty RAM or contact your manufacturer Technical Support.

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

    Microsoft Student Partner 2010 / 2011
    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
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer 

    • Marked as answer by Cloud_TS Wednesday, October 19, 2011 3:54 AM
    Monday, October 3, 2011 9:46 PM
  • Yup, like Vegan mention, are the new & old ram sticks of the same brand & capacity and did you ensure the ram timing is either set to auto or the specific timing as what the ram manufacturer site states?
    Tuesday, October 4, 2011 4:19 AM
    Answerer