Find centralized, trusted content and collaborate around the technologies you use most. Connect and share knowledge within a single location that is structured and easy to search.
I am interested to learn: what are the most common technical causes from the perspective of operating system programming of an operating system crash not limited to Windows crashes? I'm looking for an answer not like "too many apps open", but what specifically happens when too many apps are open that causes the crash. It's Buggy Drivers that cause OS crashes.
Only the OS itself and drivers are able to harm the system. No OS has problems if an application accesses the same memory as the OS. Either the memory is accessible or it is not.
If an application tries to access memory that it should not the CPU generates a segmentation-fault. The OS hands this over to the application and the problem is solved. You're suggesting that slower programs are more safe. That's not true.
The OS does not need to know what exactly your program is doing. In modern OS, application code and OS code run in separate address spaces. The application code cannot crash the operating system. See here:. The most common readon for a crash is code that is acting as part of the OS interfearing with other code that is acting as part of the OS. A common cause is poorly written device drivers that live in the OS's address space.
Power Related problems : Improper functioning of the System Power Supply can lead to immediate shutting down of the System. This can lead to definite crash where reset is a must. Improper Overclocking : Causes Overheating. Certain Hardware Components are sensitive to heat.
Because your computer keeps important data in RAM, issues with your memory can cause Windows to crash. Error names like Fatal Exception Error usually pop up when Windows tries to retrieve data from memory but can't do so properly. If this keeps happening, your RAM may be failing. It's also worth making sure that your RAM sticks are seated properly in their slots. Note while insufficient RAM can cause your system to grind to a halt, it usually won't cause Windows to crash. If you're sure that RAM isn't the culprit, sometimes a motherboard problem can result in similar issues.
Drivers are specialized pieces of software that allow Windows to interface with the various hardware connected to your computer. Most of the time, drivers install and update automatically when you connect a new peripheral or run Windows Update. However, when drivers go bad, they can cause serious problems. Manually installing the wrong driver, or updating to a buggy version provided by the manufacturer, are common ways for this to happen.
When troubleshooting the blue screen error , keep an eye out for mentions of any specific hardware, as it may be the culprit. It's also a good idea to open the Device Manager accessible by right-clicking the Start button and check for any warning symbols, which represent hardware conflicts.
If the storage drive whether a hard drive or solid state drive in your computer is going bad, you may experience Windows crashes. This might manifest itself through crashes that only happen when you try to open specific files, which indicates that a certain section of the drive is dying. For an older HDD, a clicking sound is another telltale sign of a failing drive. Because Windows needs to access files across your storage disk to run properly, it can crash if the disk can't read those files.
If this sounds like your problem, find out what to do about a dying hard drive certainly back up your data as soon as possible! Too much heat causes major problems for the sensitive components inside your computer. A system that runs too hot for a long period of time might become permanently damaged. It usually saves time in the long run to check compatibility before purchasing or installing new hardware. Problems after an upgrade. Hardware incompatibility problems also crop up occasionally after operating system upgrades on systems whose hardware has not changed, due to withdrawn support for previously supported hardware or because of undetected bugs in the new release.
You can confirm that the new operating system is the problem if the system still boots correctly from bootable backup tapes or installation media from the previous release. If you encounter sudden device-related problems after an OS upgrade, contacting the operating system vendor is usually the best recourse. Device conflicts. All devices that operate at the same time must have unique values for the items relevant to it values are set via jumpers or other mechanisms on the device or its controller or via a software utility provided by the manufacturer for this purpose.
Keeping detailed and accurate records of the settings used by all of the devices on the system will make it easy to select appropriate ones when adding a new device and to track down conflicts should they occur. Errors in configuration files. This type of problem is usually easy to recognize. The solution is to boot to single-user mode and then correct the erroneous configuration file or reinstall a saved, working versions of it.
Unbootable kernels. There are at least two ways that this can occur: you may have made a mistake building or configuring the kernel, or there may be bugs in the kernel that manifest themselves on your system. The latter happens occasionally when updating the kernel to the latest release level on Linux systems and when you forget to run lilo after building a new kernel. Once the system is up, you can track down the problem with the new kernel.
Frequently, the problem will disappear. Errors in initialization files are a very common cause of boot problems. Usually, once an error is encountered, the boot stops and leaves the system in single-user mode. So only the root disk got mounted. There was no ls , no cat , not even ed. I typed:. Although it was probably out of date, it could get things going. I executed it manually:. The moral of this story is, of course, test , test , test.
Note once more that obsessive prudence is your best hope every time. Skip to main content. Start your free trial. Troubleshooting: Handling Crashes and Boot Failures. Other environmental problems: roof leaks, air conditioning failure, etc. With Windows 10 you get 2 years more than Windows 8 and five years more than windows 7.
This may be a great help when it comes to solving crashes but does not stop the crashes itself. One can recall the KB update which was forced on users shortly after the launch of windows to fix a bug that caused frequent crash loops. There were reports popping up in the web that not only did the update force a reboot but would install only partially, and after the reboot would re-install again.
But of course is this has nothing on Linux which is also free to download amongst many other advantages. That being said, most reports show that all things considered, a Linux operating system is less likely to crash. Mac OS X too has very limited chances of crashing and some would prefer it over a Linux. Modou Sarr is from the Gambia West Africa, he loves to read write and is an avid sportsman. He studied International Development studies and also Law and hopes to one day own a successful eCommerce business.
0コメント