Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
my computer will not boot past either dmi pool data or verifing dmi pool data. Please tell me what i should do because i cant figure it out please!!!!

Go into the BIOS and copy down all important settings. Then install BIOS defaults.
A similar thing is when a SCSI controller bios does not run, but if booting stops rignt at Verifying DMI pool data the defaults are your best bet.

This could be a CPU prob. The only time I get the same symptoms is when I've tried to overclock the CPU.
Dip into the bios and do the "restore defaults". Also, if you have the option, reset the system bus speed to the slowest available. (Not all bios's allow this however.)
If it still won't boot, looks like your motherboad's died.

I had the same problem with WinXP. It worked again after I formated the hard drive and reinstal the OS from scratch (scorched earth). Executing the XP function, system restore, that you get by tapping on the F10 key during boot up didn't solve the problem -- only completely new burn on the HD would work.
Here we are a month and a half later and the same thing just happened!!! It is a dual CPU system, though, so I guess I' just asking for problems.

I found this:
The solution is fairly simple. If you've never had this problem before and think "I can ignore this message", write it down anyway and save yourself the trouble.
Boot to DOS using a floppy disk. For whatever reason, I couldn't boot using a normal bootable disk, it HAD to be a Win98 setup disk. I can't explain why that is. But I can tell you this much. If you get this error message, just get yourself into DOS and type this:
fdisk /mbr
this will effectively "format" the master boot record, setting it back to its original state. The reason "Verifying DMI Pool Data" is on the screen is because it's the last command that your PC can actually process before it attempts to boot your hard drive. However, if the boot sector of your hard drive is screwed, it just stops...
and that message is the only hint you're left with.NOTE: THE INFORMATION ON THE MICROSOFT WEB SITE IS *MISLEADING AND UNHELPFUL*
It is NOT an unfixable problem with your hardware, and you do NOT need to contact your system vendor! It's a simple problem with a simple solution that Microsoft don't feel the need to tell anyone about!
Anyway, I really hope that helps some of you avoid all the problems I've been through with this thing!

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |