Memory Issues

Page 2 of 4 FirstFirst 1234 LastLast

  1. Posts : 9,582
    Windows 8.1 Pro RTM x64
       #11

    Have a look at this from Intel.
    Intel said:
    If you are using DDR3 1600 MHz DIMMs, it is recommended that you only populate two of the four DIMM slots, specifically one slot in each channel. It is recommended that you populate slot 1 of each channel (black connectors).
    More... Intel® Desktop Board DX48BT2 - System memory
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #12

    I do think both Brink and Dwarf are correct it seems most likely that it is the added (new ) memory but it can hurt to verify it.
      My Computer


  3. Posts : 1,161
    Windows 8.1 PRO
       #13

    Did you ever experience any blue screens with the "old memory" alone?

    Did you run Memtest on the new memory ?
      My Computer


  4. Posts : 32
    Windows 7 Ultimate x64 Retail
    Thread Starter
       #14

    Brink said:
    Are you sure that the new RAM sticks have the exact same voltage and timing settings as the older sticks?

    Do these voltage and timing settings above match what is set in the BIOS for the memory?
    i actually copy and pasted the previous memory order and yes i checked everything. oddly enough the chips in the dimm 1 slots are running differently. dimm 0 channel a & b are running 7-7-7-16 and dimm 1 a & b 7-7-7-20 and this is the case with all the chips. here is the dmp link MEGAUPLOAD - The leading online storage and file delivery service
      My Computer


  5. Posts : 32
    Windows 7 Ultimate x64 Retail
    Thread Starter
       #15

    i actually tested both sets seperately and they are good. as we speak i am using the newer ram and i removed the older ram to see if anything would happen. so far everything seems to be fine
      My Computer


  6. Posts : 9,582
    Windows 8.1 Pro RTM x64
       #16

    If you swap the RAM chips over, i.e. place the RAM from dimm 0 channels a & b into dimm 1 channels a & b and vice-versa, do you get the same timing as above?
      My Computer


  7. Posts : 32
    Windows 7 Ultimate x64 Retail
    Thread Starter
       #17

    Dwarf said:
    If you swap the RAM chips over, i.e. place the RAM from dimm 0 channels a & b into dimm 1 channels a & b and vice-versa, do you get the same timing as above?
    yes. both chips have the same sticker on them. they say 7-7-7 @ 1.9v
      My Computer


  8. Posts : 28,845
    Win 8 Release candidate 8400
       #18

    Well You weren't kidding 99Meg dmp file. It took me 3 minuutes to open it. I dont have a true debugger to analyse this but Im posting the info for someone who does. It appears that ntkrnlmp.exe caused this and only part of it was trapped. that leads me back to the memory. the dump paged out of memory. While waiting for a guru debugger, I would see if I could sync the settings for the old memory and the new mem. Failing that try pulling the new set to see if you get bsod's, then pull the oldd just to narrow it down.

    ken
    Code:
     
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
     
     
    Loading Dump File [C:\Users\K\Desktop\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available
     
    Symbol search path is: SRV*d:\symbols*Symbol information
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02a4a000 PsLoadedModuleList = 0xfffff800`02c87e50
    Debug session time: Wed Sep 9 16:12:45.968 2009 (GMT-4)
    System Uptime: 0 days 1:35:49.578
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 000007ff`fffd8018). Type ".hh dbgerr001" for details
    Loading unloaded module list
    ..........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
     
    Use !analyze -v to get detailed debugging information.
     
    BugCheck 1E, {ffffffffc0000005, 0, 8, 0}
     
    PEB is paged out (Peb.Ldr = 000007ff`fffd8018). Type ".hh dbgerr001" for details
    PEB is paged out (Peb.Ldr = 000007ff`fffd8018). Type ".hh dbgerr001" for details
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+460da )
     
    Followup: MachineOwner
    ---------
     
    3: kd> !analyze -v
    *******************************************************************************
    * *
    * 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: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000008, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
     
    Debugging Details:
    ------------------
     
    PEB is paged out (Peb.Ldr = 000007ff`fffd8018). Type ".hh dbgerr001" for details
    PEB is paged out (Peb.Ldr = 000007ff`fffd8018). Type ".hh dbgerr001" for details
     
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
     
    FAULTING_IP: 
    +5a99952f03b0d804
    00000000`00000000 ?? ???
     
    EXCEPTION_PARAMETER1: 0000000000000008
     
    EXCEPTION_PARAMETER2: 0000000000000000
     
    WRITE_ADDRESS: 0000000000000000 
     
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
     
    BUGCHECK_STR: 0x1E
     
    PROCESS_NAME: csrss.exe
     
    CURRENT_IRQL: 0
     
    TRAP_FRAME: fffff8800822e7f0 -- (.trap 0xfffff8800822e7f0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000000c000000d rbx=0000000000000000 rcx=fffff900c01154e8
    rdx=fffffa8006314da0 rsi=0000000000000000 rdi=0000000000000000
    rip=0000000000000000 rsp=fffff8800822e980 rbp=0000000000000000
    r8=0000000000369ea1 r9=000000000000000c r10=0000000000000000
    r11=fffff8800822e960 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na pe nc
    00000000`00000000 ?? ???
    Resetting default scope
     
    LAST_CONTROL_TRANSFER: from fffff80002afba17 to fffff80002abbf00
     
    STACK_TEXT: 
    fffff880`0822df68 fffff800`02afba17 : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx
    fffff880`0822df70 fffff800`02abb542 : fffff880`0822e748 00000000`00000000 fffff880`0822e7f0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x460da
    fffff880`0822e610 fffff800`02aba0ba : 00000000`00000008 00000000`00000000 fffff880`0822e900 fffff900`c0120020 : nt!KiExceptionDispatch+0xc2
    fffff880`0822e7f0 00000000`00000000 : 00000000`fffffc81 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
     
     
    STACK_COMMAND: kb
     
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+460da
    fffff800`02afba17 cc int 3
     
    SYMBOL_STACK_INDEX: 1
     
    SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+460da
     
    FOLLOWUP_NAME: MachineOwner
     
    MODULE_NAME: nt
     
    IMAGE_NAME: ntkrnlmp.exe
     
    DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
     
    FAILURE_BUCKET_ID: X64_0x1E_nt!_??_::FNODOBFM::_string_+460da
     
    BUCKET_ID: X64_0x1E_nt!_??_::FNODOBFM::_string_+460da
     
    Followup: MachineOwner
      My Computer


  9. Posts : 32
    Windows 7 Ultimate x64 Retail
    Thread Starter
       #19

    zigzag3143 said:
    I would see if I could sync the settings for the old memory and the new mem. Failing that try pulling the new set to see if you get bsod's, then pull the oldd just to narrow it down.
    I tried syncing the settings. i matched them up to 7-7-7-16 and 7-7-7-20 and had no luck. right now i have the new chips in and everything is working fine and i also had the old chips is for a few days and still nothing
      My Computer


  10. Posts : 71,977
    64-bit Windows 11 Pro for Workstations
       #20

    drklazarus26 said:
    zigzag3143 said:
    I would see if I could sync the settings for the old memory and the new mem. Failing that try pulling the new set to see if you get bsod's, then pull the oldd just to narrow it down.
    I tried syncing the settings. i matched them up to 7-7-7-16 and 7-7-7-20 and had no luck. right now i have the new chips in and everything is working fine and i also had the old chips is for a few days and still nothing
    Do you have the option to set all 4 to the same timings in the BIOS?
      My Computer


 
Page 2 of 4 FirstFirst 1234 LastLast

  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 16:39.
Find Us