Windows Vista RAM upgrade problem

loremasterj · 2008/07/25

Hello everyone,
I thought I'd post this here since I think it is a problem with my OS and not my RAM. Anyway, I recently purchased some KVR800D2N5K2/2G for my computer. I purchased a total of two of those kits, so I now have 4gigs of RAM to install. When I try installing them I get a BSOD when it tries to log into windows. Here is my current build.

DG965WH mobo
550w power supply
evga geforce 8600
120g sata HD

And just in case here is a MEMORY.DMP reading:

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18063.x86fre.vistasp1_gdr.080425-1930
Kernel base = 0x8223a000 PsLoadedModuleList = 0x82351c70
Debug session time: Thu Jul 24 20:33:21.156 2008 (GMT-7)
System Uptime: 0 days 0:00:10.937
Loading Kernel Symbols
.............................................................................
Loading User Symbols

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {c0000005, 8a3ad234, 8b55f70c, 8b55f408}

Probably caused by : pci.sys ( pci!PciDispatchPnpPower+10c )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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: c0000005, The exception code that was not handled
Arg2: 8a3ad234, The address that the exception occurred at
Arg3: 8b55f70c, Exception Record Address
Arg4: 8b55f408, Context Record Address

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

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
acpi!ACPIAmliGetNamedChild+8
8a3ad234 8b400c mov eax,dword ptr [eax+0Ch]

EXCEPTION_RECORD: 8b55f70c -- (.exr 0xffffffff8b55f70c)
ExceptionAddress: 8a3ad234 (acpi!ACPIAmliGetNamedChild+0x00000008)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 55f7f00c
Attempt to read from address 55f7f00c

CONTEXT: 8b55f408 -- (.cxr 0xffffffff8b55f408)
eax=55f7f000 ebx=00000000 ecx=8236f27c edx=8236f27c esi=8b55fa50 edi=84b78608
eip=8a3ad234 esp=8b55f7d4 ebp=8b55f7d4 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210202
acpi!ACPIAmliGetNamedChild+0x8:
8a3ad234 8b400c mov eax,dword ptr [eax+0Ch] ds:0023:55f7f00c=????????
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

READ_ADDRESS: 55f7f00c

BUGCHECK_STR: 0x7E

LOCK_ADDRESS: 8236e5e0 -- (!locks 8236e5e0)

Resource @ nt!PiEngineLock (0x8236e5e0) Exclusively owned
Threads: 8477e020-01<*>
1 total locks, 1 locks currently held

PNP_TRIAGE:
Lock address : 0x8236e5e0
Thread Count : 1
Thread address: 0x8477e020
Thread wait : 0x2bc

LAST_CONTROL_TRANSFER: from 8240fb5d to 82307163

STACK_TEXT:
8b55f7d4 8a3d8146 55f7f000 4e55535f 8653d198 acpi!ACPIAmliGetNamedChild+0x8
8b55f80c 8a3e06dc 855bfaa8 855035fc 00000000 acpi!ACPIBusAndFilterIrpQueryCapabilities+0x1be
8b55f834 8a3c191a 855bfaa8 86726018 8b55f87c acpi!ACPIIrpCompletionRoutineWorker+0x5a
8b55f844 822740e4 855bfaa8 8653d198 86726018 acpi!ACPIIrpGenericFilterCompletionHandler+0x40
8b55f87c 807af11c 8653d224 85512b70 86726018 nt!IopfCompleteRequest+0x11d
8b55f894 822f6053 85512c28 8653d198 8653d248 pci!PciDispatchPnpPower+0x10c
8b55f8ac 8a3e07f5 8653d198 8a3d9a94 8653d109 nt!IofCallDriver+0x63
8b55f8c0 8a3d9ab2 84b78608 8653d198 8a3d7f88 acpi!ACPIIrpSetPagableCompletionRoutineAndForward+0xd3
8b55f8e8 8a3b4e4b 855bfaa8 8653d198 8653d198 acpi!ACPIFilterIrpQueryCapabilities+0x1e
8b55f918 822f6053 855bfaa8 84b78608 8655d0e0 acpi!ACPIDispatchIrp+0xff
8b55f930 8a9a355c 8653d26c 00000000 8b55f9a0 nt!IofCallDriver+0x63
8b55f940 8a9a3295 8655d0e0 8a9a61e1 8b55f974 USBPORT!USBPORT_PassIrp+0x93
8b55f9a0 8a99a354 8655d028 8653d198 8b55f9c8 USBPORT!USBPORT_FdoPnP+0xccc
8b55f9b0 822f6053 8655d028 8653d198 8b55fa38 USBPORT!USBPORT_DispatchPnP+0x21
8b55f9c8 823eb856 8b55fa38 8b55fa50 85512b70 nt!IofCallDriver+0x63
8b55f9f8 8239e179 85512b70 8b55fa14 00000000 nt!IopSynchronousCall+0xce
8b55fa3c 8239ee7a 85512b70 00000000 00200286 nt!PpIrpQueryCapabilities+0x5c
8b55fa90 8239fcc0 85518668 00000000 00000000 nt!PnpQueryAndSaveDeviceNodeCapabilities+0x17
8b55faf4 8239c625 00000001 8236c530 00000000 nt!PipProcessStartPhase3+0x31d
8b55fcec 82245b33 847852f8 865615d0 8b55fd38 nt!PipProcessDevNodeTree+0x2d1
8b55fd44 8227241d 00000000 00000000 8477e020 nt!PnpDeviceActionWorker+0x229
8b55fd7c 8240fb18 00000000 aacf9296 00000000 nt!ExpWorkerThread+0xfd
8b55fdc0 82268a3e 82272320 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

