On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting startup loops, frozen screens, incomplete booting, or configuration loading failures caused by power, connections, accessories, network communication, or software-related faults.
Step-by-Step Troubleshooting
1. Ensure Patient Safety First
Do not troubleshoot a frozen or repeatedly restarting monitor while it is the only device supporting an actively monitored patient.
- Notify the clinical team that reliable monitoring is unavailable.
- Assess the patient using another approved clinical method.
- Transfer monitoring to another verified patient monitor when continuous monitoring is required.
- Do not rely on displayed values or alarms from a monitor that is frozen or not fully operational.
Expected outcome: Required patient monitoring continues without depending on the affected monitor.
Continue Clinical Engineering troubleshooting only after the device can be safely removed from patient use.
2. Confirm the Exact Failure
Observe and document whether the monitor:
- Continuously restarts during startup
- Stops at the Philips logo or startup screen
- Displays a configuration-loading message indefinitely
- Reaches the monitoring screen and then freezes
- Responds to hard keys but not the touchscreen
- Displays an error code or service message
- Experiences the problem only after connecting to the network or another device
Photograph or record any displayed error before restarting the monitor.
Expected outcome: The failure pattern and the point at which startup stops are clearly identified.
3. Check for a Temporary Interface Freeze
Determine whether only the touchscreen is unresponsive or the entire monitor is frozen.
- Try an available physical key or control.
- Observe whether waveforms, clock, indicator lights, or alarm messages continue updating.
- Disconnect any external mouse, keyboard, barcode scanner, or USB accessory, if present and approved for removal.
If the monitor continues operating but only the touchscreen is unresponsive, the problem may involve the display interface rather than a complete software freeze.
Expected outcome: A touchscreen-specific problem is distinguished from a full system freeze.
If normal control returns after removing an external accessory, replace or evaluate that accessory and stop troubleshooting.
4. Verify AC Power and Power-Cord Condition
Inspect the AC power cord, inlet, and approved power adapter arrangement, as applicable.
- Confirm the power cord is fully seated.
- Check for damaged insulation, bent contacts, loose connectors, or evidence of overheating.
- Test the wall outlet with an approved outlet tester or known-good device.
- Bypass an external power strip, extension, or damaged isolation-power connection when permitted.
- Confirm the AC power indicator behaves normally.
Unstable input power can interrupt startup and create repeated restarts.
Expected outcome: The monitor receives stable power from a verified outlet.
If correcting the power source resolves the issue, complete an operational check and stop.
5. Check the Battery Condition
For MX models equipped with removable or internal battery support:
- Note whether the problem occurs on AC power, battery power, or both.
- Confirm the battery is properly seated and latched.
- Inspect accessible battery contacts for contamination or damage.
- Remove a removable battery only when permitted by facility procedure, then test the monitor on verified AC power.
- Substitute a compatible, known-good battery when available.
A defective or unstable battery can interfere with startup even when AC power is connected.
Expected outcome: The monitor starts normally on a stable power source with a serviceable battery configuration.
If replacing or removing the faulty battery resolves the problem, replace the battery and complete the required functional checks.
6. Remove External Accessories and Data Connections
Power the monitor down using the normal shutdown method when it remains responsive. Disconnect nonessential external connections, including:
- Network cable
- USB accessories
- Video-output cable
- Printer or recorder connection
- Serial or interface cables
- Docking-station connections
- Measurement extensions or external modules that can be safely removed
- Third-party integration equipment
Leave only the minimum connections needed to power and start the monitor.
Expected outcome: The monitor starts without an external accessory or communication device affecting the boot process.
If the monitor starts normally, reconnect accessories one at a time. Stop when the failure returns. Evaluate the last connected accessory, cable, port, or associated system.
7. Inspect Measurement Modules and Docking Connections
Inspect externally accessible module and docking connections for:
- Partially seated modules
- Bent or damaged connector contacts
- Debris or dried cleaning residue
- Damaged housings
- Loose latches
- Fluid intrusion
- Incorrect or incompatible modules
Remove and reseat only user-accessible modules according to approved handling practices. Do not force a module into place.
Expected outcome: All connected modules are compatible, clean, undamaged, and fully seated.
If removing a particular module allows the monitor to boot normally, label and evaluate that module separately.
8. Perform a Controlled Power Cycle
After documenting the failure and disconnecting nonessential accessories:
- Shut the monitor down normally when possible.
- Disconnect AC power.
- Remove removable batteries when permitted.
- Allow the monitor to remain fully de-energized briefly.
- Reinstall a verified battery if required.
- Reconnect verified AC power.
- Start the monitor using the normal power control.
Philips instructions identify the power on/standby control as the normal method for starting compatible IntelliVue monitors.
Expected outcome: The monitor completes startup and reaches a responsive monitoring screen without restarting.
If normal operation returns, continue observing the monitor through multiple controlled restarts before returning it to service.
9. Evaluate Network Influence
If the monitor starts normally with the network cable disconnected:
- Inspect the network cable and connector.
- Test with a known-good approved cable and active wall port.
- Confirm the monitor is connected to the correct clinical network jack.
- Check for recent network, central-station, or device-integration changes.
- Coordinate with the appropriate monitoring-network or IT support team.
- Do not modify IP addresses, certificates, host names, or protected network settings without authorization.
Philips IntelliVue monitors are designed to operate as networked patient-monitoring systems, making network isolation a useful external troubleshooting step when startup problems occur only while connected.
Expected outcome: The monitor remains stable when network communication is restored.
If connecting the network consistently recreates the failure, remove the monitor from clinical service and escalate the network or software issue.
10. Check Configuration Behavior
After the monitor boots, verify whether:
- The expected screen layout appears
- Licensed parameters are available
- The correct department or profile is loaded
- Date and time are reasonable
- Required network and central-monitoring indicators appear
- Configuration changes persist after a controlled restart
Do not load, copy, reset, or overwrite configurations unless authorized and using an approved facility or Philips procedure.
Expected outcome: The correct approved configuration loads and remains available after restart.
If the monitor loads a default, incomplete, incorrect, or corrupted configuration, keep it out of clinical service pending authorized configuration restoration.
11. Observe for Recurrence
When the monitor appears operational:
- Allow startup to complete without repeatedly pressing controls.
- Verify that the touchscreen and physical controls respond.
- Confirm waveforms and parameter areas update using approved simulators.
- Check alarm audio and visual indicators.
- Perform at least two controlled shutdown and startup cycles.
- Leave the monitor operating long enough to detect another freeze or restart.
- Review any accessible event or error information permitted under facility procedures.
Expected outcome: The monitor remains stable, responsive, and correctly configured through repeated operation.
If the monitor freezes, restarts, or loses its configuration again, stop testing and escalate the device.
If the Problem Persists
If verified power, battery condition, external accessories, modules, docking connections, network influence, and controlled restart procedures do not resolve the problem, common external causes have been ruled out.
The failure may involve internal storage, memory, power regulation, system software, configuration data, the display processor, or another internal component.
The monitor should be:
- Removed from service
- Labeled Out of Service
- Sent for repair or authorized bench evaluation
- Escalated to Philips support or a qualified service provider when software recovery, configuration restoration, or internal diagnosis is required
Do not repeatedly interrupt startup, reload software, access protected service functions, or perform internal disassembly without the appropriate authorization, documentation, and service resources.
Knowing when to stop is proper troubleshooting.
Clinical Use Tip
Never return an IntelliVue monitor to patient care solely because one restart temporarily cleared the problem. Boot loops and intermittent freezes can eliminate monitoring and alarm availability without warning. Verify repeated startup, configuration retention, parameter operation, and alarm functionality before release.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that the Philips IntelliVue MX monitor repeatedly restarted at the Philips startup screen and would not load the assigned monitoring configuration."
Cause
What was observed during troubleshooting.
Example:
"The monitor started normally after a defective external measurement module was disconnected, and the boot loop returned whenever that module was reconnected."
Resolution
What action was taken.
Example:
"Removed the defective module from service, verified stable monitor startup and alarm operation with a known-good module, and returned the monitor to service after functional testing."
Helpful Details to Include (If Known)
- Exact MX model and serial number
- Software revision, if accessible
- Location where the failure occurred
- Startup screen or message where the monitor stopped
- Displayed error codes or service messages
- Outlet tested
- AC power indicator behavior
- Battery condition and charge status
- Power cord or battery swapped
- Modules and accessories disconnected
- Network cable disconnected or swapped
- Behavior with and without network connection
- Configuration or profile displayed after startup
- Recent software, network, or configuration changes
- Number of successful restart cycles
- Alarm and parameter functional-test results
- Unusual heat, odor, noise, or evidence of fluid intrusion
- Final device status
Final Thought
Safe troubleshooting begins by protecting the patient, then isolating power, battery, accessories, modules, network connections, and configuration behavior in a logical order. An intermittent restart or freeze must not be dismissed after a single successful boot. Appropriate escalation and detailed CCR documentation help prevent an unreliable monitor from returning to clinical use.
That is successful troubleshooting.