Discussion Locked

BSOD with more than 64mb RAM in W2K Pro

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a WS that has 600mhz Celeron with 64mb RAM running W2K Professional. When I tried to add more RAM (in any combination), I get a BSOD with a message about "page fault in non page area" as Windows is loading. It gets past the POST fine, so I'm thinking maybe it is something with the OS.
I have an identical WS that does not have this problem. The only differences in the two are; mine has SP1 and Norton AntiVirus installed. I also have Windows 2000 Recovery Console loaded. Every thing else is the same, including BIOS setting and jumpers on the Main Board. Speaking of the Main Board, our vender send me another because they thought it might have been bad, but the new one is doing the same thing.
I tried "Safe Mode" and the last file that loaded was ...\winnt\system32\drivers\mup.sys before it BSOD'd.
Any help would be greatly appreciated.
Thanks.
(This may be posted in duplicate. If so, sorry)

8 replies

by dean_magnusson

Are you set for ecc? your memory may or may not be set to the correct spec's. Is the memory seated correctly? Sometimes they work loose, or not installed correctly, as an oversight. I use mem turbo, to clean up the ram after booting, and when windows won't let go of the ram I need. 64 megs doesn't sound like you have enough to be running nt along with all the other programs you have running at startup. Just a few things to ponder on.

by swetbak

Thanks for the suggestions. I have no doubt that the RAM is seated correctly. Believe it or not, but 64mb on this machine runs W2K Prof. fine. I would however like it to run optimally which is why I am trying to install more RAM.

by kgosnell

Seems like you need to uncheck the memory hole, as that when activated, will limit you to 64 meg on some MOBOs, because my AMD is that way.
Hope this helps

by swetbak

Thanks for the suggestion, but my BIOS doesn't have that setting. I came across a very good "Bios Configuration Guide" at http://www.rojakpot.com/ while researching your suggestion, if you are interested.
I'm still looking for my solution.

by kgosnell

This is an outside shot, go into system info,tools, then system ini and select v-cache , and uncheck the maximum setting , leaving Win to set it to the defaul setting, provided there is a setting for maximum, as at times there is software that setsthis to a value not compatable with what we are doing. And thanks for the suggestion you gave me, I'll check it out.

by swetbak

There is no reference to v-cache in the system.ini file. Thanks for your time with this. Who would have thought adding RAM would be such an ordeal.

by swetbak

It seems I have fixed the problem, although I am not quite sure what the cause was. Here is what I did.
Since the second (identical) machine was working fine, I knew it's motherboard and HD were good. I swapped HD's between machines expecting oneof them to experience the same behavior, either the good machine if my HD was bad, or "my" machine if it was a problem with the motherboard (MB) or some other component still on the MB. Well, both machines worked fine with any combination of RAM. I was stumped so I replaced the HD's back to their original machines, and low and behold I was now able to add RAM without consequence. The only thing I did (which was incidental) was straighten a sharp crease in the HD ribbon of my machine during the swap.
Anyhow, whatever was the problem is behind me now. Thank God!! and thanks for your input.

This discussion is closed to new replies.