On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting Skyra host startup, measurement, reconstruction, or boot failures before escalating for Siemens service evaluation.
Step-by-Step Troubleshooting
Ensure Patient Safety First
Confirm there is no patient in the bore and no active scan in progress before troubleshooting.
If the failure occurs during patient imaging, stop the exam safely, remove the patient from the scanner room, and move the patient to another MRI system if clinically necessary.
Expected outcome: Patient care is protected before system troubleshooting begins.
Verify the Reported Failure
Ask MRI staff what failed and when it occurred:
- Host will not boot
- Exam software will not open
- Measurement will not start
- Reconstruction is delayed or failed
- Scanner stopped during startup
- Error appeared after power event, reboot, software lockup, or scan attempt
Record the exact error message, system state, and whether the issue is constant or intermittent.
Expected outcome: The failure type is clearly identified before resets or escalation.
Check for Active Patient or Exam Data Concerns
Confirm whether any patient images, unsent studies, or incomplete reconstructions are present.
Do not repeatedly reboot the host if staff are concerned about missing studies or interrupted reconstructions.
Expected outcome: Clinical data risk is considered before power cycling or further action.
Check Room Power and Visible System Status
Verify that the MRI control room equipment, host computer, monitors, keyboard, mouse, reconstruction equipment, and scanner electronics indicators appear powered.
Check for obvious facility power problems, tripped local power strips, disconnected cords, or failed UPS indicators.
Expected outcome: External power loss or disconnected equipment is ruled out.
If restoring power or reconnecting an external cord resolves the issue, confirm normal startup and stop.
Check Host Workstation Peripherals
Verify that the monitor is powered, the video cable is secure, and the keyboard and mouse are connected.
A blank screen or unresponsive workstation may be a display or input issue rather than a full host failure.
Expected outcome: The host workstation can be viewed and controlled.
If the workstation was functioning but the display or input device was disconnected, correct it, confirm normal operation, and stop.
Look for UPS or Power Conditioning Problems
Check whether the host, reconstruction computer, or related control room equipment is connected to a UPS.
Look for UPS alarm lights, overload warnings, low battery indicators, or outlets that are not supplying power.
Do not bypass hospital-approved power protection unless directed by site policy or Siemens service.
Expected outcome: Power backup or conditioning issues are identified before assuming system hardware failure.
Check Network and System Communication Indicators
Verify that network cables to the host, reconstruction system, scanner network equipment, and control room switches are seated and undamaged.
Look for link lights where visible.
Expected outcome: A loose network connection is ruled out as a cause of host-to-measurement or reconstruction communication failure.
If reseating an external network cable restores communication, confirm system function and document the finding.
Confirm Scanner Console Startup Sequence
Observe where startup stops:
- Operating system does not load
- Host loads but MRI application does not launch
- Application launches but cannot connect to scanner
- Measurement system does not become ready
- Reconstruction server does not respond
- Patient browser opens but images do not reconstruct
Expected outcome: The failure is narrowed to host boot, application startup, measurement communication, or reconstruction workflow.
Perform a Controlled Software Restart if Safe
If no patient is present and no data loss concern exists, perform a normal software restart using the available shutdown or restart method.
Avoid hard power cycling unless the system is frozen and local policy allows it.
Expected outcome: Temporary software lockups or communication hangs may clear after a controlled restart.
If the system returns to normal operation, perform a basic readiness check and stop.
Check for Recent Events or Changes
Ask staff whether the failure followed:
- Facility power interruption
- Network outage
- Software update
- System service
- Coil or table issue
- Failed scan sequence
- Emergency stop or system shutdown
- Unusual noise, odor, heat, or alarms
Expected outcome: A triggering event is identified that may help Siemens service or internal support.
Check Reconstruction Behavior
If acquisition appears to complete but images are missing, delayed, or stuck, determine whether the issue affects one exam, one sequence, or all exams.
Check whether prior images can be opened and whether new images appear after waiting an appropriate amount of time.
Expected outcome: The issue is separated into a single-study reconstruction delay versus a broader reconstruction system failure.
Check Measurement System Readiness
If the host boots but scans cannot start, check whether the scanner reports ready status, table status, coil status, door status, and system communication readiness.
Do not assume the measurement system has failed until basic interlocks and connected accessories are checked.
Expected outcome: External readiness conditions are ruled out before escalation.
Confirm Error Persistence After Basic Recovery
If the same boot, host, measurement, or reconstruction fault returns after a safe restart and external checks, stop troubleshooting.
Repeated reboot attempts can delay patient care and may risk incomplete data handling.
Expected outcome: The issue is confirmed as persistent and appropriate for service escalation.
If the Problem Persists
If power, peripherals, network connections, system readiness, and safe restart checks do not resolve the issue, the likely cause is internal to the host workstation, measurement system, reconstruction hardware, scanner control electronics, software environment, or system communication path.
The MAGNETOM Skyra should be:
- Removed from clinical use
- Labeled Out of Service
- Scheduled for Siemens service or qualified MRI bench/system evaluation
- Reported with exact error messages, startup behavior, and recent event history
Knowing when to stop is proper troubleshooting. MRI host, measurement, and reconstruction failures can involve system-level hardware, software, or communication faults that should not be handled through deep internal disassembly by general Clinical Engineering.
Clinical Use Tip
Do not troubleshoot host, measurement, or reconstruction failures while a patient remains on the table or in the bore. Remove the patient first, secure the area, and only continue troubleshooting when the scanner is safe and not needed for immediate patient care.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"MRI staff reported that the Siemens MAGNETOM Skyra would boot to the host console, but the measurement system would not become ready and exams could not be started."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering verified control room power, workstation peripherals, network connections, and performed a safe software restart, but the measurement communication fault returned."
Resolution
What action was taken.
Example:
"Unit was removed from service, labeled Out of Service, Siemens service was contacted, and error behavior with startup details was documented for follow-up."
Helpful Details to Include (If Known)
- Whether patient was on the table when the fault occurred
- Exact host, measurement, reconstruction, or boot error message
- Whether the operating system loaded
- Whether Numaris/exam software opened normally
- Whether the scanner became ready
- Whether reconstruction was delayed, failed, or missing images
- Whether the issue followed a power outage or network outage
- UPS status and indicator lights
- Monitor, keyboard, mouse, and workstation power status
- Network cable/link light observations
- Any unusual sound, heat, smell, or alarm behavior
- Whether a controlled restart was attempted
- Final device status
Final Thought
For MRI system boot, host, measurement, and reconstruction faults, Clinical Engineering should focus on patient safety, external power and communication checks, clear symptom verification, and controlled recovery attempts. Once common external causes are ruled out, escalation is the correct path. Accurate CCR documentation gives Siemens service and internal stakeholders the information needed to resolve the issue efficiently.
That is successful troubleshooting.