XGRIDS Pro Guide™ / Module 10: Resources

10.4 Error Message Reference

Exact error text from LixelStudio, LCC Studio, and the field apps. What caused it, what to do, and when the fix requires XGRIDS engineering access.

How to Use This Page

Finding the Right Entry

This reference is organized by application. Each entry shows the error message exactly as it appears in the software, which application displays it, the confirmed cause, and the resolution steps. Error messages that require XGRIDS engineering access are marked accordingly. Do not use workarounds on those entries; contact XGRIDS Technical Support directly.

LixelStudio LCC Studio LixelGO / LCC Scan Requires XGRIDS Support

If a message you are seeing is not listed here, do not attempt to interpret it without official guidance. Submit the error log via the in-software feedback tool and contact XGRIDS Technical Support.

LixelStudio

LixelStudio Processing Errors

These errors appear during SLAM optimization, filtering, or export in LixelStudio on Windows. LixelStudio requires an NVIDIA GPU. AMD and Intel discrete GPUs are not supported.

Error Message
Application
Cause
Resolution
lio drift - try robust mode
LixelStudio
SLAM tracking failed during processing. Most common causes: the scan included an open or featureless space, the device was not held still during initialization, or the scan path entered a degraded environment without a return loop.
  1. In the project settings, enable Robust Mode and reprocess. This is the first and correct response to this error.
  2. If Robust Mode succeeds, review the trajectory in the preview. Verify the output quality before delivery.
  3. If Robust Mode also fails, see the entry below for "too few effective points."
too few effective points
trajectory drift
LixelStudio
Robust Mode processing failed. The drifted segment of the scan contains insufficient trackable geometry for the SLAM algorithm to reconstruct a valid trajectory. The data in that portion is not recoverable through software.
  1. In the project's advanced settings, adjust the mapping end time to exclude the drifted segment. This salvages the clean portion of the scan.
  2. If the drifted segment contains critical coverage, the area must be rescanned. There is no processing workaround for a fundamentally broken trajectory.
Data Loss Risk The recording period after the in-field "Record Warning Only" alert should not exceed 20 minutes. Data collected beyond that point becomes progressively harder to process and may be unrecoverable.
RTK invalid
LixelStudio
LixelStudio cannot apply RTK coordinate data to the scan. Common causes: the RTK fix had not stabilized before the scan began, not enough RTK-fixed distance was walked before the scan path started, or the RTK antenna tilt exceeded the valid range during collection.
  1. Confirm the LixelGO app showed more than 10 satellites and a Fixed status before the scan began.
  2. After achieving Fixed status, walk at least 33 ft (10 m) before beginning the scan route. RTK data captured during the initial fix period is often insufficient for processing.
  3. Confirm the RTK antenna remained within 20 degrees of vertical throughout the scan. Exceeding this invalidates the fix record even when the LED appeared green.
  4. If all field conditions were correct and the error persists, process as pure SLAM and apply GCPs in post-processing as a recovery path.
Point Cloud Mapping HBC file parse failure

Also appears as: file corruption or unreadable project on import
LixelStudio
The scan data file is corrupted or incomplete. This happens when data transfer was interrupted, the device was powered off before saving completed, cloud storage transfer corrupted the file, or there is a version mismatch between device firmware and LixelStudio.
  1. Verify the data copy is complete. Use TeraCopy or a similar hash-verification tool to confirm the source and destination files are identical before processing.
  2. Never power off the scanner immediately after stopping a recording. Wait for the save indicator to complete. Powering off during save corrupts the HBC file and the data is not recoverable.
  3. Check for version mismatch: devices running firmware 1.4 or later require LixelStudio 2.4.6 or later. Using LixelStudio 2.4.5 or earlier with newer firmware produces HBC parse failures.
  4. If the file is confirmed corrupted and no backup exists, the scan must be repeated. Contact XGRIDS if the corruption is suspected to be a firmware issue rather than a transfer issue.
Activation code expired

Appears even when the code is unused and valid
LixelStudio
3 possible causes: the computer has no internet connection at activation time, the system clock is not synchronized with internet time servers, or the activation code has already been used on another machine.
  1. Confirm the computer is connected to the internet and that the system time is synchronized. Check Windows time settings and force a sync if needed.
  2. Verify the code has not already been used. Each device SN is entitled to 3 permanent activation codes. Used codes cannot be reactivated.
  3. If the code is confirmed unused and valid, and the error still appears after fixing connectivity and time sync: do not use a second code. Contact XGRIDS Technical Support. Using a second code will not resolve the underlying issue and consumes a code permanently.
Blank white screen on launch or after creating a new project
LixelStudio
One of 4 causes: missing or outdated system .dll libraries, outdated or unsupported GPU driver, OpenGL version below 4.0, or Windows Core Isolation conflicting with the application.
  1. Update Visual C++ Redistributable libraries from Microsoft's official page (search "latest-supported-vc-redist").
  2. Update the NVIDIA graphics driver from nvidia.com/drivers. LixelStudio does not support AMD graphics cards. If the workstation uses AMD, this is the root cause and there is no workaround.
  3. Open the LixelStudio installation directory and run contextinfo.exe to verify the OpenGL version is 4.0 or higher. If it is below 4.0, the GPU or driver does not meet the minimum requirement.
  4. If the above 3 steps do not resolve it, disable Core Isolation in Windows Security settings (Virtualization-based security) and relaunch.
