Overclock.net › Forums › AMD › AMD - General › HELP! New System stuck at "verifying DMI pool data" at Startup
New Posts  All Forums:Forum Nav:

HELP! New System stuck at "verifying DMI pool data" at Startup

post #1 of 8
Thread Starter 
just put together a new system for my sister today

parts are:

GA-MA78GM-S2H (with onboard video)
AMD 5200+
2GB DDR2Ram
350w generic PSU
WD 320GB Sata HDD
Liteon DVD drive

was trying to install windows and it crashed half way through, second time i booted up im getting this error message "verifying DMI pool data" during startup and the system just hangs there/

trying shorting out the CMOS jumpers (havnt tried taking out the battery yet) and changing boot sequences with no success.


does anyone know whats going on? please help was suppose to finish this computer tonight but now i have no idea whats going on

thanks in advance
post #2 of 8
This issue can be caused by any of the below reasons.

1. Corrupt boot files on the computer.
2. Settings for hard disk drive are not correct.
3. Floppy diskette or CD in computer causing issue.
4. Boot devices not set properly.
5. BIOS corrupt or misc. setting not set properly.
6. Connections loose or disconnected.
7. Bad Hard disk drive or other bad hardware.

If the computer has no bootable files on the drive it is attempting to boot from it is possible that the computer may halt at " verifying dmi pool data..."

To resolve this issue:

* Boot from a bootable floppy diskette. Ensure that this diskette was made on the same Microsoft Windows operating system that is installed on your computer.
* Once at the A:\\> prompt type "sys c:" and press enter. This should report the message "File system transferred." Once transferred remove the diskette and reboot the computer.

If the computer continues to not boot attempt to re-create the master boot record by booting from the bootable floppy diskette again. Once at the A:\\> prompt type "fdisk /mbr" and press enter. This should return you to the prompt without giving you any message. Once at the prompt remove the diskette and reboot the computer.

Additional information about the "fdisk /mbr" command can be found on document CH000175.

Note: The above information only applies to Microsoft Windows users. If you are running a Linux / Unix variant or other operating system such as OS/2 and the computer is freezing at this DMI message ensure that Linux / Unix has been properly installed first and/or your boot manger is not corrupt.
post #3 of 8
Quote:
This issue can be caused by any of the below reasons.

1. Corrupt boot files on the computer.
2. Settings for hard disk drive are not correct.
3. Floppy diskette or CD in computer causing issue.
4. Boot devices not set properly.
5. BIOS corrupt or misc. setting not set properly.
6. Connections loose or disconnected.
7. Bad Hard disk drive or other bad hardware.

If the computer has no bootable files on the drive it is attempting to boot from it is possible that the computer may halt at " verifying dmi pool data..."

To resolve this issue:

* Boot from a bootable floppy diskette. Ensure that this diskette was made on the same Microsoft Windows operating system that is installed on your computer.
* Once at the A:> prompt type "sys c:" and press enter. This should report the message "File system transferred." Once transferred remove the diskette and reboot the computer.

If the computer continues to not boot attempt to re-create the master boot record by booting from the bootable floppy diskette again. Once at the A:> prompt type "fdisk /mbr" and press enter. This should return you to the prompt without giving you any message. Once at the prompt remove the diskette and reboot the computer.

Additional information about the "fdisk /mbr" command can be found on document CH000175.

Note: The above information only applies to Microsoft Windows users. If you are running a Linux / Unix variant or other operating system such as OS/2 and the computer is freezing at this DMI message ensure that Linux / Unix has been properly installed first and/or your boot manger is not corrupt.
Good response buddy, this could help others in the future.. good instructions also

+REP

Slim123
Dark Matter
(14 items)
 
  
CPUMotherboardGraphicsRAM
i7 2600k @ 3.4ghz MSI Z77 G45 Nvidia 980GTX Corsair 8gb Vengeance DDR3 @1600mhz 
Hard DriveHard DriveOSMonitor
480 Crucial SSD 2TB WD (storage) Win 10 Ultimate 24" BENQ 
KeyboardPowerCaseMouse
Microsoft Wave Be Quiet! 850w Modular Thermaltake V3 Logitech MX-518 
  hide details  
Reply
Dark Matter
(14 items)
 
  
CPUMotherboardGraphicsRAM
i7 2600k @ 3.4ghz MSI Z77 G45 Nvidia 980GTX Corsair 8gb Vengeance DDR3 @1600mhz 
Hard DriveHard DriveOSMonitor
480 Crucial SSD 2TB WD (storage) Win 10 Ultimate 24" BENQ 
KeyboardPowerCaseMouse
Microsoft Wave Be Quiet! 850w Modular Thermaltake V3 Logitech MX-518 
  hide details  
Reply
post #4 of 8
Quote:
Originally Posted by Regz View Post
was trying to install windows and it crashed half way through, second time i booted up im getting this error message "verifying DMI pool data" during startup and the system just hangs there/
Regz, during the OS installation what kind of crash occurred? Did it completely lock up or was their a BSOD error message? Failing/faulty memory might be the culprit. It is possible to receive brand new memory that is bad. For testing reasons, you could try downloading memtest and perform a diagnostic on the memory. I always recommend to run tests 5 and 8 each for at least 20 minutes. If you have a working stick of DDR2 try that as well. Are all of these parts brand new? It wouldn't hurt either to perform a full surface scan on the WD drive using the Digital Lifeguard tools.

