When the host hardware configuration changes, but we use the POST function, the system can not recognize the newly added hardware, will be working according to the old configuration, then there will be a power on the power, but there is no normal startup "beep", and the monitor has no image display, only the sound of fan rotation. The display does not show an image, but only the sound of the fan rotating.
There is also a reason that the compatibility of the newly added hardware is not good, leading to the above situation.
2. BIOS setup changes
When the BIOS setup is wrong, such as incorrectly setting the read/write parameters of the RAM, incorrectly setting the mode of the hard disk, incorrectly setting the onboard sound card and the integrated sound card, etc., it will result in a failure to boot normally.
3. Hard drive cable connection errors
This type of situation has a hard drive data cable poor contact, data cable quality caused by the poor quality of the data number output too many errors, data cable insertion error (connected to the motherboard end and connected to the hard drive end of the inverted child), the master-slave hard drive jumper error, the hard drive capacity or mode settings are wrong, and so on.
4. Hard drive boot sector content is destroyed
When the hard drive's boot sector content is rewritten by other programs or destroyed by viruses, or when the hard drive partition table is cleared or artificially set up into a logical lock state, it will be at this point in time to crash.
For the hard drive's boot sector, we can use the Fdisk/MBR command to repair the boot sector, or use the KV3000's disk editing function to find out if there is a backup of the boot sector program in the other 62 sectors of the 0 path 0, and then restore the boot sector program to the 0 path 0 0 area.
For the partition table is destroyed is more troublesome. If only the partition table does not have the "80" sign or more than one "80" sign, or no "55AA" sign, we just use the KV3000's disk editing function of the KV3000 to manually repair it. If it is a logical lock, you need to make a special disk to unlock it. If the partition table is completely destroyed or encrypted, then we can only repartition it.
5. Hard disk failure
Nowadays, hard disks are getting bigger and faster, but the quality of hard disks seems to be getting worse. The market is still in the 94,95 years of production of hundreds of M of the second-hand hard disk in the sale it. But now, just bought a new hard disk, within a few days will be bad channel into pieces or inexplicable loss of data, or "bam" of the opinion of the strike quit. When the hard drive hardware failure, will also appear in the above situation, such problems hard drive in CMOS can recognize the hard disk, recognize the disk is very smooth, but is not into the system, can not be normal partitioning and formatting.
6. Problems with the motherboard
With the motherboard is also mainly related to the motherboard's hard disk controller problems, resulting in unstable data transmission, the error rate is too high.
7. Damage caused by overclocking
If we overclocked too much, it will also appear after the boot to the hard disk here on the crash. The best way to do this is to check the frequency of the CPU on the boot screen, and then open the case to check the frequency of the actual CPU, and whether it is the same. The newest addition to the UEFI DualBIOS? system is a new, more advanced version of the UEFI DualBIOS? system, which is designed to be more efficient, more reliable, and more cost-effective than the standard UEFI DualBIOS? system.
The solution:
1. Restore the state of the hardware before the change and check if the system can start normally.
2. Check that all connecting cables or expansion cards are properly connected.
3. Try to reconfigure the "PNP/PCI configuration" in BIOS "Reset Configuration Data" can also be used. "Force Update ESCD" and other BIOS options are set to "Enabled", and then save the disk to exit. If you can't boot, try setting it to "Disabled" again.
4. Check your motherboard's manual for the CMOS jumper information and clear the CMOS. Please note: You must unplug the host computer's power cord or set the host computer's power switch to off or 0 when clearing the CMOS settings.
5. Disconnect the hard drive cables, including the CD-ROM drive or any other IDE devices, and then enter the BIOS setup to select the boot sequence of the floppy diskette, and then press F10 to store and exit. F10 to store and exit, and then put a bootable system disk in the floppy drive to check if the system can boot normally.
6. After clearing the CMOS settings, set the "PNP/PCI configuration" option in the CMOS settings to "Enabled" and restart the computer again to update the settings. The DMI data, also known as forced ESCD data update.
7. If the host is able to boot from a floppy disk, but not from a hard disk, it is possible that the data in the hard disk's main boot area is corrupted, which can be repaired by the partitioning software with the program code of the main boot area, e.g., after booting the computer with a floppy disk, use the FDISK/MBR command to repair the main boot area. You can also go to the website of the corresponding hard disk manufacturer to download a special hard disk analysis DMI is an abbreviation of the English word Desktop Management Interface, that is, desktop management interface, which contains configuration information about the system hardware. The computer checks the DMI data every time it starts up, and if there is an error in that data or a change in the hardware, the machine is tested and the tested data is written to the BIOS chip for safekeeping. So if we disable the refresh function of the BIOS chip in the BIOS setup or use jumpers in the motherboard to disable the refresh function of the BIOS chip, then the DMI data of this machine will not be updated. If you change the hardware configuration, the machine will still work according to the old system configuration when doing WINDOWS. This does not allow you to fully utilize the performance of the newly added hardware, and sometimes it fails in one way or another.
If we see this message above when starting the computer, the system stops for a long time or in a dead state, for the machine such failures are generally difficult to deal with. Because it can not be like a failure that occurs after entering the system, we can check the system logs and other files to analyze. However, according to the principle analysis of the process of PC startup, the emergence of this message generally have the following possibilities:
1. Hardware changes
When the host hardware configuration changes, but we use the POST function, this time the system can not recognize the newly added hardware, will be based on the old configuration to work, this time there will be a power on the boot can be powered up, but no The system will not be able to recognize the newly added hardware, and will work as it did in the old configuration, which means that the system will power up after booting, but there will not be a "beep" when booting, and there will be no sound of the fan rotating.
Another reason for this is the poor compatibility of newly added hardware, which leads to the above situation.
2. BIOS setting changes
When the BIOS settings are wrong, such as wrongly setting the read/write parameters of the memory, wrongly setting the mode of the hard disk, wrongly setting the on-board sound card and the integrated sound card, etc., it will result in a failure to boot normally.
3. Hard drive cable connection errors
This type of situation has a hard drive data cable poor contact, low quality data cable caused by the number of data transmission error too much, data cable insertion error (connected to the motherboard end and connected to the hard drive end of the inverted child), the master-slave hard drive jumper error, the hard drive capacity or mode settings are wrong, and so on.
4. Hard drive boot sector content is destroyed
When the hard drive's boot sector content is rewritten by other programs or destroyed by viruses, or when the hard drive partition table is cleared or artificially set up into a logical lock state, it will be at this point in time to crash.
For the hard drive's boot sector, we can use the Fdisk/MBR command to repair the boot sector, or use the KV3000's disk editing function to find out if there is a backup of the boot sector program in the other 62 sectors of the 0 path 0, and then restore the boot sector program to the 0 path 0 0 area.
For the partition table is destroyed is more troublesome. If only the partition table does not have the "80" sign or more than one "80" sign, or no "55AA" sign, we just use the KV3000's disk editing function of the KV3000 to manually repair it. If it is a logical lock, you need to make a special disk to unlock it. If the partition table is completely destroyed or encrypted, then we can only repartition it.
5. Hard disk failure
Nowadays, hard disks are getting bigger and faster, but the quality of hard disks seems to be getting worse. The market is still in the 94,95 years of production of hundreds of M of the second-hand hard disk in the sale it. But now, just bought a new hard disk, within a few days will be bad channel into pieces or inexplicable loss of data, or "bam" of the opinion of the strike quit. When the hard disk hardware failure, will also appear in the above situation, such problems hard disk in CMOS can recognize the hard disk, recognize the disk is very smooth, but is not into the system, can not normal partition and formatting.
6. Problems with the motherboard
With the motherboard is also mainly related to the motherboard's hard disk controller problems, resulting in unstable data transmission, the error rate is too high.
7. Damage caused by overclocking
If we overclocked too much, it will also appear after the boot to the hard disk here on the crash. The best way to do this is to check the frequency of the CPU on the boot screen, and then open the case to check the frequency of the actual CPU, and whether it is the same. The newest addition to the UEFI DualBIOS? system is a new, more advanced version of the UEFI DualBIOS? system, which is designed to be more efficient, more reliable, and more cost-effective than the standard UEFI DualBIOS? system.
The solution:
1. Restore the state of the hardware before the change and check if the system can start normally.
2. Check that all connecting cables or expansion cards are properly connected.
3. Try to reconfigure the "PNP/PCI configuration" in BIOS "Reset Configuration Data" can also be used. "Force Update ESCD" and other BIOS options are set to "Enabled", and then save the disk to exit. If you can't boot, try setting it to "Disabled" again.
4. Check your motherboard's manual for the CMOS jumper information and clear the CMOS. Please note: You must unplug the host computer's power cord or set the host computer's power switch to off or 0 when clearing the CMOS settings.
5. Disconnect the hard drive cables, including the CD-ROM drive or any other IDE devices, and then enter the BIOS setup to select the boot sequence of the floppy diskette, and then press F10 to store and exit. F10 to store and exit, and then put a bootable system disk in the floppy drive to check if the system can boot normally.
6. After clearing the CMOS settings, set the "PNP/PCI configuration" option in the CMOS settings to "Enabled" and restart the computer again to update the settings. The DMI data, also known as forced ESCD data update.
7. If the host is able to boot from a floppy disk, but not from a hard disk, it is possible that the data in the hard disk's main boot area is corrupted, which can be repaired by partitioning software with the program code of the main boot area, such as using a floppy disk to start the computer, and then using the FDISK/MBR command to repair the main boot area. You can also go to the corresponding hard drive manufacturer's website to download a special hard drive analysis tool program to check the specific failure of your hard drive.
8. If you can't troubleshoot after the above setup, this should be considered a problem with the motherboard or hard disk's IDE interface, which can be solved by the replacement method.
I suspect that the hard disk problem, generally speaking, the hard disk thing, change a piece of the package quasi-OK
.