Ok, probably in wrong SECTION, but when I turn on my comp normally it gets to the loading windows xp screen then a blue screen appears for about a sec and the comp restarts. I can open comp in safe mode, but what can I do now? I've done a system restore back like 5 days ago when it wasn't happening, but that didn't work!

What can I do?You COULD run multiple virus and spyware scans in safe mode to eliminate that as a cause.
http://www.pandasoftware.com/activescan/
Also AVG, Ewido, Msoft antispyware, Spybot S&D.Did virus scan using Windows AntiSpyware and TrendMicro, but that didn't fix the problem.

Could it be I have to slurp the comp? hope it doesn't come down to it...OK, computer clean or near enough.
Because you can start in safe mode but not in normal mode it sounds like something that's starting in normal mode is giving you a problem.
Run msconfig and disable all the things in startup and re-boot back to normal mode.
If you can then get back into normal mode start re-enabling the startup items one at a time and rebooting.
I'm not sure if xp has msconfig so you may have to download it.
1st go to start>run and type msconfig & click OK.That didn't help =/

I wish we could somehow freeze the monitor so I could read what the blue screen says in that half a second...

If I can't find anything in the next few hours I'm just gonna get my comp slurped...Hmmm...
Just wondering should I also make it so it doesn't load any SERVICES? Or do you DOUBT that it is a Microsoft Corporation thing?There are many services that can be disabled or set to manual to make your computer run better.
I will look for some xp suggestions (I run w2k)
You can download Hijackthis from
http://www.hijackthis.de/index.php?langselect=english
Bookmark it & use that site to analyse the log it makes.Ok... (No offense to anyone, but...) Let's stop fiddlin' around! We need to find out what the blue screen says... In safe mode, right-click on My Computer, and click on Properties... Click on teh Advanced tab... Under the Startup and Recovery section, click on the Settings button... When the next window pops-up, look for "Automatically Restart", and remove that check. Apply and save the changes. Now, I want you to get that blue screen and give us some detail as to what the error is about... Keep in touch...

[glb]Flame[/glb]Ok!

A Problem has been detected and Windows has been shut down to prevent damage to your computer.

NO_MORE_IRP_STACK_LOCATIONS

If this is the first time you've seen this error command restart your computer, blah, blah, blah...

Technical information:

*** STOP: 0x00000035 (0x81F5B00*, 0x00000000, 0x00000000, 0x00000000)

Beggining dump of PHYSICAL memory.
Physical memory dump complete.
Contact your administartor for more information regarding blah, blah, blah...Have you installed any new hardware/software before this happened? Also, you know how you select to go into safe mode? Well, in that list, select Last Known Good Configuration, and see if that works...

[glb]Flame[/glb]Last known config didn't work, tried before.

I installed Fallout 2 (game) 2 days ago, but I don't see how that would effect it. I unistalled it before and tried again, that didn't work. Maybe it did have something to do with it. It did freeze yesterday and I had to force shutdown.

My computer froze while I was playing Enemy Territory (game) yesterday and then I had to turn off comp by holding down buton. Turned it on today this happened.

Could that have been a problem?Possibly, but not likely... This one's a thinker... I'll have to think on it for some ideas... Anyone got some ideas to contribute? :-/

[glb]Flame[/glb]Thinking of getting it slurped today...please if someone can help! Will lose all my games T_TSlurped? That's a new one... What does it mean? Erased?

[glb]Flame[/glb]If you google "NO_MORE_IRP_STACK_LOCATIONS"
you will see that there are registry fixes for it but I don't think you should go there yet.
While Flame thinks, can you do the Hijackthis thing.
The more info we get the easier it is to sort out.
Don't slurp you may finish up in the same situation next week. LOL