New
#91
Be sure to post results! I personally have had a hard time replicating the issue in my systems, and I am still awaiting log files from other users. The issue seemed to act much like an I/O error which is why I wanted to target CPU and Chipsets. If only I could spend some time in front of an infected machine, I could potentially pull up more statistics on what exactly is happening. If anyone can get the infected machine into a VM, we may be able to debug it in that environment. The infected computers I worked on were Toshiba and HP - AMD - if I am correct. I will have those stats confirmed when the log files come through, hopefully very soon.