BSOD'S after installing RAM


  1. Posts : 10
    Windows 7
       #1

    BSOD'S after installing RAM


    Hi,
    Today i have installed 4 gb more ram on my machine. Difference is just the speed, rest is the same, so i doubt it can cause the problem. After couple hours I've got first bsod, after relaunching windows there was an error "The ofcommon.dll is missing" and after couple more minutes it crashed again. Now running for 30 minutes, no problems so far.
    Any help will be appriciated.


    30min after, crashed again.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Today i have installed 4 gb more ram on my machine. Difference is just the speed, rest is the same
    That should be enough difference.

    If you want to enhance memory, get one that is essentially identical with the existing one.
      My Computer


  3. Posts : 10
    Windows 7
    Thread Starter
       #3

    Arc said:
    Today i have installed 4 gb more ram on my machine. Difference is just the speed, rest is the same
    That should be enough difference.

    If you want to enhance memory, get one that is essentially identical with the existing one.

    Hi, thank you for your answer.
    As far as i know my motherboard Asus p5q se runs at maximum 800hz. My old Corsair 2x2gb ram was 1033 CL7 if im right, that never made any problems. What i bought is the same corsair 2x2gb just 800hz CL5. Seller said it will make no difference and everything should work perfectly. Would be amazing to get some info what dmp file says.

    Will try that software from a tip when come back home.
      My Computer


  4. Posts : 25,847
    Windows 10 Pro. 64/ version 1709 Windows 7 Pro/64
       #4

    Your system specs will help us help you.
    Two tutorials that will help you show your specs.

    By Brink:
    System Info - See Your System Specs

    By Kari:
    Speccy - Publish Snapshot of your System Specs
      My Computer


  5. Posts : 4,161
    Windows 7 Pro-x64
       #5

    The different memory modules probably will "work" but all installed memory will run at the lowest compatible speed of the slowest module. The key word here is compatible speed. If the BIOS can't negotiate a compatible speed, you'll get errors. The dump says you're getting Memory Management Errors or more specifically, memory corruption. Hmmmmmm Wonder why.

    You could try running Memtest86.

    Code:
     
    BugCheck 1A, {8886, fffffa80006ade20, fffffa80006b4a50, 205}
    Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+19c )
    Followup: MachineOwner
    ---------
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000008886, The subtype of the bugcheck.
    Arg2: fffffa80006ade20
    Arg3: fffffa80006b4a50
    Arg4: 0000000000000205
    Debugging Details:
    ------------------
    
    BUGCHECK_STR:  0x1a_8886
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  svchost.exe
    CURRENT_IRQL:  2
    LAST_CONTROL_TRANSFER:  from fffff80002ed53fc to fffff80002ec4bc0
    STACK_TEXT:  
    fffff880`06ed21a8 fffff800`02ed53fc : 00000000`0000001a 00000000`00008886 fffffa80`006ade20 fffffa80`006b4a50 : nt!KeBugCheckEx
    fffff880`06ed21b0 fffff800`02ea5974 : fffff8a0`0bb72988 fffffa80`006ade20 00000000`00000000 fffff8a0`0bb72988 : nt!MiUnlinkPageFromLockedList+0x19c
    fffff880`06ed2230 fffff800`0319f3b1 : fffffa80`08eb67a0 fffff6fc`40069ca8 fffff8a0`00000002 00000000`00000000 : nt!MiValidateImagePages+0x244
    fffff880`06ed22e0 fffff800`0319f4f0 : ffffffff`ffffffff 00000000`00000001 fffff8a0`0bbc3000 00000000`0000fe00 : nt!MiSwitchBaseAddress+0x61
    fffff880`06ed2310 fffff800`031c1f7f : 00000000`00000004 00000000`00000080 00000000`01000000 00000000`01000000 : nt!MiRelocateImageAgain+0x100
    fffff880`06ed2360 fffff800`0319ec2e : fffff880`06ed25b0 fffff880`06ed2800 fffff880`06ed2658 fffff880`06ed25a8 : nt!MmCreateSection+0x2df
    fffff880`06ed2560 fffff800`03324e53 : 00000000`00000000 fffff8a0`07daa188 00000000`00000000 00000000`00000001 : nt!NtCreateSection+0x171
    fffff880`06ed25e0 fffff800`033253e1 : 00000000`00000000 fffff8a0`07daa188 fffffa80`06f0eab0 fffff880`00000060 : nt!PfpFileBuildReadSupport+0x163
    fffff880`06ed26d0 fffff800`0332d4fe : fffff8a0`00000000 fffff8a0`00000001 fffff8a0`00000059 00000000`00000000 : nt!PfpPrefetchFilesTrickle+0x121
    fffff880`06ed27d0 fffff800`0332ddd7 : 00000000`00000000 fffff880`06ed2c60 fffff880`06ed29c8 fffff8a0`00d82060 : nt!PfpPrefetchRequestPerform+0x30e
    fffff880`06ed2920 fffff800`0333a68e : fffff880`06ed29c8 fffff880`06ed2a01 fffffa80`09c7dd60 00000000`00000000 : nt!PfpPrefetchRequest+0x176
    fffff880`06ed2990 fffff800`0333eeba : 00000000`00000000 00000000`0000004f 00000000`00000000 00000000`0c052001 : nt!PfSetSuperfetchInformation+0x1ad
    fffff880`06ed2a70 fffff800`02ec3e53 : fffffa80`09364b50 00000000`00000000 00000000`00000001 00000000`00007d64 : nt!NtSetSystemInformation+0xc8d
    fffff880`06ed2be0 00000000`77c729aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`01ccf968 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c729aa
    
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt!MiUnlinkPageFromLockedList+19c
    fffff800`02ed53fc cc              int     3
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt!MiUnlinkPageFromLockedList+19c
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035
    IMAGE_NAME:  memory_corruption
    FAILURE_BUCKET_ID:  X64_0x1a_8886_nt!MiUnlinkPageFromLockedList+19c
    BUCKET_ID:  X64_0x1a_8886_nt!MiUnlinkPageFromLockedList+19c
    Followup: MachineOwner
      My Computer


  6. Posts : 10
    Windows 7
    Thread Starter
       #6

    Thank you for the help. Problem was caused by bad RAM's
      My Computer


  7. Posts : 4,161
    Windows 7 Pro-x64
       #7

    I'm glad you found the problem. Was it the new module or the old one?
      My Computer


  8. Posts : 10
    Windows 7
    Thread Starter
       #8

    The new one.
      My Computer


  9. Posts : 4,161
    Windows 7 Pro-x64
       #9

    Dang, that's a bummer. Sorry.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 07:36.
Find Us