Insufficient physical memory
Filter crash
LixelStudio
The workstation RAM is insufficient for the scan duration. LixelStudio requires approximately 2 GB per minute of scan data. Other memory-intensive applications are running during processing, the project is saved to the C: drive causing access conflicts, or the target drive is low on free space.
  1. Close all other applications before running LixelStudio processing. Memory usage spikes are not always visible in the foreground.
  2. Ensure the project is not saved to the C: drive. Save and process from a dedicated high-speed SSD on a separate drive letter.
  3. Verify the target drive has sufficient free space for the processing output. A full or near-full drive causes filter crashes that look like memory failures.
  4. If the scan exceeds your available RAM (approximately 15 minutes on 32 GB, 30 minutes on 64 GB, 60 minutes on 128 GB), split it into shorter segments and use Map Fusion to combine them.
LCC Studio

LCC Studio Errors

LCC Studio requires an NVIDIA GPU with CUDA support. AMD and Intel discrete GPUs are completely unsupported with no workaround. All entries below assume the correct GPU is installed and confirmed. If the GPU is AMD, the application will not function regardless of driver state.

Error Message
Application
Cause
Resolution
0x34041002

Reconstruction failure
LCC Studio
Required program components are missing. This is caused by antivirus software quarantining or deleting LCC Studio files after installation, or by an incomplete initial installation.
  1. Temporarily disable real-time antivirus protection and reinstall or repair the LCC Studio installation.
  2. Add the LCC Studio installation directory to your antivirus exclusion list before re-enabling protection.
  3. Verify the installation completed successfully by running a test reconstruction on a known-good dataset.
0x34040100

Reconstruction failure
LCC Studio
Project file corruption. Some data in the project file is missing. This typically results from an incomplete file copy or a transfer that was interrupted before completion.
  1. Verify that the project file was fully downloaded or copied before opening it in LCC Studio. Use TeraCopy or equivalent hash verification to confirm completeness.
  2. If copying from cloud storage, confirm the download finished before LCC Studio accessed the files. Partial downloads cause this error silently.
  3. If the source data is intact, re-copy the full project folder and reprocess.
Reconstruction failure (unspecified error)
LCC Studio
CPU instability caused by overclocking microcode issues. Intel 13th and 14th generation desktop processors are known to be affected by an instability defect in certain batches. This causes silent corruption during compute-intensive tasks like 3DGS reconstruction.
  1. Identify the CPU model and check whether it is listed in Intel's published advisory for 13th and 14th generation desktop instability. Intel has released BIOS microcode updates to address this.
  2. If the CPU is affected and no BIOS update has been applied, contact a qualified IT technician to update the system BIOS before attempting further processing.
  3. After the BIOS update, re-run reconstruction on the same dataset to confirm the issue is resolved.
  4. If reconstruction continues to fail after addressing the CPU issue, submit logs via the in-software feedback tool and Contact XGRIDS Technical Support.
Invalid data directory
LCC Studio
The selected save path contains characters that LCC Studio does not support. Spaces in the path are the most common cause. As of version 1.6.1, the path may only contain uppercase letters, lowercase letters, digits, hyphens, underscores, and periods.
Move the project to a path that contains only supported characters. Rename any folders with spaces, special characters, or non-ASCII characters. For example, C:\Projects\scan data\ will fail; C:\Projects\scan-data\ will work. Verify the full path from the drive root, not just the final folder name.
The network is not available. Please check the network.
LCC Studio
LCC Studio cannot reach XGRIDS authentication servers. This appears at login. The most common cause in professional environments is a corporate firewall blocking outbound connections to XGRIDS domains.
  1. Contact your network administrator and request that all https://*.xgrids.com domains be allowed outbound on port 443.
  2. If wildcard rules are not permitted, the minimum required domain is https://api-gw.xgrids.com on port 443.
  3. To confirm whether the issue is a backend service problem rather than a firewall, attempt to log in via browser at https://developer.xgrids.com/#/login. If that also fails, the issue may be temporary and on XGRIDS servers.
  4. If no corporate firewall is in use, check for an active VPN. VPN traffic routing can block the authentication handshake.
Nvidia graphics driver not installed

