Solved multiple BSOD over last few days

[mattr]

Windows 7 64-Bit Home Premium Edition (bought from newegg for pc builders)
Intel i5-2500K 3.3GHz
GeForce GTX 560 Ti
8GB Ram

Built this computer just a month or two ago.

I've been experiencing BSOD over the past few days at random points in times. Yesterday, I was listening to music on Spotify, downloading data on the SWTOR launcher, and surfing the web on Chrome when BAD_POOL_HEADER popped up. That was the only case where I remembered what the error was.

I've attached the needed files.

 

[writhziden]

The BAD_POOL_HEADER crash shows Spotify as the application running during the crash. That may not mean much. Your other crashes indicate 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).
  
  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.
  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 210261
  • 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.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  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.

 

[mattr]

I ran memtest86 for more than 12 hours. I know it recorded over 4 million errors, but I thought it'd store the results somewhere so I didn't write everything down. I'm not overclocking anything. After the memtest, my computer loaded into Windows Repair, but it ran into errors like: "The instruction at 0xfabd2b54 referenced memory at 0x00000000. The memory could not be read." and then had to quit.

 

[James7679]

Okay, over 4 million errors? The answer should be clear. You need to run the sticks individually, and in each slot to confirm if any of the sticks are good, and to verify integrity of the slots. Also, please do us all a huge favor and update your System Specs.

 

[mattr]

i will take out one stick of ram and run the tests again.

what am i looking for during the tests?

p.s. i've updated my system specs.

 

[James7679]

errors during the test mean either the RAM is bad or the slot is bad. In most cases it is the RAM. But swapping the sticks that get no errors, to other slots will verify that the slots are good.

Thank you for updating your stats.

 

[mattr]

how many passes should I do?

 

[James7679]

As soon as you start to see errors, you can stop. If you are not getting errors, do 11 passes, then call it a day. This is time consuming, so be patient.

 

[mattr]

so, lets see if I get this right.

take out 1 stick, test it. If I see any errors, take out the stick, put in the other one (same slot) and test it. If I see any errors, put it in another slot and test it again. If I see any errors, swap it with the first stick in the 2nd slot and test it.

Pretty much, try all the combinations and see if any combination results in 0 errors. That will tell me if a ram stick is messed up or if a ram slot on the motherboard is messed up.

Did I get it right?

 

[James7679]

1 stick, pass until you get errors, remove, test next stick. If you get errors on both sticks, then test individually on each slot. If you get errors on all slots, buy new RAM.

 

[mattr]

so, last night, i pulled out one stick of ram and tested it other. it went for 10+ sweeps with no errors whatsoever.

this morning, I pulled the good stick out, put the bad stick in the same slot the good stick was in, ran the test, and instantly pulled up errors.

I guess that is enough evidence that the bad stick is the culprit?

i also got a BSOD last night, reason why I tested right afterwards.

I'm going to try to reproduce the BSOD. I think it has to do with Spotify, as that program has been open both times it has BSOD.

and I plan on buying a new stick of ram to replace the one that seems full of errors.

 

[James7679]

A new stick is a good idea. Be sure to buy ram that matches your current ram. You should not mix and match ram as it can cause stability issues as well. If need be, purchase a new matched set. Once you have the new RAM installed, let us know if you continue to have problems so that we may assist you further.

 

[mattr]

I just bought the same exact RAM i bought originally, so it should work alright.

I can't get it to BSOD, even if I use the same programs at the same time.

Thanks for the help!

 

[writhziden]

You're welcome. Glad the RAM solved it.

Thank you James for the good hardware troubleshooting steps.

 

[James7679]

Nice work mattr!

You're welcome. Glad the RAM solved it.

Thank you James for the good hardware troubleshooting steps.

And thank you writhziden for your .dmp cracking skills.