Ongoing BSOD caused by dxgmms1.sys

Hello Cory360.

It is TP-LINK Wireless N Adapter driver that is crashing. It uses Athores drivers.

Code:

Name    [00000013] TP-LINK Wireless N Adapter
Driver    c:\windows\system32\drivers\athurx.sys (2.0.0.53, 1.83 MB (1,918,976 bytes), 8/4/2012 5:21 PM)
=================================================================================
BugCheck D1, {0, 2, 0, fffff88000f4f48c}

*** WARNING: Unable to verify timestamp for athurx.sys
*** ERROR: Module load completed but symbols could not be loaded for athurx.sys
Probably caused by : athurx.sys ( athurx+925e )

Followup: MachineOwner
--------------------------------------------------------------------------------------------------------
fffff880`0260e000 fffff880`027e9000   athurx   T (no symbols)           
    Loaded symbol image file: athurx.sys
    Image path: athurx.sys
    Image name: athurx.sys
    Timestamp:        Wed Jul 28 17:31:39 2010 (4C501C23)
    CheckSum:         001DD606
    ImageSize:        001DB000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You may try either Atheros AR9271 Wireless Network Adapter's driver from ATHEROS Wireless drivers for Windows, or you may get it from the manufacturer's site.

Also, your Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC driver is very old, too.

Code:

fffff880`02e00000 fffff880`02e85000   Rt64win7   (deferred)             
    Image path: Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Fri Jun 10 12:03:15 2011 (4DF1BAAB)
    CheckSum:         0008B67F
    ImageSize:        00085000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Realtek

Intel Graphics driver.

Code:

fffff880`07af46c8  fffff880`0f368e3fUnable to load image igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
 igdkmd64+0xb3e3f
fffff880`0f2b5000 fffff880`100b7f80   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        Wed Feb 15 00:17:30 2012 (4F3AAC42)
    CheckSum:         00E03C3D
    ImageSize:        00E02F80
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update the Intel HD Graphics Driver, either from our forum link, Latest Intel HD Graphics Driver for Windows 7, or You may get it from Intel Download Center.
Moreover, you may run the Intel (R) Driver Update Utility to auto detect the appropriate driver for your computer.

Let us know the results.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d898f338c4, 0, 757b59802da001cc, 101}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

This crash is not providing any probable cause, how much deep I may search.

Wait and observe, if the crashes continue to occur, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Do some general USB related troubleshooting. For the port, first, uninstall and reinstall the USB ports drivers.

1. Right click on Computer icon > manage. It will open the computer management window.
2. Click on "Device Manager" in the left pane, it will list all installed devices up.
3. Expand "USB Serial Bus Controllers" by clicking on the triangle in front of it.
4. Click on one item to select, then right click and uninstall.
5. Do the same for all.
6. Restart the computer.
7. At restart, windows will auto configure the appropriate drivers.

And, Disable USB Selective Suspense too.
USB Selective Suspend - Turn On or Off

For the devices, first, detach all the USB devices other than the keyboard and mouse.
Then, Update the drivers for them all, including the keyboard and mouse, if any third party drivers are installed for them.

Upload a screenshot of Speccy summery tab, after say 30 minutes of computer run. Clean the air vents, fan grills.

And, we need to know what happens when Driver Verifier is enabled.