BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL and others on new install

[alx13]

I experienced a variety of BSODs over the past year, all unresolved, so I finally wiped the whole thing clean, reformatted and reinstalled Windows 7 64. And they're back. Most of them are DRIVER_IRQL_NOT_LESS_OR_EQUAL, although a couple others have shown up as well. I've made sure I have up to date drivers for all hardware, the latest BIOS rev, etc. I have run memtest in the past with successful results after about 12 hours.

I've tried with Norton 360, and with MSE, but both have crashed. The only fairly consistent condition seems to be that it is always when I am online, but then again, that is always. Sometimes it is just using a browser, sometimes while a bittorrent is downloading, etc. Firefox seemed to be a problem, so I switched to Chrome, which seems slightly better, but is also crashing.

Specs:
-Windows 7 x64
-This is the second clean install
-system is about 18 months old
-OS reinstalled about a month ago

 

[usasma]

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center.
Please uninstall the AMD OverDrive program.
If it's the stand-alone app, uninstall it via Control Panel...Programs...Uninstall a program
If it's in the AMD VISION Engine Control Center, you can uninstall it using the AMD uninstall tool (or uninstall the entire AMD VISION Engine Control Center application through Control Panel

Daemon Tools (and Alcohol % software) are known to cause BSOD's on Win7 systems due to the sptd.sys driver.
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

There is an older CD/DVD program that uses the afc.sys driver installed on your system. The driver dates from 2006 and is likely not compatible with Win7. Please uninstall this program.

The memory dumps point at networking, so I'd suggest that you:
- download fresh copies of your networking drivers (both wired and wireless if so equipped)
- uninstall the current networking drivers from your system
- install the freshly downloaded networking drivers
- monitor for further BSOD's

With you having done a clean install, I wouldn't be surprised to see further BSOD's
If so, then please run Driver Verifier according to these instructions: http://www.carrona.org/verfier.html

