I’m sure atleast one of your devices must have had a problem at one point of time or another, the obvious thing you would have done at that point was reboot the system. Suddenly, it starts working mysteriously. Have we ever thought how this works? Do we know anything about what is happening internally? To know about this Continue reading this post!
Hey guys, This is Manas Hejmadi from csopensource.com – “Your one stop destination for everything computer science.”. Today’s topic is interesting so sit back and enjoy this freshly brewed article.
Reason for occurrence of Errors
It turns out that most of the problems on your computer happen due to a certain mishap in its internal code. Sometimes, certain dll’s fail, The memory encounters issues, The CPU is not able to process data etc. These problems are the type of problems that cannot be fully recovered while the computer is active. Take the example of a memory error or Dynamic Linked Library Crash. Once this error occurs it constantly gives error messages to the user in the form of Message Boxes. An Example of a Dynamic Library Crash and Memory Error Messages are given below.
Such errors are hard to resolve while the computer is switched on.
let us take a simple example of a collapsed bridge that is the only way to cross a river for hundreds of kilometers. Unless you have a car that runs on water, the most logical option is to traverse the direction in which you came and find another path. Computers behave in such a way. In cases of extremely fatal errors which are usually very less, The infamous Blue Screen of Death(BSOD) appears. This occurs when Windows encounters a fatal error and is similar to the Kernel Panics on the Apple and Linux Devices.
When this occurs you are either forced to reboot or enter Windows Recovery mode.
Sometimes Programmers write code in such a way that it demands certain resources to be allocated to itself. When this condition isn’t satisfied it goes haywire and causes errors.
Some other causes
There is a certain type of error that occurs when Windows tries to read a piece of code from memory that simply doesn’t exist. In this case rebooting forces Windows to wipe out the old data from memory and rewrite it with the appropriate memory allocation and required data. Which makes your system usable again. Sometimes poorly written software are generally unoptimized and may lead to memory overuse. Some programs may also get stuck in an infinite loop hogging resources. Rebooting will break the loop and free up your system.
Sometimes, excessive running applications and services tend to screw up your computer’s performance. In this case a hard reboot kills these extra processes and restarts with only the processes currently required by the computer.
So in short, Rebooting helps to clear residual memory issues as well as dll errors that cause system wide crashes. Since the computer can’t recover on its own when it is running a reboot is required. Now you know the reason why that code you wrote suddenly started working after you shut down your system.
Thank you for spending your valuable time! I will be back soon! Thank you so much!