BSOD when connected to the internet

Welcome to the Forum.

Please update these drivers:

ASACPI.sys Mon Mar 28 08:30:36 2005 (42476C4C)
Asus ATK0110 ACPI Utility (a known BSOD maker in Win7 and Win8). Also a part of many Asus utilities (Win8 versions available from Windows Update as an Optional Update - but check Asus first!)
Driver Reference Table - ASACPI.sys

anodlwfx.sys Fri Mar 6 16:10:08 2009 (49B0F680)
ALPHA Networks Filter Driver
Driver Reference Table - anodlwfx.sys

xusb21.sys Fri Aug 14 04:10:17 2009 (4A848F49)
XBox USB wireless controller [br] BSOD issues in Win7 with 2009 driver (found in mid-2012)
Driver Reference Table - xusb21.sys


AODDriver2.sys Thu Apr 5 15:23:37 2012 (4F7D6499)
AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7
Driver Reference Table - AODDriver2.sys

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems.

Please uninstall all AMD/ATI video stuff from Control Panel...Programs...Uninstall a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from http://ati.amd.com (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Uninstall". Reboot for changes to take affect.

Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

I would also recommend that you uninstall Avast! antivirus for testing purpose.

• Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:
  
  • Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase
  • Help protect your PC with Microsoft Security Essentials
  • Malwarebytes Free

   Note

Do not start the trial version of MalwareBytes

• Also take a look at: Good & Free System Security Combination

• Virus Check:
  
  • Make scans with these tools below:
    
    • TDSSKiller Rootkit Removal Utility Free Download | Kaspersky Lab US
    • Online Virus Scanner Eset
• Application conflict:
  
  • Reduce the start-up items. This will help avoid software conflicts:
    
    • Remove Startup Programs in Windows 7
    • Clean Startup in Windows 7

• System File Checker
  
  • The SFC /SCANNOW Command - System File Checker scans the integrity of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible. If you have modified your system files as in theming explorer/system files, running sfc /scannow will revert the system files to it's default state.
    
    • Link to full tutorial: SFC /SCANNOW Command - System File Checker
• Run Disk Check in Windows 7
  
  • Run this on your Hard Drive(s). This will show you how to run Check Disk or chkdsk in Windows 7 to check a selected hard disk for file system errors and bad sectors on it. With both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
    
    • Link to full tutorial: Disk Check

Code:

Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Thu Oct 17 09:58:07.113 2013 (UTC + 6:00)
System Uptime: 0 days 0:11:19.206
BugCheck D1, {fffff8800ac5a069, 2, 0, fffff880044ec850}
*** WARNING: Unable to verify timestamp for anodlwfx.sys
*** ERROR: Module load completed but symbols could not be loaded for anodlwfx.sys
Probably caused by : anodlwfx.sys ( anodlwfx+2850 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Thu Oct 17 08:50:41.218 2013 (UTC + 6:00)
System Uptime: 0 days 0:01:08.311
BugCheck D1, {fffff88005def069, 2, 0, fffff88004364850}
*** WARNING: Unable to verify timestamp for anodlwfx.sys
*** ERROR: Module load completed but symbols could not be loaded for anodlwfx.sys
Probably caused by : anodlwfx.sys ( anodlwfx+2850 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Thu Oct 17 08:48:29.489 2013 (UTC + 6:00)
System Uptime: 0 days 0:07:31.582
BugCheck D1, {fffff880095ef062, 2, 0, fffff880043298e0}
*** WARNING: Unable to verify timestamp for anodlwfx.sys
*** ERROR: Module load completed but symbols could not be loaded for anodlwfx.sys
Probably caused by : anodlwfx.sys ( anodlwfx+28e0 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Thu Oct 17 07:57:39.319 2013 (UTC + 6:00)
System Uptime: 0 days 0:07:02.412
BugCheck D1, {fffff88005f86069, 2, 0, fffff88004090850}
*** WARNING: Unable to verify timestamp for anodlwfx.sys
*** ERROR: Module load completed but symbols could not be loaded for anodlwfx.sys
Probably caused by : anodlwfx.sys ( anodlwfx+2850 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Thu Oct 17 07:49:35.862 2013 (UTC + 6:00)
System Uptime: 0 days 0:03:16.362
BugCheck D1, {fffff88005383062, 2, 0, fffff88002f8c8e0}
*** WARNING: Unable to verify timestamp for anodlwfx.sys
*** ERROR: Module load completed but symbols could not be loaded for anodlwfx.sys
Probably caused by : anodlwfx.sys ( anodlwfx+28e0 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Thu Oct 17 07:45:39.548 2013 (UTC + 6:00)
System Uptime: 0 days 0:04:14.641
BugCheck D1, {fffff88004fef269, 2, 0, fffff8800400b850}
*** WARNING: Unable to verify timestamp for anodlwfx.sys
*** ERROR: Module load completed but symbols could not be loaded for anodlwfx.sys
Probably caused by : anodlwfx.sys ( anodlwfx+2850 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Thu Oct 17 07:40:48.355 2013 (UTC + 6:00)
System Uptime: 0 days 0:08:13.447
BugCheck D1, {fffff88005def062, 2, 0, fffff880045a28e0}
*** WARNING: Unable to verify timestamp for anodlwfx.sys
*** ERROR: Module load completed but symbols could not be loaded for anodlwfx.sys
Probably caused by : anodlwfx.sys ( anodlwfx+28e0 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Mon Oct 14 22:47:57.729 2013 (UTC + 6:00)
System Uptime: 0 days 0:13:38.822
BugCheck D1, {fffff88002def068, 2, 0, fffff880042af861}
*** WARNING: Unable to verify timestamp for anodlwfx.sys
*** ERROR: Module load completed but symbols could not be loaded for anodlwfx.sys
Probably caused by : anodlwfx.sys ( anodlwfx+2861 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Mon Oct 14 22:33:38.695 2013 (UTC + 6:00)
System Uptime: 0 days 0:24:25.788
BugCheck D1, {fffff8800afdd2e6, 2, 0, fffff88004155875}
*** WARNING: Unable to verify timestamp for anodlwfx.sys
*** ERROR: Module load completed but symbols could not be loaded for anodlwfx.sys
Probably caused by : anodlwfx.sys ( anodlwfx+2875 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

You can google it maybe

Msinfo32:

• please go to start and type in "msinfo32.exe" (without the quotes) and press enter> save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
  

  • also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

It appears that the driver anodlwf.sys ANOD Network Security Filter driver (c:\windows\system32\drivers\anodlwfx.sys) Is bundled with D-Link.

Here the D-Link product is D-Link DWA-130 Wireless N USB Adapter. So update to that device may be needed. It is available in D-Link | Technical Support | Downloads.

http://tsd.dlink.com.tw/

In the first select, put DWA in the drop down menu.
In the second select, put 130.
Then go.

It will take you to the appropriate place.

Clean install might be a good solution. Have you tried a clean installation of drivers.

• To perform a clean install of a driver, follow this tutorial:
  
  • How to Clean Left Over Driver Files with Driver Sweeper