BSODs :(

[dave87]

Hey Guys,

got a reoccuring BSOD with my Dell laptop - PFN_LIST_CORRUPT

Just wondering what it could be that is triggering it - I doubt device drivers, though it has done it a couple of times when I've turned on my external hard drive. Otherwise its completely random.

I gather its to do with the Page File list, but I haven't got a clue what would cause it. I think it did a memory dump, any help finding that (if it would be useful) would be much appreciated

Dave

[Craig321]

Post your most recent minidump here (C:\WINDOWS\Minidump) and i'll debug it for you.

[dave87]

I had a hunch last night that one of the things that could cause it would be dodgy memory - as I've randomly had these kind of errors since new (sporadically, so never tracked down the fault) - and my memory is borked. Memtest throws up numerous errors - so time to phone dell and have a moan

Cheers anyhow

Dave

[dave87]

Maybe not as transparent as initially thought...

Memtest86, though showing up errors yesterday, today isn't.
Dell Diagnostics cant find anything wrong.

Help?

EDIT -

dump now here

Thats the last few (from about the last 8 BSODs)

[dave87]

any ideas? anyone?

[CrazyMonkey]

EDIT- Sorry just seen craigs post, ill let him Debug as hes 1st.

[dave87]

I honestly don't mind if you both look, just need to get an answer so I know what to do - look at getting dell to accept the memory is at fault, or sort whatever the software issue is which is causing it

[CrazyMonkey]

Ok ill have a look through im on a different computer so im installing debugging tools now shouldnt be too long. Have you tried sending your dumps to Microsoft?
Or searching "PFN_LIST_CORRUPT" on Microsoft.com?

[dave87]

The error reporting tool sent some information to microsoft, but I haven't done anymore than that.

Searching for PFN_LIST_CORRUPT was how I found out it was related to the pagefile, but that was about it.

I'm better with hardware than I am software unfortunately

Dave

[CrazyMonkey]

Sorry, I get c+ error a break then client shuts down. If craig doesnt get back to you soon then i can give it a shot tommorow on the other computer.

[dave87]

Ah, cheers for your help anyway

Dave

[CrazyMonkey]

By the way what OS are you running? Im gonna look into it but i need to know some basics.
I would think it is a Driver conflict, have you installed any drivers recently? if so try the Windows XP/Pro/MC roll back feature.
Try running Memtest to see if its a memory conflict.

[dave87]

XP Pro With SP2

CoreDuo 2ghz
2gb DDR2 SODimm

Anything else you need to know?

[charleski]

Can you remember when it first began? If so, take a look back through your System Restore points to see what the last driver change was prior to the crashes, sometimes the fault takes a while to percolate through.

Just noticed that you say memtest was showing errors - it's faulty RAM then. AFAIK memtest can throw up false negatives, but not false positives, a RAM test should never show any errors at all.

[CrazyMonkey]

Forget this go to next post.
EDIT- All the different Dump files are reporting to different problems. I personally think its a memory issue, however it could be my Kernel as i dont have the required Symbol files so i may get errors.

[CrazyMonkey]

ntoskrnl.exe keeps coming up but ive found problem!
Latest dumps return "memory_corruption" your ram's had it mate. Send it back!
Yeah 100% sure its memory corruption, the last 2 dump's both return same errors.