Hello everyone,
after a BSOD I can now write it all again, forgive me some sloppiness. I am currently using KIS 18.0.0.405 and have encountered a severe problem although I do not know if the behavior is not intended. I have not seen this before at least on my machine.
As of yesterday, KIS has apparently crashed for the 2nd time without notice within around one month, which I only realized after I hovered the tray-icon which would then disappear upon which I restarted KIS. As usual I was concerned and began a full scan. I left the computer to do this and much later, as the scan was still running wanted to open some files and realized that my C Drive, a 500 GB 850 EVO showed me 5 GB of remaining space. As I was absolutely certain that I would’ve never filled up my SSD that much I tried to instantly investigate but upon refreshing, I also realized that I could literally watch my drive space disappearing into thin air at an alarming rate. Within less than 30 seconds I was down to less than 1 GB and thought of a virus, expecting a crash as I refreshed a last time around 200 MB left. At that point however my SSD space magically went back to my original ~65 GB of remaining space.
The problem didn’t disappear as my SSD space was once more rapidly disappearing in front of my eyes, first checking my SSD health and an SSD tool I made sure that this wasn’t just some error, no something was indeed writing at an alarming rate onto my SSD. Using Process Explorer, Process Monitor and the Resource Monitor I figured out that apparently KIS was writing at insane rates to my SSD, all into C:\Windows\Temp as PR****.log. Stopping the full scan would instantly stop the writes, while starting it again would instantly resume the writes.
KIS did not find anything under the quick scan and 70 % into the total scan - which is where I aborted - nothing either. MBAM has not come up with anything either. Computer stable - at least until I tried to recreate the issue - for 24 hours.
After a lot of internet research I saw some other people had similar problems way back until 2008 and 2010. I eventually restarted the scan and then realized that the write-rates were normal while it was scanning my C Drive, but instantly went crazy once it hit one of my data-drives. Now my assumption at this point is that this is connected to how Kaspersky checks archives. I have a lot of packed files on my data-drives and – I have no idea – at this point guess that Kaspersky analyzes those by somehow unpacking them in a safe environment.
On the one hand that wouldn’t be so bad, although my SSD program told me I was currently writing around 2.5 TB of data per day and a full scan of my system might easily take that long which absolutely cannot be healthy. Especially if KIS decides to crash a few more times on me, prompting me to do another full scan. On the other hand even if that is the case, none of my archives is bigger than ~5 GB and I could see no reason why Kaspersky would write that much data onto my SSD and keep it there until the system runs out of memory instead of deleting it again once an archive would be checked.
At first I was still not convinced as my storage had magically reappeared as it hit zero, but just as I was still researching my computer had a BSOD for probably the first time in… years. I cannot say whether this BSOD is connected to Kaspersky writing to my drive at all at this point, but it seems too convenient to be a pure coincidence.
Trying to turn off the options for checking archives and enabling additionally that KIS should not check archives bigger than 100 MB has proven futile at solving this problem. As I am not even certain whether this is the cause, how Kaspersky actually works in such situations or what I can do at this point apart from moving my TEMP-Folder to another drive – I decided to see if someone can help me at figuring this out.
Also note that moving my TEMP-Folder to another drive would not really bother me but it still seems incredibly strange that KIS would write hundreds of GB to a drive and then keep them there until the drive runs out of space. Is that really intended behavior? Would upgrading KIS even solve this problem? Am I on the right track about the archives at all or is it wrong anyway?
Thanks for any kind of help.
System Info in short: Windows 10, KIS 18.0.0.405, Samsung 850 EVO 500 GB SSD, 4 Drives total (500 GB, 3 TB, 3 TB and 600 GB), 16 GB RAM
The rest I assume would not matter.
TL; DR: KIS writing insane amounts of data to SSD until SSD runs out of storage, then apparently resets (or crashes to BSOD) while running a full scan, possibly packed files causing the issue.