Memory Test [MEMORY]

Top  Previous  Next

The Memory test, tests the reliability of the RAM installed in the computer. As BurnInTest runs within windows some of the available RAM is being used by windows and any other applications running. Any memory that is not already in active use will be tested by the Memory test.

The Memory test works by writing a pattern numbers in the RAM, then verifying the numbers read from the RAM match this sequence. The pattern used can change automatically from one cycle to the next. Possible test patterns are,

1.Sequence (0,1,2...)
2.Binary 1 (10101010...)
3.Binary 2 (01010101...)
4.Zeros (00000000...)
5.Ones (11111111...)
6.Cell adjacency test

See RAM test preferences.

The Test pattern may be selected to be one of the above test patterns. Alternatively, the default (Cyclic) setting will cycle through each of the test patterns.

The total amount of free RAM is displayed in the Memory Test Window. Some memory is always left available to avoid Out of Memory Errors, and disk thrashing caused by Windows swapping to disk. The MBs Written and MBs Verified fields on the Memory Test Window are cumulative since the start of the test and can be greater than the size of the installed RAM.

For the Memory test, a cycle is defined to be the number of times the above 3 step sequence is completed. The ‘operations’ count represents the number of bytes read or written.

It should be noted that not all RAM faults will be detected by this test. This is especially the case if Windows or the Windows cache is using a large proportion of the available RAM. RAM faults may show up as system crashes or disk errors however. RAM fault detection is improved by running a RAM pre-test, available with the Standard memory test. See RAM test preferences.

 

How the tests work

There are 3 steps that the Sequence, Binary 1, Binary 2, Zeros, and Ones (11111111...) tests goes through. These are:

1/Memory allocation. The test will dynamically allocate and release memory depending on how much is currently available. The amount that has been allocated  and is under test is displayed in the Test Ram field.
2/Writing the test data from the low address to the high address.
3/Verifying the test data from the low address to the high address.

 

The Cell adjacency test aims to find the RAM problem of adjacent memory cells being incorrectly changed when writes occur to a memory cell. A known 8-bit data pattern is written to memory from the high address range to the low address range. Then starting at the low address and testing towards the high address, each  byte is checked that it was not altered by an adjacent write in the previous writing of memory and a new 8-bit data pattern is written. A final pass is then made starting at the high address and testing towards the low address, with each  byte is checked that it was not altered by an adjacent write in the previous writing of memory.

 

Standard memory test

The standard memory is the normal test for testing memory. See the description in the RAM test preferences window for more details.

Torture test (Memory over-allocation & disk swapping test) (BurnInTest Professional only)

The torture test is a multi-process memory test. Multiple processes are started in their own virtual address space and each process allocates and tests a block of RAM. This avoids the problem of virtual memory fragmentation which the standard test can experience trying to allocate a single large block of RAM. Each process runs asynchronously, so writing and reading of various memory blocks will take place at the same time in different processes. The other advantage over the standard test is the possibility to over-allocate the RAM. (The standard test attempts to prevent this to avoid disk swapping). Over-allocation takes place when more RAM is used by the torture test than is currently available in the system. This then results in Windows disk swapping memory blocks into a paging file on the disk. This continual swapping to and from the disk places a very heavy load on the system. The I/O activity on the disk will increase dramatically but CPU load can actually decrease as more and more time is spent waiting for the paging activity to complete. Depending on the level of over-allocation Windows may need to extend the paging file or may even fail as it runs out of available RAM.

Addressing Windows Extension (AWE) memory test (32-bit BurnInTest Professional only)

The Addressing Windows Extension (AWE) memory test allows a larger area of memory to be tested on 32-bit versions of Windows. It requires some additional administrator user rights. It will also only work in Window XP. See the description in the RAM test preferences window for more details. The advanced memory test is only available in the Professional version of the software.

See also

RAM test preferences

Setting administrator user rights