Frequent BSOD and rebooting, memory dump?

Day 1 Update: I took out my other hard drive and left my computer running. Normally I would have had a restart/BSOD by now. I feel you are probably right about it being the hard drive. Will be sure after another day or two.

I do not. Guess I'll give you that update in a week then. Thanks for everything!

... And I'm back. Somewhere along the line I was using my computer and it freezes on me forcing me to restart. Right before the login screen (directly after the windows logo), my computer hangs.. and my monitor self test comes on meaning my computer isn't booting to windows. Joy. So I restart my computer after awhile of waiting, it does the same thing. Reboot again with windows 7 disk, and try to run a repair on the drive, it says it can't find anything wrong with the drive. Try a memory repair, it reboots instead of going into the memory repair test thing, goes past the "press any key to boot from disk" message, and hangs on an error message screen that says "STOP: c0000006 The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x."

A couple more tries with the windows disk yield no results, so I format. Formatting gets me into windows, but whenever I restart the computer after downloading drivers, it repeats the same thing (hanging right after windows logo). The only way to get past that is to format again. So after formatting a 2nd time, here I am. Crystal disk info is in the blue, and telling me my drive is in "good" health, and Chkdsk scans aren't revealing anything. Currently running Seagate tools Long Generic Test, and it's still running. It even came up with a pop-up message telling me the test is running longer than usual. Googling this issue reveals that people are saying it's a hard drive issues still. What do you guys think? =/

not other than the one I took out before, which crystal disk read as "caution" in the health department.

All your crashdumps and your symptoms are common with either a bad hard drive or a bad drive controller on the motherboard (or PCI card depending what your drives are connected too). The I/O NTSTATUS error that occurred during a paging operation is also conducive of this.

The only way to discern which is causing this is to do hardware swapping, preferably with just a drive you know is in good condition. If the system is stable using that drive, the drive itself was bad, otherwise if still experiencing problems the mobo is the cause. Hard drive tests are not a guarantee on a hard drive's health, nor is SMART data also completely dependable.

I did notice on your CrystalDiskInfo that your drive's SMART data is reporting that a number of Command Timeouts have occurred (11 to be exact). This is caused by a drive not responding properly to commands issued by the PC and are conducive of either a bad hard drive, a bad/insufficient PSU, or a damaged or poorly connected data cable.