Solved BSOD playing Civ 5, and downloading a game

[joezilla29]

Recently reinstalled Windows 7 OS and let Windows Update download some 200 updates. First BSOD was when I left my computer on when I was away to download some games. I came back to it at the User accounts screen, so I suspected it had crashed. Second BSOD was when I was playing Civilization 5 solo with Steam downloading in the background.

Just a hunch, but I think it may be my video card (GTX 760). When Windows Updates was rebooting and installing the updates, my PC would not boot to OS, or even the Windows 7 Installation CD. There was no POST beep either, when before there was. I had to remove video card and install my previous GTX 560TI, then there was POST beep and the video card drivers installed. Took out the GTX 560TI and put in GTX 760, and there is no POST beep, but it boots up. Funny thing is, if I have my USB headset connected the USB 3.0 port it does not boot either, though it will boot if connected to non-USB 3.0 port.

Don't know if that helps. Thanks for looking at my post.

 

[BorisTheAnimal]

Hi Joe and welcome to Sevenforums!

Both the BSODs point to something wrong with the ram but updating drivers might solve it.

Though I would first recommend that you visit this click me and download the following:
AMD all in 1 driver
Realtek high definition audio driver
Realtek Lan driver
ASMedia USB 3.0 driver

And then I would also recommend you to run Memtest86+ - Advanced Memory Diagnostic Tool preferably for 3-4 hours or overnight whichever is more handy for you!

And post back the results!

Cheerio /Boris

 

[joezilla29]

Hey Boris, sorry for the late reply I have not had time to run memtest yet, but I have a USB prepped. Should be able to try it either tonight or tomorrow. I got another BSOD just last night. It's attached. I assume the reasons are the same as well? Thanks for your help!

Edit: I forgot to mention, I followed your advice and updated all the motherboard drivers. But it still gave me the BSOD.

 

[BorisTheAnimal]

Hi Joe.

Well I will need some time to get this one sorted out, your last BSOD point to a USB audio device, mayhaps you have one? Either way the only thing I've found about it is in older version of Windows like 2k and ME.

But run the memory test and hopefully it will shine some light on what might be the root of this problem.

/Boris

 

[joezilla29]

Ok, I ran Memtest for ~4hrs. I did not know how to save the results or create a log, but I took a screenshot, but if you want me to run the test again and save an actual detailed report, I can (just tell me how ).

As for the USB audio device, I have a USB Turtle Beach headset that I have plugged in all the time. If it is plugged into a USB 3.0 port, the computer fails to boot.

 

[BorisTheAnimal]

Joe, thanks for the photo, I think we can manage but if you wan't to get this log thingy working you would have to download Memtest v5 as it has a new feature that enables logging.

As for the headset, head over to Turtle Beach's support download page and try to find if your headset has a firmware update available:
Turtle Beach :: Knowledgebase - Files

/Boris

 

[joezilla29]

I went to Turtle Beach site, but they have nothing to download for my headset except the manual :/ . I did get another BSOD recently trying to answer a Skype call while alt-tabbed out of a game. I'll post it. Thinking upgrading my CPU did more harm than good.

BTW, if I can ask, how do you determine what's wrong? Because I would like to learn how as well.

 

[BorisTheAnimal]

Hi Joe,

Thanks for responding and submitting the new dump, which points to a hardware error and reading about your motherboard + your cpu, it seems you are right with upgrading the cpu made more harm than good.

Oh and when it comes to troubleshooting BSODs, I use Windows Debugger and Nirsoft's BlueScreenView and then you check the codes and the caps text and start your research, but I'm such a beginner that you might also ask the more professional laddies like Golden, Essenbe or axe0.

/Boris

 

[axe0]

To start learning debugging bluescreens, prepare yourself for a lot of headaches, invest a lot of time in researching everything you find to understand it and keep trying.
A lot quit because this could be very difficult sometimes which is the an important reason why bluescreen forums have the least active members.

For the setup of Windbg
WinDBG - Install & Configure - Windows 10 Forums
For more information about stop codes
BSOD Index & https://msdn.microsoft.com/en-us/library/windows/hardware/hh994433(v=vs.85).aspx

I don't use Bluescreenview, given it up after I started to understand more about bluescreens, but I'm thinking of using it again as it sometimes shows relevant data (not directly helpful though)

 

[axe0]

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

 

[joezilla29]

Thanks guys. I just got another BSOD a few minutes ago, lol. I suppose I will revert back to my previous CPU and shop around for a new motherboard that will work with the new CPU. Though I will have to buy another OS if it comes to that

 

[axe0]

Please run the dm log collector another time and upload a new zip

 

[joezilla29]

Here is the BSOD report from last night. I also uploaded a photo of the memtest I ran for almost 2 hours with my previous CPU, and got 2 errors. If it's a RAM error, should I just buy some new RAM? I also read on other forums removing some sticks of RAM could determine which one is bad. Does unseating the RAM and moving them fix the issue, or is it once a RAM stick goes bad, there's no saving it?

I think all this trouble started when I updated my BIOS to support the newer CPU.

 

[axe0]

In your previous post I didn't notice the 2 errors.

Yes, test each stick in each slot separated from the other stick(s) to find what exactly is giving the errors.

 

[joezilla29]

What's the general procedure for testing individual sticks? Can I stop after it produces 1 error, or let it do more passes? I'm testing a stick right now and I already have 6 errors in 1 pass after 34 minutes.

 

[axe0]

The tutorial explains that completely.

 

[joezilla29]

Ahh, alright.

Also, I just noticed this after moving the stick. I'm assuming this is not a good thing... I don't know how long it's been like that. Anyway, I'll need to set some major time aside if I'm going to do 8 passes. Thanks again.

 

[axe0]

That isn't good, the stick is damaged, keep going with the tests without that stick.

 

[joezilla29]

So that damaged RAM that I tested which gave me 6 errors in 30 minutes seems to be the culprit. I didn't know it was even damaged until after I completed a test. I took it out, and tested it's pair, which produced no errors.

I went on a hunch and reinstalled my FX 8350, and left in the other pair of RAM that had no physical damage, and ran memtest while I was away at work. Came back 7 hours later and no errors. I'd run each stick if it had given me an error, but for now, I think I would just be happy with this.

Thanks again Boris and Axe0. I'll post again in this thread there's another issue.

 

[axe0]

Please mark this thread solved if you think it is solved, after you have marked it solved and get new problems create a new thread.