BSoDs randomly on various of games

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

Code:

 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

Code:

*************************************************************************
***                                                                   ***
***                                                                   ***
***    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 (Screenshots and Files - Upload and Post in Seven Forums) 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.

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

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

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