Windows 7: Clean Win 7 install on new SSD, BSOD out of nowhere, previously stable

Just added a 120gb Patriot Pyro SSD, replaced existing ram with 16gb Patriot DDR3-1333 Kit, and did a clean install of Win 7 Ultimate x64 on my Corsair H50-cooled Phenom II X6 1055t/ Asus M4A89GTD PRO/USB3 machine. Previously was running at 3.8ghz stable. After overclocking from scratch was able to get to stable 3.8ghz clock with no errors or overheating after 12 hours of prime95. Dialed back to 3.75Ghz for peace of mind. Everything was going great, then suddenly BSOD.
Any and all help is appreciated!



Windows 7 Ultimate 64bit Clean Install 04/25/2012
Full Retail
Entire build well under 2 years old
See attachments.

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP


We could also use some system information, which you can get easily by running msinfo32.
To do that go to start>run>type msinfo32>enter

When it is finished running go to file>save>name it and upload to us here.


You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

Quote:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

Quote:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

Let me also add:
Die Gedanken sind frei.

Die Gedanken sind frei - Wikipedia, the free encyclopedia

Hey, thanks for the quick response, sorry I completely forgot to attach the files! I have attached them now. As far as the overclocking is concerned, everyone tells me that its no problem to run this processor at 4ghz with proper cooling and I ran it for well over a year 24/7 at 3.8ghz, the only substantial hardware change was going from using one of my caviar drives as the system drive to using this new patriot pyro ssd, and switching from 4GB(2x2GB) Patriot DDR3-1600 to 16GB(4x4GB) Patriot DDR3-1333. One thing there I thought might be the culprit is that I was previously underclocking the old ram at around 1450 and am now overclocking the new ram around 1450. In retrospect I was wishing I had purchased 16GB DDR3-1600 instead of 1333 for this reason, but it seemed to be very stable as I said besides this random BSOD I haven't been able to make it crash or throw an error in all the stress testing I tried with prime95 and AMD overdrive. Thanks again for any help and let me know if there is more info needed.

Please explain to us the significance of your comment in relation to this BSOD thread.
TIA.

Two of the crashes were related to USB, and two to Bitlocker. I am wondering if you are using bitlocker on an external USB drive.

I would do the following. De-crypt and turn off bitlocker.

Run a system file check to verify the OS.

Were it me I would return the OC to stock to test, but hey its your crashes.


SFC /SCANNOW Command - System File Checker

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

Has nothing to do with the thread, but rather as a predecessor of the Bill Watterson quote.

And the relevance is?

You rock man, I bet it had something to do with a funky old harddrive I had attached to the machine at the time through a USB-sata interface. I never intentionally enabled bitlocker, is it enabled by default?
Anyway, thanks, glad to know it is likely not a processor or memory issue.