Page 1 of 1
Blue screen of death. What does this mean?
Posted: 2004-03-26 09:43am
by Superman
What does PAGE_FAULT_IN_NON_PAGE_AREA mean? I'm pretty sure that's what it said.
Posted: 2004-03-26 09:56am
by Faram
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.
Posted: 2004-03-26 09:57am
by Superman
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...
Posted: 2004-03-26 10:09am
by Faram
Try this memory tester:
http://www.memtest86.com/
The memory might have been damaged from ESD
Posted: 2004-03-26 10:55am
by phongn
Could be bad RAM, but could also be bad drivers.
Posted: 2004-03-26 10:57am
by Superman
Thanks. It's passed the memory tests. My PC has it's own system doctor. What should I do now?
Posted: 2004-03-26 08:37pm
by Vertigo1
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.
Posted: 2004-03-27 01:16am
by Superman
Next time it shits on me, I'll write it down... If it survives.
Posted: 2004-03-27 01:37am
by Superman
Got it.
First of all, it said: PFN_List_Corrupt
The numbers are: Stop: 0x0000004E (0x00000099, 0x000z95B7, 0x00000000, 0x00000000)
What should I do now?
Posted: 2004-03-27 01:38am
by Sarevok
It may possible that a program tried to deference a null pointer.
Posted: 2004-03-27 01:42am
by Superman
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?
Posted: 2004-03-27 01:56am
by Sarevok
Try to run your PC with the 256 first then the 512. The one that crashes is the one causing the problems.
Posted: 2004-03-28 01:24am
by Vertigo1
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.