Alright, the blue screen .dmp files are pretty general and are hard to narrow down the problem. I'll have to ask some questions to determine how to proceed from here.
Are you running a laptop or a desktop?
Is this a pre-built machine from a vendor (HP, DELL, SONY, LENOVO, ETC.), or was it custom built?
Have you added any hardware to the machine recently that may have been added around the time the problems started?
Are you overclocking any hardware?
Okay this is a custom built desktop PC that was made about 1 year ago. I've just recently started getting BSOD messages about 1-2 months ago but then was kind of dealt with by cleaning out my computer. About 3 weeks ago, I started getting more and more BSOD messages that had to deal with memory corruption and all that stuff but I did what I was told and nothing came up as an error. So I did a fresh install about 2-3 weeks ago and got a couple of BSOD messages after the fresh install but then after that I was free from BSOD until the day I made this thread. No new hardware was installed at all during that whole time. Nothing is overclocked, BIOS values are at default.
I've tried placing RAM sticks in different slots, made sure the temps are acceptable and not overheating. At times I would be able to play a game without BSOD but then afterwards it would BSOD a couple of times the next day.
I just noticed that in my event viewer, I get an error saying "Session "Microsoft Security Essentials OOBE" stopped due to the following error: 0xC000000D". I've just done what they said to get rid of this error. Could this have anything to do with my BSOD even though my dmp files don't specify it?
Did you do any registry cleaning between the time you did a clean install and the BSODs started?
It's possible the registry has been compromised and is causing your crashes. Normally, CCleaner is safe to use, but it does cause problems on some systems. I used it once on a system and the system would not even boot into Windows other than in Safe Mode. I had to restore the registry from the backup I made before using CCleaner. Over the past year, I've learned to avoid any registry tools and rely strictly on manual cleaning when actual problems pop up.
If you encounter registry errors in the future (which are uncommon in 7), please visit these forums and ask for help and instructions in fixing them rather than relying on an automated tool to do the work for you. There is too much risk with automated registry tools.
As to your current problem, disable Verifier and run through any Win7 Basic Troubleshooting Steps that you have not yet tried.
If you are concerned about any possible hardware problems, check Hardware Diags for diagnostic tools for basic hardware. :)
Alright I will look into this.
In your opinion, do you think I should do another fresh install or would a repair install work just the same?
A fresh install guarantees any system/registry corruption is a thing of the past. A repair install may fix the problem, but is not guaranteed. The repair install is usually suggested first as it re-installs Windows system files and fixes most issues without sacrificing user files and programs. It is really up to you which to do. Typically, we recommend a repair install first, and then if that does not resolve problems, we will recommend a clean install as a last resort. If problems persist after a clean install before any user programs are installed, the problem can be narrowed down to hardware.
Alright I will try the repair install first and see if I get any BSOD messages, I won't use any registry cleaners this time around. haha
Quote