"Verifying DMI Pool Data" and keyboard not workin


Recommended Posts

Let me start with, this is my first "from scratch" machine that I have put together. I did my best to research the parts for compatibility and to do my homework for installation. So, I put everything together, and besides having a heating problem that was fixed with a better Heatsink everything was fine for the first 48 hours.

After rebooting I found that Gigabytes app (and for the life of me I am forgetting its name) that displays the PC's Health Status was freaking out. It displayed 0 RPM for both fans and put the CPU Temp at 120C. The fans were definitely running, if anything on overdrive. So I restarted again and jumped into the BIOS to see what it was reading for the Health status. I found that all the power readings were listed as "failed":

VCore: FAIL

DDR12v: FAIL

ect

Also, CPU temp read "-" and rpm was zero. So I restored to factory settings and saved and exited. On reboot I got to "Verifying DMI Pool Data..." and the system hung. So I thought.. maybe its the boot order (I don't have a floppy on it yet) and it was looking for the floppy that wasnt there. So I restart and the keyboard isnt working! I power down, unplug the power (and all devices becides the keyboard and display) and when I plug the power back in I see the "lock" keys light up. (So I know power is getting across the board). Sure enough the keyboard still doesnt work.

So now what? lol.

Thanks for your help!

Board: Gigabyte: GA-8N-SLi Pro

Processor: Prescott P4 561 (3.6 Ghz)

Power: Enermax Noisetaker (480W)

i had problems with the "Verifying DMI Pool Data" issue. turns out that my boot system files in Windows were screwed and i ended up reformating, but i dnt think u have to do that. i was in the process of a recovery of Windows, still stopping at "Verifying DMI Pool Data", when i found the boot files on the net, and was able to boot into windows, too badi was doing the recovery and it all went to hell, so i formated.

Boot.ini

NTLDR

Ntdetect.com

  Quote
Create A XP Boot Disk from System Files

As a hedge against being unable to start XP, you can create a boot disk specifically for Windows XP that may allow you to boot the operating system. This can occur when the active partition boot record or other required files become corrupted.

Using Windows XP, place a blank floppy in drive A and format the disk. Navigate to the root folder of the system (in most cases this will be C:\) and copy the following files to the floppy disk.

Boot.ini

NTLDR

Ntdetect.com

If you can't see the files, click [Tools] and [Folder Options...] in the Menu Bar of Windows Explorer. Click the [View] tab and click the radio button next to [show Hidden Files and Folders]. Remove the check mark next to [Hide Protected Operating System Files (Recommended)] then click [Apply] and [OK]. The files should now be visible in Windows Explorer. If the files still cannot be copied, right click each file, click [Properties] and remove the checkmark from the Read-Only attributes. Reset whatever attributes were unchecked after the copy procedure is completed.

In addition to the files listed above, check the same directory for bootsect.dos and ntbootdd.sys files. If they are present on your system, copy them to the same floppy diskette.

The disk is used as any other boot disk, inserting it into the floppy drive (A:\) and initiating a cold boot. Make sure the BIOS is set so that the A:\ drive is first in the boot sequence.

http://www.theeldergeek.com/create_xp_boot_disk.htm

get those files from another XP computer, put on a formatted floppy disk, and boot to windows. then i think u can copy those files into there correct locations and itll work.

sorry not sure about the keyboard issue, probably get that sorted out first, since u wont be able to do the above with out it :p

Ok, now I am finding that if I let the machine sit for a while it seems to let me use the keyboard on the first try. It will also get into windows. Also note that I was using the machine for a day and a half before things went screwy, and then, only when I restarted did this begin... so weird...

I guess my main question is? Is it due to something I have put in incorrectly or not have hooked up all the way, a hardware issue (something broken), or is it a configuration problem?

Dolbex

Just in case someone stumbles on this topic (I HATE unfinished topics :) ), I never did figure out what the source of the problem was and decided that it had to be just a faulty motherboard (either due to it just being a lemon, or something I accidently did during installation). I ended up returning it to the store for an exchange of the same board. New board works fine so I am assuming that was the source...

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Similar to what started me on the path to switching to Linux... for the first 6mo of Win10 it was installing an AMD GPU driver that broke audio over HDMI which was essential to me. Driver from AMDs site was fine.
    • I have avoided many deer, a few moose, and other smaller animals during my years of driving and have managed just fine with only ABS and ESP, both of which can also be problematic depending on circumstance. I have never feared driving and I live in a rural area with a lot of deer and other animals. Winter or summer, heavy rain or sunshine, night or day, I always prefer and like to drive myself, and I drive constantly in my job. People die in accidents and they always will, that is a fact of life. Something like self-driving busses I can advocate for because they can be set to drive on static routes that always stay the same - i.e. those routes can be specially designed and maintained for them. I've already seen enough idiots doing random idiotic things with their Tesla autodrives that I would rather see them crash and burn because of their own stupidity instead of their "computer failing". I've also been a PC and tech enthusiast of over 25 years so I I'm fine with tech but I want to be the one who uses it, and decides how much of it I use. I also do not want it to make my hands, feet and brain obsolete. For me it's not really about if a computer can do it but about people not having to do things themselves (responsibly). I think that basic driving education should be done with a manual car and these "automatic only" cards should not exist (yes, I'm European and we drive a lot of manual cars, I even prefer them). If a person doesn't have enough coordination to manage a steering wheel, shitfer and pedals, how on Earth are they able to react to any unforseen situation on the road? And giving them autodrive doesn't make me feel any better if the person behind the wheel can't manage even basic driving themselves. One of the things I hate most in today's society (in general) is how pretty much everything that is considered even a bit dangerous is eliminated instead of educating people to assess risks and avoid problems themselves. Instead we make brains obsolete by building systems that do everything for us.
    • I know, I was just speaking about people in general.
    • I would say that's a purely subjective opinion, Phaseman.
  • Recent Achievements

    • One Month Later
      KynanSEIT earned a badge
      One Month Later
    • One Month Later
      gowtham07 earned a badge
      One Month Later
    • Collaborator
      lethalman went up a rank
      Collaborator
    • Week One Done
      Wayne Robinson earned a badge
      Week One Done
    • One Month Later
      Karan Khanna earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      681
    2. 2
      ATLien_0
      274
    3. 3
      Michael Scrip
      220
    4. 4
      +FloatingFatMan
      170
    5. 5
      Steven P.
      161
  • Tell a friend

    Love Neowin? Tell a friend!