If the Software Crashes

Software fails. The exam platform freezes, the proctoring tool quits, the lockdown browser stops responding. None of this is your fault and all of it has a procedure.

Students balancing exam preparation with paid work can review this supporting resource as a practical way to separate rehearsal, support calls and work sessions. The value is a voluntary log that clarifies the sequence without copying any proctoring data.

Immediately

Note the time.

A useful outside source on revision practice is Quizlet. Compare it with your institution’s written procedure before making decisions.

Photograph the screen with your phone if you can do so without leaving your seat. An error message is evidence and it disappears when you restart.

Wait a moment. Some freezes resolve.

Then

Contact support through your written-down channel, which may be a phone number, a chat, or an email depending on your institution.

Say what happened, at what time, and what you can see.

Ask explicitly what to do: restart, wait, or stop. Do not guess, because restarting is right in some systems and loses work in others.

Follow their instruction and note what it was and who gave it.

If you cannot reach support

Try the alternative channel if one exists.

Email the exams office, timestamped, describing the problem as it is happening. A message sent at 11:22 saying the software has frozen is worth far more than the same account given the next day.

Then follow the instructions your institution published for this situation, if any.

After

Write a full account the same day: times, what you saw, what you did, who you contacted, what they said.

Attach the photograph of the error if you took one.

Send it to the exams office, not only to the supplier's support. Your institution is responsible for the assessment.

What to ask for

Depending on how much was lost: time restored, a resit without penalty, or the affected component discounted.

Ask promptly. Most institutions have a deadline for mitigating circumstances and it is usually short.

And ask that the session's flags be annotated, so that a reviewer seeing an abrupt interruption knows the cause.

What not to do

Do not spend twenty minutes troubleshooting alone. Contact support early; the clock is usually still running.

Do not reinstall anything mid-exam.

And do not assume that finishing means it does not need reporting. A crash that you worked through still affected your performance and still produced flags.

The preparation that helps

The support contact on paper, off the screen that is about to fail.

Your phone charged and reachable, within the rules.

And the practice run, which catches the conflicts that cause most crashes before they cost you anything.

If the same thing happens twice

Report it as a pattern rather than as two incidents.

Repeated failure on the same setup means something specific is wrong — a conflict, a driver, an unsupported configuration — and the institution's IT support should diagnose it before your next exam.

Ask for that explicitly.

What to check

Do you know your support channel and is it written off-screen?

Would you know whether to restart or wait?

Is your phone reachable within the rules of your exam?

And do you know your institution's deadline for reporting mitigating circumstances?

The point

Photograph the error message before restarting, because it disappears and it is evidence.

Then ask support explicitly whether to restart or wait.

Additionally

Report a repeated failure as a pattern rather than as two incidents, and ask the institution's IT support to diagnose it before your next exam..

Finally

Report a repeated failure as a pattern rather than as two incidents, and ask the institution's IT support to diagnose it before your next exam..

In summary

Report a repeated failure as a pattern rather than as two incidents, and ask the institution's IT support to diagnose it before your next exam..

A note on this

Contact support early rather than troubleshooting alone for twenty minutes.

The clock is usually still running.

Bottom line

Contact support early rather than troubleshooting alone for twenty minutes.

The clock is usually still running.

Worth repeating

Almost everything in this collection comes down to three habits: prepare the technical side a week early, know what the process actually is before you need it, and write down the time whenever something unusual happens. None of them takes long, and between them they prevent or resolve the great majority of what goes wrong with monitored exams.