Verifying DMI Pool Data......

[IB]

My computer hangs at start up...showing the message "Verifying.......". It´s very annoying. I must restart the computer and after 1-2 minutes I can see the desktop again.
Anyone knowing how to fix this permanently without partitioning and reformating the drive?

[IB]

...so I´m the only one with this problem...?

[Megaduce]

Be moore specific what OS are running or post a copy of the event log so you can get some help [img]smile.gif[/img]

Knowledge----is%%%Power

[Megaduce]

[b:cf2bbccebf]The information in this article applies to:

- Microsoft Windows Millennium Edition
- Microsoft Windows 98 Second Edition
- Microsoft Windows 98
- Microsoft Windows 95
-------------------------------------------------------------------------------

SYMPTOMS
========

When the computer is running the power-on self test (POST), it may stop
responding (hang), and a "Verifying DMI pool data" error message may be
displayed.

CAUSE
=====

This issue is caused by the hardware.

RESOLUTION
==========

To resolve this issue, please contact your computer manufacturer.

MORE INFORMATION
================

Desktop Management Interface (DMI) is a method for managing computers in an
organization. The main component, Management Information Format Database (MIFD),
is a database that contains all the information about the local computer and its
components.[/b:cf2bbccebf]

[Crowdirt]

Hi IB, this sounds like a MOBO hardware problem to me. I have had similar "hangs" on newer machines and the solution turned out to be "Timing" problems with cards added to the machine (Modem etc.). Some older add in cards are just not up to the faster motherboard speeds that are out there.

[IB]

Thanx guys, Ok more specific..
I´m running WinME on a Epox-MVP3-G5 board, powered by K6-2@550, IBM 22GXP 13,5GB, 3x128 RAM....
This config have worked well during the last 8 month without any severe problems. It started last week.

From a "cold" boot everything looks OK until...
Verifying DMI pool data....then it halts. If I reboot, scandisk find errors in bootrecord...repair...yes....and then I can see the desktop again.
If I turn off the computer and restart within 3-5 minutes, there is no problem but if I keep it OFF during the night, in the morning it freezes again, the fault is back...
funny..isn´t it

I welcome all GOOD suggestions fixing this mysterious lockup
Thanx

[Bads]

Does Win ME run with 3 sticks of 128 megs ?

I'm not shure,

Try to remove one stick and reboot

[Megaduce]

Hey dude here is the thery that I get from the info below.[b:4398e0a300]From a "cold" boot everything looks OK until...
Verifying DMI pool data....then it halts. If I reboot, scandisk find errors in bootrecord...repair...yes....and then I can see the desktop again.[/b:4398e0a300], what is happening is that when you do a cold boot the Bios starts to probe the system for Hardware detecting this where the DMI come in, The Dmi provides direct access and eliminate the need for error prone operations like probeing the system for Hardware detecting. So that is telling me one or two things one of your expansion cards is bad or you may need to update your Bios or get a new motherboard. the expansion cards can cause the system to hang or not boot it seems that one of the cards is intermiting, meaning it only works now and then, and work when the PC does a warm boot thus causing the Pc not to hang after a warm boot lets runa test and find out really what is going on first before you go updateing your bios let start with the card's remove one the cards and restart the PC cold boot please so give some time to cool down a little. see the result with each cards after removeing one card if you get the same result as before just remove another if you remove all the cards and the prob is still there then get a Bios update from your motherboard vendor and apply it, OH yeah if you have a integrated Video card that could be the prob also and make sure wheen you're upadeting the bios [b:4398e0a300]NOT TO POWER CYCLE THE PC[/b:4398e0a300] hat is if ya have good luck dude

[Crowdirt]

Hmmm....sounds like a "Thermal" problem to me. When the machine is Warm all is ok. Fails when the MOBO chips are cold. Over time this kind of thing only gets worse. I suspect the MOBO is starting to show signs of failure. This could be related to the "Effects" of Overclocking or other Heat related damage.

[Megaduce]

Yeah Crow heat is definitely a factor there also the memory and the any expansion cards could be @ fault also