I'm running the demo version of avast! 4.7 Professional and according to WinDbg a BSoD that has just happened was probably caused by the aswTdi.SYS file.
Microsoft (R) Windows Debugger Version 6.7.0005.0
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Mini050707-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_qfe.070227-2300
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805535a0
Debug session time: Mon May 7 18:32:56.265 2007 (GMT+9)
System Uptime: 0 days 7:34:48.861
Loading Kernel Symbols
...
Loading User Symbols
Loading unloaded module list
.........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {16, 2, 0, 804f8f66}
*** WARNING: Unable to verify timestamp for aswTdi.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswTdi.SYS
*** WARNING: Unable to verify timestamp for cmdmon.sys
*** ERROR: Module load completed but symbols could not be loaded for cmdmon.sys
Probably caused by : aswTdi.SYS ( aswTdi+44d )
Followup: MachineOwner
---------
At the time I was printing to a network pinter (which is a Canon i560 running off a WinXP machine) from Firefox 2.0.0.3. I have only had one BSoD and don't want to print anything to this network printer until I can fix the (alleged) problem. I have had avast! installed for about a week and haven't had any BSoD's on this machine before, and haven't actually used the network printer while having avast! installed.
My avast! 4 version numbers are:
Build: May 2007 (4.7.1001)
Xtreme Toolkit version 1.9.4.0
Using ActiveSkin version 4.2.7.3
Compilate date: 05/05/2007
File version: 000738-3
I have read
this thread from 2005 and found posts searching for this SYS file that said this problem had been fixed in a previous version.
I am going to run the printer locally for now, but am curious if this error will occur transferring files and using Remote Desktop to another machine on the LAN? It hasn't so far but would still like to know.
Is there anything I can do to fix this problem?
Thanks.