Hope that helps
Workstation
(13 items)
 
  
CPUMotherboardGraphicsRAM
Athlon II X4 620 Asus M4A785-M Asus 5770 G.Skill 8GB DDR2-800 
Hard DriveOSMonitorPower
WD3200AAJS Windows 7 Pro Acer AL2216W, Samsung P2770 Corsair 550VX 
Case
Tagan Black Pearl 
  hide details  
Reply
Workstation
(13 items)
 
  
CPUMotherboardGraphicsRAM
Athlon II X4 620 Asus M4A785-M Asus 5770 G.Skill 8GB DDR2-800 
Hard DriveOSMonitorPower
WD3200AAJS Windows 7 Pro Acer AL2216W, Samsung P2770 Corsair 550VX 
Case
Tagan Black Pearl 
  hide details  
Reply
post #5 of 8
Quote:
Originally Posted by Regz View Post
trying shorting out the CMOS jumpers (havnt tried taking out the battery yet) and changing boot sequences with no success.
what the hell ???/ are you trying to fry your system, or maybe damage it otherwise ? you have to take out the battery before you short anything. repeat- take it out.
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
QX6850 Ga-p35-Dq6 BFG 8800 OC2 4gb ocz pc2-8000 
  hide details  
Reply
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
QX6850 Ga-p35-Dq6 BFG 8800 OC2 4gb ocz pc2-8000 
  hide details  
Reply
post #6 of 8
Quote:
Originally Posted by Laz View Post
what the hell ???/ are you trying to fry your system, or maybe damage it otherwise ? you have to take out the battery before you short anything. repeat- take it out.
Laz, I believe Regz's recommendation was merely a description of how to use the "Clear CMOS" jumpers.
    
CPUMotherboardGraphicsRAM
Phenom II X3 720 BE Gigabyte GA-MA790FXT-UD5P Sapphire Radeon HD 3870 2 x 2GB Crucial Ballistix Tracers PC3 10600 
Hard DriveCoolingOSPower
Almost 8TB of storage AMD Stock Cooler Windows Home Server CoolerMaster SilentPro M 700W 
Case
Lian Li PC-V2000B (with thlnk3r mods) 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Phenom II X3 720 BE Gigabyte GA-MA790FXT-UD5P Sapphire Radeon HD 3870 2 x 2GB Crucial Ballistix Tracers PC3 10600 
Hard DriveCoolingOSPower
Almost 8TB of storage AMD Stock Cooler Windows Home Server CoolerMaster SilentPro M 700W 
Case
Lian Li PC-V2000B (with thlnk3r mods) 
  hide details  
Reply
post #7 of 8
Thread Starter 
thanks guys i got it sorted today, problem was that the mb doesnt know how to jump to 2nd and 3rd boot device if 1st boot device is not responding.
post #8 of 8
Quote:
Originally Posted by Laz View Post
what the hell ???/ are you trying to fry your system, or maybe damage it otherwise ? you have to take out the battery before you short anything. repeat- take it out.
Uh, no you don't. You don't have to remove the battery when resetting CMOS. I don't know where you got that idea, but it's not true.
1880478
(13 items)
 
  
CPUMotherboardGraphicsRAM
Core i5-750 @ 4.0GHz [200x20] [1.44V] [B#L928B214] MSI P55-CD53 [1.5 BIOS] GeForce 9800GT 512MB 4GB Corsair XMS3 DDR3 @ 1600MHz [9-9-9-24][1.65V] 
Hard DriveOptical DriveOSMonitor
30GB OCZ Vertex, 500GB WD Caviar Lite-On DVD-DL Burner Windows 7 Professional x64 Samsung 216BW 1680x1050 
KeyboardPowerCaseMouse
Razer Lycosa Corsair 650TX Antec Twelve-Hundred Razer Salmosa 
Mouse Pad
A Skylit Drive Custom Mousepad 
  hide details  
Reply
1880478
(13 items)
 
  
CPUMotherboardGraphicsRAM
Core i5-750 @ 4.0GHz [200x20] [1.44V] [B#L928B214] MSI P55-CD53 [1.5 BIOS] GeForce 9800GT 512MB 4GB Corsair XMS3 DDR3 @ 1600MHz [9-9-9-24][1.65V] 
Hard DriveOptical DriveOSMonitor
30GB OCZ Vertex, 500GB WD Caviar Lite-On DVD-DL Burner Windows 7 Professional x64 Samsung 216BW 1680x1050 
KeyboardPowerCaseMouse
Razer Lycosa Corsair 650TX Antec Twelve-Hundred Razer Salmosa 
Mouse Pad
A Skylit Drive Custom Mousepad 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD - General
Overclock.net › Forums › AMD › AMD - General › HELP! New System stuck at "verifying DMI pool data" at Startup