FOLLOWUP_IP:
pci!PciDispatchPnpPower+10c
807af11c 8bc6 mov eax,esi

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: pci!PciDispatchPnpPower+10c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: pci

IMAGE_NAME: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b89

STACK_COMMAND: .cxr 0xffffffff8b55f408 ; kb

FAILURE_BUCKET_ID: 0x7E_pci!PciDispatchPnpPower+10c

BUCKET_ID: 0x7E_pci!PciDispatchPnpPower+10c

Followup: MachineOwner
---------
Click to expand...

demon · 2008/07/25

please start your own thread.

Arie · 2008/07/25

"loremasterj said: ↑

Hello everyone,
I thought I'd post this here since I think it is a problem with my OS and not my RAM. Anyway, I recently purchased some KVR800D2N5K2/2G for my computer. I purchased a total of two of those kits, so I now have 4gigs of RAM to install. When I try installing them I get a BSOD when it tries to log into windows.
Click to expand...

Hate to tell you, but the problem is with your memory, not with your OS.

They are either not compatible, or there's a defect somewhere.

Start by testing your memory. Run Memtest86.

Please note:

Memory checking programs are not adequate because they don't test the memory the way that Windows uses it. Most, if not all, memory checkers use read/write cycles when scanning memory. Since Windows is executing code from the memory, it uses execute cycles. Execute cycles are physically different from read/write cycles and are more vulnerable to parity errors. It is possible for memory checking programs to find parity errors if the memory is extremely faulty.
Click to expand...

Try running with 2x1GB. does that work? Try changing the memory around, running it in different combinations... does it always work?

loremasterj · 2008/07/26

I literally tried EVERY combination possible. I tried just running dual channel, I tried running with 3 sticks, and I just gave up. I paid $120 total for the memory and I decided to just wait a couple of weeks and I am going to invest in a new motherboard and new RAM. With my current configuration I cannot overclock my CPU or RAM so here is what I want to get. Suggestions?

Motherboard

RAM

mattman · 2008/07/28

You "recently purchased" the extra RAM, can you return it, explaining that it appears to be incompatible with the motherboard?

Motherboard...go to the manufacturer's website. Do they have a list of compatible RAM for it? (Some do.) Download and check through the motherboard manual. Is it "comprehensive "? Does the manufacturer's website have a broad knowledgebase? What if you have problems apart from RAM?

Go to the manufacturer of the RAM's website. Major manufacturers have a list of motherboards and the model of their RAM that has been tested as compatible.

Matt

Log in or Sign up

Windows Vista RAM upgrade problem

loremasterj Inactive Thread Starter

demon Well-Known Member

Arie Administrator Administrator Staff

loremasterj Inactive Thread Starter

mattman Inactive Alumni

Share This Page

Log in or Sign up

Windows Vista RAM upgrade problem

loremasterj Inactive Thread Starter

demon Well-Known Member

Arie Administrator Administrator Staff

loremasterj Inactive Thread Starter

mattman Inactive Alumni

Share This Page

Useful Searches