Mouse still moves but cant click, crashes with code 0x000000f4

[Calbearpig]

My laptop has two hard drive bays. It shipped with a 3GB/s 750 GB HDD. I installed a 120GB Corsair Force GT SSD into the second bay after I got it and did a clean install of the OS onto the SSD without erasing the HDD. I now have the option to boot into either the SSD or the HDD. Unfortunately, the computer freezes with relative frequency when I run off the SSD. The mouse will turn into a spinning circle indicating activity, and I will be unable to click anything in the background. I can still move the mouse, but I can't click anything, and Ctrl-alt-del will not respond. Occasionally, the computer will also fail to boot when I boot into the SSD and stay on black screen before the windows login screeen pops up. If i leave the computer alone for long enough during one of these lockups, it will blue screen and tell me a critical process has been terminated. Did I screw up something with the SSD install process, and would it cause these issues? If not, any ideas what would?

==================================================
Dump File : 042312-14414-01.dmp
Crash Time : 4/23/2012 6:26:33 PM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`0d238b30
Parameter 3 : fffffa80`0d238e10
Parameter 4 : fffff800`033d5660
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc80
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17803 (win7sp1_gdr.120330-1504)
Processor : x64
Crash Address : ntoskrnl.exe+7cc80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\042312-14414-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 292,792
==================================================

In the BIOS, the drives are set to RAID mode (not SAT or AHCI) but I am NOT using a raid configuration (raid0 or raid1).

 

[nsafreak]

In the BIOS, the drives are set to RAID mode (not SAT or AHCI) but I am NOT using a raid configuration (raid0 or raid1).

^^ That is likely your problem. The way Windows handles drives when they're in RAID mode vs SATA/AHCI is very different. Quickest fix would be to change the BIOS settings to AHCI for both drives and do a clean install of Windows again.