30GB SSD with Windows 7 install is super tight, especially with 8GB RAM wanting to create a swap space of up to 12GB!!!
How much free space is on the SSD? Have you ever pointed swap space to be on the 80GB drive to where removing the 80GB drive and introducing the 2TB drive now leaves the SSD at C: with a broken/no swap space allocation?
Before updates and other software installed to my recent Windows 7 Home Premium 64-bit install, it consumed 17.6GB for Windows and up to 6GB for the swap space of my 30GB SSD.
I have an older dual-core Athlon 4450B 2.3Ghz system with Biostar MCP6PB M2+ motherboard that also is running with a 30GB Corsair SSD performance upgrade, and I got this SSD cheap off of newegg as a refurb for $30 and it works well, however it is a tight install for Windows 7 64-bit using up about 23GB of the 30GB leaving 7GB free after fully patched and a few programs installed to C: I ended up putting my old drive a 164.7GB drive that is a SATA I Hitachi HDD in as a slave drive at D: and moving my swap space to be on D: vs C: so that the 6GB of swap space was on D: vs C: and this way I had 7GB free vs just 1GB free on C:. And your system with 8GB RAM, I can see you running into issues with no room for swap space on that SSD at C: and so you may have to remove RAM to get the system to boot at say 4GB of RAM, and then allocate swap space to be on that 2TB, and then shut down and add the other stick back to have 8GB RAM, and the 2TB drives swap space should be set to Windows Managed and grow to the size it needs to be.
If your running into this swap space issue this will fix it!
BTW: The Corsair SSD has a neat statistic in the SMART data to know how many READs and how many WRITEs the drive has performed since installed. I monitor my drive with Crystal Disk occasionally to check on the SSD health and the HDD health and this was a neat feature that you can keep track of how much use the drive has not in just power cycles and operating hours, but also you are able to know if you are writing too much to this C: drive SSD to which you can redirect the program that writes often to the HDD instead to conserve the life the SSD by limiting the write cycles to the SSD and sending them to the HDD that is best for frequent writing and deletion tasks, such as video editing etc which if one process that I have that I am working with large files written, editied, and the final result saved and the massive source deleted after such as is in the case of using FRAPS to record game play to share with others and then compress it to smaller format and make a 17GB file size down to 600MB in the end with VirtualDub64.
I would also download and run Crystal Disk on your drives to make sure that all is well. It will bring to your attention any problems detected with SSD or HDD's. I would use the portable version though vs the one that has the installer. There is no need for it to be anchored to Windows install when it will run the same in the portable version. * I try to avoid programs that anchor to installs when there is a portable version available to keep the install as clean as possible when so many are trying to slip in toolbars and other unneeded software as part of their installs these days.
Edited by goldfist, 04 January 2014 - 04:52 PM.