I got a BSOD today, very shortly after Avast’s latest update. Here is the info from Whocrashed:
On Thu 02/07/2015 8:52:26 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswstm.sys (aswStm+0x4F48)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\aswstm.sys
product: Avast Antivirus
company: Avast Software s.r.o.
description: Stream Filter
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: aswstm.sys (Stream Filter, Avast Software s.r.o.).
Google query: aswstm.sys Avast Software s.r.o. KMODE_EXCEPTION_NOT_HANDLED
Other info:
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core™ i5-2500K CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17092952064 total
VM: 2147352576, free: 1920364544
The exact series of events here, as I remember them:
I was having issues running an unrelated program, Game Maker Studio, and was trying out a few different things to get it to run. One of these things was to temporarily turn off Avast for 10 minutes, in case it was interfering with it somehow. Another was to cut off my internet connection, in case Game Maker’s DRM server was having problems at the moment, stopping the software from launching. When I disconnected my internet, while still under the 10-minute Avast disable, the computer crashed to a BSOD. It really seems like stopping my internet connection (by unplugging my router’s wire) is what triggered this, it happened very quickly after I unplugged, although not instantaneously. It is possible, although I cannot be sure, that the 10 minutes time ran out and Avast kicked back in shortly after I unplugged my internet? Could this possibly trigger the error? Seems like a pretty specific series of events, the kind that could result in unexpected problems!
Also of note, I updated drivers for my Razer Mamba mouse, like less than 20 minutes before all this happened. Its the start of the month so every program and their moms are pushing updates out, makes an environment ripe for crashes!