Solved Random BSODs after clean installations

[Hatchling]

Hi, I have bought this pc arround 6 months ago and I installed windows myself. Everything worked well, however. I had a little problem with my videocard drivers but I figured it out myself and the pc worked perfectly for 5 months. Arround a month ago I have decided to reinstall windows due to neglacting small viruses and corruptions here and there.
Here is where the problem starts. After a clean install, if I updated windows, I would get random BSODs, arround 2-3 a day. At which point I reinstalled windows again, and again. And I decided not to update anymore. But the thing now is my pc gives me a BSOD even though I refuse all kinds of updates and I can't figure out why. I have tried not installing basic drivers, softwares until a bsod happend. Nothing worked. I am here now asking for help as last resort because I am incapable of figuring this out myself.

The original OS is a windows 7 professional edition 64 bits.
As I said, I have installed it myself.
This version was given to me for free by my university while I used to do computer sciences.
My hardware is arround 6-7 months old.
I have installed this new OS yesterday, 18/06

Any help is appreciated, I am attaching the zip files required in this post.
Thank you.

 

[writhziden]

I would recommend installing all Windows Updates, especially since avoiding doing so is not helping your cause and may actually be hurting it.


Also, remove the Gigabyte utilities. Your Gigabyte Power utility and EasyTune 6 are known to cause problems when out of date as yours are.


Crashes are pointing to memory problems or driver conflicts.

• If you are overclocking any hardware, please stop.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  Once these steps have been followed, it is safe to remove and replace components within your computer.
  
  
• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    View attachment 217282
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset​
  -> Restart your computer.

 

[Hatchling]

Hi writhziden, sorry for taking a long time to post, I had little time and I was waiting to get as many bsods as possible as possible. Thank you for helping me out.
I have used the verifier for the past days and I have had a few bluescreens. I am uploading the crash reports here (I hope it is enough). I tried updating windows numerous times, since it was a very big download I would go do something else and leave it downloading. But when I get home and check on the pc again, boom, theres a nice sexy bsod on screen. It can't stay long without crashing it seems.
Oh, I removed the gigabyte utilities like you suggested.
Tell me if you need anything else.

 

[writhziden]

You should download and install your Windows Updates with Verifier disabled...


Your Verifier Enabled crashes still indicate memory problems. Let us know the results of Memtest86+.

Also, we should check hardware compatibility with your memory modules: Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.


Leave Verifier disabled for the time being. The instructions for disabling Verifier are in my previous post.

 

[Hatchling]

Hey again, I did the memtest overnight and I have got 9 passes (nearing 10!) with no errors to be found. The screenshot you asked is uploaded. Verifier was disabled as you asked.

 

[writhziden]

Compatibility looks good. After you install the Windows updates, let us know whether you are still having crashes.

 

[Hatchling]

Right-o, I will travel for a few days however, so I will take a while to reply though. But im getting to the bottom of this.

 

[Hatchling]

Fully updated, still having crashes

 

[writhziden]

Remove one of your RAM modules and see if you still have crashes. Test the memory slots and modules as follows.

1. Shut down and turn off your computer.
2. Unplug all power sources to the tower (unplug the power from the outlet/surge protector or PSU).
3. Hold down the power button for 30 seconds (for your safety and the safety of the components) to close the circuit and drain all power from components.
4. Remove the casing.
5. Remove all but one memory module making sure you are grounded while doing so.
6. Replace the casing and put the remaining memory modules in a safe, static free environment.
7. If the problem persists, repeat steps 1-4 and move the memory module to another slot (while staying grounded, of course).

Do this until all slots have been tested. If all slots fail, the memory module may be bad. Test with one of the remaining modules. Continue one module at a time in one slot at a time until you find a good module and good slot. Test remaining modules in the good slot, test good modules in other slots to find bad slots, etc.


Test by doing your normal routine in Windows for twice as long as it takes to get a crash or until you get a crash, whichever comes first. You can also test by doing the tasks that generally cause crashes.

 

[Hatchling]

After a long time of testing looks like it really was a faulty memory. Weird since memtest didn't point any problems at all. Well, thank you for your help gentlemen, I think this case is closed.

 

[writhziden]

Glad to see it solved!!

Also, in case you are interested, here is some further reading about RAM issues: Finicky RAM.