• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Verifying DMI Pool Data ..........

TheCrusher

Junior Member
My PC was running fine today, then I got a couple of error messages in IE 5.0 (not all that unusual), but after I rebooted, the PC got stuck with the message in the title of this message. I let it sit for about 5 minutes, still nothing. I've since tried to reboot several times (more than 10) and nothing happens at all. I can get to the BIOS screen before getting to this hangup, but I have no idea about what this might mean.

Any suggestions?

Thanks
 
without more system details, can only suggest you go into bios & enable reset configuration, save the changes on exiting & reboot!
 
Make sure the PC is off and make sure everything is seated correctly, the ram, CPU, connectors, etc. . If that doens;t work, reset the bios to default setting again, save, reboot, and enter bios and set up your CPU settings. If that doesn't work, remove all your add in cards, excpet the video card. If that doesn't work, get the PC hardware down to just the video card, 1 stick of ram and CPU, remove and disconnet the HD's, cd-rs, and add in cards.

good luck-Armand
 
Hardware setup here is Epox 8KTA2L, Duron 750, 128 MB PC100 SDRAM (single stick, NEC chips), Diamond Viper V770 video, onboard sound, Linksys LNE100TX LAN card, separate Sony CD and Sony CD-RW, WD 30GB and Maxtor 20GB.

I've tried as suggested: reseating memory, CPU and cards (only video and LAN are currently installed). No success.

Removed all except video card, memory, CPU, hard drive, and 1 CD. No success.


Does the phrase (verifying DMI pool data) mean anything in particular? It seems to me this may signify a motherboard failure of some time, or perhaps a hard drive problem. Any comments?

Thanks for any help.
 
i had a similar problem when I removed my scsi-based burner and replaced it with an IDE-based burner. I got the exact same "veryifying DMI pool data" message at the beginning my boot-up, but for me it only stayed suspended at that step for 30 seconds, it would then boot win2k like normal. i fixed the problem by switching the drive boot order. It used to boot A, then C, then cd-rom -- then i switched it so the first boot device was the cd-rom and somehow it got rid of the problem. I get the "verifying DMI pool data" message, but it flashes by so quickly that I hardly notice it. it doesn't slow the boot sequence at all.

to this day, i have no idea why this fixed my problem, and I don't know what the original problem was. All i know is that the above solution worked. go figure.
 
Another try:
Go into BIOS, set drive type to none or not installed. Load the defaults, save and reboot with start up disk, shut computer off after memory is counted. Power on, go into BIOS, auto detect hard drive, make sure LBA is enabled, save and reboot normal......... hopefully this might help.
The DMI message is a hardware problem, hopefully the hard drive as you suspect. Probably nothgin wrong with drive.... Better yet would be to format the drive if you can.......
 
Just to update everyone who made suggestions:

I removed everything but the memory, CPU, video card and floppy. I was able to boot up to the floppy, getting by the hangup message. I added the CD rom back in, and a different hard drive, and have been able to reinstall Win98 on the hard drive, then successfully boot up the system with the hard drive.

I've left the memory, CPU, video card all the same, so I'm guessing the original problem was the hard drive which was removd. I've since installed it as the second drive on another PC, and I can access, read, and write to it just fine, so I'm not sure if that was ever really a problem or not.

In any event, I didn't lose any data, and everything seems to be working fine right now, though I don't have any real solid answer as to how it was fixed.

Thanks for the input.

 
Back
Top