Hi,
I've been having lower scores in CPU benchmarks in Windows 10 for the last couple of weeks. Restoring from a system image would initially fix it, but then the degradation would occur after around 15 minutes of being connected to the internet and would be permanent whether I were offline or online. However, if I never connected to the internet after restoring, the issue would not occur.
I found the reason for this yesterday, when I went to "Feedback and Diagnostics" in the "Privacy" section of "Settings" and changed "Diagnostic and Usage Data" from full to basic, my performance was restored!
I was wondering whether someone could run Cinebench R15 CPU and OpenGL tests firstly with the default full "Diagnostic and Usage Data" setting and then the basic setting and tell me if there is any difference so I can confirm if this bug is unique to me or not; it would be much appreciated.
It costs me about 2% in the CPU test and 11% in the OpenGL test. However, in the game "Tyranny" my frame rate is around 30% lower which is how I noticed this problem.
I've been having lower scores in CPU benchmarks in Windows 10 for the last couple of weeks. Restoring from a system image would initially fix it, but then the degradation would occur after around 15 minutes of being connected to the internet and would be permanent whether I were offline or online. However, if I never connected to the internet after restoring, the issue would not occur.
I found the reason for this yesterday, when I went to "Feedback and Diagnostics" in the "Privacy" section of "Settings" and changed "Diagnostic and Usage Data" from full to basic, my performance was restored!
I was wondering whether someone could run Cinebench R15 CPU and OpenGL tests firstly with the default full "Diagnostic and Usage Data" setting and then the basic setting and tell me if there is any difference so I can confirm if this bug is unique to me or not; it would be much appreciated.
It costs me about 2% in the CPU test and 11% in the OpenGL test. However, in the game "Tyranny" my frame rate is around 30% lower which is how I noticed this problem.