Z
Zaman
My advice to you: DON'T USE THEM UNLESS YOU WANT YOUR SYSTEM TO CRASH!
Through a long and costly process of puzzling hardware failures I
figured out that the dasteredly 3D screensaver that I had so proudly
configured to appear on my screen burnt out my CPU and resulted in a
confusing hunt for the problem.
It is hard to believe but do the following to see what I mean. Open
Windows Task Manager and monitor your CPU usage. Then activate any
screensaver other the 3D ones listed. Wait for a minute or two and
look at your CPU usage. The usage of this type of screensaver barely
registers.
Then switch to one of the 3D screensavers and do the same. The CPU
usage shoots up to a solid 100%!!!! Yes you are saving your screen but
your CPU is bound to overheat after a while no matter what kind of fan
you are using. My computer kept freezing and I couldn't figure out
what was going on. After a while CPU gave out and could no longer boot
up.
I am wondering if this can be substantiated by independent testing.
Any comments? If I am correct about this, I believe Microsoft is
liable. I wonder how many other poor saps got screwed without knowing
what happened.
Through a long and costly process of puzzling hardware failures I
figured out that the dasteredly 3D screensaver that I had so proudly
configured to appear on my screen burnt out my CPU and resulted in a
confusing hunt for the problem.
It is hard to believe but do the following to see what I mean. Open
Windows Task Manager and monitor your CPU usage. Then activate any
screensaver other the 3D ones listed. Wait for a minute or two and
look at your CPU usage. The usage of this type of screensaver barely
registers.
Then switch to one of the 3D screensavers and do the same. The CPU
usage shoots up to a solid 100%!!!! Yes you are saving your screen but
your CPU is bound to overheat after a while no matter what kind of fan
you are using. My computer kept freezing and I couldn't figure out
what was going on. After a while CPU gave out and could no longer boot
up.
I am wondering if this can be substantiated by independent testing.
Any comments? If I am correct about this, I believe Microsoft is
liable. I wonder how many other poor saps got screwed without knowing
what happened.