Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem








and yeah i do clean my appartment often enough, both with the vacuum cleaner and with a rag and water+soap ... you can almost eat off of the floor here, still my pc accumulates a lot of dust. What also helps a lot is the use of dustcovers on all i n and out-takes, then you only have to clean the dust from the covers...
Removing the dust from a pc can make a 10°c difference, if the system has never been cleaned before and it's loaded with dust the difference will be even bigger. Also dust starts to creep into your fan-motors, which will eventually destroy them.
I can't really say if that helps .. if the OC is stable and not too extreme, then it should all work just fine... I've been using intel K-series processors since the Ivy Bridge (i5-3570K) and have always overclocked my cpu's to run constantly at turbo-boost clocks and sometimes a bit higher if the temps didn't rise too much. My current cpu is also slightly overclodked (i5-10600K)and have not a single crash that was related to my cpu, the XTU driver or any overclock... I very rarely get crashes, and most of the time it's because of a detoriated cell on my ssd so it reads corrupt data.. a chkdsk fixes that.
i'm not saying oc'ing can't be the source of gamecrashes or systemcrashes.. it surely can, but always first test if the system is and stays stable under max load for at least 30 minutes to an hour. And test with your case closed , because testing with open case and then after testing closing the lid is guaranteed going to deliver you some heat-problems and crashes related to overheating.
you can run dism also in an elevated CMD screen, (takes less resources)
Dism is actualy a tool to keep up your platform image, updates edit your platform image so yeah, it can help to cleanup a bit with dism (this mainly removes files which have gotten newer versions.
I even made a script that shuts down windows update service, cleans up it's cache, then removes all packages files that are no longer in use, then does 3 dism operations, then does a chkdsk (check only) and if you read that things needs to be fixed you can then reboot so they get fixed, and then i run an SFC.
It's been quite a while since when i needed that little .CMD file for my own problems though.. (and i've been running windows for over 10 years with all security removed (AV, Firewall,... all completely removed/disabled) although i don't advice this for the average user. I can advice to remove/disable telemetry, this gives you about 10-15% extra performance and stops your pc talking back to MS all the time