Error Message Reference
Error text from LixelStudio, LCC Studio, and the field apps. What caused it, what to do, and when the fix requires XGRIDS engineering access.
Finding the Right Entry
This reference is organized by application. Each entry shows the error message as it appears in the software, the application that displays it, the confirmed cause, and the resolution steps. Error messages that require XGRIDS engineering access are marked with the Escalate tag. Do not use workarounds on those entries. Contact XGRIDS Technical Support directly.
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 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.
SLAM optimization failed (insufficient effective points)
Cause
The SLAM solver could not converge on a stable trajectory. Caused by long featureless paths, insufficient loop closures, or high walking speed in repetitive geometry.
Resolution
- In the project settings, enable Robust Mode and reprocess. This is the first and correct response to this error.
- If Robust Mode succeeds, review the trajectory in the preview. Verify the output quality before delivery.
- If Robust Mode also fails, the data from the drifted portion cannot be recovered. The area must be rescanned.
Trajectory drift detected
Cause
The SLAM optimization completed but the solver detected accumulated drift that exceeded the acceptable threshold for the full trajectory.
Resolution
- In the project's advanced settings, adjust the mapping end time to exclude the drifted segment. This salvages the clean portion of the scan.
- If the drifted segment contains critical coverage, the area must be rescanned. There is no processing workaround for a fundamentally broken trajectory.
RTK data invalid or unusable
Cause
The RTK track recorded with the scan does not meet validation criteria. Common causes are insufficient satellite count, Float status at scan start, excessive antenna tilt, or RTK loss during overlap zones.
Resolution
- Confirm the LixelGO app showed more than 10 satellites and a Fixed status before the scan began.
- 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.
- 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.
- If all field conditions were correct and the error persists, process as pure SLAM and apply GCPs in post-processing as a recovery path.
HBC file parse failed
Cause
The project file from the device cannot be parsed. The two confirmed causes are an incomplete data transfer and a version mismatch between device firmware and LixelStudio.
Resolution
- 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.
- 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.
- Confirm LixelStudio version matches the device firmware lineage. Running an older LixelStudio version against firmware from a newer release produces HBC parse failures. For the K2 firmware v2.4.1+ lineage, use LixelStudio v4.0 or later.
- Escalate 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 already used or invalid
Cause
The activation code entered has already been consumed or cannot be verified by the activation server. Each device serial number is entitled to a fixed number of permanent activation codes.
Resolution
- 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.
- Verify the code has not already been used. Each device serial number is entitled to 3 permanent activation codes. Used codes cannot be reactivated.
- Escalate 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.
OpenGL initialization failed
Cause
LixelStudio could not initialize the OpenGL graphics context. Caused by missing or outdated runtime libraries, incompatible GPU drivers, or Windows security settings blocking initialization.
Resolution
- Update Visual C++ Redistributable libraries from Microsoft's official page (search "latest supported vc redist").
- 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.
- Open the LixelStudio installation directory and run
contextinfo.exeto 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. - If the above three steps do not resolve it, disable Core Isolation in Windows Security settings (Virtualization-based security) and relaunch.
Out of memory or filter crashed
Cause
Processing exceeded available system memory or workspace disk capacity. May appear as a filter crash, an out-of-memory error, or a silent processing termination.
Resolution
- Close all other applications before running LixelStudio processing. Memory usage spikes are not always visible in the foreground.
- Ensure the project is not saved to the C: drive. Save and process from a dedicated high-speed SSD on a separate drive letter.
- 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.
- 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 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.
Installation failed or application will not launch
Cause
The installer was blocked or quarantined by real-time antivirus protection, or the installation did not complete successfully.
Resolution
- Temporarily disable real-time antivirus protection and reinstall or repair the LCC Studio installation.
- Add the LCC Studio installation directory to your antivirus exclusion list before re-enabling protection.
- Verify the installation completed successfully by running a test reconstruction on a known-good dataset.
Project file corrupted or incomplete
Cause
The project file was not fully copied or downloaded before LCC Studio tried to open it. Cloud-storage downloads that appear complete but were still streaming cause this silently.
Resolution
- 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.
- If copying from cloud storage, confirm the download finished before LCC Studio accessed the files. Partial downloads cause this error silently.
- If the source data is intact, recopy the full project folder and reprocess.
Reconstruction failed mid-process
Cause
A confirmed cause on Intel 13th and 14th generation desktop CPUs is the CPU instability advisory. Intel has released BIOS microcode updates to address it. Workstations without the update may produce inconsistent reconstruction failures under sustained load.
Resolution
- Identify the CPU model and check whether it is listed in Intel's published advisory for 13th and 14th generation desktop instability.
- 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.
- After the BIOS update, rerun reconstruction on the same dataset to confirm the issue is resolved.
- Escalate If reconstruction continues to fail after addressing the CPU issue, submit logs via the in-software feedback tool and contact XGRIDS Technical Support.
Login or authentication failed
Cause
The application could not reach XGRIDS authentication servers. Most commonly caused by a corporate firewall blocking outbound traffic to XGRIDS domains, or a VPN routing traffic in a way that breaks the handshake.
Resolution
- Contact your network administrator and request that all
https://*.xgrids.comdomains be allowed outbound on port 443. - If wildcard rules are not permitted, the minimum required domain is
https://api-gw.xgrids.comon port 443. - 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. - If no corporate firewall is in use, check for an active VPN. VPN traffic routing can block the authentication handshake.
GPU not detected
Cause
LCC Studio could not identify a CUDA-capable NVIDIA GPU. The driver may not be installed, two discrete GPUs may be confusing the auto-selection, or the GPU is not supported.
Resolution
- 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. - If the system has two 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.
- An integrated GPU (Intel HD/UHD/Iris Xe) does not need to be disabled. LCC Studio will automatically assign processing to the NVIDIA GPU when an integrated GPU is also present.
- If
nvidia-smifails, contact an IT professional to reinstall the NVIDIA driver cleanly. NVIDIA recommends using DDU (Display Driver Uninstaller) to remove the existing driver before reinstalling.
System crash or blue screen during reconstruction
Cause
Workstation hardware failed under reconstruction load. Causes can be thermal (GPU or CPU exceeding safe temperatures), memory (faulty RAM), or driver-related (older NVIDIA drivers with sustained-load instability).
Resolution
- 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.
- Verify that cooling is adequate. Monitor GPU and CPU temperatures during reconstruction. If temperatures exceed thermal limits, improve case airflow or clean cooling components.
- Close all other applications before running reconstruction to reduce competing load.
- Escalate 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.
App and Device Errors
These messages appear in the LixelGO or LCC Scan mobile apps, or are displayed as device status codes.
Region restricted (error 316aa)
Cause
The device's region of purchase does not match the region of attempted use, or the app's regional version does not match the device's region. XGRIDS enforces region-specific activation.
Resolution
- Escalate 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.
- 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.
- After the sales manager resolves the restriction, download the correct regional app, log in with the original activation account, and reconnect.
- If a VPN is active on the phone, disable it and retry. The app detects the apparent location mismatch and blocks activation.
LIO drift warning (active scan)
Cause
The SLAM solver detected accumulated drift during the active scan and is warning the operator that data quality is degrading.
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.
Resolution
- End the recording as soon as possible after this status appears.
- When processing in LixelStudio, enable Robust Mode for this scan.
- If Robust Mode fails, adjust the mapping end time in the project's advanced settings to exclude the portion collected after the warning.
Account binding conflict
Cause
The app account is no longer recognized as the device's bound activation account, or the session has expired.
Resolution
- Log out of the current account in the app and log back in. An expired session is the most common cause and resolves immediately.
- 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.
- Escalate 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.
When to Contact XGRIDS Directly
Any error involving firmware, account access, hardware defects, or licensing requires XGRIDS engineering access. The entries marked above with the Escalate tag 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 Log directory 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.
©2026 Alpine Reality Capture LLC • XGRIDS Pro Guide™ • Site Disclaimer