BSoDs randomly on various of games

[TheJmJ]

My SATA ports were at AHCI modes. Both my CD-player and HDD.
My RAM timings were automated in the BIOS when I checked them. Before and after optimization my timings were 11-11-11-28-33. DRAM frequency was 717.6 MHz before optimization and after the opt. it was 802.7 MHz.

So according to CPU-Z they're 1600 MHz rams, but I still have a feeling that they might have been 1866 MHz... I gotta ask someone to check the shopping ticket just to make sure.

Also, should I manually set the timings or should I just leave them to auto?

 

[TheJmJ]

Another BSoD, this time it happened in middle of rebooting computer. Here's what happened exactly

Basically, I was watching a youtube video, and chatting with a friend on teamspeak
> Lost connection to Teamspeak, and I noticed that my wireless connection status was at "limited access"
> Tried to finish watching the youtube video, while it stopped too due no internet access.
> Plugged the WiFi-adapter out of the computer and plugged it back in, no fix, and the program didn't recognize the adapter anymore, yet the light turned on on the adapter.
> Pressed on the restart button at the arrow next to the Shut Down button
> Windows was shutting down, and I went to the kitchen, and when I came back the BSoD happened, blaming the USB driver again.

 

[essenbe]

What I can tell you is that you were right, it was the USB hub

 usbhub
start             end                 module name
fffff880`04b09000 fffff880`04b63000   usbhub     (pdb symbols)          c:\symcache\usbhub.pdb\7ACC879946324EA48B13386DE80EC2E61\usbhub.pdb
    Loaded symbol image file: usbhub.sys
    Mapped memory image file: c:\symcache\usbhub.sys\52954DD05a000\usbhub.sys
    Image path: \SystemRoot\system32\DRIVERS\usbhub.sys
    Image name: usbhub.sys
    Timestamp:        Tue Nov 26 19:41:36 2013 (52954DD0)
    CheckSum:         0005F52B
    ImageSize:        0005A000
    File version:     6.1.7601.18328
    Product version:  6.1.7601.18328
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        2.0 Dll
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     usbhub.sys
    OriginalFilename: usbhub.sys
    ProductVersion:   6.1.7601.18328
    FileVersion:      6.1.7601.18328 (win7sp1_gdr.131126-1436)
    FileDescription:  Default Hub Driver for USB
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

However I can also tell you it was a third party USB driver that caused it. My debugger will not pull up the actual driver that caused it, meaning it is a third party driver that is not in Microsoft's data base. This is what tells me that

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: usbhub!_DEVICE_EXTENSION_HUB                  ***
***                                                                   ***
*************************************************************************

I suspect it is most likely your USB Dongle or whatever you are using for WiFi given the way you are describing the event. As for your Ram settings, please download
CPU-Z CPUID - System & hardware benchmark, monitoring, reporting and post screenshots (http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html) of the Memory and SPD tabs. The SPD tabs are for each Dimm slot, which can be selected from a drop down in the upper left of the screen. I only need the ones for the Dimm slots that are populated with ram.

 

[TheJmJ]

View attachment 334736
View attachment 334737View attachment 334738

I will call my parents if they have the list of my parts somewhere safe, because I'm not 100% sure what ram exactly I bought, because I had some switching back and forth with them. Most likely this evening or tomorrow I'll be calling there...

EDIT: G.Skill 8GB (2 x 4GB) RipjawsX, DDR3 1866MHz, CL8, 1.5V

Called my parents and they confirmed the part.

 

[essenbe]

set your voltage to 1.5V, Set your Dram frequency to 1866 Your timings are currently set to 11-11-28-39 It is usually the first 4 timings listed, change them to 8-9-9-34-33 The Command rate is usually slightly faster at 1T, but is more stable at 2T. You will notice no difference between them so I recommend setting it to 2T. Try that and see if it works OK. If you are up to it, I would run 8 passes of memtest86+ to make reasonably sure it is stable with those settings.

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask​

 

[TheJmJ]

My BIOS settings for RAM timings. I set the DRAM speed to 1866 as you told me to.

View attachment 334750

