I’d repost all the pics, but why waste space here. The work around is to turn off “scan file when writing” in the file system shield.
How dangerous is this? Anyone from Avast tech support wish to answer this?
It is smart to use scanning on writing as well but in general, the most important is scanning on read. It’s a strange bug though, i hope they’ll find a reason why is it so. I’m also using Crucial M4 but only one drive and never paid much attention if anything behaves differently with avast!. Probably a RAiD0 thing…
Try doing the benchmark test with it on and off, I’d like to see if it only affects raid, or if it’s a sata II thing, or if it effects everyone.