BSoD hours after clean Win7 install, rig is "seasonally unstable"

[EphemeralDream]

BSoD hours after clean Win7 install, rig is "seasonally unstable"

Performed an "enhanced secure erase" on my SSD and then did a clean install of Win7 Professional 64-bit from Microsoft pressed upgrade discs. Every update installed flawlessly expect Service Pack 1 which had 1 failure. I've also seen numerous apps crash since (mostly IE and chrome). sfc /SCANNOW already showing unrepairable files. BSoD in middle of the night while I was sleeping.


A bit of history, not sure if it is helpful:
Had rig for nearly 3 years, stability issues from the start but goes through periods of stability for weeks to months only to become unstable again. First time I installed Windows 7, it took multiple tries (probably 4+) and kept stopping at "Expanding files..." On a later install to the HDD, I had the same problem. I do not have these problems installing Win7 to the SSD.

Over the three years I've made some changes. Put an SSD as primary, added a MOSFET heatsink, custom CPU cooler, and changed video card. Stability issues persist, sometimes with BSoD errors night after night. Sometimes the instability is "only" constant crashing of Chrome/Opera. System restore has never really helped but eventually the rig returns to a period of stability, typically for a month or two. And then back to unstable.

Some googling encountered another guy with the same RAM and mobo that seemed BSoD free after switching out the RAM to another brand. My g.skill memory is not on the supported list available on the gigabyte website. I've run hours of passes with no errors on the RAM (but only in the first pair of slots). It's also worth mentioning that the RAM is listed as 1.5v, but voltage in the BIOS shows 1.616v


Would like to have a stable machine once and for all as trying to upgrade my way out of it hasn't worked, appreciate any help.

 

[zigzag3143]

Analysis inconclusive.

It is much easier to find patterns, etc, when there are more than one crash dmp.

We prefer you wait until you have at least two so that if one is corrupt the other probably wont be.

 

[EphemeralDream]

After about a month of working off the SSD and an external hard drive that gave me very good stability, I finally reconnected my HDD and problems started quickly. See logs for BSoDs

 

[writhziden]

No .dmp files included. You probably deleted them using CCleaner without realizing it. Please refrain from using CCleaner for the duration of your troubleshooting.


Nevermind, my mistake, the .dmp files were there.


Your crashes primarily indicate hard disk problems. This could mean hard disk corruption, bad sectors, a failing hard disk, Windows files or registry corruption, viruses, or memory problems.

• If you are overclocking any hardware, please stop.
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html (you may need to search for wininit instead of chkdsk).
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run the short and long tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS​
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, uninstall it in device manager and see if the system performs better.
  
  
• Check Windows for corruption. Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to provide us with the sfcdetails.txt file if errors occur.
  
  
• Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan. Also run a full scan with your antivirus software installed on your system. If you do not have antivirus software installed, see the http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627 for better security steps and scanning tools. Make sure to update the security software before running the full scan.
  
  
• 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.

 

[EphemeralDream]

Thank you writhziden for your help and thorough response. I've spent the last day or so going through your tasks and have managed basically every one but memtest which I plan to do tonight. I hope this report to this point is comprehensible.

1. Disk Check - I have a SSD for OS and an HDD with two partitions for games and data
-SSD OS drive - no errors
-HDD - both partitions showed no errors although explorer.exe crashed numerous times while checking the games partition. The games partition test still finished but was not recorded in the log for some reason and the system BSoD when I shut down after the test

2. Sea Tools for Windows
Did three tests on HDD - Short DST, Short generic, long generic - ALL PASS

NOTE: I had to install .Net 4.0 as per the Sea Tools installation which then required some Windows updates. System Update Readiness Tool was listed as an update and I tried running multiple times but it failed. Eventually it disappeared so perhaps the .Net updates cleared some corruption?

3. SFC - ran three times, restarted three times - still shows errors, sfcdetails.txt attached

4. I plan to run MalwareBytes but almost certain viruses/malware are not the issue

5. Memtest to be done tonight

I can't say for certain but the system seems stable at the moment and I haven't had constant browser crashes as tend to happen. Nevertheless, I've attached a zip with the jcgriff file, Performance Monitor report, and sfcdetails.txt

Thanks again

 

[kegobeer]

It looks like your hdd is the culprit. Can you slave it into another computer to see if the BSODs follow it? What's the make/model of the HDD in question?

 

[EphemeralDream]

Nevermind about my system being more stable as there's been appcrashes and one BSoD since, but I do have something with a little more teeth as seen in the thumbnail.

After about six hours of memtesting, 74 errors showed, mainly on test 5 but there is at least one on test 7. Is it possible to scroll? This was done from a USB stick and with all RAM in the system (2x2gigs). I believe this is the same RAMkit here: Newegg.com - G.SKILL 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10600) Dual Channel Kit Desktop Memory Model F3-10600CL9D-4GBNT

