Random BSOD

[fleischer]

I have been having random BSOD on my computer always while playing games. Usually when I quit a game.
Here is a one of the minidumps. But im having some problem understanding it.
Its not just one game. I have reinstalled the graphics driver.

q6600 2gb ram Xp service pack 3

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: 0004913a, page frame number
Arg3: 00000003, current page state
Arg4: 00000000, 0

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


BUGCHECK_STR: 0x4E_99

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: DOW2.exe

TRAP_FRAME: b2aa8910 -- (.trap 0xffffffffb2aa8910)
ErrCode = 00000000
eax=53310000 ebx=b2aa8d64 ecx=00001000 edx=fffff000 esi=5330fd20 edi=53310000
eip=80615a8f esp=b2aa8984 ebp=b2aa898c iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!ProbeForWrite+0x39:
80615a8f 8a06 mov al,byte ptr [esi] ds:0023:5330fd20=??
Resetting default scope

LAST_CONTROL_TRANSFER: from 805173a0 to 804f9f43

STACK_TEXT:
b2aa882c 805173a0 0000004e 00000099 0004913a nt!KeBugCheckEx+0x1b
b2aa884c 805224ab 81e85500 0000003f 00000000 nt!MiRestoreTransitionPte+0x12e
b2aa8864 80522c2e 00000000 0000000d c0299878 nt!MiRemovePageFromList+0xd1
b2aa887c 80514b2f c06014c8 c0299878 00000000 nt!MiRemoveAnyPage+0xc8
b2aa8894 805205bd 5330fd20 c0299878 88543da0 nt!MiResolveDemandZeroFault+0xe5
b2aa88f8 80544588 00000000 5330fd20 00000000 nt!MmAccessFault+0xbeb
b2aa88f8 80615a8f 00000000 5330fd20 00000000 nt!KiTrap0E+0xd0
b2aa898c 80504344 5330fd20 000002dc 00000004 nt!ProbeForWrite+0x39
b2aa8cf8 804ff975 00000000 b2aa8d64 7c901166 nt!KiInitializeUserApc+0x74
b2aa8d4c 8054181e 00000001 00000000 b2aa8d64 nt!KiDeliverApc+0x1d5
b2aa8d4c 7c8106e9 00000001 00000000 b2aa8d64 nt!KiServiceExit2+0x3a
WARNING: Frame IP not in any known module. Following frames may be wrong.
00000001 00000000 00000000 00000000 00000000 0x7c8106e9


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiRestoreTransitionPte+12e
805173a0 8b5008 mov edx,dword ptr [eax+8]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiRestoreTransitionPte+12e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48a3fbd9

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x4E_99_nt!MiRestoreTransitionPte+12e

BUCKET_ID: 0x4E_99_nt!MiRestoreTransitionPte+12e

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

 

[Route44]

The error PFN_LIST_CORRUPT (4e) is a very strong indicator of corrupted memory. In fact, if you scroll to the bottom of what you posted it says memory_corruption. So..


1. Go to www.memtest.org and download the latest ISO version. It is free and perfectly safe.

2. Burn to a CD.

3. Place CD in your drive and reboot with CD in drive. The test will take over.

4. Let it run for a LONG time. The rule is a minimum of 7 Passes. There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.

5. If you have errors you have corrupted memory and it needs to be replaced.

6. Also, with errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you begin getting errors on a stick you don't need to run it the full 7. You know that it is bad and needs to be replaced.

* Get back to us with the results.

 

[fleischer]

Thanks alot. I let you know what I find out. So memory corruption is always ram and not HD? Can I run a test on both ram to check for the error and if I get one then check the single one? Or wont the error show with both rams?

 

[Route44]

Memory corruption is RAM onjly and Memtest is for RAM only. If you ever need to diagnose your harddrive your harddrive manufacturer will supply you a free utility to test.

Run with all your sticks in. If you get errors it won't tell you which one(s). That's why you'll want to run this test one stick in your system at a time if you get errors..

Here is a personal example. I was getting random crashes and reboots. One of my errors was the same as yours. At the time in this system I was running a 4x512 RAM configuration. I ran memtest and I didn't even get to the first PASS when I got all kinds of errors (though one time in another system I didn't get errors to the fifth Pass).

So I took out three of the sticks and ran them one at a time. It was the third one out of four but I still needed to run Memtest on the fourth. Needless to say I won't ever use another 4x512 configuration again.