Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Hello.
Well, where do i start. A couple of days ago my PC was full of c***, so i decided to reboot the PC. I put the CD in, and it got to 10% when an error came up, it said 'Critical Error......Read Fault'. So then i took out the CD and then restarted the comp. It loaded up normally but it came to the screen where it said 'Verifying DMI Pool Data' and it just stays there now, it wont load up. So i rang PC Service Call, and the pseron said that the DMI Chip in the motherboard it broken or something.(i know that is probably bull****) (If you think it is something else that is the problem then please say). My PC Specs are as follows:
Advent (Advent 8737)
Pentium 3
128mb Ram
20GB
600MhzBTW, i found out that i can solve this problem by going into the BIOS set-up, by pressing DEL when you on the PC, so i tried this by theres a password set to it and can't get in.

the verifying dmi pool data is a real nasty one, that I hardly ever managed to solve...
if you can boot with a windows 98 startup floppy disk, try to run scandisk
the command is:
scandisk c: /autofix /nosave
/nosummary /surfacethis will take quit a long time, let it do its work, even if it takes several hours
be sure to keep the hard disk that is in your computer when the problem first occurred, for it is most certain that very hard disk that causes the trouble

I don't want to frighten you, but somehow this problem looks like what makes Windows XP so user unfriendly.
I mean this: when you take a hard disk out of one Windows 98 computer and put it in another computer, the computer starts Windows 98, detects that the motherpoard with all its components and add on cards have changed.
the difference between XP and Windows 98 is, that Windows 98 will smoothly detect all of the new hardware and will install it. A perfect system.
Not so XP: XP won't even start, it just stops with a blue screen.This built in 'attitude' of XP looks like the built in 'attitude' of most motherboards when the "Verifying DMI Pool Data" message appears. The system seems to keep searching for specific data, that only seems to exist on the hard disk that it used to detect at startup.
Though I must says, that ony one time I managed to get the computer running, but that was when I put in an old hard disk. The DMI message appeared. So I put back the original hard disk, and then the message did not appear anymore.
There are lots of sites that have suggestions to overcome the problem, but they never helped me solve it.
The only thing I can think of (and that I have not yet tried) is to put the hard disk in another computer (as a slave) and let Partition Magic check the drive and fix errors. Partition Magic is a very powerful program.

I've already tried doing the full surface scan, but no errors come up, i haven't tried the passwords for CMOS setup, and if one of them were to work, what do i do next?

"I put the CD in, and it got to 10% when an error came up, it said 'Critical Error......Read Fault'. So then i took out the CD and then restarted the comp."
Is that the Win98 CD and during the reinstall is when it stopped at 10%?
If so then try cleaning the CD going from the center to the edges. You can use a mild dishwashing liquid to clean it. Make sure it is thoroughly dry before trying to use it again.
Bryan

I only gave the password link 'cause you mentioned it
among the hints for a solution, some people advise changing settings in the bios
they never helped me, but maybe they do to you
here they are:

<<use advice at ur own risk>>
if you find the password for your bios, enter and check in the second option for an option called: "Virus Warning". if you find it, make sure its disabled. this sometimes prevents operating systems from installing.
if you dont have the option, then this is not the problem
good luck

There should be a 'clear cmos' and/or a 'clear password' jumper on your motherboard. Check the manual or the board itself. Enable the jumper, turn the computer on for a few seconds, turn it off, replace the jumper in the 'normal' postition, then reboot and hit whatever key gets you into cmos/bios setup.
If it's hanging at the 'verifying DMI pool data' how did you run scandisk?

Here are a few things to try, because this error can come from a variety of problems, must fixable on your end.
Determine if the OS CD you used to reload was actually the first operating system installed onto that Hard Drive, if was use a boot disk of that operating system and boot up with that.
When you get a A:> prompt type "sys c:" san quotes
if that doesn't help try at prompt a:>fdisk /mbr
Now if that doesn't work you'll need to get into the Bios and see if the settings for the drive parameters have changed. If you can't get in b/c of PW try filling the password box with 1's, surprisingly this works on 80% of systems. Crazy but true.
There also may be a jumper on the motherboard itself that can be set to clear the CMOS if not, removing the battery completely from the motherboard and leaving it out for a good while may do the trick. This will reset ALL settings but the one that you will be concerned with is that the HD is set to auto detect.Try installing your OS again. If you still get an error, then it may be that the OS on the HD was not the OS that was originally installed on the drive. In this case determining what that OS was can be tedious and bootdisks of previous OS will be neccessary.
Also some overlay software and HD installation software can cause this error if the OS install verision you are using is not the same as the version that was used to setup the HD.
In most cases this error comes from the corruption of the microcode on the PCB(controller board on the drive itself) to the continued corruption of the microcode on the "service area" of the HD. This is caused by things mostly related to: 1. Bad CMOS data, (which we've discussed) 2. Virus Infection, 3. Failing HD
I'm betting on the wrong OS senario and that you bought this system used or this is the very first time you have reinstalled this OS on that drive.
I hope some of this helps

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

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