"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

    • Hello, Yes, and yes. More specifically, there are lots of features in Windows that I do not use--I cannot recall the last time I needed to run EUDCEDIT.EXE or ODBCAD32.EXE on a computer I own, but I'm sure that for some people they are useful, and for a smaller set of people they might even be indispensable. I don't begrudge Microsoft for including them as part of the standard Windows installation nor the people who need such tools; sometimes it is convenient to have some little utility or feature readily available. One thing I do begrudge is Microsoft's over-reliance on its own telemetry, and perhaps surpisingly on the flip side, customers who disable it. Collecting telemetry is generally a good thing, if it is done for good reasons and does not include any customer PII. However, how you interpret that telemetry is even more important, as that can lead to all sorts of disastrous decisions. On the customer side of things, telemetry is your "vote:" it's how you tell companies what features you use in the program, and lets them prioritize things appropriately. One glaring example is Windows 8, which shipped with the full-screen Start Screen because Microsoft's telemetry told them the average Windows user pressed the Windows key to bring up the Start Menu less than once a day. I have often wondered how many "power users" of previous versions of Windows (XP, Vista, and 7) that relied on the Start Menu disabled the telemetry that would have told Microsoft a difference story about its usage. More recently, I came across a young lady who had a problem with a third-party sync program on her computer running Windows 7. An update for the utility removed Windows 7 compatibility, and broke her backup process. Now, support for Windows 7 ended over 5 years ago in 2020, but there are ISVs who still support their software on it, but decisions about stuff like that are made, in part, by knowing what percentage of your customer base is on what operating system version. When I asked about that, she mentioned she had specifically disabled the telemetry from the sync program to its developers, which was optional to begin with. What made things even worse was that this was an open source utility, and its authors had a very clear, well-designed and scoped policy on the telemetry they collected, the pains they went through to avoid collecting any PII, and even other ancillary risks involving information disclosure (like just using of the software) because of the network connection made for the checks. Yet, she took herself out of telling the project maintainers "Hey, I use your software and I'm running Windows 7" by disabling the telemetry checks, which could have let them know they needed to continue supporting it. In a sense, sending telemetry is just like voting: Individually, you may not think it matters much, but it is often the basis for very important decisions. Regards, Aryeh Goretsky
    • Hello, My thoughts on this are mixed. Microsoft has hosted malicious code in the Microsoft Update Catalog where third party device drivers are stored; I wrote about one such incident about fifteen years ago, so if there are any other old malicious drivers floating around in the catalog, this will be a good step towards preventing any infestations from reoccurring. Another thing, which surprisingly is not mentioned in Microsoft's announcement, is that this helps protect against BYOVD (Bring Your Own Vulnerable Driver) attacks, where malware either comes with or downloads an older device drivers with vulnerabilities in it that can be exploited to gain access to kernel memory. Removing all those old device drivers from the Windows Update Catalog, potentially with all sorts of undisclosed vulnerabilities in them, means an attacker can no longer leisurely count on being able to download them from Microsoft's servers--something that may go unnoticed or ignored by security analysts. This makes the adversary attack a little more noisy, since they have to either include the device driver with the rest of their initial payload or download it from a third-party site at some point prior to beginning their BYOVD attack. On the other hand, it means that people who are looking for a specific version of an older device driver for whatever legitimate reasons, like compatibility, performance or stability, may end up going to dodgy third-party sites in search of older drivers, which increases the risk of exposure to everything from nuisance advertisements and unwanted software to actual malicious code. As for me, I have keeping copies of all the device drivers, firmware updates, etc. I have downloaded over the years, some dating back to DOS and Windows 3.x era, not just for hardware I won, but popular things like unified chipset and video card drivers, just in case I ever needed it. It might seem silly to collect such a thing, but the hardware drivers, firmware updates, and documentation are just about 2 TB in size. From my perspective, it is an inexpensive form of insurance, especially given that disk space is always getting cheaper over time. Regards, Aryeh Goretsky
    • @Raze Bold it boy. (I admit, we all did it from time to time..)
    • Fan Control V227 by Razvan Serea Fan Control is a powerful and versatile portable utility that allows you to monitor, control and customize the fans of your GPU and CPU to keep your machine cool and running smoothly. Fan Control supports a wide range of devices and hardware configurations, giving you complete control over your computer's cooling system. Fan Control backend is mainly based on LibreHardwareMonitor, an open source fork of the original OpenHardwareMonitor. This means that hardware compatiblity is entirely open for anyone to contribute, and doesn't rely on a single developer who may stop caring at some point. Combined with the plugin system, Fan Control is unlocked for many generations of hardware to come. Main features Guided setup process on first launch Save, edit and load multiple profiles Change the theme and color of the application. Multiple temperature sources ( CPU, GPU, motherboard, hard drives... ) Multiple fan curve functions, including a custom graph Mix fan curves or sensor togethers (max, min, average) Low resource usage Advanced tuning with steps, start %, stop %, response time and hysteresis FanControl V227 changelog: Allow decimal with hysteresis values Radeon Pro support through ADLX Fix a bug when cancelling the graph editing dialog Update LibreHardwareMonitorLib Download: FanControl V227 | Installer ~15.0 MB (Open Source) View: Fan Control Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Lol tf you are talking about. People are PAYING by using this app exclusively, just indirectly. Do you have any idea how much facebook charges for api access to WhatsApp which has become more or less a monopoly in e-commerce.
  • Recent Achievements

    • Contributor
      GravityDead went up a rank
      Contributor
    • Week One Done
      BlakeBringer earned a badge
      Week One Done
    • Week One Done
      Helen Shafer earned a badge
      Week One Done
    • First Post
      emptyother earned a badge
      First Post
    • Week One Done
      Crunchy6 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      660
    2. 2
      ATLien_0
      266
    3. 3
      Michael Scrip
      235
    4. 4
      Steven P.
      165
    5. 5
      +FloatingFatMan
      149
  • Tell a friend

    Love Neowin? Tell a friend!