I. Black screen fault resolution
The most prominent manifestation of a computer startup failure is that the screen is dark and there is no prompt. This type of fault is generally difficult to identify, mainly related to the display, graphics card is very close; System motherboard, CPU, cache, memory, power supply and other components of the failure can also lead to a black screen.
1. No self-check for black screen faults
After the host is turned on, the host panel indicator is on, and the fan in the host rotates normally, but the display is not displayed. When the keyboard is started, the three indicators in the upper-right corner of the keyboard do not shine, and the self-check memory is not displayed ......" And PC speakers.
From the fault phenomenon, we can see that the power supply of the host is basically normal (it is not ruled out that the host power supply is faulty), but failure to start the self-check program in the BIOS will cause a crash. Check the display, video card, memory, CPU, and motherboard.
Because there is no prompt for non-self-check of black screen faults, the "minimum system method" is usually used for troubleshooting. The "minimum system method" refers to the minimum system consisting of the motherboard, memory stick, CPU, graphics card, display, power supply, and other basic devices, after checking and confirming that the minimum retained system can work properly, further check other devices.
2. Black screen fault caused by insufficient power supply
After a large-capacity hard disk is added to all normal systems, the power indicator is on, but the screen is dark and cannot be started.
Because only one hard disk is added, you should first start with the hard disk. After you re-plug the Main Boot hard disk interface line and change the data line, it still cannot be started, but after you remove the hard disk, the computer can start again. It is okay to take this large-capacity hard disk to another computer for test. It can be inferred that the hard disk is normal. Why is the black screen? This is because the hard disk is added with an IDE interface and a power interface for computer systems. The IDE interface is okay (the reverse interface will also cause a black screen, this determines the power configuration of the power supply. If the power supply problem is determined, the fault can be eliminated after the original power supply is replaced with a high power supply.
3. Black screen Fault Caused by CPU damage
A computer has been running normally and has no signs of CIH virus attacks. The user once removed the CPU and installed a fan on the CPU sink. As a result, a black screen is displayed when the computer is started, and does not perform self-check.
When the chassis cover is uncovered, it is found that the hard disk and optical drive lights are on, and the CPU fan (connected to the CPU fan interface of the motherboard) is also running normally. Use A multimeter to test the power supply of ± 12 V, the ± 5 V output is normal, and the power supply problem can be eliminated first.
The machine's CPU, memory, graphics card and other components are removed and re-installed once, to ensure that the installation in place, good contact. Start again and the fault persists, eliminating the problem of poor contact. Remove the sound card, optical drive, hard disk, and so on. Only the CPU, memory, and video card are left on the motherboard to form a minimal system. At this time, the boot screen is not displayed. In this step, you can determine the cause of the failure on the CPU, memory, or motherboard.
Observe the CPU carefully and find a deep scratch on the two pins of the CPU. It may be that the two pins have been cut off. Therefore, we were very careful to use the soldering iron to weld the two broken pins. After completing the welding, we inserted the CPU back to the original motherboard. This time, we finally started it normally and solved all the problems.
4. Black screen Fault Caused by Memory Corruption
There is no display on the screen, and a black screen occurs. If you press any key, no response (the monitor or host power indicator is on) will occur, and no self-check alarms will be reported. Sometimes it works normally. The latest version of Kv 3000 is used to clear the virus and discover that the hard disk is non-toxic. However, if the disk is shut down or hot-started, a black screen is sometimes displayed. After a while, it will be normal, and it will not work for a while.
Because the screen is not displayed, first consider whether the display is faulty. Use the replacement method to check the monitor. No problem. Therefore, the video card is replaced with another computer and displayed normally when it is started. Then I suspected that there was poor contact with the PCI expansion slot. I switched the good video card to another expansion slot, and the fault remained. Another slot remains unresponsive. Next, remove the motherboard, check carefully, and use a multimeter to detect the fault. Use a good ISA bus graphics card, insert the ISA expansion slot, open the machine, and the fault disappears.
Unplug the video card and reboot the system. When the host self-check is detected, no alarm is reported about the video card fault. Therefore, it is suspected that the alarm is related to the memory. Unplug the memory stick, change the sequence, and reinstall it. First, install the original 3rd and 4th memory stick, and then reboot. The on-screen Display memory is 8 MB (4 MB for each). After shutdown, the original 1st and 2nd memory records are installed. If the fault occurs again, replace 1st with 3rd, replace 2nd with 4th with 4th with a memory failure. According to the analysis of the memory stick, the memory stick is unstable or of poor quality, resulting in an error when the computer starts addressing.
Ii. troubleshooting during startup
Solved the fault of black screen startup. The following describes other faults during startup. Compared with the black screen fault, the display is not dark, and sometimes there are error prompts on the screen, so as long as you can understand the following typical faults, it is much easier to handle them.
1. the reset key cannot be started because it is damaged.
A computer crashes after it starts up for a period of time. After a period of time, the same phenomenon occurs again. After several restarts, the machine does not perform self-check after it is started.
In the beginning, I thought that the hard disk or Board was not properly plugged in. I opened the chassis and re-inserted the hard disk and video card and didn't respond after I started the system again. It was useless to change the memory stick. Then I suspect that there is a problem with the power supply. After inspection, the power supply is working, and then I use a multimeter to measure the output voltage of the power supply. Everything is normal, so I can judge that there is a problem with the motherboard.
No obvious signs of burning were found on the motherboard. Unplug everything on the motherboard (CPU, memory, power plug, and video card cannot be unplugged) after self-check, it proves that the motherboard is correct. Finally, the reason was finally found out: it turned out that the "reset" key on the chassis was broken. After the press was down, it didn't play back, and it was always in a short circuit. No wonder the machine could not be started.
2. startup failure caused by two-in-one sound card
A multimedia computer, with a Lenovo phonograph decompressing the two-in-one card, has been working normally. However, machine self-check exceptions have occurred recently when the machine is started, and it is always unable to pass the self-check without regularity. Then, the machine crashes. On average, it must be switched five or six times before it passes the test. The operation is normal.
The Analysis of Human surface phenomena seems to be a problem with the video card. After replacement, the fault still persists. After careful observation of the sound at boot, it was found that after the hard disk was powered on, there was no movement after reading the 0 track. Under normal operation, scan the hard disk with Windows 98 disk, everything was normal, no bad track, you can eliminate the possibility of failure caused by hard disks.
The problem is concentrated on the two-in-one card. The two-in-one card works normally in the Process of occasional successful startup. After being explained by the maintenance personnel, it may be that a circuit of the dual-in-One Card is short-circuited due to the impact of high boot current. Therefore, the above fault is triggered. After the switch, everything is normal.
3. Hard Disk boot failure caused by DOS interpreter Error
Boot the computer, hard disk dos boot failure, screen prompt: bad or missing command interpreter (command interpreter program error or loss ).
This fault shows that the command interpreter command.com of the DOS system has an error or is missing.
Command file error may be caused by: The file information is damaged; the hard disk sector where the file is stored is damaged, resulting in a failure to read the file.
The cause of the loss of the command file may be that the file was accidentally deleted by the user. When copying the file, the user replaced the command file of the same DOS version with the original command file.
Whatever the cause, you only need to use the DOS system disk of the same version as the hard disk to boot the system from the soft drive and copy the command file on the disk to the hard disk. If the system cannot be booted from the hard disk, use the Sys command to transmit the entire system.
Crash
In computer faults, apart from the failures that occur during computer startup, the most common faults are crash failures. There are many causes of computer crashes. The following are common crash failures and troubleshooting.
1. Frequent host crashes due to heavy dust
A pc Often crashes when running programs, especially when the weather is wet.
This kind of fault is difficult to check because of both the component and non-component reasons. During the inspection, we generally start from the simple non-component aspects.
Open the shell and find that there is much dust on the system board. When the Yin value between the data line and the ground on the I/O slot is measured using a digital table, it is found that the D0 male is more than 4 m, indicating that there is slight leakage between the data line and the ground, especially when the weather is wet, greater leakage. Eliminate the dust on the motherboard and each plug-in card in the chassis and troubleshoot the fault.
2. Crash due to poor performance of the reset switch
After a computer starts up for a period of time, the screen turns black and the optical drive light is on. Press the "reset" key or press the "CTRL + ALT + DEL" key. If the instance cannot be restarted immediately after it is shut down, it can only be started after it is stopped for a while. If the instance fails to run for a long time, the instance can work for a while when it is turned on.
Find out the possible causes of the fault. The sound card, hard drive, and optical drive are removed one by one, and the video card, CPU, and memory are replaced one by one. The failure still persists. Changing the power supply and motherboard still cannot solve the problem. During the check, it is found that after a period of time, you only need to press the "reset" key to crash.
First, we suspect there is a problem with the "reset" key. Unplug the "reset" key from the motherboard and start the system. After several hours, the system has not crashed. It seems that the problem lies in the "reset" key. After the "reset" Key is changed, the fault will be rectified.
Under normal circumstances, the "reset" Key is normally on, the system is reset when it is pressed (Short Circuit), and the computer starts when it is disconnected. Due to the poor performance of the "Reset" key, the resistance at both ends of the "Reset" key is reduced as the working time is prolonged after the machine is started. To a certain extent, the computer is reset when the circuit is reset and connected. However, because the resistance of the "reset" key is always very small, it is as if the "reset" key is not released, so the computer can only reset and cannot start. This fault may occur, even if it is restarted. After cooling, the resistance at both ends of the "reset" Key gradually increases. When it increases to a certain value, the computer can start again.
3. Access to the soft drive will cause a crash
A computer operating system is Windows 98, whether in Windows or in MS-DOS mode, as long as the access to the soft drive system is in a long wait state, when you press Ctrl + ATL + DEL, a blue screen is displayed, and you cannot close the program.
The indicator of the soft drive is not on when a fault occurs, and it is suspected that the CMOS settings are incorrect. After entering CMOS, I found that the disk is correctly set, but the second hard disk is mounted in the hard disk settings, so I suspect that an error occurred here. The second hard disk was not found after Windows 98 was started, and the fault still occurred.
I have installed Ultra. CMA/33 driver, so after entering Control Panel → system, found performance prompts that a driver with a MS-DOS reduces system performance, some settings use MS-DOS compatibility. Therefore, it is suspected that the driver may conflict with Windows 98 in config. sys commented on the driver and deleted it in system. several drivers related to the driver in ini, everything works after restart.
4. crashed due to incorrect bus Mode settings
After a computer starts from the hard disk, it can read and write the floppy disk drive normally; but when it starts from the floppy disk drive (floppy disk), it will crash after it runs to the starting MS-DOS, there is no cursor or the cursor flashes at any position.
After the disk is started, you can perform normal read/write operations on the floppy disk drive, so you can eliminate the possibility of a soft drive failure. If you suspect that the system floppy disk is infected with a virus or the system file is damaged and the floppy disk is replaced with another computer of the same type, the general floppy disk read, write, and format operations can be completed normally, where is the fault?
Based on the principle of "soft first and hard", we decided to use the test software to perform a comprehensive diagnostic evaluation for the entire system before opening the chassis.
The test system information shows that the bus type is ISA (PC/AT). It is estimated that the fault may be caused by improper parameter settings in the computer CMOS setup utility (CMOs utility setup program. Reboot, enter the CMOS Parameter setup program, after careful observation, in the PCI configuration setup, "PCI ide IRQ map to" an original set as PCI-AUTO: set "primary ide int #" to a: "secondary ide int #" to B. Therefore, the "PCI ide IRQ map to" item is set to ISA, stored in the bios, restarted, inserted into the system disk in the soft drive, boot from the soft drive successfully, troubleshooting.
5. Memory Stick parameters are improperly set to cause a crash
A computer with 4 MB memory is used. After the memory is damaged, two 8 MB memory disks Without parity bits are purchased for trial use on 586 computers. The qplus test proves that the two memory modules are basically qualified. The memory stick is installed on the computer. The total memory size displayed on the boot screen is KB. The parity error is displayed, and then the system crashes. In addition, the CMOS settings cannot be entered at any time during the startup process.
The reason is that the memory in CMOS is set to the parity status, but the new memory stick does not have the parity function, so that the total number of memory reported by the system does not match the actual installation. Because the system cannot enter the CMOS settings during the startup process, you only need to remove the memory entry with a parity bit from the original three-piece on the other computer, and install it on the computer for which you want to change the memory entry. After the system is started, go to the CMOS settings and change memory parity error check to disabled. Shut down and re-install the new memory stick on the machine. Turn on the computer power, and find that the situation has improved, you can enter the CMOS settings, but after exiting the CMOs, it will crash. Check the settings of CMOS carefully and find no improper settings. Try to start from a floppy disk again.
It is estimated that the memory is in conflict with the CMOS settings. After studying the memory-related items in CMOS, try to write the memory read wait state (memory read wait state) and memory write wait state (memory write wait state) change from 0 w/s to 1 W/S. Save the CMOS information and exit. The computer runs normally.
6. Crash due to hard disk damage
A computer Often crashes when running Windows 98 applications. However, running dos WPS and other programs is normal. It was initially regarded as a virus, but no signs of the virus were found by the antivirus program. Reinstall windows, the installation process is normal, but a program, even the notepad, card and other programs that come with windows, will also crash.
First switch the memory and CPU to another computer. There is no problem, which means it is not a memory or CPU problem. The computer can also start dos and perform UCDOS, WPS and other programs, so the possibility of motherboard failure is very small.
Consider whether the computer runs all the DOS programs normally. Try a game running under DOS in a casual environment. The program dos4gws.exe crashes. This is the case after several retries.
The main task of this dos4gws.exe is to create a large super file on the hard disk to make up for insufficient computer memory when running a large program, this file requires a large enough continuous hard disk space. Windows 98 will also create such a file named win386.swp. The files created by dos4gws.exe are different from those created by Windows 98. The former creates a fixed-size swap file, while the latter creates a swap file that varies with the application. Generally, when Windows 98 is started, this file is only about 1 MB. Once the program is run, it will reach 20 MB, and sometimes it may even exceed 100 MB. All swap files require continuous hard disk space. That is to say, swap files cannot be separated and stored like other files. If there is a bad cluster on the hard disk, and the file exchange happens to encounter a bad cluster, it will obviously Crash. Because dos4gws.exe is a large fixed exchange file, it will crash once it is run. While Windows 98 swap files are constantly increasing during use, so it can be started normally when there are not many hard drives in the east and west. However, once the program is run, the larger swap file encounters a bad cluster, and the data cannot be exchanged on the hard disk, but the memory is insufficient, so a crash occurs. It turns out that there are bad clusters on the hard disk of this computer.
Use the Scandisk of DOS 6.22 to check the hard disk. No logic error is found. When the disk is scanned, a dozen red bits are found, proving that the above judgment is correct. The switch file error may cause a crash. If you change the switch file to another disk without any bad cluster, the problem may be solved.
It is also found that all bad sectors are in the first half of the hard disk, so the hard disk is divided into two areas (the hard disk is 1.2 GB), the C area is 700 mb, and the D area is 500 mb. After formatting, disk C shows bad clusters, but disk D does not. Try again to install Windows 98 to D. After the installation is complete, start. Everything is normal. Install Office 97 and run the word again, without the crash. The problem is solved.
7. memory crashes
A computer that was previously installed with Windows 95 and occasionally crashed while pulling the window scroll bar. Hot Start is invalid, but the mouse moves when the machine crashes, and after a period of time, the sound of a continuous "tick" occurs. all the buttons on the keyboard also make a "tick" sound, which does not work. After the virus is ineffective, uninstall Windows 95 and install Windows 97, there is no strange crash. A few days ago, Windows 97 was reinstalled because windows could not normally enter due to power failure, and the previous strange crash appeared again.
VRV, Kv 3000, AV 98 in turn, no exception. So I suspected that there was a problem with the memory, so I replaced them one by one and there was still no result. Because the crash may be related to the mouse, the driver that comes with the mouse is used, or the mouse is not used, the crash still occurs. Prepare to reinstall windows 97. The idea is that when eru.exe is run in a security mode to restore windows, it enters safe mode and does not crash.
Security mode can run normally, which may be a problem of display. Then we found that this host is equipped with the popular cirrus gd5466 graphics card in the past two years, with 2 MB video memory. Currently, the Main Board uses 800*600 real color, which seems to be a little reluctant. Then we changed to 16-bit color restart to solve the problem.
8. The video card driver causes a crash
One computer is the Asus motherboard, and the operating system is a Windows 98 Chinese version. It often crashes and even enters dir in DOS.
First, frequency reduction is often caused by over-frequency faults. When the calibration frequency is reduced to 300, the DOS prompt of Windows 98 still occasionally shows dir frequency and crash. Replace the memory, and the fault persists. Because I first found two other brands of 9750 and 9850 graphics cards, I also tried it. It was found that this problem exists with the previous friends and friends. It seems that it is not likely to be a problem with the video card driver.
Dial-up Internet access, view the video card manufacturer's URL, and find that new drivers can be downloaded. So we downloaded the new driver of Trident 9750. After installing the new driver, have not had time to store such as winmtr software testing, directly transferred to the MS-DOS prompt. After the command Dir, DIR/s, DIR/W is input several times, everything is normal and the input dis is no longer crashed.
9. the system crashes after startup
"PCI device listing..." is displayed on the screen after self-check on the computer ..." Then crash.
If an emergency boot disk exists, insert the emergency boot disk into the drive, and restart the system with a floppy disk. If no boot disk is created, you can insert a floppy disk into the drive on a computer running Windows 98 normally, double-click "my computer", right-click "3.5 inch floppy disk", and select "format" from the shortcut menu ", select "copy only system files" for the formatting type ". Copy the "sys.com" file in the Windows/command directory to a floppy disk and insert the prepared floppy disk into the faulty machine.
After boot with a floppy disk, a> appears, entering the DOS mode of windows. Windows cannot be started mainly because the windows system is damaged and can be re-transmitted using a floppy disk to recreate the hard disk Windows system. Run "sys C:". After the system transfer is completed, start it with the hard disk.
10. Random crash
The computer crashes randomly in Windows 98 operating system.
Windows 98 crashes may be caused by memory quality problems, unstable power supply, and software problems, but they are generally caused by hardware drivers.
In order to compete for the market, every hardware manufacturer is always eager to put some new hardware devices into the market, but not enough in the development and testing of the device driver. Some less formal vendors do not provide drivers when selling hardware products. Instead, they allow users to use the old and even 16-bit DOS-based drivers. These hardware drivers will induce random crashes at any time.
You can obtain the latest drivers from the vendor or download these drivers from the vendor's site over the Internet. Check the "config. sys" file to see if there are any outdated 16-bit drivers. The extensions of these drivers are mostly sys or DRV. For outdated 16-bit drivers, you can directly delete them from the Device Manager on the control panel.
Shutdown fault
After processing all kinds of data, the computer shuts down the computer, but it is often unable to shut down normally. You can use the following methods to solve this problem.
1. Unable to automatically shut down
After a computer is upgraded to Windows 98, it cannot be automatically shut down.
The shutdown failure of Windows 98 may be caused by hardware or software and can be eliminated separately.
(1) software: Check all running programs and use the microsoftsystem Configuration tool (msconfig.exe, in the C:/Windows/system directory) to check which programs are running and clean the system boot (that is, to load the least driver. And do not run any program in the startup group for system boot at startup ). If clean boot can solve the problem, you can use the System Configuration tool to start the relevant programs one by one to determine the programs that cause the shutdown to fail. If the problem persists, select start/Program/attachment/system tool/system information ", then select the tool/automatic skip driver proxy tool to enable drivers for all disabled devices.
(2) Hardware: Go to the "control panel", disable all devices under the "Device Manager" tab of "system", and then reboot the system. If the problem is solved, enable the disabled devices one by one to identify whether the shutdown fails due to a hardware problem. When it is determined that a hardware caused an abnormal shutdown problem, update its driver or hardware.
2. Windows 98 does not respond when Shutdown
The computer does not respond every time you click "Close computer.
The computer cannot be shut down normally for the following reasons:
(1) due to the advanced power management function. You can turn off the advanced power management function, that is, "Start/set/control panel/system/Device Manager/system device/advanced power management/set clear enable power management ", click OK to restart the computer.
(2) System File conflicts. For example, there is a conflict between the "system. ini" file or the "win. ini" file, and the "config. sys" file or the "autoexec. Bat" file. You can enter the protection mode at startup. Because the specific location of the conflict cannot be determined, only the possible conflicts in the system file can be modified.
(3) The system enables the quick shutdown mechanism. Quick shutdown is incompatible with some hardware. You only need to disable quick shutdown. Run "hsconfig", select the "advanced" tab in the pop-up menu, select "Disable quick shutdown", and then restart the computer.
3. reinstalling wiondows 98 cannot be more shutdown
After Windows 98 is reinstalled, it cannot be shut down and canceled.
Windows 98 cannot be shut down normally due to the following reasons:
(1) Windows 98 does not support quick shutdown. Select Start/Program/attachment/system tool/system information, open the Microsoft system information dialog box, and select tool/System Configuration Utility ", on the "General" tab, click the "advanced" button, select the "Disable quick shutdown" check box, and then return.
(2) Some resident memory programs did not exit. During shutdown and logout, windows must close all the tasks and open ports to Ensure network disconnection. Even if the network connection is disconnected, the system still considers it to work online because it does not select "offline work. If shutdown is selected directly, Windows soft shutdown may occur.
(3) the operating system and the main board do not fully support ACPI or APM. Select Start/set/control panel/system, double-click system devices on the Device Manager option, and double-click Advanced Power Management in the device list ", click the "Settings" tab, clear the check box before "force use APM mode", and click OK.
4. Windows 2000 cannot be shut down normally
When advanced power management is enabled on a computer with Windows 2000, the computer is restarted.
This is mostly because the motherboard BIOS is incompatible with Windows 2000. You need to upgrade the bios and remove "APM" from the power management of Windows 2000.
5. Windows XP cannot be automatically shut down
After Windows XP is installed, when the system prompts "you can shut down", pressing the shutdown button does not work.
This may occur if the motherboard does not support advanced power management. You can open the "power" option in the "control panel" and select the "APH" option, Windows XP will automatically perform power management.