← Back to catalogue
Research draft

system crash

vr.tr.system-crash · thing-q333501

Let an agent explain system crashes, relay causes, symptoms, diagnosis and prevention from computing sources, describe the named forms and flag the unverified alias, give general troubleshooting and backup guidance, and distinguish crashes from hangs, kernel panics as a specific type, planned shutdowns and security breaches.

Thing Registry Cross-cutting context XCT.QLT

Research draft, second pass

A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.

Researched by: Claude

Bundle → Layer → Finding → QuestionsClassifiersWhat it isWhy it existsDistinguishing featuresWhat robots and AI may and may not doMoral aspectsOwnersLinks to other meta-modelsIdentity and identifiersDirect propertiesRecognitionCapabilities and actionsHazards and failure modesStandards and interfacesContext of useSources

Bundle → Layer → Finding → Questions Filled

4 bundles · 8 layers · 8 findings · 16 questions

Understand What a crash is.

Definition

Definition.

Definition

Definition.

  1. What is a system crash, and how does it differ from hangs, kernel panics, planned shutdowns and security breaches? definition
  2. Is a crash affecting a medical, vehicle or industrial safety system, in which case stop use and contact the manufacturer or safety authority? boundary

Forms

Named forms.

Forms

Forms.

  1. What are the black and white screens of death, bootloops, crash to desktop and fatal system errors, and what might A Bend be? definition
  2. Which entry fits the specific form? action
Causes Causes.

Software

Software bugs.

Software

Software.

  1. How do bugs, memory errors and drivers cause crashes? provenance
  2. Which references are standard? provenance

Hardware

Hardware faults.

Hardware

Hardware.

  1. How do overheating, failing memory and power problems cause crashes? provenance
  2. Which sources are cited? provenance
Diagnosis Diagnosis and prevention.

Dumps

Crash dumps and logs.

Dumps

Dumps.

  1. How are crash dumps and logs used to diagnose problems? provenance
  2. Which entry fits core dump? action

Backups

Backups.

Backups

Backups.

  1. Why do regular backups and updates from official sources reduce harm from crashes? action
  2. Is the information current? boundary
Context Safety-critical systems.

Safety

Safety-critical software.

Safety

Safety.

  1. How do standards reduce crash risk in avionics and medical devices? provenance
  2. Is the presentation neutral and attributed? boundary

Incidents

Major outages.

Incidents

Incidents.

  1. What did investigations report about major crash-related outages, with findings attributed? provenance
  2. Which entry fits 2024 CrowdStrike incident? action

Classifiers Filled

Family
Thing Registry
Category
Cross-cutting context
Entry kind
thing
Plane
XCT
Domain
XCT.QLT
Other names and narrower kinds
black screen of death, A Bend, Bootloop, Crash to desktop, fatal system error, White Screen of Death

What it is Filled

A condition in which a computer, operating system or application stops functioning properly and exits, freezes or restarts unexpectedly, caused by software bugs, driver faults, hardware failures, overheating or memory errors, with forms the registry aliases name such as the fatal system error, the Blue Screen of Death s relatives the black screen of death and White Screen of Death seen on some systems and web platforms, a crash to desktop in games, and a bootloop, where a device repeatedly restarts without finishing booting, while A Bend could not be verified. Crash dumps and logs help diagnose causes, and regular backups reduce data loss; crashes in safety-critical systems are addressed by engineering standards.

Why it exists Filled

Let an agent explain system crashes, relay causes, symptoms, diagnosis and prevention from computing sources, describe the named forms and flag the unverified alias, give general troubleshooting and backup guidance, and distinguish crashes from hangs, kernel panics as a specific type, planned shutdowns and security breaches.

Distinguishing features Filled

  • Unexpected termination
  • Software or hardware cause
  • Diagnostic dumps
  • Data loss risk

What robots and AI may and may not do Filled

Must not

  • Deliberately crash systems the agent does not own or administer.
  • Hide, delete or alter crash records to cover a fault.
  • Restart safety-critical systems without following their procedures.
  • Share crash dumps that contain personal data or secrets beyond the people fixing it.

Only with a human decision

  • Restarting or rolling back production or safety-critical systems.
  • Disclosing a crash that may be a security vulnerability.

May

  • Collect crash logs and diagnostics on systems the agent is authorized to manage.
  • Restart services or roll back changes following the operator's runbook.
  • Report crashes with the version, time and steps that led to them.

Moral aspects Filled

  • Crashes in medical, transport or industrial systems can endanger people.
  • Crash dumps can expose private data held in memory.

Who is affected

  • Users of the system
  • Operators and engineers
  • People whose data is in memory

Owners Filled

Steward

The operator of the affected system.

Links to other meta-models Filled

parent

  • Q1095373 - registry parent class
  • Q124805656 - registry parent class
  • Q19977811 - registry parent class

related

  • computer error - in registry terms
  • Blue screen of death
  • kernel panic
  • hang (computing)

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Vercy registry: vr.tr.system-crash
  • Wikidata: Q333501 (https://www.wikidata.org/wiki/Q333501)

Direct properties not applicable Not applicable

  • Windows stop error screen: from Windows NT 3.1, 1993 note - Blue Screen of Death
  • crash dump: memory snapshot for diagnosis note
  • registry parents: fault, computer error, breakdown note

Plane XCT: no invented physical properties.

Recognition optional Filled

  • Unexpected stop of a computer system or program
  • Black screen of death, A Bend, bootloop, crash to desktop, fatal system error, White Screen of Death
  • Hangs freeze without exiting; kernel panics are OS-level crashes; planned shutdowns are deliberate; breaches are security incidents
  • Error screens, frozen displays, sudden restarts or apps closing.

Capabilities and actions required Filled

  • explain causes and symptoms
  • relay diagnosis tools
  • describe named forms
  • relay prevention and backups

Hazards and failure modes required Filled

  • Data loss
  • Crashes in safety-critical systems
  • Unsafe fixes from untrusted downloads

Standards and interfaces required Filled

  • IEC 61508 functional safety
  • DO-178C for avionics software

Context of use required Filled

  • Not applicable; a failure condition.
  • application crashes
  • operating system crashes
  • boot failures and bootloops
  • hardware-induced crashes
  • web platform fatal errors

Sources Filled

  1. Wikidata item Q333501: system crash - identity and sense of the item
  2. Wikipedia: Crash (computing) - general description of the item

Open questions

  • The registry alias A Bend could not be verified and should be reviewed
  • Should bootloop be a separate entry?
  • How should vendor error code references be linked?

Machine files

Card as JSON Specification Card backlog vercy.card/1

Provenance

thing registry research (pass 2) · unreviewed

Built from: models/things/publications/thing-q333501/spec.json