BSOD Debugging

Hi. I've been getting some BSODs lately on my laptop, talked to tech support and they thought it was the hard drive, so I wrote zeros to it, reinstalled everything, and still have the problem. My personal thought is drivers or RAM. I have experience with computers, but generally nothing this technical. Anyhow, I decided to find out how to read the minidump files, and this is what I got from the last BSOD. I was installing some windows updates at the time, so the offending process was msiexec.exe. Anyhow, This is what I got from the dump file. Thanks for any help you can provide.

I'm also going to try to get more blue screens to narrow the results.

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

Use !analyze -v to get detailed debugging information.
BugCheck 4E, {99, 7d2af, 0, 0}
Probably caused by : memory_corruption ( nt!MiDeleteValidAddress+126 )
Followup: MachineOwner
---------

1: kd> !analyze -v

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000099, A PTE or PFN is corrupt
Arg2: 0007d2af, page frame number
Arg3: 00000000, current page state
Arg4: 00000000, 0

Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x4E
PROCESS_NAME: msiexec.exe
LAST_CONTROL_TRANSFER: from 805256bd to 805371aa

STACK_TEXT:
b2f0cbe0 805256bd 0000004e 00000099 0007d2af nt!KeBugCheckEx+0x1b
b2f0cc14 8058c8e8 77d45001 877150b0 003ffffc nt!MiDeleteValidAddress+0x126
b2f0cc34 80503d2d 877150b0 877151e8 877150b0 nt!MiDeleteAddressesInWorkingSet+0x65
b2f0cc68 8058c292 007150b0 87594d20 c0000005 nt!MmCleanProcessAddressSpace+0x193
b2f0ccf0 8058c9f1 c0000005 b2f0cd4c 804e75c2 nt!PspExitThread+0x621
b2f0ccfc 804e75c2 87594d20 b2f0cd48 b2f0cd3c nt!PsExitSpecialApc+0x22
b2f0cd4c 804dda0a 00000001 00000000 b2f0cd64 nt!KiDeliverApc+0x1af
b2f0cd4c 7c90eb94 00000001 00000000 b2f0cd64 nt!KiServiceExit+0x59
WARNING: Frame IP not in any known module. Following frames may be wrong.
0092ff78 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiDeleteValidAddress+126
805256bd 00ff add bh,bh
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77
SYMBOL_NAME: nt!MiDeleteValidAddress+126
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x4E_nt!MiDeleteValidAddress+126
BUCKET_ID: 0x4E_nt!MiDeleteValidAddress+126
Followup: MachineOwner
 
Could well be a ram problem!!!!

Google and get memtest and run it for at least 7 passes!!!!
 
Would it be safe to say that it's a memory issue if it has 125000 errors and is only half-way throught the first pass?
 
Back