System won't boot -- stuck at "Verifying DMI Pool Data"
Hello folks!
I'm new here, so please bear with me as I learn the process. If you need further details, please do not hesitate to ask.
Our company has recently purchased parts for four new systems. I assembled them yesterday, and to avoid having to re-install all programs, I simply used a drive cloning utility to clone the old HD to a new one, and installed the new disk in the freshly assembled box.
At first, the hard disk is read and XP tries to run, but before showing a BSOD or the standard boot screen with the rotating three bars, the system reboots. If I allow the reboot to proceed, I am prompted for starting Windows normally, Last Known Good Config, Safe Mode, &c. I tried booting in safe mode with the same result as before.
I then tried a repair install from the setup disk. The repair install completes flawlessly (apparently), the 15 seconds reboot timer expires, and the system reboots.
At this point, when the BIOS hits "Verifying DMI Pool Data......................
A forced shutdown/reboot at the above point serves no purpose.
Anybody have any ideas? They would certainly be most appreciated.
Please let me know what additional info, if any, I might provide.
Many thanks!
I'm new here, so please bear with me as I learn the process. If you need further details, please do not hesitate to ask.
Our company has recently purchased parts for four new systems. I assembled them yesterday, and to avoid having to re-install all programs, I simply used a drive cloning utility to clone the old HD to a new one, and installed the new disk in the freshly assembled box.
At first, the hard disk is read and XP tries to run, but before showing a BSOD or the standard boot screen with the rotating three bars, the system reboots. If I allow the reboot to proceed, I am prompted for starting Windows normally, Last Known Good Config, Safe Mode, &c. I tried booting in safe mode with the same result as before.
I then tried a repair install from the setup disk. The repair install completes flawlessly (apparently), the 15 seconds reboot timer expires, and the system reboots.
At this point, when the BIOS hits "Verifying DMI Pool Data......................
A forced shutdown/reboot at the above point serves no purpose.
Anybody have any ideas? They would certainly be most appreciated.
Please let me know what additional info, if any, I might provide.
Many thanks!
ASKER
Thanks. To respond to several of the items, most of which I had already seen and tried already, I tried unplugging the optical drive and booting the HD by itself---same result.
I also tried booting the setup CD into the Recovery Console and executing "fixmbr" and "chkdsk /r" commands, also with the same result.
Admittedly, I have not yet tried flashing an updated BIOS. Will try that when the morning comes. In the meanwhile, all further constructive input is both greatly needed and appreciated.
I also tried booting the setup CD into the Recovery Console and executing "fixmbr" and "chkdsk /r" commands, also with the same result.
Admittedly, I have not yet tried flashing an updated BIOS. Will try that when the morning comes. In the meanwhile, all further constructive input is both greatly needed and appreciated.
ASKER
An additional possible solution I tried was resetting the BIOS with the jumper. Again--same result.
If you still have the HDD you cloned from, then try a wipe and reload. Maybe there is another issue with the computer. Also are you having issues with all the new builds or just one?
ASKER
Hey cfcindustries,
What do you mean by "wipe and reload"? Yes, I still have the source HDD. I have tried booting into GParted and deleting all partitions, applying, and rebooting, and then trying to re-clone the drive. Unfortunately, the same situation seems to happen with the two cloners I've tried so far, which are GParted and HDClone.
The issue seems to occur with all the new builds that have been cloned from this particular source disk. I know, I initially thought hardware too, and I appreciate your thoroughness.
I plan to try a source disk from another system tomorrow.
I have presumed due to the fact that initially the system performs as expected when moving an HD from one mobo/proc to another (ie., requires a repair install), that a fresh OS install would be sufficient. However, we're too sorry as of late to implement a Domain/Active Directory network structure, and so such a reconfiguration would be quite complex.
However, I will go that route as an absolute last resort, but I was hoping to finger the culprit before embarking in such bleak territory.
What do you mean by "wipe and reload"? Yes, I still have the source HDD. I have tried booting into GParted and deleting all partitions, applying, and rebooting, and then trying to re-clone the drive. Unfortunately, the same situation seems to happen with the two cloners I've tried so far, which are GParted and HDClone.
The issue seems to occur with all the new builds that have been cloned from this particular source disk. I know, I initially thought hardware too, and I appreciate your thoroughness.
I plan to try a source disk from another system tomorrow.
I have presumed due to the fact that initially the system performs as expected when moving an HD from one mobo/proc to another (ie., requires a repair install), that a fresh OS install would be sufficient. However, we're too sorry as of late to implement a Domain/Active Directory network structure, and so such a reconfiguration would be quite complex.
However, I will go that route as an absolute last resort, but I was hoping to finger the culprit before embarking in such bleak territory.
By wipe and reload I mean, put a fresh copy of the operating system on the HDD, not a clone. This way you could be 100% sure the problem isn't the new build. Also have you tried booting into safe mode right after the repair. Sometimes letting the drivers load in safe mode is the only way to get the computer to boot correctly
You could always run the second(older) drive as a slave and install a fresh copy of your OS on the new drive. It would be easier and solve your problem faster if you needed the files as asap.
ASKER
cfcindistries: I will try booting in safe mode after a fresh clone/repair first thing tomorrow. I also will try a more powerful power supply, just in case. Will post results as soon as I know them.
raymorda: Thanks for the idea, and I will try that one as a last resort.
Thanks for the ideas, and feel free to keep them coming...they are greatly needed!
500 pts. to the winner(s)!!!
raymorda: Thanks for the idea, and I will try that one as a last resort.
Thanks for the ideas, and feel free to keep them coming...they are greatly needed!
500 pts. to the winner(s)!!!
ASKER
Also as another thought...I still have the original build, and because the source volume is still in tact, it is still bootable. Just taking a stab here as I've never tried anything like it before. The current OS on the source is Win XP SP 2. So long as that was the OS on the new drive, would it be extraordinarily disastrous to export the registry entries for the various programs (ie. Quicken 2008), import them into the new instance of XP on the target volume, and then simply drag+drop the program files in place? Just a wild stab, and apologies for the naivity...just a little panicked is all. :-)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks nobus! I will try those recommendations as well before going the last resort route. Many thanks.
ASKER
Thanks much, Nobus! You win! http://www.michaelstevenstech.com/moving_xp.html did the trick.
you're very welcome !
ASKER
For the record and future reference, here is what I changed.
Prior to my successful attempt yesterday, the source machine was running Win XP SP 2. Yesterday, I obtained the Windows XP w/ SP 3 Open Volume Licensing install media. I also obtained the disk for installing SP 3 by itself.
1) Clone source computer hard disk.
2) Place new HDD in source computer, setting original HDD aside for recovery later if necessary.
3) Upgrade source to SP 3.
4) Insert Win XP w/ SP 3 install media.
5) On autorun, click to install XP, then choose the upgrade option.
6) When the source machine reboots, turn it off before it accesses the HDD.
7) Remove the new HDD from source and install in target computer.
8) Upgrade BIOS on target computer to latest version, loading optimised defaults.
9) Insert Win XP w/ SP 3 install media in target computer.
10) Boot target machine and successfully complete Win XP repair install, rendering system operable.
So there were basically two changes that resolved the issue.
1) I upgraded to SP 3 and made sure I had a Win XP w/ SP 3 install disk, to keep OS versions identical.
2) I started the repair install on the source machine, then finished it on the target machine, as recommended by http://www.michaelstevenstech.com/moving_xp.html.
Prior to my successful attempt yesterday, the source machine was running Win XP SP 2. Yesterday, I obtained the Windows XP w/ SP 3 Open Volume Licensing install media. I also obtained the disk for installing SP 3 by itself.
1) Clone source computer hard disk.
2) Place new HDD in source computer, setting original HDD aside for recovery later if necessary.
3) Upgrade source to SP 3.
4) Insert Win XP w/ SP 3 install media.
5) On autorun, click to install XP, then choose the upgrade option.
6) When the source machine reboots, turn it off before it accesses the HDD.
7) Remove the new HDD from source and install in target computer.
8) Upgrade BIOS on target computer to latest version, loading optimised defaults.
9) Insert Win XP w/ SP 3 install media in target computer.
10) Boot target machine and successfully complete Win XP repair install, rendering system operable.
So there were basically two changes that resolved the issue.
1) I upgraded to SP 3 and made sure I had a Win XP w/ SP 3 install disk, to keep OS versions identical.
2) I started the repair install on the source machine, then finished it on the target machine, as recommended by http://www.michaelstevenstech.com/moving_xp.html.
http://www.google.com/search?sourceid=navclient&ie=UTF-8&rls=GGLG,GGLG:2006-38,GGLG:en&q=System+won%27t+boot+%2d%2d+stuck+at+%22Verifying+DMI+Pool+Data%22