Kegobeer, the HDD is a Western Digital Blue 640 and I unfortunately have nowhere else to test it.

 

[writhziden]

At this point, the most important step would be to resolve your RAM errors. 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.

Also, go into your BIOS and post all Voltages (CPU, RAM, NB, IMC, etc.) and all RAM settings (timings, frequency, etc.)

Thanks to Dave76 for help learning RAM Stability


Also, go through part 3 of http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[F5ing]

Not sure if it'll make a difference, but you might check to make sure you're using Memtest86+. There are at least two different strains of memtest86 out there. It appears you're running one without the "+" sign.

 

[writhziden]

Nice catch! Thanks F5ing.

 

[EphemeralDream]

That is Memtest86+, the + just blinks and I snapped a picture when it was gone. Silly feature in my opinion.

Here are my voltage and RAM shots as requested although I'm not very good at interpreting them. From left to right: default voltages, actual voltage?, RAM timings, and a hwmonitor image.


DDR VTT or whatever it's called is not listed although it appears it should be. I ran HWMonitor and saw a VIN at .88V that is most likely the VTT? Also the RAM is rated for 1.5v but there isn't an option to set it below 1.6 manually.

 

[EphemeralDream]

And the requested images from CPUID

 

[writhziden]

Your NB Voltage control is on the outside of the requirement that it be within 0.5 V of the DRAM Voltage. Bump NB Voltage to 1.2 V to go with the DRAM 1.6 V so they are within 0.4 V. (If you cannot get 1.2 V, choose the closest value that is higher, i.e. 1.205 V instead of 1.195 V)

NB Voltage is basically VTT Voltage, by the way.


Post back whether that increases stability.

 

[EphemeralDream]

Your NB Voltage control is on the outside of the requirement that it be within 0.5 V of the DRAM Voltage. Bump NB Voltage to 1.2 V to go with the DRAM 1.6 V so they are within 0.4 V. (If you cannot get 1.2 V, choose the closest value that is higher, i.e. 1.205 V instead of 1.195 V)

NB Voltage is basically VTT Voltage, by the way.


Post back whether that increases stability.

Not to be a skeptic but this review with the same model motherboard shows pictures of the BIOS with both.

I'm referring to the image below. Just want to be sure of this since I've never touched voltages before.

 

[EphemeralDream]

I bumped up the voltage to 1.2 and did a few minutes of memtest test #5 and within 3 minutes there were 21 errors. This is across all 4 gigs, so I guess I'll switch out a stick tonight.

 

[writhziden]

Not to be a skeptic but this review with the same model motherboard shows pictures of the BIOS with both.

I'm referring to the image below. Just want to be sure of this since I've never touched voltages before.

Sorry, I was not as clear as I should have been. There is a VTT Voltage that feeds the memory termination logic. There is also an Intel VTT that provides voltage to the CPU Memory Controller much as the NB Voltage does. Those are the two that are interchangeable. Since you have an AMD board, that is why there are VTT and NB Voltages; your VTT is for the Memory termination logic.

Understanding All Voltage Configurations from the Motherboard | Hardware Secrets

I bumped up the voltage to 1.2 and did a few minutes of memtest test #5 and within 3 minutes there were 21 errors. This is across all 4 gigs, so I guess I'll switch out a stick tonight.

Does not look like a simple Voltage bump is going to resolve the errors. You likely have a faulty module or slot. Let us know how the RAM swapping goes.

 

[EphemeralDream]

Hi all, over the past few days, I've been running a battery of memory tests. Here's my results which seem a bit inconclusive. Also the RAM pairing in my rig is 1+2 and 3+4.

1. RAM 1+2, slot 1+2 - Many errors mostly test 5 and some 7
2. RAM 1+2, slot 1+2 with voltage 1.2 - quickly showed errors test 5
3. RAM 1, slot 1 - 1-2 errors per pass on test 7
4. RAM 2, slot 1 - 18 std passes, no errors
5. RAM 1, slot 3 - 6 passes test 7, no errors
7. RAM 1, slot 3 - 12 passes std test, no errors
8. RAM 1, slot 1 - 6 passes test 7, no errors
9. RAM 1+2, slot 3+4 - 7 passes std test, 20 errors on test 7
bluescreen during windows usage
10. RAM 2, slot 3 - 13 passes std test, no errors
11. RAM 2, slot 3 - 5 passes on Windows Memory Diagnostic extended, no errors

I guess I need to go back and test RAM 2 in slot 1 to make sure it was indeed error-free

 

[writhziden]

Looks like good troubleshooting. Make sure slot 1 is good as you mentioned. Also, you may want to set aside the suspected bad module for now and see if the other module causes any issues.

My guess is RAM 2 is good and RAM 1 is bad. RAM 1 may not show errors on all tests depending on whether Memtest86+ checks the bad parts of the RAM or not. The fact that you had errors at any time running only 1 shows that it is likely bad, but it could also be the slot, as you also suspect.

Nice work!