Analysis of the phenomenon of computer failure caused by memory
Memory failure is a common fault of computer hardware, mainly for the following reasons
1. Memory and motherboard compatibility is not good. Plug the memory into other motherboards, and it will be stable and reliable for a long time. Plugging other memory into the faulty motherboard also runs reliably and stably, and no alarm appears. But when you put the two together, the "Di Di" alarm sounds. Replace the memory or motherboard to solve.
2. The memory slot of the motherboard is of inferior quality. The performance of "Di Di" alarm sound appears when replacing multiple brands of memory. Occasionally, there is a certain memory that does not alarm, but it may alarm after shutdown and restart. This kind of failure mainly occurs on the low-end motherboard. The reason is that the memory slot of the motherboard is of poor quality and can only be replaced by replacing the motherboard.
3. Memory chip failure. Such a fault is relatively serious. The host can find that the memory has an error defect during the power-on self-test, and cannot pass the self-test and issue a "Di Di" alarm sound. This type of fault requires the memory to be plugged into other hosts to check for the same "Di Di" sound. If there is, you can conclude that there is a problem with the memory; if not, it may belong to the first or second reason above.
Memory is one of the most important accessories in a computer. Its role is unquestionable. What are the most common faults in memory?
Common fault one: no display at boot
This type of fault occurs because the memory module is in poor contact with the motherboard memory slot. Just rub the rubber finger back and forth with the eraser to solve the problem (do not use alcohol or other cleaning), or the memory is damaged or Problems with the motherboard memory slot can also cause such failures.
The main unit speaker will beep for a long time (for the award bios) because there is no display failure due to the memory stick.
Common fault 2: Windows registry is often damaged for no reason, prompting users to recover
Such faults are generally caused by poor quality of the memory modules, and it is difficult to repair them, only one way to replace them.
Common fault three: windows often automatically enter safe mode
Such faults are generally caused by incompatible motherboards or memory modules. Commonly used in high-frequency memory for some motherboards that do not support this frequency memory, you can try to reduce memory reading in the cmos settings. Speed can see if the problem can be solved. If not, then only replace the memory module.
Common fault four: random crash
This type of fault is generally due to the use of several different chips of the memory chip, due to the difference in speed of each memory bar to cause a time difference, resulting in a crash, this can be resolved in the cmos settings to reduce the memory speed, otherwise, only use the same type of memory . Another possibility is that the memory module is not compatible with the motherboard. This kind of phenomenon is generally rare. In addition, it may be caused by poor contact between the memory module and the motherboard.
Common fault five: the system resources are reduced after the memory is increased
This kind of phenomenon is generally caused by the incompatibility between the motherboard and the memory. Commonly used in high-frequency memory memory modules are used on some motherboards that do not support this frequency. When such a fault occurs, you can try to use it in coms. Try to set the memory speed lower.
Common fault 6: Frequent memory shortage prompts when running certain software
This phenomenon is generally caused by insufficient space in the system disk. You can delete some useless files, and leave more space. Generally, it should be kept at about 300m.
Common fault seven: when booting from the hard disk to install windows to detect disk space, the system prompts insufficient memory
This type of failure is generally caused by the user adding the emm386.exe file to the config.sys file. Just mask it to solve the problem.