Frequent BSOD

I am receiving BSOD's on my laptop all over the place. This has been going on ever since I got the computer. I've sent it into Gateway and supposedly got it back fixed (after three months) yet still is having the same problems. Here is my minidump file that I sent into windbg.

Computer is a P6831FX with 3 gig of ram running intel core 2 duo T5450 @ 1.66 ghz / 32 bit OS Vista Service pack 1 Home premium

I've put in 2 PNY 1gb ddr2 pc2-5300 stick in and still receive BSOD's.

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


Loading Dump File [C:\Documents and Settings\n3demonic\Desktop\Mini122308-10.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 Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x81c06000 PsLoadedModuleList = 0x81d1dc70
Debug session time: Tue Dec 23 23:25:05.618 2008 (GMT-5)
System Uptime: 0 days 0:02:05.538
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 81c7b005, 8ec8f6cc, 0}

Probably caused by : memory_corruption ( nt!MiDeferredUnlockPages+26 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 81c7b005, The address that the exception occurred at
Arg3: 8ec8f6cc, Trap Frame
Arg4: 00000000

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


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

FAULTING_IP:
nt!MiDeferredUnlockPages+26
81c7b005 750f jne nt!MiDeferredUnlockPages+0x37 (81c7b016)

TRAP_FRAME: 8ec8f6cc -- (.trap 0xffffffff8ec8f6cc)
ErrCode = 00000000
eax=00000002 ebx=00000000 ecx=00000000 edx=00000001 esi=00000000 edi=00000000
eip=81c7b005 esp=8ec8f740 ebp=8ec8f79c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!MiDeferredUnlockPages+0x26:
81c7b005 750f jne nt!MiDeferredUnlockPages+0x37 (81c7b016) [br=0]
Resetting default scope

CUSTOMER_CRASH_COUNT: 10

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 81cf587d to 81c7b005

STACK_TEXT:
8ec8f79c 81cf587d 00000000 00000000 00001068 nt!MiDeferredUnlockPages+0x26
8ec8f87c 81cf429c 9a71b000 9a71b000 8ec8f964 nt!MiFreePoolPages+0x10c
8ec8f8e4 81e18c14 9a71b000 00000000 bbd7a941 nt!ExFreePoolWithTag+0x40e
8ec8f930 81e33c4a 81c4ca01 bbd7a9d1 00000014 nt!PfpPfnPrioRequest+0x15b
8ec8f9a0 81e3f1c9 00000000 81c4ca01 8ec8fd30 nt!PfQuerySuperfetchInformation+0xea
8ec8fd4c 81c5da1a 0000004f 01e6f44c 00000014 nt!NtQuerySystemInformation+0x2201
8ec8fd4c 77289a94 0000004f 01e6f44c 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
01e6f418 00000000 00000000 00000000 00000000 0x77289a94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiDeferredUnlockPages+26
81c7b005 750f jne nt!MiDeferredUnlockPages+0x37 (81c7b016)

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiDeferredUnlockPages+26

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7fa

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x8E_nt!MiDeferredUnlockPages+26

BUCKET_ID: 0x8E_nt!MiDeferredUnlockPages+26

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

 

Possible failing RAM modules.

After making sure mod's are seated correctly and compatible with your systems mobo specs, run Memtest in order to determine your RAM's good health!

http://majorgeeks.com/MemTest_d350.html

Let us know the results!

Regards