I got this problem but it went away after I uninstalled Avast.
I used to get a bsod soon I logged into the PC.
Edit:
This only happens after I install Windows updates.
I got this problem but it went away after I uninstalled Avast.
I used to get a bsod soon I logged into the PC.
Edit:
This only happens after I install Windows updates.
My zip file is androidappme
I have send the dump file over.
There is a thread about it here
I just installed Windows 8 Pro yesterday and installed Avast today and I have this issue as well. I randomly get either the aswnet.sys or ndis.sys crashes.
If you disable all the shields… sure the crashing stops. But then Avast is useless for on-demand protection.
I really hope this gets solved soon as I really like Avast. But for now I will need some other protection until this is solved.
Except that solution has nothing to do with the fact this our ndis.sys and AWSnet.sys crashing happens with Avast installed and does not happen without Avast installed. So it’s definitely something with Avast being installed. As it’s the first and only thing I have installed since Installing Windows 8 Pro yesterday. It was fine all day yesterday and crashing today after Avast. I uninstall or disable the shields and the crashing stops.
Same here…my ATI radeon driver and OADriver.sys crashed when avast was running on my Win7 and when I completely remove avast it doesnt crash…my dump TOI.DMP.7z and TOI.7z will be uploaded to ftp.avast.com/incoming
Such a bad experience with my highly favoured AV Program >:(
EDIT: TOI.DMP.7Z uploaded and now uploading TOI.7Z kindly check avast! team
The only shield you have to disable is Web shield. Then Windows 8 and Avast will work together. The reason may be that, there is MSE included even Defender is off.
TOI.DMP.7Z and TOI.7Z now uploaded to ftp.avast.com/incoming
Sorry for taking a long time…My internet is crap as you all know ;D
thanks avast! team
EDIT: Looks like adding the ATI and OA driver to behaviour shield exclusions solves the issue However,these drivers werent a problem in 1466.