Verifying DMI pool data ....

When the computer is started to verifying DMI pool data solution:
DMI is the abbreviation of the English word "Desktop Management Interface", that is, the desktop management interface, which contains configuration information about system hardware. The computer verifies the DMI data every time it starts up. If the data fails or the hardware changes, the computer detects the data and writes the data to the BIOS chip for storage. Therefore, if we disable the BIOS chip refresh function in the BIOS settings or use jumpers on the motherboard to disable the BIOS chip refresh function, the DMI data of this machine cannot be updated. If you change the hardware configuration, the machine still works according to the configuration of the old system during the Windows system. In this way, the performance of the newly added hardware cannot be fully utilized, and sometimes some faults may occur.
If the system stops or is in the dead state after we see the above information when starting the computer, it is generally difficult to handle such machine faults. Because it cannot be like a fault that occurs after entering the system, we can check system logs and other files for analysis. However, according to the analysis of the PC startup process, the following information may occur:
1. Hardware change
When the hardware configuration of the host changes, but we use the post function, the system cannot identify the newly added hardware and will work according to the old configuration, at this time, the system will be able to power up after the power is turned on, but there is no "beep" sound when the power is started normally. At the same time, there is no image display on the display, only the sound of the fan rotating.
Another reason is that the compatibility of the newly added hardware is poor, which leads to the above situation.
2. BIOS settings change
When the BIOS is set incorrectly, for example, the memory read/write parameters are incorrectly set, the hard disk mode is incorrectly set, and the on-board sound card and integrated sound card are incorrectly set, the startup may fail.
3. Hard Disk line connection Error
In this case, the hard disk data line has poor contact. The poor data line quality leads to too many data transmission errors, and the data line is inserted incorrectly (the motherboard side is connected to the hard disk side). The Master/Slave hard disk jumper is incorrect, the hard disk capacity or Mode settings are incorrect.
4. The content in the boot area of the hard drive is damaged.
When the content of the primary boot area of the hard disk is rewritten or damaged by viruses, or the Partition Table of the hard disk is cleared or manually set to a logical lock status, the system crashes.
If the boot program in the Main Boot area of the hard disk is damaged, we can use the fdisk/MBR command to fix it, you can also use the disk editing function of kv3000 to check whether there are backup programs in the master boot area for 62 other sectors with 0 rows and 0 rows and 0 rows and 0 rows.
It is more troublesome for partitioned tables to be damaged. If the partition table does not have the "80" or multiple "80" or "55aa" logo, you only need to use the disk editing function of kv3000 for manual repair. For logical locks, you need to create a special disk to unlock it. If the partition table is completely damaged or encrypted, we can only re-partition it.
5. Hard Disk faults
Now the disk capacity is getting bigger and faster, but the hard disk quality seems to be getting worse and worse. Up to now, hundreds of MB of second-hand hard disks produced in and 95 are being sold. But now, the new hard drive that we just bought will be broken into slices or inexplicably lost data in just a few days, and it will not be a matter of "too busy" comments. When the hardware of the hard disk fails, the above problem also occurs. The hard disk can recognize the hard disk in CMOS, and the hard disk can be recognized smoothly, but it cannot enter the system, partitions and formatting cannot be performed normally.
6. Problems with the motherboard
The main problems related to the motherboard are the hard disk controller Problems of the motherboard, resulting in unstable data transmission and a high error rate.
7. Damage caused by overclocking
If we exceed the frequency, it will also appear after the boot to the hard disk here to crash. In this case, we 'd better check the CPU frequency displayed during the self-check, and then open the chassis to check whether the actual CPU frequency is the same. Especially for the CPU after the PIV, its integration is extremely high. If we use it frequently, it is very likely that the CPU's internal electronics will experience excessive attenuation in a short period of time, leading to CPU decommission in a short period of time.
Solution:
1. Restore the status before the hardware changes and check whether the system can be started properly.
2. check whether all connection lines or expansion cards are correctly connected.
3. try to reconfigure "PNP/PCI configuration" and "Reset configuration data" in the BIOS. You can also use BIOS options such as "Force update escd" to set it to "enabled" and then save the disk and exit. If it cannot be started, try setting it to "disabled" again.
4. Check the information about the CMOS jumper in the motherboard manual and clear the CMOs. Note: When you clear the CMOS settings, you must unplug the host power cord or set the host power switch to off or 0.
5. disconnect the hard disk connection line, including the optical drive or other ide devices. Then, enter the BIOS settings, select the boot sequence as the floppy disk, and press F10 to exit storage. Then, put a bootable system disk in the soft drive, check whether the system can be started normally.
6. after the CMOS settings are cleared, set the "PNP/PCI configuration" option in the CMOS settings to "enabled" and restart the computer to update the DMI data, it is also called Force update of escd data.
7. if the host can be started through a floppy disk but cannot be started through the hard disk, this may be because the data in the master boot area of the hard disk is damaged. In this case, you can use the partition software to fix the program code in the master boot area, if you start your computer with a floppy disk, run the fdisk/MBR command to repair the Master Boot zone. You can also download a special hard disk analysis tool program from the website of the corresponding hard disk manufacturer to check the specific failure of your hard disk.
8. If the fault cannot be ruled out after the above settings, you should consider the problem of the IDE interface of the motherboard or hard disk, which can be solved by replacement.