Appears even when the driver is confirmed installed
LCC Studio
3 possible causes: the GPU is not NVIDIA (AMD/Intel are not supported), the driver installation is corrupt, or the system has multiple discrete GPUs installed and LCC is encountering a GPU conflict.
  1. Confirm the GPU is NVIDIA. Open Command Prompt and run nvidia-smi. If the command executes and returns driver and GPU information, the driver is correctly installed. If it fails, the driver needs to be reinstalled.
  2. If the system has 2 discrete GPUs, disable the secondary GPU in Device Manager. LCC Studio does not support multi-GPU operation and may fail to select the correct GPU automatically, causing this error even with valid hardware.
  3. An integrated GPU (Intel HD/UHD/Iris Xe) does not need to be disabled. LCC will automatically assign processing to the NVIDIA GPU when an integrated GPU is also present.
  4. If nvidia-smi fails, contact an IT professional to reinstall the NVIDIA driver cleanly. NVIDIA recommends using DDU (Display Driver Uninstaller) to remove the existing driver before reinstalling.
Blue screen or system reboot during LCC reconstruction
LCC Studio
The workstation is experiencing thermal throttling or hardware instability under the sustained high GPU and CPU load of 3DGS reconstruction. LCC reconstruction is one of the most demanding tasks a professional workstation will run.
  1. Check Windows Event Viewer for the specific blue screen error code at the timestamp of the failure. The error code identifies whether the cause is thermal, memory, or driver-related.
  2. Verify that cooling is adequate. Monitor GPU and CPU temperatures during reconstruction. If temperatures exceed thermal limits, improve case airflow or clean cooling components.
  3. Close all other applications before running reconstruction to reduce competing load.
  4. If the error persists on a well-cooled system, have an IT professional evaluate the workstation hardware. Contact XGRIDS if the issue appears to be software-related rather than hardware.
The number of devices has reached the limit

Appears when logging into LCC on a second computer after logging out of the first
LCC Studio
LCC Studio does not support forced logout. After logging out manually, the server-side login node count takes approximately 6 minutes to clear. Attempting to log in on a second machine before this interval elapses triggers this error.
Log out manually from the original device if still accessible. Then wait 6 minutes before logging into LCC on the new machine. The system automatically refreshes the login node count after 6 minutes. Do not repeatedly attempt to log in during this window.
LixelGO / LCC Scan

App and Device Errors

These messages appear in the LixelGO or LCC Scan mobile apps, or are displayed as device status codes.

Error Message
Application
Cause
Resolution
Device status: 316aa
Device not in activatable region
LixelGO / LCC Scan
The device's serial number is registered to a different sales region than where it is currently being used, the wrong regional version of the app is installed, or a VPN is making the app detect cross-region usage.
  1. If the device was purchased in mainland China and is being used internationally (or vice versa), the region lock requires resolution by the XGRIDS regional sales manager. Contact XGRIDS to initiate this process. Do not attempt further activation steps until the restriction is lifted.
  2. If the device region matches its location, confirm you are using the correct regional version of the app. A mainland China device paired with the international app version constitutes a mismatch.
  3. After the sales manager resolves the restriction, download the correct regional app, log in with the original activation account, and reconnect.
  4. If a VPN is active on the phone, disable it and retry. The app detects the apparent location mismatch and blocks activation.
Record Warning Only

In-field status indicator, not a post-processing error
LixelGO / LCC Scan
SLAM tracking has degraded. The device is still recording but confidence has dropped below acceptable thresholds. Caused by entering featureless or repetitive environments (tunnels, corridors, large flat surfaces), extreme device movement, or prolonged operation outside tilt limits.

Stop recording immediately when this status appears. Continuing to record beyond this point makes the drifted segment progressively harder to process and potentially unrecoverable. Recording should not continue more than 20 minutes after this warning appears.

  1. End the recording as soon as possible after this status appears.
  2. When processing in LixelStudio, enable Robust Mode for this scan.
  3. If Robust Mode fails, adjust the mapping end time in the project's advanced settings to exclude the portion collected after the warning.
Device has been bound by another user
LixelGO / LCC Scan
3 possible causes: the app login session expired, the device recently had a 316aa region restriction that required a sales manager to resolve and you did not re-log in with the original account, or there is a genuine account binding conflict.
  1. Log out of the current account in the app and log back in. An expired session is the most common cause and resolves immediately.
  2. If the device recently had a 316aa restriction resolved, log in using the original account that first activated the device. A different account will not be recognized.
  3. Device binding cannot be cleared by the user. If the issue is a genuine binding conflict, Contact XGRIDS. Clearing the binding also clears the activation and warranty record, which cannot be undone.
Escalation

When to Contact XGRIDS Directly

Any error involving firmware, account access, hardware defects, or licensing requires XGRIDS engineering access. The entries marked with the XGRIDS Support badge above cannot be resolved by local troubleshooting. Contact support with the following information ready: device serial number, firmware version, software version, operating system, GPU model, and the complete log file from the failed task.

In LixelStudio, logs are in the Logdir and Report folders inside the project directory. In LCC Studio, use the in-software feedback button to submit logs directly.

For errors requiring engineering access, licensing issues, or hardware defects: contact XGRIDS Technical Support directly.

XGRIDS Technical Support →
← Previous 10.3 Troubleshooting Index Next → 10.5 Firmware and Software Updates

©2026 Alpine Reality Capture LLC  •  XGRIDS Pro Guide™  •  Site Disclaimer