Chapter 6 Operation and Application Fault 1. Definition Example This type of failure is mainly referred to in the application and system failure of the shutdown before the startup is completed. Second, possible fault phenomenon 1, you can't wake up normally after sleep; 2. Blood screen, crash, illegal operation in the system operation; 3. System running speed; 4. Run an application, resulting in hardware function failure; 5 , The game is not working properly; 6, the application cannot be used normally. Third, it may be involved in the hunger, CPU, memory, power supply, disk, keyboard, plug-in board, etc., judge points / order 1, preparation before repair 1) Clean available hard drives; 2) anti-virus software; 3) As new drivers, several versions of the BIOS; 4) disks connected to the data lines, etc. 2, Environmental Inspection 1) Motel and Connection Check: a. Check if the mains are normal, whether it is sloppy; whether there is a ground; b. Whether the cable between the devices is wrong or missed. 2) Peripheral and appearance check: a. Check if other peripherals connected to the host is normal; b. Does the driver have abnormalities, whether the speed of the CPU fan is too slow or unstable; c. Observing the dust in the machine Many, causing indirect contact with each insert. First remove the dust fingers, remove the oxide or dust. Then re-insert; d. Whether the system is odor, whether the temperature rise of the component is too high or too fast. 3) Display and setup check: a. Detailed record error information, determine the location that may cause a fault; b. Note that the hardware information and the hardware information displayed when the CMOS is displayed, pay attention to the hardware information and machine configuration displayed during the self-test. Compilament; c. Read the software's guide carefully, pay attention to the environmental requirements of the software. 4) Fully communicate with users: a. Understand the user's usage; b. Phenomenon before the failure; c. What operations do have currently fault. According to the above understanding, it is initially judged to determine the cause of possible failure. 3. Troubleshooting points 1) Check if the user's misoperation causes a. When the machine has crash, blue screen or no reason, first stroke if the user's operation is in line with the operating specifications and requirements, to carefully ask, observe the user's operation method Whether it meets common sense, and is operated by the engineer with the right way, apply the user's machine to see if the user repairs the fault. If there is no, it can be considered to be improperly operated by the user, and the engineer explains and demonstrates the correct operation method. b. If the above operation fault still exists, the available system file inspector checks if the user's machine system has a lost DLL file, and try to recover. c. Note that the user's machine has no rules when crash, blue screen or no reason, and find out the cause of the machine failure (such as the machine starts to stand in a certain period of time). d. By comparing the same, the same flexible machine, see if the file size of the fault is the same or the difference is not large, and the version of the main program is consistent. 2) Check if the virus or antivirus procedure causes fault a. Check if the user's machine is infected, use anti-virus anti-virus; b. Check if the user has two or more anti-virus software, it is recommended that users use one of them And uninstall other anti-virus software; c. Check if there is a Trojan, use the latest version of the anti-virus program to detect Trojans. You can make up for security vulnerabilities in the program by installing patches, or install a firewall. 3) Check if the operating system problem causes a fault a. Check if the hard disk has enough remaining space and check if the temporary file is too much.
Finishing hard disk space, deleting unwanted files; b. For system file corruption or loss, you can use the system file inspector to check and repair; c. Check if the operating system is installed (for Winnt can be started at startup Service pack version, recommended use of SP6; Win2K and WinXP can be viewed in the system properties, Win2K recommends using SP3, WinXP recommends using SP1.); d. Check if DirectX driver is normal, upgrade DirectX version; E. Check if it is correctly installed The driver of the device and the driven version are appropriate. Check that the order in which the drive is installed is correct (for example: first installing the motherboard driver). 4) Check if the software conflict is compatible, compatible with the failure a. Check if the runtime environment of the user application is compatible with the existing operating system (NT / 98 / 2K / XP), can pass the software manual or to the application software web page Find relevant information and view the upgrade programs or patches for this software on the web. b. Available Task Manager Watch whether the background of the faulty machine has an abnormal program running, and trying to close the program only to keep the most basic background program. c. Pay attention to see if there is a shared DLL file in the fault, solve the problem by changing the installation order or installation directory. 5) Check if the hardware setting is incorrect, first, check if the CMOS settings are correct, can restore the default value; b. Check if the hardware is normal, the interrupt has a conflict, such as conflict, adjust system resources (for a certain Some hardware, to read the instructions, follow the instructions to properly set the hardware); c. Remove the hardware drive in Device Manager, reinstall the driver (best to install the correct driver), check whether the hardware driver returns to normal; d. Running hardware detecting programs, such as AMI and other detection hardware failures; e. In software minimum system, re-update hardware drivers, and observe whether the fault disappears. 6) Check if it is compatible problem a. When compatibility issues, check the hardware specifications and standards (such as when using multiple memory, check whether the memory is the same manufacturer, the same specifications, the same capacity, memory particles together) Whether it is allowed to be used together. b. Read the instructions or to the web page to find relevant information, check the software requirements required for the user's hardware, and whether the software environment meets the requirements, whether the hardware and software supports each other. c. Check if the user's system resources have conflicts in the device manager, such as conflict, manually adjust the system source. d. Check if the hardware of the user machine is installed correctly, updates the appropriate version of the device driver (such as some graphics cards with Win2000 or WinXP self-contained public version, can cause certain large 3D games that cannot be running) : Check the maintenance BOM, remove the hardware of Lenovo, check whether the system can work properly, if you can work, it is recommended that the user replaces the hardware or find hardware related information to solve it. 7) Check if a network fault causes a. When the machine is connected to the network, the crash, run slow, blue screen, etc., should first turn off the network, isolate the network environment, observe whether the fault disappears, if the fault disappears, Network problems cause malfunctions. b. Depending on the fault caused by the network problem, it is judged to resolve the network part of the network.
