Avast!Free 5.0.677 and Windows 7 Home Premium x64 Crashes

Avast Free Antivirus / Premium Security
1

Hello All!

I have some troubles with my laptop - Acer Aspire AS3810TZG-414G50n with Windows 7 x64 Home Premium. I have a lot of BSOD crashes. I have installed Avast!Free 5.0.677 and Outpost Firewall Pro 7.0.4. The crashes are always ndis.sys ( ndis+17c1e ) and ntoskrnl related, and today after upgrade to Outpost 7.0.4 the computer crashes every 30-40 mins. I posted it to the Outpost support, but the thing is that I got a crash after I stopped the Outpost Firewall and I was wondering if Avast could be the problem.

My laptop specs:
Intel SU 4100 1.3 GHz
Radeon HD 4330 512 dedicated memory and Intel switchable graphics
4GB Ram
Atheros AR8131 PCI-E Gigabit

BTW I love Avast, I have been using it for years know and it had never failed me!

I cannot attach the minidumps as they are above 200KB but at the end of the post I included the last one.

Thanks in advance.

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\112610-19890-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***

  • Symbol loading may be unreliable without a symbol search path. *
  • Use .symfix to have the debugger choose a symbol path. *
  • After setting your symbol path, use .reload to refresh symbol locations. *

Executable search path is:

  • Symbols can not be loaded because symbol path is not initialized. *
  •                                                               *
  • The Symbol Path can be set by: *
  • using the _NT_SYMBOL_PATH environment variable. *
  • using the -y <symbol_path> argument when starting the debugger. *
  • using .sympath and .sympath+ *

Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff80002c67000 PsLoadedModuleList = 0xfffff80002ea4e50
Debug session time: Fri Nov 26 15:32:37.498 2010 (UTC + 1:00)
System Uptime: 0 days 0:58:11.823

  • Symbols can not be loaded because symbol path is not initialized. *
  •                                                               *
  • The Symbol Path can be set by: *
  • using the _NT_SYMBOL_PATH environment variable. *
  • using the -y <symbol_path> argument when starting the debugger. *
  • using .sympath and .sympath+ *

Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
…
…
…
Loading User Symbols
Loading unloaded module list
…

  •                                                                         *

  •                    Bugcheck Analysis                                    *

  •                                                                         *

Use !analyze -v to get detailed debugging information.

BugCheck D1, {28, 2, 0, fffff880016ccc1e}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

**
*** WARNING: Unable to verify timestamp for ndis.sys
*** ERROR: Module load completed but symbols could not be loaded for ndis.sys

Probably caused by : ndis.sys ( ndis+17c1e )

Followup: MachineOwner

2

If you had no problems untill you upgraded outpost then i would try deleting outpost just to see what happen’s, there might be something about the latest update that doesn’t agree with your system or a corrupted install that didn’t show itself untill after you disabled it.

3

ndis.sys is related to networking - which would suggest that although you have disabled outpost it still has drivers running

4

Hi, thanks for the replies to both of you, the problem is from a while, but today after the update is severe. At the moment both are disabled and no problems so far. I will uninstall Outpost and run Avast for a while to see if there is a problem.

5

I was having severe crashes due to using Comodo Cleaner. What are you using to uninstall your programs, clean registry and so forth? As soon as I did a reinstall of what Comodo Cleaner deleted my system was back to normal. I have not had any problems with Avast Pro and Online Armor but I did have some problems when I started using that cleaner product. At first I thought it might be my Firewall program causing the blue screens but then found out it was something completely different. Did you ever use just Avast and have these sort of issue’s?

6

I have been using Outpost firewall pro for some time, last night I allowed it to update to the latest version and no issues.

Have you done as suggested in the compatibility window after the OP update and excluded the outpost folder in avast ?
I don’t do that, I just click the not done (which changed to done), but I do have the following file excluded in the File System Shield, Expert Settings, Exclusions - C:\Program Files\Agnitum\Outpost Firewall Pro\wl_hook.dll

7

I just checked on the Comodo cleaner. It is made for use with Windows XP and Vista. It does not list Windows 7. There are others listed for Windows 7. It includes the Home Premium x64. It is one thing I check. It is which version of Windows software is compatible with. It is a firewall. It is with the free avast! I found Windows firewall is sufficient. It’s if set right. No additional firewall is needed. I hope this helps.

8

You need to check your date’s before posting, this is a three week old thread.