Oct, 4th EDIT -- I have taken out my bad harddrive yet the BSOD's continue. I just got a BSOD with 0x0124 error which usually means hardware, but everything hardware wise has been tested. I got a mini dump and am wondering if it says anything to anyone who can make sense of it... is it drivers, should i just do a fresh install? I still get the random freezes and right click nonsense which makes me still think its an explorer problem. I just recently build this computer and since the beginning I get the same BSOD that does the exact same thing every time other then when it randomly happens. My computer first freezes for about 5 seconds then goes into the BSOD. The error code is a 0x000000f4 (0x0000000000000003, 0xFFFFFA800A911B30, 0xFFFFFA800A911E10, 0xFFFFF80002D83880). When the BSOD attempts a memory dump it never even begins and after about 20 seconds it just restarts. The minidump folder is empty, and BlueScreenView doesnt even show a BSOD happened. After the BSOD restarts, my computer can never boot back into windows. It always says that a drive with an OS is not recognized and I have to completely kill the power to the computer (through flipping the switch on the power supply, not just turning it off) and only then does it boot back into windows. I've searched around and the 0x000000f4 seems to a problem for several different things such as memory, HDD, video cards etc etc. Everything is at stock clocks other then graphics card but problems still persists whether its overclocked or not. I've checked the disks for errors. I've tested the memory with mem test and no errors have come back. I've reset the CMOS battery. I've reseated the RAM. My system specs are: Motherboard: P8P67 (pro rev3.1) CPU: I7-2600K Sandy Bridge Video Card: GTX285 RAM: 8gb DDR3 Gskill (2gb stick each slot) SSD: OCZ Vertex3 (Windows 7 64bit) HDD: WD Cavier black 1TB Other Info: It does tend to happen when firefox is open, but it also happens when its not. Firefox randomly freezes a lot, so i don't know if its not co operating with 64bit or possibly a memory leak as firefox is heavy on resources, but I never had these problems when I was on 32bit.