Hello everyone, last time we were talking about disk cleanup and its benefits, but as you need to keep your System clean you should also clean and keep your hardware clean as well. Many system issues could be traced and could happen due to dirty PC. In this article, we will give you tips on how to perform safely cleaning on your computer and hopefully point good sides to it so you can develop a healthy habit of regularly cleaning it and keeping it tidy.
Keeping your PC clean is not rocket science and you can do it with things you already and probably have in your house. One thing that I would recommend tho to purchase is antistatic gloves since they could prevent any kind of electrostatic discharges thus protecting your electric components.
If you have the option to disconnect your PC and get it outdoors, I would highly recommend this approach since all the dust will be dusted outside and not in the room where your computer is. If you can not it is still ok, but since some portion of dust will be set in the room, you might need to dust your room after cleaning your computer.
The first thing after disconnecting your computer is to dust it from outside, here you will need a vacuum cleaner and a brush, gently brush outside dust from your casing and vacuum it with your vacuum cleaner. You can use dustcloth for larger parts but use the brush for fans and connectors.
After you have done cleaning the outside part, open the side of your computer casing, put on your antistatic gloves, and get a fine and soft brush, repeat dusting and vacuuming of the inner parts of your computer. If your computer is not regularly been cleaned this part will take a little longer since there would be excess dust inside and it will take a longer time to vacuum it all but keep going until you are left with no dirt.
Fans are troublesome to clean since they will rotate when brushed and that could make you miss certain sports, in order to battle this get a tape and stick the fan into one position, brush areas that you can reach, then unstick it, rotate the head, stick it again in another position and dust off remaining areas which you could not reach before.
If your computer is very dirty and some hard dirt is at bottom of the connectors, disconnect desired component and clean the connection properly. plug it back in immediately after cleaning to avoid connecting it somewhere else.
Harder stains that could not be dusted could be cleaned with little alcohol. Get your dustcloth just a little wet with alcohol, just a corner, and gently wipe out sticky dust or spills if they are present. Leave it 10 minutes for alcohol to evaporate before plugging it back into an electric socket.
If you have money and expertise, every 2 years would be a good idea to change the thermal paste on your processor, all you need to do is buy it from your local computer store online, remove the CPU fan clean the CPU and bottom of the fan and apply new thermal paste, place fan back and lock it. If you do not have expertise in this area, call someone who has to show you how it is done.
When cleaning it would be a good idea if you do not have any cable management to do it now, nice and tidy cables not only look good, they also improve your air circulation inside your casing making your computer cooling better.
once you are done with it, close back the casing side and plug it back in the wall.
When you are cleaning your computer, do yourself a favor and clean your keyboard, mouse, and screen as well. the keyboard can be quickly cleaned with compressed air in the can and screen and mouse with dustcloth.
That's it, remember, keep your PC clean and tidy and enjoy the benefits of non-hardware malfunctions caused by dirt and dust.
“D3dx9_43.DLL Not Found" "The file d3dx9_43.dll is missing" "File d3dx9_43.dll not found" "D3dx9_43.dll not found. Reinstalling might help fix this."
ST0P 0X00000024 (x00190203, 0x82700550, 0xc000012, 0x00000000)Due to this error, both Safe and Normal modes become inaccessible.
“Operation could not be completed (error 0x00000643)”
Stop: 0x0000000A (parameter1, parameter2, parameter3, parameter4) IRQL_NOT_LESS_OR_EQUAL *** Address x has base at x - filename
“The instruction at 0xf77041d24 referenced memory at 0×00000000. The memory could not be read.”
A newfound bug in Google docs is causing it to crush and upon reopening it will crush again making it very difficult to re-access your document. The bug is manifested when a series of the same word is typed into a document and Show grammar suggestion is turned on.
A Google Docs user, Pat Needham brought up the issue on Google Docs Editors Help forum.
"I've only tried in Google Chrome, with documents from three separate Google accounts (personal, G Suite Basic, and work one which might be enterprise). All three experience this same issue".
"It's case-sensitive. So trying with 'and. and. And. and. And.' doesn't cause it to crash."
While Needham publicly reported the bug, it appears that the issue was discovered by Eliza Callahan who was writing a poem novel for her novel using Google Docs.
Needham's findings have also been confirmed by other users running Firefox 99.0.1
Another user, Sergii Dymchenko, said strings like "But. But. But. But. But." triggered the same response. Some also noticed putting any of the terms like "Also, Therefore, And, Anyway, But, Who, Why, Besides, However," in the same format achieved the outcome.
A YCombinator HackerNews reader suspected the cause to be the "Show grammar suggestion" option in Google Docs.
A Google spokesperson confirmed the presence of the issue adding, "we're aware of this issue and the team is working on a fix."
First thing first, turn off Show grammar suggestions so you do not run into issue by accident. In order to turn it off go to Tools and then into Spelling and grammar and untick Show grammar suggestions.
Now, if you already have a document that has been crushed, fear not because there is a workaround to access it. For some strange reason this bug does not manifest on Google Docs mobile app, so you can open the crushed document in the mobile app, delete words that have caused the bug and reopen the document on your desktop.
Until Google comes up with the solution this is currently the only way to address the issue.