here it is the result of “WhoCrashed” application after a bsod. Could you please tell me where to upload a dump file for more usefull debug infos?
This was probably caused by the following module: aswndisflt.sys (aswNdisFlt+0x11A04)
Bugcheck code: 0xBADC0DE (0x52646441, 0xFFFFFFFFB6012541, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\aswndisflt.sys
product: Avast Antivirus
company: AVAST Software
description: avast! Filtering NDIS driver
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswndisflt.sys (avast! Filtering NDIS driver, AVAST Software).
Please read my previous post…I reported the exact version of my OS and Avast. Win 8.1 64 bit (fully patched with windows update). Avast 2015.10.0.2208 (updated from 2006 version using internal program update feature).
I will upload the dump on the web application you reported on your post. I’m connecting to the internet using a cabled connection to a router with a lan cable on a Gigabit Ethernet interface controlleb by a Marvell chipset (using latest marvell driver v 12.10.16.0 on a Yukon chipset 88E8056)
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
Machine Name:
Kernel base = 0xfffff80282013000 PsLoadedModuleList = 0xfffff802822e9370
Debug session time: Sat Nov 8 15:52:49.810 2014 (UTC - 5:00)
System Uptime: 0 days 2:15:02.688
No need to try a repair for a first time BSOD…not even a clean install. Let’s wait for an Avast developer to have a more detailed investigation about this issue.
I will try a clean install for sure if needed Btw, Thanks for your help.
Simone
P.S Dump file is just 295kb. I can put on Dropbox to send a download link to an Avast dev for inspection. I will not post that link on this forum because i’m not sure about the fact that this dump can contain sensitive information about my system usage.
Whilst it may take some time for a developer to come on scene - save your dump files - that one looks like a Mini dump given its size, if your BSOD settings create a full memory.dmp that would be more useful, but mini dump files are better than nothing.
Upload any minidump or memory.dmp files, zipped to reduce size. Give the zip file you are uploading a unique name (e.g. forumusername-mem-dump.zip, etc), so they can identify it. It might not be a bad idea to create a text file (readme.txt) with any relevant information, avast topic URL, user name, etc. etc. in the zip file. Not to mention posting the name of the file you uploaded in the topic, this acts as another searchable reference.
Memory dump locations, Mini Dump files in, C:\Windows\Minidump\ - Full Kernel dump file, C:\windows\memory.dmp
Using Windows Explorer, Connect to the link and drag the file into the Right pane and drop it, that starts the upload, you don’t have read access to this folder.
Another user of Avast free that experienced a Win 8.1x64 BSOD (DPC watchdog violation) after upgrading to the 2015 version. I battled this issue for a full day before realizing the apparent cause of the issue. While I had updated some driver files and some program files, the one thing that was common to my BSODs was the new version of Avast. The BSODs seem to have begun after installing the update.
I ran multiple instances of sfc /scannow to no avail. I ran DISM /online /cleanup-image /restorehealth to no avail. I tried to restore to a known good restore point, (and had to uninstall Avast in order to do so), but as soon as I installed a fresh copy of Avast Free, within a few minutes the Core i7/8GB ram Win8.1x64 fully updated system would freeze and then display the DPC watchdog violation screen.
Avast has been my favorite goto AV program for years now. But sadly, I had to move to another AV in order to get around this issue. Since uninstalling Avast and installing another AV, I’ve had no other issues with the DPC watchdog violation error.
Just a fyi and a tag-a-long to the OP as it appears to possibly be a similar issue afflicting Win 8.1x64 systems.
Apart the fact I’m not an user of Avast Free (I’m on Avast Internet Security), my issue has been caused by ndis firewall driver as far as I can understand. If you have a different memory dump analysis from min I suggest you to open a different topic on the forum. Otherwise you’re welcome in this one.
Btw, Thanks for your help.