Repeated BSOD With Error 0x00000124

My computer has recently been "randomly" giving me a BSOD. Now, I am pretty sure it is happening because I also recently overclocked my cpu, however, I did have problems before overclocking it (although not as often). I find my computer tends to BSOD either overnight, when I only have Folding@Home running, or during the day when all I have running is Chrome (F@H is running, but paused). I have also noted that my gpu (1x GeForce GTX 560 Ti) almost always fails while running F@H in the first 24hrs the system is up. However, my main concern is the BSOD.Now the reason I stated that I have had problems before oc my cpu is that ever since I first powered it up nearly 10 months ago I have had problems with the computer freezing on me. Note this was before I oc my cpu, and even before I installed F@H. Originally I thought it might be bad memory, but testing has ruled this out I just restarted my computer, and it now only detects 4.00 GB of installed memory, when it should detect 8.00 GB. The system will hang, sometimes for a few seconds, but most often for a couple of minutes, before suddenly "fixing" itself. This has, on occasion, led to a BSOD, though most of the time it resolves itself. Also, on occasion it doesn't fix itself and I have to do a hard reboot. After a while I decided to have task manager open on my second monitor at all times so that I could monitor the cpu usage and memory, incase something odd happened when it froze. Doing so, I noticed that every time the computer froze, all four cores of my cpu would shoot up to 100% and then drop back down after the system resolved itself. However, memory usage never changed (note this was also done with F@H not running). Also, the source of the freezing seemed to change. Sometimes my monitors would go black for a few seconds and then everything would come back. A message would pop up on my task bar stating something along the lines of "your graphics display driver/kernel has crashed and successfully recovered." Other times, a window would pop up stating that "the memory instruction could not be read" and giving me some error code. Still other times the system would resolve itself and nothing would happen, no error message or temporary black screens.

- Windows 7 Home Premium 64 bit Service Pack 1
- Original installed OS
- OEM full retail (OEM I installed)
- System is about 9-10 months old
- original OS installation (9-10 months old)