Windows Vista Vista Blue Screen, Mini Dump Result

Hello everyone my name is Mike, new on these forums hopefully you guys can help me resolve this interesting dilema i am having recently..

background: i have a laptop with 512mb x2 = 1gb of memory, i recently got it upgraded to 1gb x2 to make obiously 2gb. Although when i installed the updated memory and booted my PC up i received the blue screen of death! and the pc restarted.. and this is where i am now i did a mini dump check using WinDbg.

------

Results:

Loading Dump File [C:\WINDOWS\Minidump\Mini010908-09.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16575.x86fre.vista_gdr.071009-1548
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Wed Jan 9 15:02:30.841 2008 (GMT-5)
System Uptime: 0 days 0:01:30.451
Loading Kernel Symbols
..............................................................................................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {82d48740, 0, 81c5e849, 0}



Probably caused by : ntkrpamp.exe ( nt!RtlSplay+a2 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: 82d48740, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 81c5e849, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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




READ_ADDRESS: GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0
82d48740

FAULTING_IP:
nt!RtlSplay+a2
81c5e849 390f cmp dword ptr [edi],ecx

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 9

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 1

TRAP_FRAME: 92755b80 -- (.trap 0xffffffff92755b80)
ErrCode = 00000000
eax=915fa8e4 ebx=915fa8dc ecx=8345fc1c edx=834f681c esi=82d4873c edi=82d48740
eip=81c5e849 esp=92755bf4 ebp=92755bfc iopl=0 nv up ei ng nz na po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010283
nt!RtlSplay+0xa2:
81c5e849 390f cmp dword ptr [edi],ecx ds:0023:82d48740=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c8fbb4 to 81ca9ef2

STACK_TEXT:
92755b68 81c8fbb4 00000000 82d48740 00000000 nt!MmAccessFault+0x106
92755b68 81c5e849 00000000 82d48740 00000000 nt!KiTrap0E+0xdc
92755bfc 81b4a21a 915fa8e4 00000000 915fa8b8 nt!RtlSplay+0xa2
92755c14 81b4a260 835a137c 00000016 915fa8b8 Ntfs!NtfsInsertNameLink+0xaf
92755c28 81b6441d 915fa8b8 00006e20 92f4f3f7 Ntfs!NtfsInsertPrefix+0x33
92755cec 81ad96b6 86aea718 8701a710 947b7984 Ntfs!NtfsCommonCreate+0xf3e
92755d2c 81c803e8 947b791c 00000000 ffffffff Ntfs!NtfsCommonCreateCallout+0x20
92755d2c 81c804e1 947b791c 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x118
947b78b4 00000000 00000000 00000000 00000000 nt!KiSwitchKernelStackAndCallout+0x31


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!RtlSplay+a2
81c5e849 390f cmp dword ptr [edi],ecx

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!RtlSplay+a2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 470c2f52

FAILURE_BUCKET_ID: 0x50_nt!RtlSplay+a2

BUCKET_ID: 0x50_nt!RtlSplay+a2

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

Please Help! extremely frustrated with this probelm.. And on an added note not sure if this matters or not but both memorys using 1gb x 2 to make 2GB they work perfectly fine in safe mode...

 

Your laptop works perfect at safe mode and you can eliminate hardware problem. One of the device driver is in error. Un-install the latest upgraded device driver may fix the problem.