Aaaand my CPU-Z. The only change what happened was at the memory tab.

View attachment 334751

 

[essenbe]

See how that works for you. If you have ram problems change the 34 to 24. It should be good though.

 

[TheJmJ]

View attachment 334798

Passes 8, Errors 0. Time taken: 14 hours and 5 minutes. I'll tell you if anything happens while gaming/stressing the computer.

 

[essenbe]

Great, you should be in good shape with the ram now.

 

[TheJmJ]

Another BSoD occured, with same steps before BSoD

The thing is, before BSoD, the screen cracks with greenish colours at some corners, and then the BSoD comes. Also when the game crashes, every screen Aero shows are solid white. Also the computer runs a bit slow for a while.

When booting the game after crash, the game (CS:GO in this case) has this intro, which is lagging a lot in the boot.

Inserted the log files, even tho I'm not sure if they're any use for you, as they repeat the same error all over again.

 

[essenbe]

The error is the exact same as before, a TDR failure, which means the drivers failed and did no recover in the time Windows allows for recovery, so Windows assumes it is a video failure. Here is what we don't know, and frankly, I don't know how to find out. That will require you to be very aware of exactly what is happening and pay close attention. We have had quite a few people with this problem with this same game. I don't play that game so can offer no insights. But, if it is the game crashing, then the Video drivers will naturally follow. Which begs the question, is it the game crashing or the video drivers. I can only tell you I have had similar problems with a game before, but I recognized that it was the game and not the video card. You are really the only person who can make that determination, and with several others having the same problem with the same game, I would be suspicious. Now, on the other hand, the symptoms you described sound like a video card going bad.

Whatever you decide you want to pursue, I will try to help, but it is a difficult thing to determine.

 

[TheJmJ]

Not sure, because the BSoD has happened in Planetside 2 too, so it's not only CS:GO then. I will try to crash the game first, and then when it crashes, I'll try to open up a different game, like ArcheAge.

Hopefully I'll find something interesting

 

[essenbe]

Archage is worse

 

[essenbe]

Try this and see if it helps
Enable driver verifier but only enable the options: Standard settings and IRP logging step 3.

CREATE A SYSTEM RESTORE POINT FIRST!

Enable Driver Verifier to monitor the drivers. Follow this Tutorial for instructions:
Driver Verifier -Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

http://www.sevenforums.com/images/infosmall1.png Information

We use Driver Verifier as it puts a stress on the drivers, and so it makes the unstable drivers crash. This should flag the driver responsible in the dump file.
It

Driver Verifier will make the system laggy, this is normal so don't worry.

Before enabling DV, make sure that you have earlier System restore points made in your computer. make a System Restore Point Manually

If there are no points, make one

 

[TheJmJ]

Ok, so I did run Driver verifier 3 times previously, and it in fact did run VERY slowly, until the screen started cracking completely. after a while of running (Mostly did not even get to use browser completely)
View attachment 334873

 

[essenbe]

That looks like a bad card, to me. I hate to tell you that, and I could be wrong, but that is usually a tell tale sign. But, driver verifier is designed to make drivers crash. The purpose is to make drivers crash in hopes of catching the bad driver. If youwant to upload the file again, I will be happy to look at it for you.

 

[TheJmJ]

Wait, what file? The BSoD log?

 

[essenbe]

Yes, if you want me to.

 

[TheJmJ]

Ok, so I'm confused here still.
So you want to get the most recent one (that I sent you already), or the next BSoD log I'll get?

Also, what would you suggest. Should I ask for a change from the shop I've bought the GPU from, or should I just stand this GPU? Because the GPU seems to be doing it once in a day/week...

 

[essenbe]

I just thought you had another BSOD. If you didn't, just send me the next one you get. If you ate getting BSODs from the card, I would have it replaced. The only thing we haven't discussed, or I forgot is your PSU or your Motherboard. The PSU is a quality brand, but even they can go bad, but I wouldn't think so. Or your Motherboard could have a bad pcie slot. That's easy enough to check but putting it in another slot. You can try that and see if you still have a BSOD. To the best of my knowledge, the card, motherboard or the PSU is about all that is involved.