NewAI Content Creation is now live in Early Access
Turning Point Training Instituteby Training Center
Skip to content
0%
Module 10 — Operating System, Software and Account TroubleshootingLesson 1 of 4
Video lesson

Application Crashes and Browser Problems

BeginnerVideo lesson
9 min readBeginner

Where you are: Module 10 — Operating System, Software and Account Troubleshooting · Lesson 10.1 · Based on Chapter 10 (§10.1–10.2) of Dr. Tahseen Al Doori's Troubleshooting Essentials.

What you'll be able to do

  • Apply the book's eight-step sequence to an application that crashes or shows errors.
  • Use scope (one file, one user or all users) to narrow the cause of a software fault.
  • Separate browser faults from website faults using four quick tests.
  • Protect the user's data before any repair or reinstallation.

Watch: Application Crashes and Browser Problems

The video follows a fictional spreadsheet application that closes as soon as it opens. It walks through the eight steps, shows what the scope of a fault tells you, solves the ticket with safe mode, and then turns to web applications and the four browser tests. While watching, think about:

  • Why is "just reinstall it" the seventh step rather than the first?
  • What does it tell you when a fault affects one user but not others on the same computer?
  • If a web application works in a private window, what has been ruled in and what ruled out?

The eight-step sequence for application faults

When an application crashes, freezes or shows errors, the book gives a sequence that runs from the simplest, least disruptive action to the most disruptive. Each step either solves the problem or rules something out.

Record errorReopen and restartOne file, user or all?UpdateClear cacheDisable add-onsBack up, repairVendor search
  1. Record the exact error message and code. Word for word, or as a screenshot or photograph. The exact text is what makes the final step work.
  2. Close and reopen the application; then restart the device. This clears stuck processes and temporary memory (Module 5).
  3. Check whether the problem affects one file, one user or all users. This is isolation, and it is covered in more detail below.
  4. Update the application and the operating system. Many crashes are known bugs that the vendor has already fixed.
  5. Clear the application's cache or temporary files. Corrupt temporary data is a common cause of repeated crashes.
  6. Disable add-ons, plug-ins or extensions; test in safe mode. Safe mode starts the application or system with only the essentials. If the fault disappears, an add-on or startup item is the likely cause, and you can restore them one at a time (the remove-and-restore technique from Module 6).
  7. Repair or reinstall the application, backing up its data first.
  8. Search the exact error message on the vendor's support site and knowledge base.

Notice that every step changes one thing, so cause and effect stay clear. This is principle 4 from Module 2: change one thing at a time.

Protect the data first. Before step 7, back up the application's data. Repairing or reinstalling can remove settings, templates, add-ins and files stored locally. A short backup protects hours of the user's work, and it is part of the plan in Step 4 of the seven-step methodology.

What the scope tells you

Step 3 is often the turning point. The table below shows how to read it; the "next test" column suggests the obvious follow-up.

Who or what is affectedPoints towardsNext test
One file onlyThat fileOpen a copy or an earlier version of it
One user onlyThat user's settings or profileTest with another account, with permission
All users on one deviceThe application or the deviceUpdates, add-ons, repair
All users on all devicesA shared service or the vendorStatus page, vendor, escalation

Testing with another account must follow organisational policy: use a test account or the user's colleague with their agreement, and never ask anyone for their password (see Lesson 10.3).

Web applications and browsers

Many applications now run inside a web browser. The book adds four tests that separate the browser from the website:

  • Test in a private (incognito) window, which disables most extensions and cached data.
  • Try a different browser to separate browser faults from website faults.
  • Clear the cache and cookies for the affected site. Clearing only that site keeps the user signed in elsewhere.
  • Check the service's status page. The fault may be on the provider's side, where no local fix can help.

Each result points somewhere specific:

ResultWhat it suggestsNext step
Works in a private windowAn extension or cached dataRe-enable extensions one at a time; clear the site's cache
Works in a different browserThe first browser or its settingsUpdate or reset that browser
Fails in every browser and on other devicesThe website or the networkCheck the status page; test the network (Module 9)
Status page shows an incidentThe providerInform users, set expectations, wait

Worked example

(Fictional scenario.) A member of an accounts team reports that their spreadsheet application closes as soon as it opens, starting on Monday morning. They ask for it to be reinstalled.

  1. Identify (step 1). The technician asks the user to reproduce the fault and photographs the brief error message: an add-in failed to load.
  2. Restart (step 2). Closing, reopening and restarting the laptop changes nothing.
  3. Scope (step 3). Other files fail too, so it is not one file. A colleague's account on the same laptop shows the same fault, so it is not the user's profile. Other laptops are fine. The fault belongs to this device's installation.
  4. Theory. An add-in was installed on Monday morning, just before the fault began.
  5. Test (step 6). The application opens normally in safe mode, which loads it without add-ins. The theory is confirmed.
  6. Plan and implement. Disable only the new reporting add-in, which is easily reversed. No reinstallation is needed, so no data is put at risk.
  7. Verify. The user opens the monthly report and confirms normal operation.
  8. Document. The ticket records the add-in and its version; the vendor is informed (step 8 in reverse: the technician reports the error message rather than only searching for it).

Steps 4, 5 and 7 were never needed, because the scope and the safe-mode test found the cause first. The sequence is an order of preference, not a list you must complete.

Try it

Use your own computer, and only reversible actions.

  1. Open your browser and visit a site you use often. Open the same site in a private window, then in a second browser if you have one installed. Record any differences in how the page behaves (for example, whether you are signed in, or whether any extension's toolbar appears).
  2. Find the status page for one online service you use and note what it reports today.
  3. On paper, apply the eight steps to this report: "My presentation program crashes whenever I insert a picture." For each step, write what you would do and what each possible result would tell you.

You have finished when you have recorded the private-window and second-browser results, one status-page observation, and a written eight-step plan for the presentation fault with at least one scope test.

Knowledge check

What is the first step in the book's sequence for an application that keeps crashing?

A fault affects one user on a shared computer; other users on the same computer are fine. What does this point towards?

A web application works in a private window but not in a normal window. What is the best next step?

Before repairing or reinstalling an application, what must you do?

Answers explained

  1. b — the exact message and code guide every later step, especially the vendor search; reinstalling, disabling add-ons and updating come later in the sequence.
  2. a — if other users on the same machine are fine, the hardware, vendor and network are working; the difference lies in that user's settings or profile.
  3. d — a private window disables most extensions and cached data, so one of those is the likely cause; the site, the network and the operating system are clearly working.
  4. c — repair and reinstallation can remove local data, so back it up first; passwords are never requested, updates are never permanently disabled, and changing other computers is out of scope.

Key takeaways

  • Record the exact error first; it guides every later step.
  • Work from the simplest action towards reinstallation, changing one thing at a time.
  • Scope the fault early: one file, one user or everyone.
  • For web applications: private window, different browser, site-specific cache clear and the status page.
  • Back up the application's data before any repair or reinstall.

Sources

  • Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), §10.1–10.2; §2.2 (principle 4), §5.6 (why restarting works), §6.5 (remove and restore)