Originally posted by auiotour:
most of the time its cause of a registry issue, the other times it could be because you swapped a new motherboard or processor, xp, is very strict about pirating xp on my then one computer. and it causes errors to keep you from pirating. Now, this error is usually not seen to often, try to start back up in the last known working configuration. It should boot back up. then restart and see if it works.



::chuckles:: XP does not purposely cause errors when you switch hardware, despite what every Linux user in the world might want you to believe. I've installed an entirely new motherboard and processor into my current installation of Windows when one of my old ram slots went bad and I was looking to replace the m/b with something decent, and it caused me little to no trouble.

Whenever you get an error like this during Shutdown, 90% of the time it has something to do with legacy drivers. It times past when Windows was still running on top of DOS, whenever it would shut down it would attempt to switch from 32 bit to 16 bit drivers, and often would hang, stall, or error out. With Windows XP being built on top of NT technology, it doesn't necessarily do that, but getting an error like that, citing an IRQ problem, generally has something to do with the failure of a driver for a specific piece of hardware to respond to a memory garbage collector--or at least that's been my experience.

Windows makes automatic backups of its system state each and every time you boot. You may attempt to perform a "System Restore" dating back to a couple days before you started having your shutdown problems. If that doesn't fix it, get a copy of your Windows cd, boot to it on bootup, and then select the "Repair Installation" option.

Backup any vital data before performing the latter option.

Cheers,
Tim

'01 GTP: 3.3" pulley, Headers, 3" Exhaust, Straight Pipe, Intense Air to Water Intercooler.Pictures Old Ride: 95 Mystique LS V6 ATX: Pictures