system
11
PK, just to confirm: the change made to Avast!, around the April 7 timeframe, made Avast! cause this BSOD even though it previously did not cause it?
I ask because the KB article is from 2009, and I’ve only been running Avast! since 2011. And, I’ve been mapping drives the entire time (until April 7!!).
I’ll try the hotfix tonight as well. I had read this KB article, but held off on applying the fix for the same reason as lm713: I don’t want to brick by system, or have to do some sort of serious back-tracking. Also, I had googled for an “official” XP version of this rdpdr.sys file without luck. I guess it is possible that MS created the fix only for Server 2003 (but that seems odd, given the date).