A couple BSOD in the last few days.

I believe two of them happened while playing Bad Company 2, and one happened while sitting at my desktop.

I ran a Memtest for 2 passes (Became impatient :P) and it came up with no errors.
Tried stressing out my video card, got up to 100c over 15 minutes with no errors.

My computer is a about 2.5 years old, haven't really had any issues with it until now.

Windows 7 x64 OEM
Intel Core i7 920 @ default clocks
6gb PC12800
Asus P6T Motheboard
Nvidia GTX 285 Graphics
120GB OCZ Vertex 2 SSD
1TB WD Caviar Black

I don't know if it matters but: G15 Keyboard, G500 Mouse, 1TB WD External

Windows has been on the SSD since December 2010

Well, just bsod'd again. It was a little different from the other 3. I was browsing the internet and all of a sudden my Chrome window froze. I tried to close it stopped responding. Then I tabbed to a My Computer I had open, it froze as well. About 10 seconds later the whole computer locked up and I got a blue screen for about 1/10th of a second and then it shut off.

Upon rebooting I got the Bootmgr missing screen. Rebooted into bios and saw that my ssd wasn't listed. Opened the case up and unhooked/rehooked it up and now it's working again. So now I wonder, is my sata cable bad? My sata port bad? My ssd itself bad? Or was this a totally unrelated BSOD from the previous 3?

Its a sign of defective hardware
Stop 0x124 - what it means and what to try

Run Prime 95 to test your CPU. Carefully the instructions in this tutorial: CPU - Stress Test with Prime95. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results.
ASACPI.sys the 2005 version is a huge cause of BSODs

   Information

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005)

Code:

ASACPI.sys        fffff880`06f5f000    fffff880`06f67000    0x00008000    0x42476c4c    28/03/2005 06:30:36

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8005f5a028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fe000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000040014a, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`03172b58 fffff800`02e27a3b : 00000000`00000124 00000000`00000000 fffffa80`05f5a028 00000000`fe000000 : nt!KeBugCheckEx
fffff880`03172b60 fffff800`02feb563 : 00000000`00000001 fffffa80`05d138e0 00000000`00000000 fffffa80`05d13930 : hal!HalBugCheckSystem+0x1e3
fffff880`03172ba0 fffff800`02e27700 : 00000000`00000728 fffffa80`05d138e0 fffff880`03172f30 fffff880`03172f00 : nt!WheaReportHwError+0x263
fffff880`03172c00 fffff800`02e27052 : fffffa80`05d138e0 fffff880`03172f30 fffffa80`05d138e0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`03172d50 fffff800`02e26f0d : 00000000`00000008 00000000`00000001 fffff880`03172fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`03172d90 fffff800`02e1ae88 : 00000000`00000000 fffff880`0316a180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`03172dc0 fffff800`02edc5ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`03172df0 fffff800`02edc453 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`03172f30 fffff800`02e2479b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`03192c70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!KeQueryPerformanceCounter+0xa7


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

Followup: MachineOwner
---------

Yes, I had the 2005 asacpi.sys and I've updated it and now have a 2009 one.

I've been busy so I haven't had an opportunity to do the other stress tests yet, but no more bluescreens since updating that file thus far.