I have to agree with Praz on this.
Real bench will most likely abort when you consider moving the mouse aborts it. Its not at all usual to benchmark a PC with the screen saver enabled and I would expect the same to happen on any system and any benchmark. Your clue should be the fact you can run for hours on end without the SS.
Real bench will most likely abort when you consider moving the mouse aborts it. Its not at all usual to benchmark a PC with the screen saver enabled and I would expect the same to happen on any system and any benchmark. Your clue should be the fact you can run for hours on end without the SS.
MMikhail wrote:
Please do not confuse benchmark and stress test loop. Benchmark measure performance, and yes, it will abort if you move mouse or something odd happens since the results will be distorted. But the stress test loop is doing something different and what it checks for apart from some crc's is a mystery as well as it's reports that don't tell you any details as to why it decided there is a problem.
As for the Win10 ScreenSaver engine, there is something really odd going on there, since even selecting the simplest blank screen version apparently requires a lot of cpu power, you can actually see the mouse pointer going busy for a very long time during SS start, which in theory should use almost no cpu time.
My current guess is that Win10 SS engine does something with timers when it is activated which results is RB confusion and fail.
Its not a mystery. Folks like me don't buy into the black box theory, or P.F.M. (pure effin magic)
Benchmarks and stress tests do pretty much the same operation, only the benchmark is taking a measurement of the performance while doing so.
What you have is simply a conflict of instructions.
SS are old and done unless you are one of the few that is still using a CRT. Some screen savers actually use more CPU power than average PC tasks, particularly the 3D animations.
If you want to call your system unstable because of software glitches that were never meant to run together, knock yourself out. The rest of us know that to get accurate stress test results and benchmarks you don't intentionally set it up to end your test with other software and disable or suspend other back ground operations. Ending a test is not unstable, post up screen shots of what message you get, maybe we can help you figure out exactly what is happening. I can say with a level of absolute certainty that is not an unstable system if it runs fine so long as you don't enable the SS.
