Can't Load Vista or anything :S

Hi everyone, i'm new here and hoping someone would be able to help. I have trawled the internet and not managed to find a solution to my problem, and i don't want to aimlessly start buying spares if i don't need them.

I was surfing the net with my girlfriend the other night... playing bingo to be precise, (we are soo rock n roll!) and my computer just turned off.. not instantly like a powercut, but alot quicker than normal shutdown.
I turned it back on and was given the options to start in safe mode, safemode with command prompt etc. Well, every option I chose lead to windows starting to load but then a very quick blue screen "flash" ....then it would restart from the beginning again.
I then dug out my vista cd, and told my bios to boot from cd, I would then get a message saying windows is loading files and as soon as the bar flled up the blue screen came back, but this time it stays on the screen.
So just to recap, i can't start windows in safe mode, command prompt, or normally, and i can't use my recovery cd.

The blue screen i get is: PAGE_FAULT_IN_NONPAGED_AREA
*** STOP: 0X00000050 (0X86300000, 0X00000000, 0X88883843, 0X00000000)

I really hope someone can make sense of this, i have tried removing each stick of ram and that didn't work, i was told it could be the power suppy, harddrive or motherboard.

I am using vista home premium 32bit, core 2 duo e6850, asus p5n32-e sli plus mobo, 2 gb corsair xms2 ddr2 ram, Nvidia geforce 8800 gt ultra. I am unsure of my hard drive.

Thanks in advance to anyone that replys. P.S sorry if i have left anything out.

Hello Locki,
Here are the results of your BSOD, can you upload your dump file with your next post.
Go to C > Windows > Minidump, zip up the files, (you may need to save them to your desktop first).
Hopefully the dump files will give us a bit more information.

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.

You could try removing this and changing that, but the dump files should point us in the right direction.

how can i get the c:\ dirctory up? I can't do anythng at the moment without it endlessley restarting. Anything i choose, whether it's start in safe mode, normally, safemode with command prompt or booting up from the cd results in a blue screen and restart

Can you go to the Bios, set first boot device to DVD/CD and try a startup repair ?.

http://www.vistax64.com/tutorials/91467-startup-repair.html

If not, then try with just one stick of ram installed, if it blue screens, try another stick of ram.
Make sure all USB devices are unplugged, if OC'ed, reset to default.
Post your results, and good luck.

Done all of that i'm afraid. I have even just this minute burnt an image of a downloaed vista recovery cd and tried that instead of my genuine vista cd and that also came up with the above error. I have done the whole swapping of ram business, tried recovering with both genuine vista cd and downloaded recovery cd, nothing works... looks like i will have to start replacing bits one by one. Probably start with th mobo i guess....

Do you or a friend have another HDD you can try, im thinking NTFS corruption, and its easier and cheaper than a new MB.

Thanks for all the replys. Had a word with a friend, who will hopefully bring his pc round this evening so I can pull it apart and test a few bits. I'll post back if I find anything.

Hey everyone. Pc is now back up and running as of today! I tried using my friends computer but nothing was compatible so i sent it to a friend of a friend who knows a bit or two about pc's and had it fixed within a couple of hours!
I was told it was first the memory...nope all ok, then the mobo....nope, all ok, then the hard drive...nope, all ok, turns out there was a fault with vista! a few mods to some files ( i don't know what, but i was asked if the computer had been subjected to powercuts, which it hadn't) and it was back up and running. He was only able to get into it by running my hard drive as a slave and fitting another drive as a master. Anyway my point is the error codes you get i.e 0x00000050 does not alway mean a hardware failure like memory, this was a sofware fault. Anyway thanks for all the help and advice i recieved, nice to know people out there care