My computer has been rebooting every so often since I installed a webcam driver on the 15th. I d/l win debugging tools and checked the minidump files. It says
BugCheck 1000000A, {16, 2, 0, 804e469a}
*** 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 )
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000016, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 804e469a, address which referenced memory
It would seem to me that it is the webcam drivers that have caused the problems, but windbg says aswtdi.sys which is an avast file. Any help would be appreciated. Lemme know what other info is needed other than the standard…
Windows XP SP2
AMD Athlon XP 1800+
512MB DDR
Thanks in advance. I’ve even reformatted the system twice and it seems the problem occurs after installing the webcam drivers. Is it possibly interfering with avast or vice versa?
Well cmdmon.sys is a comodo firewall driver/hook that could well be in the mix also since it is named too.
Recently in the forums, there have been occasions when applications incorrectly see aswTdi.sys as a firewall. One of these is Agnitum’s Outpost Security Suite 2008 (possibly Outpost Firewall Pro 2008) and it actually asks if you want to disable it to avoid conflict. The other I believe was a PC Tools application, I can’t recall which, but it too thought aswTdi.sys was a firewall.
Negeltu, I have no conflicts with aswTdi.SYS and Comodo in Vista.
My problem was different, just that Comodo does not install the network driver (the core of the firewall) in my computer…
Negeltu, thanks for your minidumps & good windbg’s analyze report 8).
Anyway, we are convinced (me & lukor) that BSOD is not our fault. We just forward all data from comodo firewall driver to network drivers and because they got invalid data, system crashed. Windows blames us, because our driver was the last one it received the invalid data from http://www.clubic.com/api/forum/img/smiley/colere.gif
.
I see, you’re using Comodo firewall (version 2.4) - latest version is from January 23 (almost one year old!). Lukor has already noticed them fixing the bugs in this driver, but they replied this version is obsolete and they do not care anymore ???.
Either uninstall network shield provider (and expect BSODs with other network drivers) or upgrade to comodo v3 (or other firewall).
Ok guys. I will give v3 of Comodo a try. I just don’t understand why this happens only after reinstalling my webcam driver. I was pretty sure it wasn’t avast’s fault. I just wanted to make sure.
Thanks again for all the help. I will install comodo v3 and give my webcam another go.
I had this before when my inside was blazing and it rebooted on me when in the middle of just installing .Net Framework then I gotten that BSOD and then realised I made a boo boo with my cooling. Forgot to turn on one of my coolers.
Yeah. I build a lot of systems and have a habit of monitoring my temps very closely. So that wasn’t my problem. I upgraded to Comodo 3 and no more problems. PK was right. And I really do appreciate all of you for the help you gave me. I still think though that the webcam driver and Comodo were conflicting in some way. If I uninstalled the webcam driver the problem went away too. But after upgrading Comodo to v3 …the webcam and Comodo are playing very nicely on my system.
