Experience of weird server faults

I recently encountered a weird server fault and it took a lot of effort to solve it. I 'd like to share it with you.

Server fault

An Intel Pentium 3/550 server has recently experienced several blue screen crashes. Upgrade the memory from MB to MB of normal memory) and select Load in the system CMOS settings. The optimal parameter settings are used to detect each memory unit. A strange Server failure occurs. When I start the system, the memory check is normal, but the screen prompts that I have to re-SETUP and press the specified [F2] key, but the machine crashes. I have a memory stick. Who is causing this? Why? What about normal memory detection?

Server troubleshooting

If a server fails, it must be solved, even if it is a weird server fault. According to the idea of narrowing down the fault source, swap back the original memory, and gradually remove all parts of the drive, hard disk, optical drive, etc.), but this strange server still exists. The analysis may be related to system SETUP settings, especially the settings for detecting each unit in the memory. As a result, the battery is unplugged, and the battery plug-in pin is discharged, which does not work. It seems that this weird Server failure is really stubborn. Later, find the motherboard to clear the CMOS patch cord settings, change the pin line from 1-2 to 2-3 for a while, and then restore the original position. Editor's note: Do not unplug the battery easily, but find the CMOS patch cord to clear the patch cord ). Upgrade the memory again, adjust the cmos setup settings, and pay special attention to the memory detection. The system is completely restored to normal after the detection of every MB.

Server fault experience

Later, I analyzed that the root cause of this weird Server failure was that the server's memory was set to ECC with verification by default), because the common memory without verification was used, in the system, each unit is set for detection, which leads to the above fault. The exclusion method is to clear the CMOS settings and adjust the relevant parameter settings. In addition, there are usually two optimal parameter settings for CMOSSETUP loading: one is the BIOS optimization parameter, which has the best stability and the other is the SETUP Optimization Parameter to optimize the entire system, however, system support is required, and its stability cannot be guaranteed. Therefore, when the system fails, load the most stable parameters first, solve the problem, and then recover.

1. Server troubleshooting methods Overview
2. You don't have to worry about troubleshooting server faults.
3. Completely resolves DHCP server faults