I am running Vista 5456.5 and was advised to use this AV. It worked fine until I went to access this computer from my home network, XP machine, and when it trys to connect to the Vista computer with Avast Free on it it goes straight to the BS, shutdown and the whole process.
I tried from various machines on the network, same thing. I uninstalled AVAST and everything is working just fine. Problem now is I have no AV on this Vista machine.
Can anyone help with this I need to have AV present on this computer!!!
How exactly were you accessing the Vista computer? I mean, you just accessed the files thorugh a share, or connected to is using Remote Desktop, or… ?
Are there any (mini)dumps corresponding to the crashes on the Vista computer?
Just simple map to drive to transfer or open files on the machine from an XP machine, simple home network. I do have .dmp files on this and here is the error message.
Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.5456.2.0.5.768.1
Locale ID: 1033
Files that help describe the problem (some files may no longer be available)
Mini070206-01.dmp
sysdata.xml
Version.txt
View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.
Extra information about the problem
BCCode: a
BCP1: 00000060
BCP2: 0000001B
BCP3: 00000001
BCP4: 8146B667
OS Version: 6_0_5456
Service Pack: 0_5
Product: 768_1
Server information: e6ca9bf4-3f04-4e30-a900-e2f1c2e5a4aa
I sent all the information requested to you by email did you not receive it or are you still working on it? I am still waiting for an AV for Vista and will be rebuilding this beta machine soon. I would like to be able to try Avast but if it continues to BS I will have to try something else???
OK, I just talked to a guy at Microsoft, and he told me they’d need a full dump.
Please do the following:
1. Enable Generation of Kernel Dump
Open Control Panel → System → Advanced System Settings → (Advanced Page) ->Startup and Recovery Settings → Write Debugging Information: set to “Kernel memory dump”. Confirm with OK, but don’t restart the machine (yet).
2. Set up the driver verifier
Run verifier.exe (part of Windows) → choose “Create custom settings (for code developers)”, click Next → select “Enabled predefined settings” and check “Standard settings” and “Force pending I/O requests”, click Next → select “Automatically select all drivers installed on this computer”, click Finish.
Let the machine reboot, and simulate the problem (note that the machine might actually bluescreen even before you expect it - that’s because of the enabled Driver Verifier). Anyway, when the system blue screens, let it generate the dump file. After it restarts, take the dump file (\windows\memory.dmp), ZIP it (call the remaining ZIP file e.g. vistacrash.zip) and finally upload it to our ftp site ftp://ftp.avast.com/incoming (please note that you will have only WRITE access to the ftp site, not read).
I did as you asked and sent the file per your instructions to the avast ftp site. If you need anymore information please notify me. I also need to know if this is a “Vista” problem so I can file the correct bug information.
ok… not to be mean or anything but cpupro… shouldn’t this be under a different thread? since… its a different topic? again… not trying to be mean or anything but this could confuse people who have the same trouble as I do.
Not sure what you mean it is all related to the same BSOD that hasn’t been determined if it is a hardware, software or ???. I would put this under another heading if I knew what the cause of the BSOD was from. It is a possibility that this could just be a OS problem, beta that is and maybe a future build will take away the problem. I know that there are lot’s of people that are using Avast with no problems so it is somewhat unique.
wlfpck
Same person, same problem since it hasn’t been resolved. So why would this need to be any where else ???
Besides all this does it take it off topic.
All cpupro wants is a resolution and, those of us following this, are also curious about the outcome and are following this thread.
I finally got a confirmation from MS that this was indeed a bug in the Vista beta2 build. A fix was checked in to the main Vista source tree in mid June, and the bug should be fixed in the latest public ctp build (5472)
All, I am still having the problem with the local network mapping to the Vista machine with Avast installed on it. At this time it doesn’t appear to be Avast that is causing the problem, it seems to be coming from Vista.
Vlk is working with Microsoft on this and will keep you up to date on this issue.
