BSOD While Gaming - Black Ops 2 & BF3

I've done everything...spent hours/days trying to figure this out. I've had a friend (who knows Windows far better than I do) look at the files and he is stumped as well...

I agree with Arc's initial diagnosis. The 0xF4 bugchecks are being caused because a device that was used (most likely a storage device) to transfer data to/from RAM disappeared, as in it was no longer responding. Almost always this is due to a bad storage device, or some problem in the storage controller on the mobo.

I noticed you said you've yet to reconnect the HDD and run Seatools. Please do those two, running Short DST, SMART (if available) and Short Generic tests on the drive. Also you will want to open up CrystalDiskInfo and provide us a screenshot of the results.

Analysts:

0xF4 with C0000006 (problem with memory-to-disk I/O). Raw stack shows C000000e (device not found) errors.

I've reconnected the HDD already and ran the long test on Seatools...I'll run those other tests and let you know. I'll post the Crystal Disk info later today...

Thanks...

Question: So the "dates created" all being the same on these errors with the modification date being in the present doesn't mean much? Also, while I've uninstalled/reinstalled the game, Black Ops 2 is now the only program involved in these crashes. Also had an "Unhandled Exception" last night...

AND, at one point during attempted play, the screen just went black and I heard the computer beep...

Crystal Disk screenshot is attached. All other tests were completed and passed...

Had another crash this AM...This one was a stop 0x0000007a with ntfs.sys failure? Again, same creation date in 2011 but modified this morning...

So the system beeped? Do you remember how it beeped? As in was it a single long beep, 3 consecutive short beeps, 1 long, 2 short, etc.? POST beep codes like that alert to hardware failure and kinda like morse code it will inform you by the beep what it is. However every system's POST beep code is different, which means you will need to consult your system manual for the list of POST beep codes and compare with what you heard.

Something tells me it actually may be the video card at fault here, given the screen going black prior to the beeping. I have yet to understand the mechanics behind it thoroughly (it may involve DMA from RAM-to-Video) but I think the 0xF4 bugchecks may also be involved. I however would need a kernel dump from one of those crashes to verify further. But that doesn't seem to coincide with the NTFS errors you're getting recently. No matter, the beep code is our best evidence right now to determine which hardware is failing, so grab your system manual, look it up and get back with us on it.