1 Overview
A small problem in system memory can cause problems for the entire computer. For example, when opening a file, it occasionally prompts that the file is damaged, but there is no problem when opening it later, or a program fails to respond inexplicably, and prompts "0X00000000 memory referenced by the 0X???????? instruction, this memory cannot be written". ...., have a lot to do with the quality and compatibility of the memory. We can use memtest to test whether it is a memory problem.
A big problem with testing system memory is that most of the memory is used by the BIOS and the operating system. But when testing memory, the most important thing is to test these places. Like other tests, memtest cannot test 100% of memory, but memtest can test more parts than other tests because memtest does not require an operating system. The advantage of using the memtest boot CD for testing is that it can be tested regardless of whether the operating system is installed or not.
2
Download the source package of memtest from the attachment, install the dependent packages (glibc-devel.i686, etc.), and execute the following commands.
[root@localhost opt]# tar xvf memtest86+-5.01.tar.gz > /dev/null
[root@localhost opt]# cd memtest86+-5.01
[root@localhost memtest86+-5.01]# make
[root@localhost memtest86+-5.01] # mv memtest.bin /boot/memtest
reboot the system, and press the c key on the grub/grub2 interface.
If using grub, test as follows.
grub> root (hd0, x) //The partition of the directory where the memtest file is located, where (hd0,0) corresponds to /dev/sda1, and so on.
grub> kernel /boot/memtest //If there is a boot partition, use kernel /memtest
grub> boot
If grub2 is used, press the method to start the test.
grub> set root=(hd0,msdosx) //Here, (hd0,msdos1) corresponds to /dev/sda1
grub> linux /boot/memtest or linux /memtest
grub> boot
A small problem in system memory can cause problems for the entire computer. For example, when opening a file, it occasionally prompts that the file is damaged, but there is no problem when opening it later, or a program fails to respond inexplicably, and prompts "0X00000000 memory referenced by the 0X???????? instruction, this memory cannot be written". ...., have a lot to do with the quality and compatibility of the memory. We can use memtest to test whether it is a memory problem.
A big problem with testing system memory is that most of the memory is used by the BIOS and the operating system. But when testing memory, the most important thing is to test these places. Like other tests, memtest cannot test 100% of memory, but memtest can test more parts than other tests because memtest does not require an operating system. The advantage of using the memtest boot CD for testing is that it can be tested regardless of whether the operating system is installed or not.
2
Download the source package of memtest from the attachment, install the dependent packages (glibc-devel.i686, etc.), and execute the following commands.
[root@localhost opt]# tar xvf memtest86+-5.01.tar.gz > /dev/null
[root@localhost opt]# cd memtest86+-5.01
[root@localhost memtest86+-5.01]# make
[root@localhost memtest86+-5.01] # mv memtest.bin /boot/memtest
reboot the system, and press the c key on the grub/grub2 interface.
If using grub, test as follows.
grub> root (hd0, x) //The partition of the directory where the memtest file is located, where (hd0,0) corresponds to /dev/sda1, and so on.
grub> kernel /boot/memtest //If there is a boot partition, use kernel /memtest
grub> boot
If grub2 is used, press the method to start the test.
grub> set root=(hd0,msdosx) //Here, (hd0,msdos1) corresponds to /dev/sda1
grub> linux /boot/memtest or linux /memtest
grub> boot