Verathon GlideScope

Startup Failure, Boot Loop, or Software Freeze

On this page

Asset Type

Video Laryngoscope

Manufacturer

Verathon

Model

GlideScope

What This Guide Helps With

Addresses failed startup or freezing caused by power, battery, connected accessories, storage media, software state, or internal system faults.

Step-by-Step Troubleshooting

1. Protect the Patient and Remove the System From Airway Use

Do not use a GlideScope that fails to start, repeatedly restarts, or freezes. Move the patient to another verified airway visualization device and maintain an appropriate backup method.

Disconnect the system immediately if there is unusual heat, odor, liquid intrusion, or electrical damage.

Expected outcome: Patient care continues with reliable equipment, and the unstable system is isolated.

2. Confirm the Exact Startup Behavior

Determine whether the screen remains blank, stops at a logo, repeatedly restarts, freezes after reaching the operating screen, or responds slowly. Record any displayed message exactly.

Ask whether the problem began after charging, transport, cleaning, accessory connection, storage insertion, or a software update.

Expected outcome: The startup stage and triggering condition are documented.

3. Verify the AC Power Source

Test the outlet according to facility policy and confirm the approved power adapter is fully connected. Inspect the cord, adapter, and plug for damage or overheating.

Attempt one normal startup on a verified AC source.

Expected outcome: The system receives stable approved external power. If it starts normally, continue battery and functional verification.

4. Check Battery Condition

Observe the battery indicator when available. A deeply discharged or failed battery may prevent reliable startup even when external power is connected in some configurations.

Allow charging according to approved instructions before one additional startup attempt.

Expected outcome: The device has sufficient power for a controlled startup test.

5. Disconnect Nonessential External Accessories

Power down when possible. Remove approved removable media, external video cables, barcode devices, network cables, and other nonessential accessories. Leave only the components required for basic startup.

Do not disconnect permanently installed internal assemblies.

Expected outcome: The system starts with a minimal external configuration. Reconnect accessories one at a time to identify the trigger.

6. Inspect Imaging and Power Connections

Check the camera, baton, handle, video cable, charger, and dock connections for partial seating, contamination, moisture, or damage. Disconnect any visibly damaged accessory before restarting.

Expected outcome: External connections are clean, dry, and secure, and no damaged accessory remains attached.

7. Perform One Controlled Power Reset

With the system removed from clinical use, follow the normal user-accessible shutdown and restart method. If the device is frozen and the applicable manufacturer instructions permit a power reset, perform it once.

Do not repeatedly force shutdowns, interrupt an update, or use undocumented key combinations.

Expected outcome: The system completes startup and remains responsive. If so, continue extended functional testing before return to service.

8. Check Removable Storage or Connected Media

If the system starts without removable media but freezes when media is installed, inspect the media for damage, incompatibility, or corruption. Test with known-good approved media when applicable.

Protect all stored patient information.

Expected outcome: The system remains stable with approved functional media, or the suspect media is isolated.

9. Observe the System Through an Extended Test

Allow the monitor to remain powered through the period when the freeze usually occurs. Test normal user-accessible menus, live video, controls, recording functions if applicable, and AC-to-battery transition.

Expected outcome: The system remains responsive without restarting or freezing.

10. Complete Final Verification or Escalate

Repeat startup several times using the normal process. Confirm reliable boot completion, control response, component recognition, live image, power operation, and no recurring software freeze.

Expected outcome: The system starts and operates consistently. If any boot loop or freeze returns, remove it from service.

If the Problem Persists

The outlet, approved adapter, battery state, external accessories, connections, removable media, and controlled restart have been evaluated. The remaining cause may involve corrupted software, internal storage, power regulation, display electronics, main processing hardware, or an incomplete authorized update.

Remove the device from service, label it Out of Service, and send it for qualified repair or bench evaluation. Use the applicable Verathon service documentation and approved tools. Do not reload software, enter restricted service modes, or replace internal boards without authorization.

Return-to-service testing must verify repeated startup, extended operation, live image, control response, battery and AC behavior, and any required safety checks. Knowing when to stop prevents an unstable system from returning to airway service.

Clinical Use Tip

Power on and verify the GlideScope before bringing it to the bedside so startup faults are discovered before airway management begins.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Clinical staff reported that the GlideScope repeatedly restarted at the startup screen."

Cause

What was observed during troubleshooting.

Example:
"Clinical Engineering found that damaged removable storage media caused the system to restart when installed."

Resolution

What action was taken.

Example:
"Clinical Engineering removed the damaged media, installed approved known-good media, and verified repeated normal startup and stable live video."

Helpful Details to Include (If Known)

Final Thought

Remove unstable airway equipment from use, verify power and external accessories before assuming software or hardware failure, avoid repeated forced resets, and document repeated successful startup before release.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide