|Keep the date and time settings in the bios current. XP and above corrects that automatically by default eventually, but until then, some programs in Windows won't work properly if they're wrong. |
Make sure you have no USB flash drives or USB connected external drives plugged in while booting. In some circumstances, with some bioses, the bios will try to boot from a USB device, and if it isn't bootable the bios may stall (freeze) , and the bios may then not try to boot anything else.
"verifying DMI pool data....... Boot from CD:"
Some bioses will display a message like that, including the Boot from CD part, every time you boot, if a CD drive is before all hard drives in the Boot Order settings or similar in the mboard's bios Setup.
- If a bootable optical disk IS detected, you will see a line "Press any key to boot fron CD." or similar, and that usually stays on the screen for 5 seconds - if you don't press a key, then the boot continues, and the bios tries to boot the next thing in the Boot Order or similar list. If you press the key within ~ 5 seconds, then the bios will try to boot the comupter fronm the optical disk.
- If a bootable optical disk is NOT detected, the boot continues within a second or so, if the next thing listed in the Boot Order or similar list is bootable.
If the next thing listed in the Boot Order or similar list is NOT detected as bootable, the bios will either hang at that point, with "verifying DMI pool data....... Boot from CD:: still on the screen, or you will get a message "Unbootable Volume" or "No operating System found" or similar - the "verifying DMI pool data....... Boot from CD:" line may or may not still be displayed.
- When the next thing in the Boot Order is NOT found to be bootable, therefore, you may notice the "verifying DMI pool data....... Boot from CD:" line that normally only appears briefly.
"if i press F8 on start up it goes into boot menu with the options of hard disk or cdrom if i select hard disc it offers ch2 m. :st3160212as or bootable add-in cards, if i do the first it just goes verifying DMI pool data, if i do bootable cards it says disk boot failure insert system disk and press enter which i don't have."
Is this a desktop computer or a laptop computer?
What brand name model is it ?
Do you have only one (physical) hard drive, or more than one ?
You probably don't have any "bootable add-in cards" so getting the "disk boot failure:" message would probably be normal for that situation.
"if i do the first it just goes verifying DMI pool data,"
" it offers ch2 m. :st3160212as"
It sounds like your bios is detecting at least one hard drive, but the boot is stalling, forever, when it trys to detect it.
If it was finding it not bootable, you would probably get the "disk boot failure:" message for that too.
Possible causes of the bios freezing / the boot stalling -
- a poor connection of the ram in it's slots. I'm assuming you have NOT just changed which ram you have installed.
See response 2 in this - try cleaning the contacts on the ram modules, and making sure the modules are properly seated:
For a laptop, or netbook, you must remove both its main battery and AC adapter before you do that.
For a brand name computer, see the Owner's or User's manual if you need to - how to remove or replace the ram is usually in that - it may already be in your installed programs. If you can't get into Windows, it may be on a disk that came with the computer, or you can go online and look at it or download it - it's in the downloads for your specific model.
For a generic desktop computer, see the mboard manual if you need to - how to remove or replace the ram is usually in that.
- If you have a desktop computer, something about your hard drive data cable connection is not right.
It is common to un-intentionally damage IDE data cables, especially while removing them - the 80 wire ones are more likely to be damaged. What usually happens is the cable is ripped at either edge and the wires there are either damaged or severed, often right at a connector or under it's cable clamp there, where it's hard to see - if a wire is severed but it's ends are touching, the connection is intermittent, rather than being reliable.
Another common thing is for the data cable to be separated from the connector contacts a bit after you have removed a cable - there should be no gap between the data cable and the connector - if there is press the cable against the connector to eliminate the gap.
80 wire data cables are also easily damaged at either edge if the cable is sharply creased at a fold in the cable.
Try another data cable if in doubt.
Check your SATA data cables. The connector on each end should "latch" into the socket on the drive and on the mboard, or on the drive controller card - it should not move when you merely brush your hand against it near the socket - if it does, mere vibration can cause a poor connection of it - use another SATA data cable that does "latch", or tape the connector in place.
(There is a slight projection or bump on one side of the outside of the connector that "latches" it into the socket - it's easily broken off or damaged)
The same thing applies for the SATA power connection.
"if i press F8 on start up it goes into boot menu..."
You have a brand name bios version that uses the same F8 key for that as for the Windows boot choices menu.
You can press Esc or some other key to exit that and immediately press F8 repeatedly, don't hold down the key, to get the Windows boot choices menu - e.g. Safe Mode, Enable VGA mode, etc.
Sometimes the hard drive will load Windows in Safe mode or one of the other modes but won't load Windows when you boot normally.
(That won't work if your hard drive is not detected as bootable.)
One of the choices is
Disable automatic restart....
When you know you have seen a glimpse of a blue screen message in Windows, choosing that will attempt to load Windows normally, and you may get a blue screen message that stays on the screen rather than the computer restarting when the error is encountered.
If you choose that and do see such a message...
quote what you see on it
STOP: 0x000000xx (we don't need the stuff in brackets beside it)
A problem file name may be at the end of the text - if so, quote that.
There may be a link to More info or similar - if you see that click on it - if it names a problem file, quote that.