Halting problem
This topic covers halting problem.
Full topic guide: the detailed syllabus page with worked examples and common mistakes lives at studyvector.co.uk/a-level/computer-science/theory-of-computation/turing-machines-halting-problem.
Topic preview: Halting problem
Sample stems from the StudyVector question bank (AQA · Edexcel · OCR) — not generic filler text.
More questions are being linked to this topic. You can still start adaptive practice after you create a free account.
Coverage and provenance
What this page is based on
StudyVector does not present unsupported question coverage as complete. Read how questions are selected and reviewed.
Topic explanation
A Turing machine is a mathematical model of a hypothetical computing device that can simulate any computer algorithm. The Halting Problem is the problem of determining, from a description of an arbitrary computer program and an input, whether the program will finish running or continue to run forever. It is one of the most famous undecidable problems in computer science.
Halting problem is easiest to revise when it is treated as a precise exam behaviour, not a loose note-taking category. In A-Level Computer Science, the goal is to recognise how the topic appears in a question, identify the command word, and decide what evidence, method, or vocabulary earns marks. StudyVector keeps this page tied to AQA · Edexcel · OCR language where coverage is available, then routes practice towards the same topic so revision moves from explanation into retrieval.
A strong revision session starts with a short recall check. Write down the rule, definition, process, or method linked to Halting problem before looking at any notes. Then answer one exam-style prompt and compare your answer with the mark-scheme logic: did you make a clear point, support it with the right step, and avoid drifting into a nearby topic? This matters because many lost marks come from almost-correct answers that do not match the expected structure.
Use this guide as the first layer: understand the topic, look at the worked examples, complete the mini quiz, then move into full practice. The full StudyVector practice loop is designed to capture whether mistakes are caused by knowledge, method, language, or timing. That distinction is important. If the error is factual, you need reteaching. If the error is method-based, you need a worked retry. If the error is wording, you need command-word calibration. That is how Halting problem becomes a controlled revision target rather than another page in a folder.
Lost marks → repair task
Why marks are usually lost here
These are the error patterns StudyVector looks for after an attempt. The goal is not a generic explanation; it is one repair move and one follow-up question.
Command-word miss
Examiner move: Answer the action in the command word before adding extra detail.
Repair drill: 60-second rewrite: start the answer with explain, compare, evaluate, state, or calculate in mind.
Missing chain of reasoning
Examiner move: Show the link between point, method, evidence, and conclusion instead of jumping to the final line.
Repair drill: Write the missing because/therefore step, then retry one isomorphic question.
Weak evidence or data reference
Examiner move: Use a precise value, quote, example, diagram feature, or syllabus term to support the claim.
Repair drill: Add one concrete reference to the answer and remove any generic sentence that does not earn a mark.
Mini quiz
Use these checks before full practice. They test topic recognition, exam technique, and whether you can connect the explanation to a marked response.
1. What should you check first when a Halting problem question appears in A-Level Computer Science?
- A.The command word and the exact topic focus
- B.The longest paragraph in your notes
- C.A memorised answer from a different topic
2. Which revision action gives the strongest evidence that Halting problem is improving?
- A.Rereading the explanation twice
- B.Answering a timed exam-style question and reviewing lost marks
- C.Highlighting every key phrase in the topic notes
Sample questions
Topic-specific public question previews are still being reviewed. We keep them off public pages until the topic match is safe.
Exam tips
- Read the command word carefully — "explain" needs reasons; "state" expects a short fact.
- For Halting problem, show structured working even when you are practising multiple choice — it builds accuracy under time pressure.
- Mark yourself against the mark scheme style: one clear point per mark, in logical order.
- Come back to this topic after a day or two; short spaced reviews beat one long cram.
Worked examples
Example 1
Modelled exam response
Imagine a program `halts(program, input)` that returns `true` if `program` halts on `input`, and `false` otherwise. The Halting Problem proves that it is impossible to write such a program that works for all possible programs and inputs without error.
Example 2
Identify the task before answering
Question type: a Halting problem prompt asks for a clear response in A-Level Computer Science. Step 1: underline the command word. Step 2: name the exact part of Halting problem being tested. Step 3: decide whether the mark scheme wants a definition, method, explanation, comparison, or calculation. Why it works: most weak answers fail before the content starts because they answer the topic generally rather than the exact exam task.
Example 3
Turn feedback into a repair task
Suppose your answer shows partial understanding but loses marks for precision. First, rewrite the missing mark as a short target: "I need to state the mechanism, unit, reason, or evidence explicitly." Then answer one similar question without notes. Finally, compare the second attempt with the first and check whether the same mark was recovered. Why it works: Halting problem improves faster when feedback creates a specific retry, not another passive reading session.
Next revision routes from this subject
Good topic pages should lead naturally into the next useful page. Use these links to stay inside the same strand or jump into the next topic area without starting your search again.
Stay in the same topic area
Explore the wider subject map
Common mistakes
- Thinking that the Halting Problem is about finding bugs in a program.
- Believing that the Halting Problem can be solved for specific programs (it can, but not for *all* programs).
- Confusing what is computable with what is efficiently computable.
Exam board notes
A theoretical topic covered by AQA and OCR. Students should understand the concept of a Turing machine and be able to explain the significance of the Halting Problem.
FAQs
Why is the Halting Problem so important?
The Halting Problem demonstrates that there are fundamental limits to what can be computed. It has profound implications for computer science, artificial intelligence, and philosophy.
Are there any other undecidable problems?
Yes, many other problems have been proven to be undecidable, such as the Post correspondence problem and the problem of determining whether a context-free grammar is ambiguous.
More on StudyVector
Full practice set
The complete adaptive question bank for this topic — personalised to your weak areas — is available after you sign in. Your session can start on this topic immediately.