Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD after adding a ram module

11 Jul 2011   #1
velt

Windows 7 Ultimate x64
 
 
BSOD after adding a ram module

So I have a win7 x64 machine, core i5, 4gb of ram recently upgraded to 6gb (more on that later). It was working fine until the new ram module.
I was using two ram modules (2gb x2), and i add a third one (2gb x3), they are the same model and it was a pack of 2gb x3, but for some reason i had only installed two modules and not three.
Si i got the following BSOD and I want to know what it means. Maybe is a ram issue, maybe i should have installed the extra ram dim on the other slot.

.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {90, b, 0, fffff8800f5b9794}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+524794 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000090, memory referenced
Arg2: 000000000000000b, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800f5b9794, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fc100
0000000000000090

CURRENT_IRQL: b

FAULTING_IP:
nvlddmkm+524794
fffff880`0f5b9794 ff9390000000 call qword ptr [rbx+90h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: ekrn.exe

TRAP_FRAME: fffff8800ad99cf0 -- (.trap 0xfffff8800ad99cf0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8004efa010 rbx=0000000000000000 rcx=0000000000000000
rdx=000000000000a817 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800f5b9794 rsp=fffff8800ad99e80 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=fffff8800ad99e50 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nvlddmkm+0x524794:
fffff880`0f5b9794 ff9390000000 call qword ptr [rbx+90h] ds:0096:00000000`00000090=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002ecc2a9 to fffff80002eccd00

STACK_TEXT:
fffff880`0ad99ba8 fffff800`02ecc2a9 : 00000000`0000000a 00000000`00000090 00000000`0000000b 00000000`00000000 : nt!KeBugCheckEx
fffff880`0ad99bb0 fffff800`02ecaf20 : 00000000`00000000 00000000`00000000 fffff8a0`001488f0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0ad99cf0 fffff880`0f5b9794 : fffff880`00000000 00000000`00000000 00000000`00000000 00000000`00001000 : nt!KiPageFault+0x260
fffff880`0ad99e80 fffff880`00000000 : 00000000`00000000 00000000`00000000 00000000`00001000 00000000`00000008 : nvlddmkm+0x524794
fffff880`0ad99e88 00000000`00000000 : 00000000`00000000 00000000`00001000 00000000`00000008 fffff880`0f2e8f1f : 0xfffff880`00000000


STACK_COMMAND: kb

FOLLOWUP_IP:
nvlddmkm+524794
fffff880`0f5b9794 ff9390000000 call qword ptr [rbx+90h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nvlddmkm+524794

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4dd73a68

FAILURE_BUCKET_ID: X64_0xD1_nvlddmkm+524794

BUCKET_ID: X64_0xD1_nvlddmkm+524794

Followup: MachineOwner
---------


My System SpecsSystem Spec
.
11 Jul 2011   #2
Devux

Windows 7 Home Premium 64bit
 
 

Really only three options when you get a BSOD from RAM. Either you have the wrong RAM installed, which doesn't sound like it is the case because they are all matching or the RAM is installed wrong. My guess is that your motherboard requires that RAM be installed in matching pairs, in which case you would need one more stick of RAM that matches the speed and size of the other three. I've run into this problem more than once. Last option would be that you have a bad stick of RAM.
Memtest86.com - Memory Diagnostic
Program from these folks will tell you if that's the case.
My System SpecsSystem Spec
11 Jul 2011   #3
velt

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by Devux View Post
Really only three options when you get a BSOD from RAM. Either you have the wrong RAM installed, which doesn't sound like it is the case because they are all matching or the RAM is installed wrong. My guess is that your motherboard requires that RAM be installed in matching pairs, in which case you would need one more stick of RAM that matches the speed and size of the other three. I've run into this problem more than once. Last option would be that you have a bad stick of RAM.
Memtest86.com - Memory Diagnostic
Program from these folks will tell you if that's the case.
Interesting. Does it have something to do with the dual channel. Maybe there is some tweak in the motherboard i can try?
My System SpecsSystem Spec
.

11 Jul 2011   #4
Devux

Windows 7 Home Premium 64bit
 
 

Quote   Quote: Originally Posted by velt View Post
Interesting. Does it have something to do with the dual channel. Maybe there is some tweak in the motherboard i can try?
In all of my experience, if a motherboard needs RAM to be installed in matching pairs, there really isn't any way around it. If you don't have the documentation on your motherboard to confirm that you may try RAM Memory Upgrade: Dell, Mac, Apple, HP, Compaq. USB drives, SSD at Crucial.com
They are ~usually~ right about motherboard specs and what you can and cannot do with RAM in your machine. Just fill out the questions on make and model of computer.
My System SpecsSystem Spec
11 Jul 2011   #5
velt

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by Devux View Post
Quote   Quote: Originally Posted by velt View Post
Interesting. Does it have something to do with the dual channel. Maybe there is some tweak in the motherboard i can try?
In all of my experience, if a motherboard needs RAM to be installed in matching pairs, there really isn't any way around it. If you don't have the documentation on your motherboard to confirm that you may try RAM Memory Upgrade: Dell, Mac, Apple, HP, Compaq. USB drives, SSD at Crucial.com
They are ~usually~ right about motherboard specs and what you can and cannot do with RAM in your machine. Just fill out the questions on make and model of computer.
my motherboard is an asus P7P55D LE
i found this regarding ram, it seems that it does support 3 ram dimms.
ASUSTeK Computer Inc. -Support-
My System SpecsSystem Spec
11 Jul 2011   #6
karlsnooks

MS Windows 7 Ultimate SP1 64-bit
 
 

You can use a program such as siw to see if they are truly all from the same batch.

Link in my sig.
My System SpecsSystem Spec
Reply

 BSOD after adding a ram module




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD caused by the following module: atikmdag.sys (atikmdag+0x19C6D)
I hope anybody can help me....i already have the latest drivers but i still get BSOD's
BSOD Help and Support
BSOD after upgrading &/or installing new memory module on brand new PC
Good day to all. Can someone please assist me, advance thanks.. I bought a PC with MSI mainboard, N430GT, with 2-2GB Kingston KVR1333D3N9/2G installed RAM (=4GB), 500GB HDD. Everything works smooth until I read that I could upgrade memory up to 16GB max. BTW my OS is Win7 64 Ultimate. So I...
Hardware & Devices
BSOD's that I think are from a corrupt RAM module.
I built my 1st PC around January as an entry level gaming PC. I started out with 4 Gigs of RAM, and all was fine. No problems when playing games, good temps, no issues at all. I then bought another of the same RAM module to make my system 8 GB. This is where I began getting BSOD's-- mostly when...
BSOD Help and Support
Many BSOD mostly on ntoskrnl.exe module and ohter
Hi there. I'm having several BSOD specially with the ntoskrnl.exe module. I've reinstalled windows 7 3 times, but still the same problem. First I tought it was related to the wireless network card (that I have removed) but still BSOD. The latest BSOD occured when I started Steam Cloud and I was...
BSOD Help and Support
Random BSOD faulting module ntoskrnl.exe
Had this happen a few times and I'm having a tough time identifying the real culprit. I've had some USB problems in the past with the board i'm on but that was running under XP. Again, these crashes seem completely random and are fairly far in between. Ran WhoCrashed on the dump file and got...
BSOD Help and Support
BSOD after adding another 1 gb RAM
i just installed an additional 1 gb ram on my pc. Then when i tried to boot Windows 7 build 7201 i got a BSOD. Then i went for a fresh installation then again i got a BSOD error. do u guys know how to solve this problem please help me??
BSOD Help and Support


Our Sites

Site Links

About Us

Find 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 13:53.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App