Editing Crash (computing) (section)

==Operating system crashes==
[[File:Windows XP BSOD.png|thumb|A [[Blue screen of death]] as displayed in Windows XP, Vista, and 7]]
[[File:OS X Mountain Lion kernel panic.jpg|thumb|A kernel panic as displayed in OS X Mountain Lion]]
An operating system crash commonly occurs when a [[Exception handling#Exception handling in hardware|hardware exception]] occurs that cannot be [[Exception handling|handled]]. Operating system crashes can also occur when internal [[Sanity check|sanity-checking]] logic within the operating system detects that the operating system has lost its internal self-consistency.

Modern multi-tasking operating systems, such as [[Linux]], and [[macOS]], usually remain unharmed when an application program crashes.

Some operating systems, e.g., [[z/OS]], have facilities for [[Reliability, availability and serviceability]] (RAS) and the OS can recover from the crash of a critical component, whether due to hardware failure, e.g., uncorrectable ECC error, or to software failure, e.g., a reference to an unassigned page.

===Abnormal end===
An Abnormal end or ABEND is an abnormal termination of [[software]], or a program crash. Errors or crashes on the [[Novell]] NetWare network operating system are usually called ABENDs. Communities of [[NetWare]] administrators sprang up around the Internet, such as [https://web.archive.org/web/20050324091448/http://www.abend.org/ abend.org].

This usage derives from the ''ABEND'' macro on IBM [[OS/360]], ..., [[z/OS]] operating systems. Usually capitalized, but may appear as "abend". Some common ABEND codes are System ABEND 0C7 (data exception) and System ABEND 0CB ([[division by zero]]).<ref>{{cite book|title=OS Release 21 – System/360 Operating System – Supervisor Services and Macro Instructions|id=GC28-6646-7|date=September 1974|section=ABEND|section-url=http://bitsavers.org/pdf/ibm/360/os/R21.7_Apr73/GC28-6646-7_Supervisor_Services_and_Macro_Instructions_Rel_21.7_Sep74.pdf#page=117|pages=97–99|edition=Eighth|url=http://bitsavers.org/pdf/ibm/360/os/R21.7_Apr73/GC28-6646-7_Supervisor_Services_and_Macro_Instructions_Rel_21.7_Sep74.pdf|publisher=[[IBM]]|access-date=8 July 2023}}</ref><ref>{{cite web|url=https://www.ibm.com/docs/en/zos/2.5.0?topic=codes-0cx|title=0Cx – z/OS MVS System Codes|publisher=IBM}}</ref><ref name="ABENDlist">[http://faculty.madisoncollege.edu/schmidt/mainframe/abendcodes.html List of ABEND codes] {{Webarchive|url=https://web.archive.org/web/20180916172643/http://faculty.madisoncollege.edu/schmidt/mainframe/abendcodes.html |date=2018-09-16 }} on madisoncollege.edu</ref> Abends can be "soft" (allowing automatic recovery) or "hard" (terminating the activity).<ref>{{cite book|title=z/VM and Linux Operations for z/OS System Programmers|first=Lydia|last=Parziale|year=2008|publisher=IBM Redbooks|isbn=9780738431598|url=https://books.google.com/books?id=Mbq6AgAAQBAJ}} page 352</ref> The term is jocularly claimed to be derived from the German word "[[wikt:Abend#English|Abend]]" meaning "evening".<ref name="dictionary">[http://dictionary.die.net/abend "Abend"] {{webarchive |url=https://web.archive.org/web/20110929160903/http://dictionary.die.net/abend |date=29 September 2011 }} on dictionary.die.net</ref>