XP Pro will not boot past " Verifying DMI Pool Data"

Possible causes: Hardware incompatibility, virus attack, electric circuitry damage/defect, corruption of data, improper BIOS settings, over-clocking damage.

Possible solutions:

Check whether all the cables and expansion cards make proper contact.
Try setting the ?Reset Configuration Data? (also known as ?Force Update ESCD?) BIOS option in the BIOS ?PNP/PCI configuration? to ?Enabled?, save and exit the BIOS. This option is a single boot setting and after being used after the reboot the option is set to ?Disabled? again.
Check your mainboard manual concerning information about the ?Clear CMOS jumper? and then clear the CMOS. Please note that with ATX power supplies based systems the power cord must be disconnected or the mechanical switch of the PSU (Power Supply Unit) must be set to ?Off? or ?0? before the Clear CMOS jumper is used.
Disconnect the IDE cables, enter the BIOS and set the boot sequence to start with the floppy drive. Try to boot from a bootable floppy with the proper BIOS update files for your BIOS and update the BIOS. After the update is finished clear the CMOS again and after booting set the ?Reset Configuration Data? (also known as ?Force Update ESCD?) BIOS option in the BIOS ?PNP/PCI configuration? to ?Enabled?.
If you can boot from floppy but the BIOS update does not help then if the problem is with a corrupt MBR of the HDD you can try to use the partitioning program that belongs to the operating system version you use on that HDD to fix the MBR. With Windows that would be the FDISK program and you would need to use a bootable floppy with that program and the command ?fdisk /mbr?. Or even better go to the website of the manufacturer of your HDD and download their special HDD diagnostic software tool which can be usually found on their websites. If you have the means to do so you can test the HDD in another system.

BAD PROCESSOR

You problem lies within the mainboard. When a computer will not pass this section of the boot process it points to damaged circuitry between the processor and the RAM, normally because of either extreme heat or a sharp blow to the case. This is a saftey feature to prevent damage to the CPU and other hardware. Unfortunatly you will need a new mainboard but the rest of your hardware will not be damaged. If you E-Mail your specs I can recommend a good mainbaord to replace the one you have. Are you sure your warranty is out?

Let me take a crack at it. Here's what I do. You have to have patience and be methodical.
First STRIP everything not needed, leaving only HD memory, and Vid card (unless its built in then use that instead) and then boot up. If It A) boots up all sudden then you know something is up with a piece of hardware, and your HD is in the CLEAR. Now, lets go with B) HD wont boot, now what you need to do is try another HD, (if you have one, I always have one with plain XP on it to test hardware...of course you may not have this luxury..) If it boots from the test drive but not the one in question, you know its the HD. Confusing yes? of course what you expect a walk in the park? Ok so now we have a variable scenerio(s) for possible solutions.

A) Assuming HD is good start installing components one by one, to isolate the problem, if for instance you install say a sound card and then it freaks out, it could be say the card,or maybe on board audio settings are preventing the DMI from being correctly addressed, etc. etc.
BAsically what im saying is process of elimination, test replace, reboot. Scientific method of sorts.

B) Bad HD, ok well HD is toast, if under warranty contact vendor, or if its old, then shell out the clams to get it.

C) This is something you could do, CLEAR the CMOS leave battery out for 10 mins and replace, and before you do unplug the pc and hit power button to rid capacitors of any charge left within. REBOOT. if this doesnt work, then

Just recheck all the connectors and RAM in its slots in the CPU this will work perfectly

Thanks everone for your help. Turns out was a bad HD. Why it happened when it did is a still a question as all I did was move the machine from one room to another.