Windows 7: Random (so it seems) BSOD

All -

My system specs on the bottom left will tell you all about my machine, but the BSOD steps says to add additional information, so:



1. This concerns Win 7 x64 SP1 (I have not had any BSOD since I updated to SP1, which I believe was yesterday, 3/10/11)

2. Original OS installed on the system was Windows XP Professional x86. The hard drive was long formatted prior to installing Windows 7 x64. The motherboard, CPU, RAM, and graphics card has changed along with the OS change to Windows 7 x64. This was purchased through a student upgrade program through Microsoft and is genuine.

3. RAM is about 6 months old, motherboard is just as old, and the processor is about 1.5 years old. I'm not exactly sure as I bought it off of a friend.

4. OS has been installed for about a year and a couple months.

I don't seem to find a pattern to the BSODs. I am overclocking from 3.0GHz to 3.5GHz, with temps around 45*C-50*C. I haven't noticed any ill issues from doing this. My friend ran this processor at 3.5GHz all the time without any issues, so I assume it's not that.

I have attached the required folder and perfmon file. Thank you for any and all help.

rule 1, when overclocked and getting bsod's the first thing you do is remove the overclock.
A driver change, new software, new operating system, climate change, dust in the box, system age. All kinds of things can make a clock that was once stable start failing.

The BSODs occured before I changed to new hardware and overclocked. Also, the BSODs occurred before and after the overclock. But, I understand your logic behind that.

well I located no minidump files in your upload. So I can't really get anymore specific.

By "minidump" do you mean the file dump Windows creates due to a BSOD? I know I've had BSODs and I'm not sure why the file wouldn't show up.

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

The procedure:

* 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.



To ensure minidumps are enabled:
** Until a .dmp file is generated, the Minidump folder may not exist.**

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

If you are running CCleaner - make sure it is configured to not delete MiniDump files.

My minidump folder is empty. Programs I am running which may erase this information (Just listing some I think may effect this stuff):

iolo System Mechanic
McAfee 2011

I don't think I have anything else running or installed which may effect this folder. I do have Spybot Search & Destroy, but I don't think it goes anywhere near the dump files. I can tinker with McAfee and System Mechanic to see if they are erasing this information after "x" number of days, but beyond that, I don't know how to stop it from happening.

Uninstall Spybot Search & Destroy. Get a BSOD crash and go check if there is a dump.

Spybot is now uninstalled. Are you asking me to post the minidump the next time I get a BSOD?

Wait... this is a kernel memory dump. Look for C:\Windows\MEMORY.DMP and upload that file.