Hello,
I have also noticed this behavior today only. It occurred shortly after boot and first the disk usage was connected with Avast Installer (instup.exe process). I guess there was some update which was followed by a quick scan afterwards. It was quite unusual and unannounced though, so perhaps some comment from Avast could dismiss the doubts and concerns.