Memory Issues

[drklazarus26]

I recently purchased 2gb of ram. I bought the same ram that was already in my machine and i now have 4gb but for some reason the they are running at different speeds and my computer seems to be crashing. All 4 chips are OCZ Platinum PC12800 DDR3 1600MHz. Im not sure if this is a motherboard issue or a windows 7 issue but i im not sure whats going on. sound like its a memory handler issue. any thoughts? thx in adv

 

[Brink]

Hello Drklazarus, and welcome to Seven Forums.

Double check to make sure that each pair are in the same color RAM slots. The timing may be different with the new sticks than the older ones even though they are the same type, so mixing them in the same colored slots may cause issues.

Next, reset the BIOS back to defaults. On some older motherboards, you may need to update the BIOS to the latest version to resolve this issue as well.

If you are still having issues, then you might run Memtest86 to test and see if you may have bad memory.

Hope this helps,
Shawn

 

[drklazarus26]

Thx for the speedy response. I've checked the ram specs as well as their placement and everything is fine. i also updated the bios and reset the settings to default and still no luck. I recieved a BSOD the other day and this is how it was logged "The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000005, 0x0000000000000000, 0x0000000000000008, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 090909-16781-01."

 

[zigzag3143]

Thx for the speedy response. I've checked the ram specs as well as their placement and everything is fine. i also updated the bios and reset the settings to default and still no luck. I recieved a BSOD the other day and this is how it was logged "The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000005, 0x0000000000000000, 0x0000000000000008, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 090909-16781-01."

DL

Coould you go into c:\windows\ zip the dump file (*.dmp) and upload it to us so we can debug it?

Thanks

Ken

edit: if you need help in uploading let us know

 

[Brink]

This may also help with this error:
How to Troubleshoot a STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED Error Message

and

0x0000001e (0xffffffffc0000005, 0x0000000000000000, 0x0000000000000008, 0x0000000000000000) - Google Search=

Try only having the new RAM in the same colored slots to see how they run by themselves. Also run Memtest86 on them. If that checks out ok, then add the older sticks back in and run Memtest86 again.

Have you installed any new drivers before this happened?

 

[drklazarus26]

um the dmp file is 99mb !!! how can i shrink it or upload it otherwise

 

[drklazarus26]

The only drivers that I updated were done when I installed W7 and I had no trouble until i installed the ram. I tried using each stick seperately in each slot and they work 2 at a time but not all together.

 

[zigzag3143]

um the dmp file is 99mb !!! how can i shrink it or upload it otherwise

That has to be more than 1 dump file right? Just upload the last one. If its just one and its 100 megs upload it to somewhere like RS and I will pull it down. Only way it can be 100 meg for 1 dump file is if you have a complete memory dump instaed of a minidump

Ken

 

[Brink]

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?

 

[drklazarus26]

yeah its has to be complete. im uploading it now. it should be up in 5 mins. btw thx for the help ive tried a few other forums and got nothing at all. i really appreciate especially the nelp from my fellow new yorker ;P

 

[Dwarf]

Have a look at this from Intel.

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

 

[zigzag3143]

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.

 

[TGSoldier]

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

Did you run Memtest on the new memory ?

 

[drklazarus26]

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

 

[drklazarus26]

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

 

[Dwarf]

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?

 

[drklazarus26]

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

 

[zigzag3143]

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

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*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
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

 

[drklazarus26]

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

 

[Brink]

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?