verifying dmi data pool shows up every time i restart my pc. i dont think this is normal. my pc seems to work fine, i was just wondering if this might be a sign that ssomething was wrong. thanks so much for your time.

[Reply or follow-up to this message]

J wrote:
|verifying dmi data pool shows up every time i restart my pc.
|i dont think this is normal.
|
You are incorrect.

|my pc seems to work fine,
|
It is fine.
If it was screwed up, you would hear something other than the single cheery beep
or you would see a message that states that an ERROR has occured
or you would see or hear nothing.

|i was just wondering if this might be a sign that [something] was wrong.
|
You worry too much.  Go get yourself a beverage while your computer boots. 
cache of http://unixhelp.ed.ac.uk/glossary/gb.html
++computer-pulled-itself-up-by-its-bootstraps

[Reply or follow-up to this message]

If the machine didn't use to do this and just started, then it isn't normal.  If 
it is an older machine the two most common causes are a weak CMOS battery not holding 
the config settings in the BIOS, causing the BIOS to rediscover the hardware and 
write the pool or,

You have a piece of hardware failing.  We usually suspect hard drives, CD ROM devices, 
floppies etc first, but any other piece of hardware, including devices on the motherboard 
can trigger this (except the PSU unless it's spiking the board, scrambling the CMOS 
settings).

A weak battery may not hold the correct time as noticed when you start the machine 
but that isn't always a good indicator.

I have seen a few motherboards that will always have this announcement when starting 
but it is rare in my experience.  (and that's on thousands of machines over 20 years)







On Friday, January 25, 2008 at 5:25 pm, J wrote:

>verifying dmi data pool shows up every time i restart my pc. i dont think this is 

>normal. my pc seems to work fine, i was just wondering if this might be a sign that 

>ssomething was wrong. thanks so much for your time. 

[Reply or follow-up to this message]

if not sure, just reformat and reinstall the OS.


On Friday, January 25, 2008 at 5:25 pm, J wrote:
>verifying dmi data pool shows up every time i restart my pc. i dont think this is
>normal. my pc seems to work fine, i was just wondering if this might be a sign that
>ssomething was wrong. thanks so much for your time.

[Reply or follow-up to this message]

(was: verifying dmi data pool shows up every time i restart my pc)

john long wrote:
|if not sure, just reformat and reinstall the OS.

You have no idea what you are talking about.
This is happening below the level of the OS--before that ever starts to load.

Yours is the kind of nonsense explanation that comes up
since the word "boot" has had its meaning corrupted
such that people now think it includes "loading the operating system".

[Reply or follow-up to this message]

Good advice. It's good housekeeping too, because it cleans up all sorts of problems. As long as you've got a proper backup regime in place, it's usually the best option in the long run.


On Tuesday, January 29, 2008 at 12:02 am, john long wrote:
>
>if not sure, just reformat and reinstall the OS.
>
>
>

[Reply or follow-up to this message]

(was: verifying dmi data pool shows up every time i restart my pc)

Alan Masterman wrote:
|Good advice.

Nope.  Both of you are blowing smoke.
This is happening during POST.
It has NOTHING to do with the operating system.
It would still happen if the operating system was wiped off the HDD.
It would happen if there was no bootable diskette in the floppy drive.

Neither of you knows enough about computers to be advising on this.

C K says it indicates an impending failure
but I have seen computers that did this their entire (long) lives.

[Reply or follow-up to this message]

http://support.microsoft.com/kb/287553








On Tuesday, January 29, 2008 at 12:02 am, john long wrote:

>

>if not sure, just reformat and reinstall the OS.

>

>

> 

[Reply or follow-up to this message]

No offence to you guys, but I think gewg is right on this one. My old PC used to do that every time it was booted up and it had a series of different OSs on it. My computer now has also had a series of OSs and has never done it (as far as I'm aware) This is definitely a BIOS issue, not OS.

[Reply or follow-up to this message]

Some years ago, one of the "major" motherboard manufacturers (who also supplies OEM's), 
 quietly recalled and replaced a series of bad motherboards that were having the 
same issue.  (there was more than one actually)  Those of us who knew it wasn't normal 
had our, and our customers boards replaced.  (bad chips)  For those who didn't know 
any better, they just went right on using them.  Wasn't critical, just caused the 
BIOS to run the discovery process everytime it booted.

It isn't actually normal, but the average consumer wouldn't know if the machine still 
boots and seems to run normally.  There was also some sloppy designs back then that 
didn't help.  If you see it on today's boards, you know you do have a problem somewhere 
in the hardware.  I've had to send some boards back for replacement when it was evident 
that the error wasn't caused by any external hardware.  Just my experience.. 

Contrary to popular belief, all motherboards are NOT tested before leaving the factory 
and individual parts are only spot/batch tested.







On Friday, February 1, 2008 at 12:25 pm, Aidan Jenkins wrote:

>No offence to you guys, but I think gewg is right on this one. My old PC used to 

>do that every time it was booted up and it had a series of different OSs on it. 
My 

>computer now has also had a series of OSs and has never done it (as far as I'm aware) 

>This is definitely a BIOS issue, not OS. 

[Reply or follow-up to this message]

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum