Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 552
  • Last Modified:

Computer not getting to verifying dmi pool data....

Very strange thing. Had 3 computers come in the shop within the last 4 days, all with the exact same problem. All different makes of computers, all different HD's and some SATA and some IDE. All of the computers do not post "verifying dmi pool data" or where that would actually come up after the normal post screens. Can boot from CD fine. Tried WINXP PRO repair option from install disc. After repair 1st stage completes, then on reboot back to same stop issue, before verifying dmi pool data can even appear.Tried chkdsk /r from Recovery Console from Install Disc. Tried bootcfg /rebuild. Tried fixboot. Nothing has worked. All 3 HD's can be seen in another computer as slave and files accessed easily. This seems to be more than coincidental for type of issue I have never seen before, especially in short time window. Been in the game for 20yrs.
0
ZionTech1
Asked:
ZionTech1
  • 9
  • 3
  • 3
  • +2
1 Solution
 
Dhiraj MuthaLevel DCommented:
Have you tried with a different Windows XP CD?
0
 
ZionTech1PresidentAuthor Commented:
All different cds, but same version. Oem
0
 
Dhiraj MuthaLevel DCommented:
Try doing an Windows Update on these systems which are effected.
Open IE > Tools > Windows Update
0
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
ZionTech1PresidentAuthor Commented:
I don't think you are understanding the problem. The systems will not boot.
0
 
ShareefHuddleCommented:
Possibley update the bios version
0
 
nobusCommented:
try a kind of system restore like this  : http://support.microsoft.com/kb/307545
----------------------------------------------------------------------------------------------
An easier way is to boot from a Bart PE CD (or UBCD4Win CD) and use the file manager for manipulating files. Here  the procedure :
1. rename c:\windows\system32\config\SYSTEM to c:\windows\system32\config\SYSTEM.bak
2. Navigate to the System Volume Information folder.
it contains some restore {GUID} folders such as "_restore{87BD3667-3246-476B-923F-F86E30B3E7F8}".
The restore points are in  folders starting with "RPx under this folder.
3. In such a folder, locate a Snapshot subfolder. This is an example of a folder path to the Snapshot folder:  C:\System Volume Information\_restore{D86480E3-73EF-47BC-A0EB-A81BE6EE3ED8}\RP1\Snapshot
4. From the Snapshot folder, copy the following file to the c:\windows\system32\config folder
 _REGISTRY_MACHINE_SYSTEM
5. Rename _REGISTRY_MACHINE_SYSTEM to SYSTEM
6. Exit Bart PE, reboot and test

Use a fairly recent restore point from at least a day or two prior to problem occurring .

** you can add the other hives also with this procedure

http://www.nu2.nu/pebuilder/       BARTPE
http://www.ubcd4win.com/            UBCD4WIN
0
 
ZionTech1PresidentAuthor Commented:
Didn't work, same issue. This is very strange though. 3 systems. Exact same problem. It's like there is something wrong with the firmware on the drive preventing booting.
0
 
_Commented:
Do these systems still error with known good drives?
Have you scanned the drives with an anti-virus/malware/rootkit?

Any bad electrical storms or powergrid issues lately?

I know you said they were different kinds of systems, but what about the motherboards?
0
 
ZionTech1PresidentAuthor Commented:
Systems boot fine with known working hard drive no electrical storms recently, All different motherboards. I have not externally scanned for viruses.
0
 
_Commented:
hmmmm... three harddrives doing the same thing is a bit bizarre. But possible.

Can you get the data off them an onto other drives?
0
 
ZionTech1PresidentAuthor Commented:
Yes I can. I have done that for one already... new hard drive, fresh OS. Going to do for the rest. A bit bizarre is true. Usually when I seen that in my line of work it means something, but once in a while I guess you have to chalk it up to coincidence. Strange thing is though I have never seen this type of problem that couldn't be fixed through the above options I have tried. That's why so bizarre. 20yrs in the business. Was introduced to UBCD finally though. Nice tool.
0
 
_Commented:
I like UBCD also. Saved me several times.    : )
Try running TestDisk on one them, and see if  will give you any helpful info.
And then maybe KillDisk, to see if nuking it will fix it.
0
 
ZionTech1PresidentAuthor Commented:
I will try that Coral. Thank you.
0
 
nobusCommented:
you talking about ubcd - or ubcd4win ?   not the same..
for testing i prefer ubcd -  much faster to load : http://www.ultimatebootcd.com/      

it looks to me like a problem from an update
0
 
ZionTech1PresidentAuthor Commented:
Ubcd4win
0
 
ZionTech1PresidentAuthor Commented:
None of these solutions worked. Reinstalled OS on new hard drives.
0
 
ZionTech1PresidentAuthor Commented:
Was not a solution, but a good resource
0
 
nobusCommented:
you're welcome
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 9
  • 3
  • 3
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now