https://errorvault.dev/tags/device-access/ Recent content in Device Access on ErrorVault — Developer Error Code Dictionary Hugo en-us Sat, 01 Aug 2026 17:32:04 +0800 https://errorvault.dev/openclaw/openclaw-clw-gpu-denied-gpu-device-access/ Sat, 01 Aug 2026 17:32:04 +0800 https://errorvault.dev/openclaw/openclaw-clw-gpu-denied-gpu-device-access/ <h2 id="1-symptoms">1. Symptoms</h2> <p>When encountering the <code>clw-gpu-denied</code> error, you will observe the following indicators and shell outputs that signal GPU device access has been blocked or denied by the OpenClaw runtime environment.</p> <h3 id="primary-error-indicators">Primary Error Indicators</h3> <p>The error typically manifests as a diagnostic message printed directly to the console or logged to stderr during computation initialization. You may encounter output resembling the following pattern:</p> <div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#282a36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"><code class="language-fallback" data-lang="fallback"><span style="display:flex;"><span>[OpenClaw] ERROR: GPU device access denied </span></span><span style="display:flex;"><span>[OpenClaw] Code: clw-gpu-denied </span></span><span style="display:flex;"><span>[OpenClaw] Device: /dev/nvidia0 or CUDA:0 </span></span><span style="display:flex;"><span>[OpenClaw] Reason: Insufficient permissions or device not accessible </span></span></code></pre></div><p>Additional symptoms that frequently accompany this error include job failures that terminate immediately upon reaching GPU-intensive code sections, applications that fall back to CPU-only execution despite GPU hardware being present on the system, and runtime exceptions that reference <code>DeviceAccessDenied</code> or similar permission-related terminology. In containerized environments, you may also notice the container failing to start or crashing during initialization of GPU-accelerated workloads.</p>