Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: jbignes5 on September 15, 2005, 02:39:19 PM
-
I tried the beta of Windows XP Pro x64 for a year and got strange shutdown problems. If I leave Avast AV running at shutdown x64 will hang at the shutdown screen for hours. If I shut off the av before shutting down x64 it shuts down normally without a hitch. Something is going on here at shutdown. Since I have upgraded x64 to retail version the problem continues to happen. Has anyone else have this problem?
I can reproduce this problem every time and fix it every time by closing the AV before shut down. Maybe Avast programmers could check into this please. Since IMHO Avast is the best thing to come round the bend for the price (free)!
Keep up the good work guys!
Thanks for your input,
Jbignes5
-
There were a few similar reports, but the problem is that we cannot reproduce the problem on our machines, and it also seems to be impossible to generate the memory dump at the frozen state :(
See this thread (http://forum.avast.com/index.php?topic=16259.0).
-
I share this problem. The pc often hangs on shutdown.
Is there anything I can do to assist in solving it?
My hardware & drivers:
Asus a8n-sli deluxe w/ bios 1013, latest whql nVidia x64 drivers (6.66)
Amd x2 3800+ at specs, latest amd x2 x64 driver
4 x 512mb generic ddr (validated by stringent prime95, pifast and memtest runs) at specs
Msi geforce 6600 gt, latest nVida x64 driver 78.01
2 x seagate barraguda 7200 hd, windows ide driver
1 x samsung dvd
1 x LG cd-rw
Roadrunner 510 external dsl modem
usb logitech keyboard
usb lugitech mouse
My software:
Windows XP x64 professional default install fully patched
Firefox latest version
Thuderbird latest version
Ad-Aware free version (non resident install)
Avast home 4 free version
Bitcomet (for 100% legal use in my country, so please no moral rants)
Windows messenger (the version that came with the windows)
Thats it!
Observations:
- The same pc without avast does not hang.
- The dsl modem light blink peridiocally when the shutdown occures. The pace of the blinking appears 100% regular (even intervalls), as opposite to unregular flashing caused by packet reguests from the net.
- Turning off (diabling) p2p, IM and outlook providers on avast does not help.
- Shutting down (by disconneting power) dls modem after hang does not help
- After shutting down hang pc with the 5 sec powerbutton press, the dsl modem remains in "bright light and blinking mode" whereas with normal shutdown it switches to "dim light and no blinking mode" (no, I am not an engineer :-)
So is there anything I could do? I will provide memory dumps if you tell me how.
-
Well, the link in my previous posts leads to a thread that explains how to create the memoru dump, but
- it seems that the memory dumping procedure doesn't work that late during the shutdown process
- the dumping procedure does not work with USB keyboard
So, I'm afraid we don't have any solution right now... :(
-
Me too, I have the exact same problem on XP x64, although it is intermittent, usually occurs if the PC has been on for a while.
Does anyone know if this also occurs if the logged on user has admin privileges ?
:Tony:
???
-
I guess that it can be somewhere in the windows core.
You can try to install avast without any modul, just scanner.
And try if that will work. Then add modules one by one, and test system how it react you differnt modules. So you can find what modul is using what.
BTW...... it can be some windows dll that have corrupt information. Update windows.
msvcr*.dll is part of system that lot of programs requid to work properly. You can try use those from windows xp 32-bit. // I am not sure if that do somthing. But you can try.
-
I'm having the same issue, but I think I've found a possible workaround.
Below is my reply to a similar post on the planetamd64.com forums (got to both threads via google): http://www.planetamd64.com/index.php?showtopic=8408&st=40&p=125975&
[jasuca @ Sep 18 2005, 09:26 AM]
I had the same problem, I think it started when I installed avast!. But I find the solution, in the configuration of avast! you must desactivate "I'm always connected to internet" so, you colse the connections. And that's all.
I think you might have something there.
The problem started right after I installed Avast on my x64 system. I've only tried it once or twice, but it doesn't seem to be freezing at shutdown anymore after I de-activated that option. It is still hanging a bit more than usual on shutdown, but it is shutting down.
-
BIOS is not to play with but it plays with us...... :'(
-
Angryguy: I must say that it's quite strange (that this option would have anything to do with the problem). Are you sure it's related? I mean, if you turn the option back on, does the problem appear again?
I know that it's rather hard to say when the problem doesn't occur every time...
-
in the configuration of avast! you must desactivate "I'm always connected to internet"
This option is not activated for my setup, I have never turned it off so I assume it was installed with this setting disabled by default.
As I still have the problem, I can say this didn't fix it for me, but as this problem is intermittent, I can only test any possible fixes over a period of time, the only sure thing is if I kill AVAST before shutdown.
-
Um..
- XP x64 oficial version, non beta and fully update in "microsoft update"
- Processor P4 650 (with EM64T)
- 2Gb DDR 2 711
Avast! work for me perfect too. You are using beta version or release of XP x64?
-
It also works correctly on our test machines... that's the problem.
Could everybody having the problems post a comprehensive description of his machine here, please? I mean CPU, motherboard (chipset), video card, disk controller... possibly also versions of the corresponding drivers? Maybe we could find a common factor... conflict of some specific drivers, or something like that.
Let's not forget low-level software, if there's any (like firewalls, if any support Win64).
Thanks.
-
I too have this same problem. And as RawOstrich has, I too have an Asus board for an Athlon 64.
My specs:
AMD Athlon 64 3500+ (939 pin)
Asus A8N-E M/B
3 GB of PC 3200 ram (2x512mb, 2x1gb)
2x 120 GB SATA HD Striped together
16x DVD NEC burner
PowerColor Radeon X850Pro (256 mb) PCIx version
MS Windows XP Pro x64 edition (retail w/ all crit updates)
Running nVidia NForce drivers ver. 6.66 w/ Asus bios 1.06
-
I have also this problem, but sometimes machine will shutdown or sometimes not. I have also noticed that it will not shutdown if the user has no admin priviledges. But even with admin priviledges the machine will not shutdown. Merely I have though this could be some "properties" ;) of a new Windows, because I remember once there was also a shutdown problem with Win98 itself when you have shared network drives.
Although I send my specs also if it helps someone
Shuttle SN25P
AMD Athlon64 3500+
NVIDIA nForce™4 Ultra MCP drivers 6.66
NVIDIA GF6600GT drivers 77.77
VIA Envy24PT drivers 4.60b
1024Mb PC3200
NEC 16x DVD
-
My PC spec is:
CPU: AMD Athlon 64 X2 4600+
Mobo: GigaByte K8NXP-SLI
RAM: Kingston 2GB DDR PC3200 400MHz Non-ECC
Disks: 3x Hitachi Deskstar T7K250 SATAII (non-RAID)
GFX: Gigabyte GeForce PCX6600GT PCI-Express
PSU: Antec 550W
Case: Antec Sonata
Nvidia System Drivers v6.66 =
Audio driver 4.62 (WHQL)
Audio utilities 4.51
Ethernet driver 4.82 (WHQL)
Network management tools version 4.85
SMBus driver 4.48 (WHQL)
NVIDIA PATA RAID driver 5.34
NVIDIA SATA RAID driver 5.34 (WHQL)
NVIDIA SATA IDE driver 5.34 (WHQL)
NVIDIA RAID Application 4.82
Installer 4.77
Nvidia Graphics Driver: GForce v7.7.7.7
-
I am using Windows XP Pro x64 with all updates on a new Gigabtyte GA-8I955X Pro motherboard with 1 GB DDR2 RAM and Intel 660 (3.6ghz) processor. It has the Intel 955 chipset.
I do not have any problem with shut down or restarting.
-
So, right now the common factor seems to be AMD with nForce chipset, possibly drivers v6.66... anybody else with the same problem and different chipset?
-
I have this problem permanently
chaintech vnf4 ultra :driver 6.69
PoV 6800GT pci-e :driver 81.95
audigy 2 zs : driver 5.12.06
corsair 2x1024
modem router olitec sx 200
printer HP 3550
-
I believed to have to find the problem, 3 days of normal shutdown
I have modiffier the times of search for update of the data base viral & program of 240 mn with 1440 mn
waste of time and effort, is a track dug nevertheless!!!!
translated by google French into English
------------------------------------------------------------------------------------------------------------------
j'ai crus avoir trouver le probleme,3 jours d'arrêt normal
j'ai modiffier la délais de recherche de mise à jours de la base de données viral & programme de 240 mn à 1440 mn
peine perdus,s'est une piste a creusé quand même !!!!
-
I have the same problem but am using a intel Xeon and 525 northbridge and the full version of XP Pro x64 everything fully updated.
-
colinpotts: So you don't have the nForce chipset which until now seemed to be the common factor?
-
I loaded XP64 trial to an ASUS A8V deluxe and installed Avast 4.6 and had the same shutdown problem. If I right click the A icon and disable then it would shut down normally. This morning I upgraded the bios to 1017 and also put in the latest VIA 4in1 and the problem disappeared. Just thought you guys should know.
Now XP and Avast work together perfectly.
-
***
I have an AMD 64 3200 on a Gigabyte GA-K8NS Ultra-939 motherboard (nForce3 Ultra chipset) with 1gig of memory. I also have Avast Home and Windows XP home. I have not had one problem with this setup. So, it seems to me that the problem should be with XP Pro x64 and not AMD nor the nForce chipset. But, I could be wrong. :o ;)
***
-
Hi!
I did not realize i had the shutdown Problems becouse of avast until i read it here. But the reason i looked here is becouse i also got a big Problem when starting Windows XP Pro 64. After a complete startup it starts Avast and a couple of seconds later it just sort of freezes.
The Taskbar is completely frozen however when i am for example in the Avast Provider Setup before it frozes i am able to switch to the different Providers and see when it scans.
Somehow it locks up everything and i am unable to get to the Task Manager (neither by Menu or Hotkeys) or something else.
To stop that i had to switch of the PC by using the Powerswitch, then startup at safe mode and then disable the automatic start of all avast services. Then i was able to make a normal startup of windows and to look for a solution...
I also uninstalled the last two Windowsupdates but, that did not help anyway. Please Help.
My System:
AMD Athlon 64 3000+, Asus A8V Deluxe Mainboard (AGP), 1 Gig RAM, 1 SATA RAID Array 160 GB
I already tried updating the Bios an the VIA Drivers, and a new installation of avast... no change.
thx, Dready
-
FYI I've just ordered such a machine (with Asus A8N-SLI Deluxe motherboard). It should come in a couple of days.
Hopefully, the problem will reproduce on this machine, and we'll be able to solve it. I'm quite curious already.
BTW we have a number of Intel based x64 computers here, and none of them seems to have this problem. Also, we have one Athlon64-based with VIA chipset - and this one is working well, too.
Thanks,
Vlk
-
Hi!
I have also a VIA Chipset and the Problem i descriped earlier. Seems like somehow the system is locked...
I use the german Version.
Bests, Dready
-
Similar to Charlie (up above)...we have no problem with this.
I have an AMD 64 3200 939 core on a MSI K8N Neo2 Platinum motherboard (nForce3) with 2gig of memory. Cheers
-
Alright folks.
I have some good news. The box has arrived, and the problem DOES simulate on it.
Now remains the 2nd part - to find out what the problem is, and fix it. :)
Back to work...
-
OK, I have had 5 months of testing this exact problem ever since i got my new pc.
the specs are
Asus A8n sli deluxe mobo
amd 4400 DC
2 xfx 7800gtx 256 sli
2 gig corsair xms ram
1 western digital sata, 1 seageate Bcudda, 1 samsung spinpoint.
Audigy 2 zs
nec dvdrw
msi cdrw
all chipsets drivers from 6.**
and both cpu drivers 1.2.2.1 and 1.2.2.2
multiple vid card drivers
mobo bios 1011, using 1015 atm
now, the problem lies within the nforce4 chipset or the acpi drivers, Although avast is being locked as a service and isnt unloading.
Because even without avast being installed on my pc, it still hangs on shutdown. less frequently might i add, but with avast being installed it hangs 95% of the time.
I checked event manager and infact there is a load of userenv errors about a unloadable service, the errors only appear after avast has been installed.
I have tried microsofts UPHClean program which supposdly forces unloadable services to shutdown, but that didnt help.
Basically, in 5 months of testing, I have came to the conclusion that its either nf4 (most likely) or my dualcore cpu. As lots of programs, mainly games have problems with dualcore, but out of the 2, I really suspect that the nforce4 chipset is to blame.
Although avast is conflicting for want of a better word with nf4 chipset, as even after a format and just the nf4 drivers and cpu drivers installed, the pc still hangs every now and then, but it does shutdown, sometimes it takes its sweet time in doing so. As soon as avast is brought into the equation the hangs gets worse.
With just windows and chipset drivers and cpu driver, i can shutdown say 30+ times without it locking up, then i may get a few lockups or extremely long shutdowns, then it will return to normal, with avast installed, i can get like 30 lockups/long shutdowns in the space of 40 tries.
I am using xp pro 32
doesnt do it on my other pc.
msi neo mobo
amd64 3000
1gb ram
6800gt
dvdrw-cdrw
VIA CHIPSET
-
I have exactly the same problem! However, the system does not always hang on shutdown and I have noticed that logging users off before shutdown also reduces chances of hanging. The common factor here is that I also have ASUS motherboard. My system is:
CPU: Intel Pentium 4 630
Motherboard: Asus P5GPL
Chipset: Intel Grantsdale i915PL
RAM: 1GB (2x 512MB PC3200 DDR SDRAM)
Graphics: ATI RADEON X800GT
No messages in log, no failure reports by auditing (though I do not audit system events - only default auditing of all failures), "always connected to internet" is not set in Avast settings.
-
OK, I have had 5 months of testing this exact problem ever since i got my new pc.
the specs are
I am using xp pro 32
Since this thread is about a problem with avast Home and windows XP Pro 64 bit OS this should really be in its own thread or one that relates to XP 32 bit shutdown problem, etc.
-
well since i got directed to this thread from avast support via an email, and he knew i was using xp pro 32, then i guess not.
he blamed it on nforce4 chipset, like i do, so i dont think it has anything todo with 32 or 64b version of windows. Although others who havent got nf4 chipsets still have similar problem, it may not necessarily be caused by the same thing.
dude also gave me a fix that i will try tomorrow when i reinstall avast.
-
Alright people. As I already said, the nforce4 machine has arrived, we have been able to simulate the problem and now, we even think we've found a cure. :)
The problem may appear on both 32-bit and 64-bit Windows, although the latter seems to be considerably more prone to it.
I'd like you to try the following patch.
1. Download this file
http://cat.asw.cz/~vlk/nforce4/x64/AavmKer4.sys (64-bit Windows only) or
http://cat.asw.cz/~vlk/nforce4/i386/AavmKer4.sys (32-bit Windows only)
and save it on your desktop.
2. Using Windows Explorer, copy the file from your desktop to the \Windows\System32\Drivers folder (replace existing version). Please note that if you're NOT asked to overwrite the existing version, you're probably copying it to an incorrect location. If running under 64-bit Windows, this may be caused by the fact that you're using a 32-bit file manager program - that's why I suggested using Windows Explorer for this. 32-bit programs don't have access to the real System32 directory.
3. Restart the computer.
That should be it.
I'm looking forward to hearing your comments.
Thanks :)
Vlk
-
Bump... Anyone?? Did this solve your issues
Side note: Props to company for amazing customer support. Too buy a new rig for testing purposes based on reports in this forum is yet another testiment to avast & its commitment to be the best.
I look forword to yet another great year with avast being my #1 choice for AV detection..
Merry Christmas & a happy NEW YEAR to all!!!
-
I think thats the file I got last night from someone at avast, anyways I am about to install avast and test, I should have an answer in a few minutes.
EDIT:
Avast is installed and the file is in place.
After i had installed avast and then restarted to put the file in place, i clicked shutdown
and youll never guess what happened ?
It shutdown without hanging/locking up ;D
am gonna do somemore checking to see if it wasnt a fluke.
but early signs look good.
-
Vlk, won't the updated file be overwritten by the self-repair feature?
-
I don't have nforce yet i have the same problem.
Here is my pc spec (http://www.octorn.com/DxDiag.txt)
-
Vlk, won't the updated file be overwritten by the self-repair feature?
As a matter of fact, it doesn't seem to be the case. Might actually be a bug - but the file doesn't get replaced (at least not on the machine I tested it on). I guess it would happen only if we replaced the <avast>\setup\inf version as well...
epox123, so, did you try the patch? Or anyone else?
-
Yippee - your change in files works! At least for the one cycle I have done thus far . . . . .
See: ashdesp.exe halt (ashDisp.exe)
It also clears up the dwwin.dll error that would show up after the ashDisp.exe halt error pop up window!!
Thanks!!!!!!!!!
JD
-
Like i said i dont have Nforce I got VIA, my mother bord is asus sk8v.
I just reinstalled windows because i had to force my pc to shutdown, this caused errors on my hard drive.
I'm going to update windows and shut down 5 times see what happends; this is with out avast
-
I spoke too soon. On the next shut down the same old problem was there.
I have also reloaded Zone Alarm and the problems with that are still there as well. As a matter of fact - with that running I couln't even get to he Avast site.
??????
-
epox, the patch is not nForce4 specific. Just try it, please...
Sawdust, it is possible that avast in fact replaced the patched file by the original one (as Igor suggested above). Could you please check the timestamp of the file (\windows\system32\drivers\AavmKer4.sys)?
Or the file size. The patched file is exactly 17,920 (x64) or 24,240 (i386) bytes long...
Thanks
Vlk
-
This is an avast problem i have shutdown 5 times with out avast and it doesnt hang.
I will try the sys, i remeber some reading that if you go in safe mode windows wont replace files. ill give it a shoot.
-
Ok i tryed that and doesn't work.
I installed windows did updates, tested by shuting down 5 times, it didn't hang then i install avast and did the sys swich and shutdown only once and it hanged on me...
so why would avast not want to stop its service.? and why can't you guys fix this...
also older versions of avast never did this so mabe look at whats been changed.
also just so you know the timestamp is in order.
-
Did you restart the computer after you replaced the sys file? (and before you tried the shutdown)
-
i went in safe mode avast doesnt even start up in safe mode there for you replace the sys file, also windows doesnt protect system files in safe mode from what i have herd. any ways i restarted then windows x64 started up and i shutdown and it hang there till i forced it to shutdown.
-
As an experiment, in avast's "program settings" (right click blue "a" circle icon in taskbar), in the troubleshooting section, switch the database from OBDC to XML... see if that helps.
This works for me I shut down 5 times and no shutdown hang, as a matter of fact the shutdown is way faster then before.
Figure out what makes us common and make a patch :) I posted my specs:
Here is my pc spec (http://www.octorn.com/DxDiag.txt)
Update: after 2 days of doing this i have to say it doesnt work becouse it still hangs so im not sure whats going on. im about to uninstall my antivirus antill i can a working one.
I think mabe it's the way the servises are set up with dependencies perhaps if you just remove the dependencies and set all that stuff to auto it will shut down. if you stop all the servises before you shutdown it will not hang.
-
Any one here ? lol what does avast think about my last comment?
-
Hi!
Tried the File, started the Service and it hook up as it did before ;-(
bests
-
Ok, after further testing, i am not so sure that it has solved the problem, when i first added the file, it shutdown perfectly for a good number of tries.
Since yesterday however i have been getting long shutdown times, I get passed the part where it says saving your settings, and it then goes onto windows is shutting down. I have a 5 minute wait from the time i see the windows is shutting down screen til it actually does shutdown, there is 0 disc activity.
At the moment i am not 100% certain its avast thats doing it, it was before but i havent dug any deeper since its the holiday season, but i will start work on it next week and see what it says, but i still think that the nforce4 chipset is playing a major part in our shutdown probs, its either that or ACPI failure somewhere ???
hope you all had a good xmas and i wish you all a happy new year.
-
It seems the patched file works for me. I have not had any shutdown issues since I installed the patch (about a week ago I guess).
-
;D ;D ;D
Patched file also worked on my x64 windows, ASUS a8v rev 2 mobo, many thanks guys for taking the time to fix this.