BSOD Caused by NDIS.SYS Driver!

luishp · 04 Jun 2013

I've had this laptop for a couple of years now. Last year I took it to a repair shop for a BSOD (I don't remember what caused it) and they had to install a fresh new HDD to it. Badly, they didn't verify my Windows 7 software, and after I noticed the shop refused to validate it! So for a year I carried a laptop without a validated Windows 7 copy (when I bought it it had the same OS, I tried to look for the validation number in the laptop but it was to worn of to recognize the code). So now, I got a BSOD a couple of days ago. It states DRIVER_IRQL_NOT_LESS_OR_EQUAL caused by the file ndis.sys. I attached my diagnostic to this post... I can't access my computer on any way but safe mode (without internet), as suggested by an engineer I know I removed most of the drivers concerned with the network adapter (both the wireless and wired ones), but it didn't help. Please help!

koolkat77 · 04 Jun 2013

Hi luishp.

Security App

Code:

aswFsBlk.SYS                Thu May  9 14:47:16 2013 
aswKbd.sys                  Thu May  9 14:47:49 2013 
aswMonFlt.sys               Thu May  9 14:47:23 2013 
aswRvrt.sys                 Thu May  9 14:47:02 2013 
aswSP.SYS                   Thu May  9 14:48:25 2013 
aswSnx.SYS                  Thu May  9 14:48:30 2013 
aswTdi.SYS                  Thu May  9 14:47:32 2013 
aswVmm.sys                  Thu May  9 14:47:06 2013 
aswrdr2.sys                 Thu May  9 14:47:41 2013

Crashes indicate Avast! being a possible cause. Remove Avast! and replace with Microsoft Security Essentials to see if it provides more stability. Uninstallers (removal tools) for common antivirus software. Microsoft Security Essentials and Malwarebytes are recommended from a strict BSOD perspective. They do not cause blue screens on the system as other AV products do.

Microsoft Security Essentials, Free antivirus for windows and Malwarebytes Anti-Malware Free

Information

Do not start the free trial of MalwareBytes, unselect that option when prompted.
Update and make full scans with both separately.

SFC /scannow to check windows for corruption:

How to Repair Windows 7 System Files with System File Checker
1. Click Start

2. In the search box, type Command Prompt
3. In the list that appears, right-click on cmd.exe and choose Run as administrator
4. In the command window that opens, type

sfc /scannow

and hit enter.

Update these drivers to their latest:
Rt64win7.sys Thu Feb 26 15:04:13 2009 - Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
athrx.sys Wed Jun 10 00:06:49 2009 - Atheros network adapter driver
HssDrv.sys Thu Sep 2 23:46:48 2010 - Hotspot shield [br] Possible BSOD cause seen in mid-2012

Daemon Tools/Alcohol %

Code:

dtsoftbus01.sys             Fri Jan 13 19:45:46 2012

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although we have seen dtsoftbus01.sys blamed on several occasions). Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ

As an alternative, many people recommend the use of Total Mounter or Magic ISO

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {10, 2, 0, fffff880014ea5d6}

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

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

Please run these tests and report back the results

1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
2. Disk check for errors on the hard drive - How to Run Disk Check in Windows 7
3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure
6. Install all updates including Service Pack 1 - Learn how to install Windows 7 Service Pack 1 (SP1)

BSOD BUGCHECK SUMMARY

Code:

Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Debug session time: Wed Jun  5 09:36:06.289 2013 (UTC + 6:00)
System Uptime: 0 days 0:02:05.476
BugCheck D1, {10, 2, 0, fffff880014ea5d6}
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+47677 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Debug session time: Wed Jun  5 09:02:58.287 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:45.787
BugCheck D1, {10, 2, 0, fffff880014e85d6}
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+47677 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Debug session time: Mon Jun  3 10:04:37.842 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:47.028
BugCheck D1, {10, 2, 0, fffff8800151f5d6}
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+47677 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Debug session time: Mon Jun  3 09:04:23.229 2013 (UTC + 6:00)
System Uptime: 0 days 0:01:01.416
BugCheck D1, {10, 2, 0, fffff880014745d6}
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+47677 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Debug session time: Mon Jun  3 09:02:07.837 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:49.024
BugCheck D1, {10, 2, 0, fffff880014595d6}
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+47677 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Debug session time: Mon Jun  3 08:45:03.224 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:31.411
BugCheck D1, {10, 2, 0, fffff880014a45d6}
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+47677 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Debug session time: Mon Jun  3 08:17:52.886 2013 (UTC + 6:00)
System Uptime: 0 days 0:01:02.386
BugCheck D1, {10, 2, 0, fffff880015205d6}
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+47677 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Debug session time: Mon Jun  3 08:15:52.860 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:52.936
BugCheck D1, {10, 2, 0, fffff8800153b5d6}
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+47677 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Debug session time: Mon Jun  3 08:09:08.208 2013 (UTC + 6:00)
System Uptime: 0 days 0:01:14.283
BugCheck D1, {10, 2, 0, fffff880014f25d6}
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+47677 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Debug session time: Sun Jun  2 06:43:26.921 2013 (UTC + 6:00)
System Uptime: 0 days 0:01:18.107
BugCheck D1, {10, 2, 0, fffff880014c45d6}
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+47677 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Debug session time: Sun Jun  2 06:36:47.237 2013 (UTC + 6:00)
System Uptime: 0 days 0:01:11.313
BugCheck D1, {10, 2, 0, fffff880014f95d6}
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+47677 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``