stop screens

A

athomas

Geek Trainee
I am getting the following stop screens when booting up, loading programs, or just randomly:

PFN_LIST_CORRUPT
IRQL_NOT_LESS_OR_EQUAL
MEMORY_MANAGEMENT

Not quite sure what they mean but everything I've looked into points to bad RAM. Is this right or what should I do?
 
You can run Memtest86+ overnight and see if you get any memory errors, and at least that could narrow your problem to a hardware error. Just download the approprate binary and either burn the image to CD or to floppy respectively, boot to it and let it go for several hours. If you get even one memory error during that period, we know something is going wrong somewhere on the memory buss. If not, we can likely start troubleshooting a Windows problem.
 
the thing is, I've tried windows 2000 and xp, fresh installs multiple times and I'm still getting the same errors. I reformatted my whole system (the normal format not the quick format) so my hdd's are fine... that eliminates that. I know it's not software related.

Thanks!
 
athomas said:
the thing is, I've tried windows 2000 and xp, fresh installs multiple times and I'm still getting the same errors. I reformatted my whole system (the normal format not the quick format) so my hdd's are fine... that eliminates that. I know it's not software related.
Click to expand...
Well then, do as I sugested and we can narrow the type of hardware problem from there. :)
 
Well I'm not seeing those screens anymore, just this one:

0x00000024

I looked it up on MSDN and it said to run chkdsk /r... did that, and nothing happened no errors found. It says there's something wrong with NTFS but if I JUST installed XP how does that happen...?
 
athomas said:
...As far as I know, RAM isn't causing this particular message.
Click to expand...
Well you would know for sure if you had tested the RAM like I suggested. I'm trying to help you narrow the possibilities by eliminating variables; bad RAM can cause strange symptoms which are often misdiagnosed. All of the error messages you listed corroborate either bad RAM or a problem somewhere on the memory buss.
 
You must log in or register to reply here.
Back
Top