The easyest way is to just copy stuff to the RAM-disk till it is full. If your miggy does not crash, your RAM is OK.
A bit has two possible values, 0 and 1, on and off, so if you have a bad bit in your RAM, there only really exists a 50% possibility the contents actually being corrupted. Not only that, but you are not reading back the data to verify the data is correct.
Ideally what you want is a routine that walks through the bits testing each one individually, reading back the value of the Byte, to make sure each bit operates correctly independently. It is very important to test each bit in both ON and OFF states and to make sure that bit is not "stuck" to another bit.
0000 0001
0000 0010
0000 0100
etc...
I wrote souch a routine to test a custom ARM based heldheld terminal. The engineers who designed the hardware defined the memory testing algorithm for me. There was more to it that that, but this was around 10 years ago. They called that technique "Walking ones". That much I remember.
