[Resolved] Version 5.1.864 conflict with Dell 1395 wireless card driver

[rwaters]

[at] rwaters: Thanks for understanding what my intention are and I hope your machine is working.

Regards,
                Tenko

I'm back up now; thanks for asking. I originally went back to the 5.0.677 version but there is a workaround using 5.1.864. If you uninstall (not disable) the Behavior Shield after updating to the new version, the wireless driver conflicts go away. But I can certainly understand not wanting to tell customers that they are operating with a workaround, so I would probably ask them to stay with the previous (stable) version for now.

[coldy]

why don't you try to downgrade avast by uninstalling the version that you have and download Avast 5.0.677

Regards,
              Tenko

Please stop telling people to downgrade. 
That fixes nothing and only prolongs the amount of time that it takes to work out any missed bugs.

I think you are only making one mistake: we are NOT beta testers.

We are end users that want their system to be stable.

We have just hit the "update program" button on the GUI, we haven't signed anything saying "yeah we want a buggy program in order to find bugs related to drivers and other software".

[bob3160]

On my Dell Vostro 1700, I'll do without the Behavioral Shield
till the problem is fixed but enjoy the updated and latest version.

[KingKull]

We had this issue on an Inspiron E1505...I just disabled Windows error reporting. No more notifications...

[rwaters]

We had this issue on an Inspiron E1505...I just disabled Windows error reporting. No more notifications...

Of course, this merely hides the problem and will also hide any other legitimate Windows notifications. If you want to stay with the new 5.1.864 version instead of going back to the previous 5.0.677 version, I'd recommend re-enabling Windows notifications and uninstalling the new Behavior Shield instead.

[Tenko]

bob... I want to see how avast bug report look like. If you don't want to share it here please me PM

Thanks

Regards,
              Tenko

[Rednose]

Personaly I never use Avast! Support to report bugs. I do that here on the forum and notify an Avast! Developer about it. But sometimes it is easier to troubleshoot a bug in a one to one conversation, like I had with Petr in the past

Greetz, Red.

[bob3160]

Quote from KingKull

If you want to stay with the new 5.1.864 version instead of going back to the previous 5.0.677 version, I'd recommend re-enabling Windows notifications and uninstalling the new Behavior Shield instead.

Disabling it is easier then you only need to reactivate it once the problem is solved.
You'll also need to make a change in the settings - status bar - uncheck behavior shield monitoring.
By doing that you will not get the warning that your system isn't secure which is usually displayed when one or more shield are off.

[Hard_ROCKER]

Bob most users are reporting that even if you disable the Behavior Shield the problems still remain. Apparently only a complete un-install of the Behavior Shield fixes it...

[NON]

Bob most users are reporting that even if you disable the Behavior Shield the problems still remain. Apparently only a complete un-install of the Behavior Shield fixes it...

+1

As far as my experience, this 0xC0000005 error does not go away with Behavior Shield disabled, you have to uninstall Behavior Shield.

Have both of you tried what was suggested by NON, uninstall the behaviour shield element ?
Windows add remove programs, Avast xxx, click the Change/Remove button, click the Change section from the new window and uncheck the Behaviour Shield entry, OK your way out and reboot.

That fixed it for me as well. Good call, NON. After my original install attempt, I disabled the Behavior Shield but did not uninstall it.

Hopefully, this will give the developers something to work with.

Thanks, guys.

[bob3160]

I haven't had any more problems since disabling the behavior shield.
If I do, I'll report back after I uninstall the shield. For now it's just disabled
and this is being posted from that Dell Vostro 1700.

[rwaters]

I haven't had any more problems since disabling the behavior shield.
If I do, I'll report back after I uninstall the shield. For now it's just disabled
and this is being posted from that Dell Vostro 1700.

Bob, you are the exception to the rule. If you read the numerous posts on this issue, no one else has been able to correct this problem by simply disabling the Behavior Shield, rather than uninstalling it. If this works for you, then great, but it's very unlikely that it will work for others. Disabling the shield definitely did not work for me.

Out of curiosity, what wireless card do you have in your Vostro?

[coldy]

Just to say: uninstalling behaviour shield fixed my problems too.

[Nesivos]

Release Date:2/1/2009
Version:   4.170.77.3 (Driver); 4.170.77.18 (Application), A22-1
Download Type:   Driver   
File Format:   Hard Drive
File Size:   58 MB

http://bit.ly/h3u08p

The driver is almost two years old.

Have you used a program like DriverMax to see if there is a more current version of the driver?

Also, what Windows OS are you using?  I don't believe that you mentioned.

Also if you go here and look at the list of computers for the Broadcom Wireless 1395 driver the Dell Inspiron 1525 is not on the list

http://bit.ly/dEzDXb

Just asking

[rwaters]

Release Date:2/1/2009
Version:   4.170.77.3 (Driver); 4.170.77.18 (Application), A22-1
Download Type:   Driver   
File Format:   Hard Drive
File Size:   58 MB

http://bit.ly/h3u08p

The driver is almost two years old.

Have you used a program like DriverMax to see if there is a more current version of the driver?

Also, what Windows OS are you using?  I don't believe that you mentioned.

Also if you go here and look at the list of computers for the Broadcom Wireless 1395 driver the Dell Inspiron 1525 is not on the list

http://bit.ly/dEzDXb

Just asking

Who is this question directed to?

This driver is the latest that Dell offers for cards based on that particular Broadcom chip set, and there are many Dell models that use these cards. The fact that this driver doesn't appear in the list of drivers for the Inspiron 1525 simply means that Dell didn't bother to update the 1525 page on their website. And there is no way I'm going to trust sites or applications like DriverMax when it comes to hardware drivers. I'm going to get those from the vendor's website, no matter how "old" they are.

From reading some of your other posts you seem to think that every problem a user has with Avast is a driver issue, but that's absurd. With all due respect, Nesivos, this conversation is really a waste of time because this particular issue is not a driver problem. It has been traced to an issue with the new Behavior Shield and it is being worked on. Let's just wait for a new build and see what happens.