Weird problem...
 

I was at a LAN this past weekend, when a friend of mine experienced another bout of the LAN disease. On the first startup after resetting his computer, he had an error saying something about "Paging Fault in a Non Paging area" After this, his computer was having partial boots, or it would power down when booting up. The most common thing was when hitting the power button, the computer would idle for several seconds, no POST, and then shut off. Randomly, it started working, and now that he has it at home, its doing the same type of thing. We reseated everything, tested it with another power supply, examined everything for visual damage, etc, and can find nothing wrong. Anyone ever hear of anything like this before???

System specs (dont know them all, ill post them when i find them out)

AMD CPU
unknown mobo
Enermax PSU
Radeon 9800 Pro

I would suspect faulty RAM, and after doing some searching around on the net, it seems to be the most likely problem. Check out what MS has to say...

http://msdn.microsoft.com/library/de...kmsgs/6093.asp

You can take a look here to find possible solutions to the problem. Scroll down to the one labeled "PAGE_FAULT_IN_NONPAGED_AREA":

http://aumha.org/win5/kbestop.htm

Ok, i guess i just wasnt understanding how the PSU would be shorting out if it was the RAM. I suspected the mobo, but that error points to the RAM. Unless maybe it was the mobo not pointing to the right RAM? What about it not posting? if there was an error in the ram, wouldnt the mobo still post?

Give us the error code. When Windows BSODs with a page fault, there is an error code in there. Write it down. It may take several reboots to get it down. Once you get that error code, you can look it up on the MS website and it will give you a better idea of what is happening.

The problem is, that the error only came up once, and then wouldnt come up again. Hard to get an error code from that. The links devnull posted were useful.

Is there any beeping by the pc speaker?
Google up dos memory test software, and try that out.
Also maybe something when move abouts when pc was moved to lan? Check everything is firmly slotted in place on the motherboard/anything else on other components.

you ought to be able to find the fault code in the windows event log, its a good idea to keep the memory dump at least on minimum , then you can get all the info you need.