you did that off of the "boot menu"?
if you really really really want to test the RAM you're talking about several hours, like 6
. if you don't have the patience, which at times i lack myself, then start the test before going to bed and look at the results when you wake up. and maybe consider doing a "check disc".
BUT at the risk of contradicting the above . . you didn't do anything that will harm the hardware
by changing the CMD rate; the T1/2 command. here is a tutorial on RAM timings
to put it generally the CPU, RAM and HD (or SSD) communicate back and forth; you tell the CPU a need to execute a command (run an application), the CPU tells the RAM i need the information to execute a command so the RAM retrieves it from the HD and then feeds it to the CPU to process. if the CPU chances the information (data) it gives the changes back to the RAM which writes it to another part of the stick and may erase the old
if the change(s) is/are permanent and then the RAM will write the permanent change back to the hard drive ( i am not including the swap file here).
so if you change the CMD rate you can be telling the RAM to go faster at retrieving/writing/rewriting data than it could and cause corruptions (bad data). if those corruptions make it back to the HD then it will be "permanent" until you erase/change it off of the HD. corrupting data causes inconveniences but won't hurt your hardware. when it comes to hardware, increasing voltages too much is what will harm it not timings or speed (that causes corruption).
- i am sure there are others that could give a better explanation but i think this covers the simple basics correctly.
edit:typos. Edited by looniam - 8/14/13 at 6:01pm