BSOD BUGCHECK SUMMARY

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011712-21859-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan 17 20:38:11.363 2012 (UTC - 5:00)
System Uptime: 0 days 10:59:58.597
BugCheck D1, {1, 2, 1, fffff8800197fe8e}
Probably caused by : NETIO.SYS ( NETIO!StreamClassify+8e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_NETIO!StreamClassify+8e
Bugcheck code 000000D1
Arguments 00000000`00000001 00000000`00000002 00000000`00000001 fffff880`0197fe8e
BiosVersion = F12
BiosReleaseDate = 03/22/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011312-31812-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan 13 01:10:28.242 2012 (UTC - 5:00)
System Uptime: 0 days 11:33:36.476
BugCheck D1, {9b, 2, 0, fffff88001b48966}
Probably caused by : tcpip.sys ( tcpip!IpSecTlPacketsOutProcessing+56 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xD1_tcpip!IpSecTlPacketsOutProcessing+56
Bugcheck code 000000D1
Arguments 00000000`0000009b 00000000`00000002 00000000`00000000 fffff880`01b48966
BiosVersion = F12
BiosReleaseDate = 03/22/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011212-20265-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan 12 10:34:47.940 2012 (UTC - 5:00)
System Uptime: 0 days 14:38:05.174
BugCheck D1, {9b, 2, 0, fffff88001aff966}
Probably caused by : tcpip.sys ( tcpip!IpSecTlPacketsOutProcessing+56 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  uTorrent.exe
FAILURE_BUCKET_ID:  X64_0xD1_tcpip!IpSecTlPacketsOutProcessing+56
Bugcheck code 000000D1
Arguments 00000000`0000009b 00000000`00000002 00000000`00000000 fffff880`01aff966
BiosVersion = F12
BiosReleaseDate = 03/22/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011112-22718-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Jan 11 02:39:10.860 2012 (UTC - 5:00)
System Uptime: 0 days 3:02:19.047
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+be2d )
BUGCHECK_STR:  0xc2_7
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc2_7_nt!_??_::NNGAKEGL::_string_+be2d
Bugcheck code 000000C2
Arguments 00000000`00000007 00000000`0000109b 00000000`00000000 fffff8a0`0daad948
BiosVersion = F12
BiosReleaseDate = 03/22/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010812-27359-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan  8 14:37:28.566 2012 (UTC - 5:00)
System Uptime: 0 days 0:14:12.800
Probably caused by : ntkrnlmp.exe ( nt!ExpScanSystemLookasideList+6a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_nt!ExpScanSystemLookasideList+6a
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`030a5572 fffff880`03716938 fffff880`03716190
BiosVersion = F12
BiosReleaseDate = 03/22/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010812-31265-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan  8 14:22:36.616 2012 (UTC - 5:00)
System Uptime: 0 days 1:53:37.803
BugCheck D1, {9b, 2, 0, fffff88001b32966}
Probably caused by : tcpip.sys ( tcpip!IpSecTlPacketsOutProcessing+56 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  uTorrent.exe
FAILURE_BUCKET_ID:  X64_0xD1_tcpip!IpSecTlPacketsOutProcessing+56
Bugcheck code 000000D1
Arguments 00000000`0000009b 00000000`00000002 00000000`00000000 fffff880`01b32966
BiosVersion = F12
BiosReleaseDate = 03/22/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010812-32375-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan  8 12:28:12.585 2012 (UTC - 5:00)
System Uptime: 0 days 23:01:30.142
BugCheck D1, {9b, 2, 0, fffff88001ad2966}
Probably caused by : tcpip.sys ( tcpip!IpSecTlPacketsOutProcessing+56 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  uTorrent.exe
FAILURE_BUCKET_ID:  X64_0xD1_tcpip!IpSecTlPacketsOutProcessing+56
Bugcheck code 000000D1
Arguments 00000000`0000009b 00000000`00000002 00000000`00000000 fffff880`01ad2966
BiosVersion = F12
BiosReleaseDate = 03/22/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010612-27437-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan  6 17:46:49.272 2012 (UTC - 5:00)
System Uptime: 0 days 22:51:13.459
BugCheck D1, {1, 2, 1, fffff880017dfe8e}
Probably caused by : NETIO.SYS ( NETIO!StreamClassify+8e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  iw5sp.exe
FAILURE_BUCKET_ID:  X64_0xD1_NETIO!StreamClassify+8e
Bugcheck code 000000D1
Arguments 00000000`00000001 00000000`00000002 00000000`00000001 fffff880`017dfe8e
BiosVersion = F12
BiosReleaseDate = 03/22/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010512-21796-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan  5 18:55:02.104 2012 (UTC - 5:00)
System Uptime: 0 days 2:57:41.291
Probably caused by : tcpip.sys ( tcpip!TcpPeriodicTimeoutHandler+34c )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_tcpip!TcpPeriodicTimeoutHandler+34c
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = F12
BiosReleaseDate = 03/22/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010512-20046-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan  5 00:28:52.800 2012 (UTC - 5:00)
System Uptime: 0 days 7:15:49.988
BugCheck D1, {9b, 2, 0, fffff88001a75966}
Probably caused by : tcpip.sys ( tcpip!IpSecTlPacketsOutProcessing+56 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0xD1_tcpip!IpSecTlPacketsOutProcessing+56
Bugcheck code 000000D1
Arguments 00000000`0000009b 00000000`00000002 00000000`00000000 fffff880`01a75966
BiosVersion = F12
BiosReleaseDate = 03/22/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010312-31093-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan  3 14:01:40.436 2012 (UTC - 5:00)
System Uptime: 0 days 3:05:11.670
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4977d )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+4977d
Bugcheck code 0000001E
Arguments ffffffff`c0000005 00000000`006d0465 00000000`00000008 00000000`006d0465
BiosVersion = F12
BiosReleaseDate = 03/22/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[alx13]

Thank you.
Uninstalling Control Center got rid of AODDriver2.sys, and afc.sys seems to be gone after uninstalling DaemonTools as well. Do you have any recommendations for a stable iso mounting tool? MagicDisk seemed to cause problems as well, and I was told that DT would be stable.
I've uninstalled and reinstalled the networking drivers, so I'll see how things go from here.
Thanks again!

 

[usasma]

I use Virtual Clone drive - but haven't used it very much so I can't tell if it's effective or not.

Once we have the system stable again, then try Daemon Tools again. If it BSOD's on you, then you can't continue using it. If it doesn't, then it's "Happy Trails to youuuuuuuu!"

 

[alx13]

Everything seemed to be running fine since reinstalling the network drivers, and I ran Driver Verifier for an afternoon with no issues just to make sure.
But I've had a couple of BSODs in the past few days again now.
BSOD report is attached.

Thanks again for any help!

 

[usasma]

The device, AODDriver4.01, is reporting "tv_ConfigMgrErr24". This device will not be available until the issue is resolved. The Plug and Play ID for this device is ROOT\LEGACY_AODDRIVER4.01\0000.

Still didn't get rid of AMD OverDrive. Please:
- Install ATI drivers and the CCC
- uninstall all ATI stuff from the system
- install ONLY the ATI Display Driver Only
- check in C:\Windows\System32\drivers for the AODDriver files (DO NOT delete them!) Let us know if you find them there.

Afc.sys dates from 2006. It belongs to an older CD/DVD program.
Please:
- make a system restore point
- make a System Repair disc (and test it to make sure it works). Go to Start...All Programs...Maintenance...Create a System Repair Disc in order to create one
- go to C:\Windows\System32\drivers and rename afc.sys to afc.BAD
- check to see which CD/DVD program it breaks and uninstall that one.

wdcsam64.sys - Western Digital SCSI Arcitecture Model (SAM) WDM driver dates from 2008. Please uninstall the Western Digital software from your system. Feel free to reinstall a fresh copy from the Western Digital website once we're done troubleshooting.

I've got a hunch (but no proof) that the Symantec firewall may be acting up also (due to the networking BSOD's). Please do this to see:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN
- IMMEDIATELY install and update the free antivirus, then check to ensure that the Windows Firewall is turned on.
- check to see if this fixes the BSOD's
NOTE: NEVER run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012812-22140-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan 28 14:40:57.490 2012 (UTC - 5:00)
System Uptime: 0 days 18:02:26.724
BugCheck D1, {9b, 2, 0, fffff880018da966}
Probably caused by : tcpip.sys ( tcpip!IpSecTlPacketsOutProcessing+56 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_tcpip!IpSecTlPacketsOutProcessing+56
Bugcheck code 000000D1
Arguments 00000000`0000009b 00000000`00000002 00000000`00000000 fffff880`018da966
BiosVersion = F12
BiosReleaseDate = 03/22/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012612-21546-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan 26 20:58:23.706 2012 (UTC - 5:00)
System Uptime: 0 days 11:53:50.893
BugCheck D1, {1, 2, 1, fffff8800163fe8e}
Probably caused by : NETIO.SYS ( NETIO!StreamClassify+8e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_NETIO!StreamClassify+8e
Bugcheck code 000000D1
Arguments 00000000`00000001 00000000`00000002 00000000`00000001 fffff880`0163fe8e
BiosVersion = F12
BiosReleaseDate = 03/22/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012612-19437-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan 26 09:03:28.600 2012 (UTC - 5:00)
System Uptime: 0 days 13:07:43.788
BugCheck D1, {9b, 2, 0, fffff8800191c966}
Probably caused by : tcpip.sys ( tcpip!IpSecTlPacketsOutProcessing+56 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xD1_tcpip!IpSecTlPacketsOutProcessing+56
Bugcheck code 000000D1
Arguments 00000000`0000009b 00000000`00000002 00000000`00000000 fffff880`0191c966
BiosVersion = F12
BiosReleaseDate = 03/22/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012012-20156-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan 20 19:58:50.407 2012 (UTC - 5:00)
System Uptime: 0 days 2:34:07.594
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonCleanup+3ad )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCommonCleanup+3ad
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`07ca06e8 fffff880`07c9ff40 fffff880`014bcd8d
BiosVersion = F12
BiosReleaseDate = 03/22/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011812-22953-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Jan 18 13:30:13.736 2012 (UTC - 5:00)
System Uptime: 0 days 0:25:24.970
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonCleanup+3ad )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCommonCleanup+3ad
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`093693d8 fffff880`09368c30 fffff880`012aad8d
BiosVersion = F12
BiosReleaseDate = 03/22/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/FONT]

 

[alx13]

I did not find AODDriver files either before or after uninstalling all ATI stuff. Could they be named something else?

Afc.sys was not in system32/drivers, but was found in C:\Windows\SysWOW64\drivers. I've renamed it, but I don't have any CD/DVD programs specifically, unless it is coming from iTunes, Quicktime or VLC. It might actually be from my external hard drive - which is what the Western Digital files are for.

I've uninstalled the WD software but the wdcsam64.sys file is still there. Should I rename it for now?

I've tried uninstalling Norton in the past as I thought it could be the source of my problems, but still had crashes with MSE. I'll give it another shot now, along with all of the other steps.

Thanks again.

 

[usasma]

Run the perfmon /report again. That'll tell you if AODDriver is still having issues
Search the hard drive for AODDriver*.*

I dunno what afc.sys is used with - it's used by several applications so it's difficult to tell which.

Before renaming a driver:
- make a system restore point
- create a system repair disk (Start...All Programs...Maintenance...Create a System Repair Disc)
- use Autoruns to disable all of the startup entries that the driver uses
- then rename the driver (DON'T delete it).

The Norton issue is just a guess on my part.

 

[alx13]

The AODDriver issue is still showing up in perfmon. I've uninstalled all ATI stuff and there are not any services running that look like they'd be using it, but it is still showing up. The only place I can still find it is in the registry, but it won't allow me to modify or delete those entries.

 

[usasma]

Did you search the hard drive for AODDriver*.*

The AOD Driver may not be a problem (since the error is "Device is not present, not working properly, or does not have all of its drivers installed." )

My concern isn't with the registry entries - as they don't hurt anything if they can't load the driver. We have to see if 1) The driver is present on your system, and 2) if it's loading when you start Windows.

The easiest way to do this is to search for it. The other way is to wait for another BSOD and see if it shows up in that (and that's not a definite solution as it may not show up - yet it could still be loading).

FWIW - this AMD OverDrive thing is giving me quite the headache. If we stop the BSOD's, that's what really counts!

 

[alx13]

I've searched for the driver and it is nowhere on my drive.
Haven't had a BSOD for a few days now at least...

 

[alx13]

Had another BSOD again this morning, although it looks different. I've attached the files. AODDriver is nowhere on my drive, nor is afc.sys.

 

[alx13]

It looks like the same issue as before is showing up again now. Report files are attached.

Thanks.

 

[usasma]

ckldrv.sys (CrypKey)
wdcsam64.sys (Western Digital software)

These 2 programs are the only suspicious things left on your system. Please uninstall both.
Monitor for further BSOD's.

The BSOD's are suggestive of hardware problems - especially since the first 3 are Driver Verifier Enabled Memory Dumps. (this assumes that you're not overclocking)

First possibility is the CrypKey software, next is the Western Digital, last is hardware (can also be overclo.
If it BSOD's after removing those 2 programs, start the free hardware diagnostics here: Hardware Diags

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs:
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please either update the older drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers.

[font=lucida console]
vmbus.sys     Sat Nov 20 04:57:29 2010 (4CE79B89)
winhv.sys     Sat Nov 20 04:20:02 2010 (4CE792C2)
amdxata.sys   Fri Mar 19 12:18:18 2010 (4BA3A3CA)
MpFilter.sys  Wed Apr 06 16:07:29 2011 (4D9CC801)
ckldrv.sys    Thu Mar 18 19:10:27 2010 (4BA2B2E3)
atikmpag.sys  Mon Dec 05 21:12:14 2011 (4EDD79FE)
Rt64win7.sys  Tue Sep 27 10:50:33 2011 (4E81E2B9)
atikmdag.sys  Mon Dec 05 21:52:23 2011 (4EDD8367)
RtHDMIVX.sys  Wed Jul 06 06:09:50 2011 (4E14346E)
RTKVHD64.sys  Tue Dec 13 05:24:54 2011 (4EE727F6)
wdcsam64.sys  Wed Apr 16 04:39:08 2008 (4805BB2C)
NisDrvWFP.sys Wed Apr 06 16:08:53 2011 (4D9CC855)
MpNWMon.sys   Wed Apr 06 16:07:23 2011 (4D9CC7FB)
[/font]

http://www.carrona.org/drivers/driver.php?id=vmbus.sys
http://www.carrona.org/drivers/driver.php?id=winhv.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=MpFilter.sys
http://www.carrona.org/drivers/driver.php?id=ckldrv.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=RtHDMIVX.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=wdcsam64.sys
http://www.carrona.org/drivers/driver.php?id=NisDrvWFP.sys
http://www.carrona.org/drivers/driver.php?id=MpNWMon.sys

BSOD BUGCHECK SUMMARY

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\020512-17125-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Feb  5 18:30:02.218 2012 (UTC - 5:00)
System Uptime: 0 days 6:33:02.453
BugCheck D1, {9a, 2, 0, fffff88001675966}
Probably caused by : tcpip.sys ( tcpip!IpSecTlPacketsOutProcessing+56 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_tcpip!IpSecTlPacketsOutProcessing+56
Bugcheck code 000000D1
Arguments 00000000`0000009a 00000000`00000002 00000000`00000000 fffff880`01675966
BiosVersion = F12
BiosReleaseDate = 03/22/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\020412-17171-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Feb  4 11:08:24.523 2012 (UTC - 5:00)
System Uptime: 0 days 0:21:55.710
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+be2d )
BUGCHECK_STR:  0xc2_7
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc2_7_VRF_nt!_??_::NNGAKEGL::_string_+be2d
Bugcheck code 000000C2
Arguments 00000000`00000007 00000000`0000109b 00000000`00000000 fffff8a0`0c391948
BiosVersion = F12
BiosReleaseDate = 03/22/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\020312-17968-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Feb  3 10:36:59.457 2012 (UTC - 5:00)
System Uptime: 0 days 1:20:29.644
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+be2d )
BUGCHECK_STR:  0xc2_7
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc2_7_VRF_nt!_??_::NNGAKEGL::_string_+be2d
Bugcheck code 000000C2
Arguments 00000000`00000007 00000000`0000109b 00000000`00000000 fffff8a0`0ee14948
BiosVersion = F12
BiosReleaseDate = 03/22/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\020112-41859-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Feb  1 12:08:01.640 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:25.828
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1283 )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_VRF_nt!ExDeferredFreePool+1283
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]