Well, I ran sfc/scannow and it says "Windows Resource Protection did not find any integrity violations."
It seems to happen randomly, sometimes in a game, sometimes on the desktop. Sometimes it has a BSOD other times it just straight up freezes.
@Nuke, I have on multiple occasions removed and replaced the RAM modules, I have tried pressing them in further to make sure they are properly installed and tried using a different brand/model modules. I am running 12GB RAM (3X4GB) 1.5v (Core i7 960 likes this voltage i hear, not 1.65v). I think it unlikely that the RAM is bad because it also had issues with the other RAM unless I have a bad module in both the Corsair and the Patriot options.
My temps are fine, no spikes or apparent correlation with the BSOD screens. I get BSOD when on the desktop processor at idle at around 45-50 degrees C (remember this is an i7, they tend to run on the hotter side) and when under load at 75-80 degrees C (again this is below the i7 100 degree max). My processor (Core i7 960) is overclocked to 4Ghz from stock 3.3Ghz (Yes I backed off my OC to stock speeds BSOD still happens).
My graphics cards also run within specified temperature ranges (GTX 560 Ti SLI). Usually my GPU 1 Temps are 10-20 degrees C higher than my GPU2 because of the lack of space between the cards (Cannot put GPU 2 onto a lower PCI slot due to the power supply blocking it so I have to run my SLI setup with them right next to each other). GPU1 tends to run at between 70-80 degrees C under load and 55-60 degrees C at idle, and GPU 2 runs at between 60-70 degrees C under load and 45-50 degrees C at idle (dangerous temps for the GTX 560 Ti is 90+ (max 100 degrees C)). My graphics cards are overclocked to 1Ghz Core Clock from stock 850MHz (technically 822MHz, but my model apparently came from the factory with a modest OC) (again I backed of the OC to stock and BSOD still happens).
Because I backed off my overclock to stock and the problem still exists I put my settings back because I don't think they are related.