Okay, here's the scoop. I'm getting several 'STOP ERROR:0x00000A' type messages that prompt me to a blue screen after sudden crashes. Here are some of the things I've seen...

- PAGE_FAULT_IN_NON_PAGED_AREA
- DRIVER_IRQL_NOT_LESS_OR_EQUAL
- (No message at all, just a reboot)

I have exactly no clue what to do about all of this. I haven't installed any new hardware or drivers, and it's a really sudden problem.

And it's pissing me off . Any of you techies here have a reasonable solution to this? Or a method of troubleshooting?

I've been getting the PAGE_FAULT BSOD at least five times a month for the past few years. I've accepted this as either

a. Faulty Hardware on the part of Dell
b. Poor Coding on the part of MS
c. Executing Software not intended to run on Win XP SP2 on the part of me

In a year I'll be off the windows teat, so I can manage.

the only way to stop the Windows blue screen of death....




is to buy a Mac.




Simple and easy.

read the last line of my post.

the fact is, some of us use a windows box for gaming. so no, buying a mac is not a solution for me.

Since Justin's not here at the moment, I'll just step in to clarify that he's been getting these errors starting just two nights ago (I think), and last night, every time he rebooted his computer, it continually kept crashing with error screens. So yeah, it's not just once every couple days or anything.

It sounds like it could be an error with RAM or your virtual memory pagefile. Here is an MS Knowledgebase article that might solve your problem: http://support.microsoft.com/default.aspx?...kb;en-us;810093.

Better yet, contact your vendor of the PC. It could be there software. Like with Acer Laptops and there “sticky keys” where the keyboard software makes the OS think that it is holding down multiple key causing it to beep and windows to “jam”. (That was a example)

And, artislife90 don't just blame everything on a operating system. I could blame Mac OSX for saying it can't find my memory on my mac Mini, but I don't. Because I called Macintosh and well it was there fault, they had a conflict or something, so I got a new one. And its still in the box. I don’t want to get it out and be disappointed on wasting my money on something that will f**k up again.

I know Windows is infallible and doesn't get BSOD's anymore, but in this case, it looks like a virtual memory problem, which is the responsibility of the OS.

It could also be him, if he had upgraded his ram anytime soon it could be a compatibly issue.

If so did he upgrade his RAM all at once? If not, make sure that he has 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.

He said he didn't upgrade any hardware or software.