Blue screen of death. What does this mean?

Superman · Post by **Superman** » 2004-03-26 09:43am

What does PAGE_FAULT_IN_NON_PAGE_AREA mean? I'm pretty sure that's what it said.

Faram · Post by **Faram** » 2004-03-26 09:56am

Straight from an other board I frequent a lot:

Did you upgrade your RAM all at once? If not, make sure that you have the same type, brand, and model RAM modules.

Every RAM module has a memory controller on-board. The memory controller tells the computer how to talk to it, and sometimes, another memory module doesn't talk the same way that the other module does, thus the system gets confused since it is getting mixed signals on which way to talk to the RAM.

Superman · Post by **Superman** » 2004-03-26 09:57am

Well, it was working fine, but I had a PC shop replace the processor a week ago, and then about two days ago it starts doing this. It was working fine before...

Faram · Post by **Faram** » 2004-03-26 10:09am

Try this memory tester:
http://www.memtest86.com/

The memory might have been damaged from ESD

phongn · Post by **phongn** » 2004-03-26 10:55am

Could be bad RAM, but could also be bad drivers.

Superman · Post by **Superman** » 2004-03-26 10:57am

Thanks. It's passed the memory tests. My PC has it's own system doctor. What should I do now?

Vertigo1 · Post by **Vertigo1** » 2004-03-26 08:37pm

What was the exact hex number it gave you? Take that number and run a search on the MSDN and it'll tell you what it means.

Superman · Post by **Superman** » 2004-03-27 01:16am

Next time it shits on me, I'll write it down... If it survives.

Superman · Post by **Superman** » 2004-03-27 01:37am

Got it.

First of all, it said: PFN_List_Corrupt

The numbers are: Stop: 0x0000004E (0x00000099, 0x000z95B7, 0x00000000, 0x00000000)

What should I do now?

Sarevok · Post by **Sarevok** » 2004-03-27 01:38am

It may possible that a program tried to deference a null pointer.

Superman · Post by **Superman** » 2004-03-27 01:42am

OKay, I did a little digging and it seems that the most likely cause is that one of my memory chips is bad. I have one 256 and a 512. How do I determine which is causing it? Just pull one out at a time and run the PC until it crashes?

Sarevok · Post by **Sarevok** » 2004-03-27 01:56am

Try to run your PC with the 256 first then the 512. The one that crashes is the one causing the problems.

Vertigo1 · Post by **Vertigo1** » 2004-03-28 01:24am

Superman wrote:OKay, I did a little digging and it seems that the most likely cause is that one of my memory chips is bad. I have one 256 and a 512. How do I determine which is causing it? Just pull one out at a time and run the PC until it crashes?

psst, read the last part of my earlier post.