I actually just joined this Forum so as to solve this problem myself. My computer was displaying a blue screen with IRQ_ is equal to or less than... but unfortunately my computer thinks its a great idea to reboot after giving me the error message within 2 seconds or so. But it would do this when I would load games or other processor intensive things. ALSO my data was becoming randomly corrupted for no real reason. I have a feeling that my ntosldr is corrupt but it won't even give me an error message, just keeps rebooting. If anyone has ever had a problem like this and knows a solution then shoot. (Btw it isn't my HDD because I have a second HDD installed with windows XP pro instead of x64 and both get to the kernel initialization screen for about a second and a half then reboot.)

Right click My Computer then click Properties

Advanced > Startup and Recovery > Settings

Under System Failure UN click Automatic Restart

This should give you the error next time.

Thats a realli good piece of info that I will definately take advantage of however it doesn't help me now since my computer won't boot at all.

Will it boot into Safe Mode?

Do you have a Retail XP CD or an OEM recovery CD?

If the latter who is the manufacturer of the computer?

I am the manufacturer of my computer lol. And I lost my x64 edition of windows (Still looking for it ><) And a cat urinated on my normal version of windows (I freakin hate room mates). So I can't load a recovery council. AND safe mood doesn't work either so I am guessing I have a drive error with a critical system or the ntosldr is corrupt. I don't know that a recovery cd will work anyways though since both OSes on different HDDs have the same problem.

Right so anyone else got any suggestions? Its currently going on in a infinite loop behind me and is about to piss me off to the point of bursting. I have removed all but critical devices (The only cords connected are power cord, keyboard/mouse, monitor.) I have shut down everything unboard. I tried to pull different portions of RAM out. I changed just about every setting in the bios that I understood and a few that i didn't I have been trying with both XP and XP x64. I am about to pull my hair out because there is absolutely no reason for this to do this. I am about to try an entirely different ram stick, (DDR333 >< ewww) and an ancient video card that I have (Gforce 4 MX440) And an old IDE HDD. if this doesn't get it to work I have no FREAKIN' clue what I can do. anyways if anyone had an error like this where the computer reaches the XP load screen (AKA NT kernel initializer)then reboots back to the post in a never ending loop please tell me what you did to fix it.

PS my system specs are as follows Athlon64 3200+ (Venice) 1gig of crucial ballistix ddr400, 160 and 40 GB SATA 1.5, Gig/s IDE CD/DVD combo drive, Asus socket 939 basic board, 420W offbrand PSU. ATI Radeon 9550 extended 256 MB GPU

I would suggest connecting only one hard drive and perform a Clean Install of which ever version of XP you desire.

If this fails then you probably have some faulty hardware somewhere but if it works then you can move on to other adventures.

Well I tried to load an old IDE HDD and the computer won't even finish posting. The Mobo is done in is my final conclusion. I subbed in a PSU and it did the same thing, Tried different RAM, and blah blah. The only thing left is the CPU or the Mobo, and the computer still posts. I am guessing its a prob with my SATA south bridge carry on. Thanks for your help though

Have you tried clearing the CMOS?

Is there an updated BIOS to load?

I have finished flashing the BIOS and got a Windows CD to get run recovery council or fresh install and it is giving me a stop error I can finally read the error is. 0x00000024(0x001902FE, etc) NTFS.sys is messed up. I can not run a new install or recovery council at all. Is it time for me to say the SATA via controller is shot? That is the only thing I can think of at all, I searched the Microsoft KB and they didn't show that error ever ocurring on XP -.- Anyways thanks for your help.