BTW guys, in case you are planning on sitting in front of a memtest screen for a while:
Depending on which version of memtest you have, you can allocate different amount of ram for testing. Obviously you want to test it all but a single run takes aaaages, so a speedier way to do it is by opening up several instances of memtest and dividing the memory you have to allocate up, by the number of instances. Each instance will put a core under load. Divide memory by four and it will complete tests four times faster!
If you run it from inside an OS, remember that you wont be able to test the Memory currently in use.
Have had a lot of memory issues with a large set of RAM recently given to me for clocking. Such a pain to have it run memtest to check for errors when you have 32gb to get through, so i am bloody grateful that memtest can be run in multiple instances.
If i was problem solving i would only use one instance from a bootable drive (due to OS taking up a portion of the memory to run) but if it is for error finding during clocking, i really abuse multiple memtest windows.
This is mainly to get any hardcore errors off the bat. Gaming/encoding/rendering or whatever the PC is used for should be how you finally check stability.