1st post. Please help, keep getting BSOD-memory dump.

[wicked45]

Hi fellas, I'm new the forum. I just recently been getting the BSOD - memory dump error.
windows 7 ultimate 64bit
dual processor e2160 1.8ghz
geforce mx 440/onboard video card
4 gigs of memory (2gigs of ddr pc-5700, 2 gigs of ddr pc-6400)

After getting the memory dump error, i thought it was my memory. I had installed the 2 gigs of ddr pc 6400 awhile back and havent had a problem. Thought it was a memory error so i took out the pc 6400 and havent been getting the BSOD every since. Installed the pc 6400 memory onto another pc without any issues so i dont think the memory is causing the problem. Also, i read up where it might be a problem with my video card (geforce nvidia mx440 64mb) so i tried updating my video card driver but was unable to find a supported driver for win 7 64 bit. Now i am using the onboard video card. Any help would be greatly appreciated. Attached are the dump files.

 

[The Howling Wolves]

Drivers - Download NVIDIA Drivers

Go here to find 64 bit for 400series

 

[wicked45]

thx for the reply but the link doesnt have an option to download the drivers for windows 7 64 bit. any other advice??

 

[The Howling Wolves]

thx for the reply but the link doesnt have an option to download the drivers for windows 7 64 bit. any other advice??

But it does have a support button at the top to answer your question.
Hope this helps!

 

[Jonathan_King]

This seems pretty straightforward. The 2 different RAM types are incompatible, thus causing memory_management BSODs.

I will contact a couple of RAM experts, and they will see if there is anything to be done about it, or if you need to return the new RAM.

Please be patient as they are in different time zones.

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 15 19:01:30.643 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:16.516
BugCheck 1A, {41284, 701d5001, 2ccd, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
BUGCHECK_STR:  0x1a_41284
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Jun 14 10:58:16.807 2010 (UTC - 4:00)
System Uptime: 0 days 0:39:00.392
BugCheck 1A, {3452, 1f17000, fffff70001086af0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33ab3 )
BUGCHECK_STR:  0x1a_3452
PROCESS_NAME:  wlcomm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jun 12 11:04:54.624 2010 (UTC - 4:00)
System Uptime: 0 days 13:04:23.071
BugCheck 4E, {99, 773, 2, cf432}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jun 12 11:27:53.610 2010 (UTC - 4:00)
System Uptime: 0 days 0:21:51.757
BugCheck 1A, {41284, 63b8001, 14cd, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 )
BUGCHECK_STR:  0x1a_41284
[COLOR=Red][B]PROCESS_NAME:  LogMeInSystray[/B][/COLOR]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jun 11 19:42:54.129 2010 (UTC - 4:00)
System Uptime: 0 days 0:19:54.314
BugCheck 1A, {403, fffff68000027af0, 9a1000000e325025, fffff680000557ca}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31f72 )
BUGCHECK_STR:  0x1a_403
PROCESS_NAME:  rundll32.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jun 11 21:59:21.155 2010 (UTC - 4:00)
System Uptime: 0 days 0:44:12.096
BugCheck 50, {fffff8a00b286000, 0, fffff80002b6c45b, 0}
Probably caused by : ntkrnlmp.exe ( nt!HvpSetRangeProtection+a3 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  rundll32.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jun 11 20:01:14.701 2010 (UTC - 4:00)
System Uptime: 0 days 0:17:11.027
BugCheck DE, {2, fffff8a003017af0, fffff6fc0007a139, f4278c0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2d2e0 )
BUGCHECK_STR:  0xDE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
 [/FONT]

I also suggest updating or removing LogMeIn. See evidence in red above. Here is some more:

lmimirr.sys  Tue Apr 10 18:32:45 2007 (461C108D)
lmimirr.sys  Tue Apr 10 18:32:45 2007 (461C108D)
LMIRfsDriver.sys Mon Jul 14 12:26:56 2008 (487B7E50)

 

[Fumz]

... I had installed the 2 gigs of ddr pc 6400 awhile back and havent had a problem. Thought it was a memory error so i took out the pc 6400 and havent been getting the BSOD every since. Installed the pc 6400 memory onto another pc without any issues so i dont think the memory is causing the problem...

Each kit of RAM has a unique SPD (serial presence detect) chip. This chip tells the motherboard what voltage to use and what timings to set for a given set of frequencies: 333MHz, 400MHz, 533MHz, etc etc. Timing and voltage tables are given for the rated speed of the RAM, as well as lower speeds should the board decide that the kit needs to be run at a lower than default speed; which is what's going on with your pc-6400.

Memory makers continually update and change these chips. Even if you buy two kits which are seemingly identical, unless you purchase them at the same time, it's almost assured that the SPD chips will have different values. That's why, if possible, you should always buy all your RAM at the same time. If that's not possible, then at least purchase RAM with the exact same specs as your current kit. It's never a good idea to buy a kit with a different frequency than your current kit because a) the board will always set memory speed to the frequency of the slowest kit, and b) the SPD chip thing.

That the memory works in another machine only tells you that it works, so no, it's not the memory, per se. What the issue seems to be is that it's just not working well with your older kit. Perhaps you can overcome this by loosening the timings and/or adjusting the voltage? The safer/easier route would be to RMA the new kit (hopefully that's still possible) and select a kit of pc-5700.... or get another kit of 6200.

 

[wicked45]

thank you guys for replying. it's just strange that i have installed these new rams awhile back and have not had any issues until lately. i ran a crucial scan and it says that my pc is compatible with the ram i have (pc6400). i am also getting another BSOD...something with reference_by_pointer when i have the ram installed, not sure if both are related. can you please check it out and let me know whats wrong? attached are the dump files. thanks a bunch!!!