Hello guys, today I have updated Avast Free Edition directly via the program (not from scratch).
Then some bugs happened and apparently, just by looking the other forum threads I think that you released a buggy version of your program
First I should describe my configuration :
Dell Studio 1537
Windows Vista SP1 32 bits
Core2Duo T5800 2 GHz
3 GB RAM
ATI Mobility Radeon HD 3400 Series
So here are the symptoms after the update (You should know that I didn’t have those symptoms just before the update so don’t tell me “you have a virus” please):
After the windows login phase, when the desktop appears I have 2 errors windows showing and saying that I have a problem with “WLTRYSVC.exe” and another with “bcmwltry.exe”.
After those windows I have 2 options:
° Let windows look for a solution online → lead to nothing
° Close the windows → the “bcmwltry.exe” error window appears again and again (Actually I can see in the task manager that this process keeps crashing and starting again, so it’s normal that the error windows keeps showing [ps: the non-stopping starting/crashing leads to a high usage of CPU and a f**ing high memory leak])
I have to say that in order to fix this problem I had to go the service manager of windows ‘services.msc’ and turn the named “Dell Wireless WLAN Tray Service” to “manual”, because this is the service launching both “WLTRYSVC.EXE” & “bcmwltry.exe”.
Those 2 processes are related with the Broadcom drivers of some broadcom hardware.
The other fact that appeared just after this update is that when I launch the software “WildPackets OmniPeek” (a network monitoring software like Wireshark), I have an error windows pop-up saying that a problem appeared with “ntdll.dll”.
It seems that both symptoms are related with something from the OS and the network layer files.
So I hope that those information will help you to fix those problems because it seems that lot of people will suffer from this update.
Hello coldy and avastyellowjacket, welcome to the forums.
Does your error message have some error-no (ex. 0xC0000005) or like that?
If you add these software to Behavior Shield’s exclusion lists, does it solve your problem?
@c0ldy
There is already Vista SP2, so I recommend to update your Vista to SP2…
Signature du problème :
Nom d’événement de problème: APPCRASH
Nom de l’application: BCMWLTRY.EXE
Version de l’application: 4.170.77.13
Horodatage de l'application: 4835b392
Nom du module par défaut: ntdll.dll
Version du module par défaut: 6.0.6001.18000
Horodateur du module par défaut: 4791a7a6
Code de l’exception: c0000005
Décalage de l’exception: 0002dc1e
Version du système: 6.0.6001.2.1.0.768.3
Identificateur de paramètres régionaux: 1036
Information supplémentaire n° 1: e51a
Information supplémentaire n° 2: 4c0d4d78887f76d971d5d00f1f20a433
Information supplémentaire n° 3: e51a
Information supplémentaire n° 4: 4c0d4d78887f76d971d5d00f1f20a433
Signature du problème :
Nom d’événement de problème: BEX
Nom de l’application: BCMWLTRY.EXE
Version de l’application: 4.170.77.13
Horodatage de l'application: 4835b392
Nom du module par défaut: StackHash_6bc7
Version du module par défaut: 0.0.0.0
Horodateur du module par défaut: 00000000
Décalage de l’exception: 0011ca08
Code de l’exception: c0000005
Données d’exception: 00000008
Version du système: 6.0.6001.2.1.0.768.3
Identificateur de paramètres régionaux: 1036
Information supplémentaire n° 1: 6bc7
Information supplémentaire n° 2: f3f6a1403802118ada460cd45530935b
Information supplémentaire n° 3: 6477
Information supplémentaire n° 4: d34edb9b57aa7d1aac3252e1a9591198
I don’t think any translation is needed. (Or at least, google translate won’t produce absurd content)
@NON : Come on, this isn’t a windows vista problem (for once), there is no need to update.
I am finding that accross the board (8 machines) three separate licenses, Two of Pro and one AIS. All are newer machines (oldest 18 months) pretty powerful hardware, min 512 video. All are running Win 7/64. All machines intel P7350 and above with most machines runnning AMD quad or 6core processors with 8 GB ram and multi disk raids. Upon first start, most tasktray programs that use internet access fail to get connectivity. IE: weather and stock programs. But upon re-starting that program once manually and manually updating the data fixes the connectivity problem permanently. Subsequent reboots work fine and the tasktray programs continue to work as intended.
Seems nice overasll, no other issues noted. Visibly faster web page loads with this vs older betas.
@c0ldy
It seems your app crashes are the same issues (0xC000005) that I had during beta testing.
Unfortunately I have to say this issue may need program update to fix.
I think uninstalling (not stopping) Behavior Shield solves your issue temporarily (but I’m not sure, sorry).
And please upload these EXE files to ftp://ftp.avast.com/incoming, this helps developers to solve this.
pk, could you analyze this issue?
@jaykaykay
Please start your own thread, your issue seems different from this thread.
Same problem here, on a Dell Inspiron 1525 running Windows Vista Ultimate SP2. Problem details:
“Dell Wireless WLAN Card Wireless Network Controller has stopped working”
Problem signature:
Problem Event Name: APPCRASH
Application Name: bcmwltry.exe
Application Version: 4.170.25.12
Application Timestamp: 46f3437a
Fault Module Name: ntdll.dll
Fault Module Version: 6.0.6002.18005
Fault Module Timestamp: 49e03821
Exception Code: c0000005
Exception Offset: 0002998c
OS Version: 6.0.6002.2.2.0.256.1
Locale ID: 1033
Additional Information 1: e51a
Additional Information 2: 4c0d4d78887f76d971d5d00f1f20a433
Additional Information 3: e51a
Additional Information 4: 4c0d4d78887f76d971d5d00f1f20a433
and “Dell Wireless WLAN Card Wireless Network Tray Applet has stopped working”
Problem signature:
Problem Event Name: BEX
Application Name: WLTRAY.EXE
Application Version: 4.170.25.12
Application Timestamp: 46f343b5
Fault Module Name: StackHash_6bc7
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 001d3282
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.0.6002.2.2.0.256.1
Locale ID: 1033
Additional Information 1: 6bc7
Additional Information 2: f3f6a1403802118ada460cd45530935b
Additional Information 3: 6477
Additional Information 4: d34edb9b57aa7d1aac3252e1a9591198
I can still access the wireless network, but if the error dialogs are dismissed they immediately recur so the work around is just to leave them open and minimized.
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.
Of course it is temporary, what other choice do you have if you can’t use your wireless lan. The behaviour shield is currently only working in passive mode as it gathers data on the any suspect behaviour and passes that bask to avast so that the rules and filters can be tweaked to try and reduce false detections. So it isn’t currently providing the same kind of protection as the rest of the resident shield which should still do their job.
Why when it is in passive mode there is this kind interaction is beyond me as an avast user, but whilst the developers are working on a resolution, this suggestion may well allow you to at least proceed. Some have set it to Ask rather than the default of Allow and that is a possible area where if there isn’t a response whatever it might be, then that device might not start.
If you have had no problems then that’s great. But I have a Dell laptop that is fully patched with all of the latest drivers and can attest that there are indeed reproducible problems with some Dell machines.
While some are quick to blame drivers when people have problems with a new software version, it should be noted that systems that coexisted peacefully with the former 5.0.677 version do not with the new 5.1.864 version. It’s not unreasonable to suspect that something is wrong with the new version, especially when other users are reporting the same issue.
Note also that the bug that has been reported affects the Dell (Broadcom) wireless cards. What wireless card do you have in your system? If you don’t have the same card that we do, then you likely won’t experience this problem.
