The rig check failed. What now?
Read the exact rejection reason, then fix the right thing. GPU, network, RAM, or compatibility issues each have specific remedies.
in this article
The Rig Check reports a pass / fail with a specific reason when your hardware doesn’t qualify. Don’t just retry blindly: the rejection reason tells you exactly what to fix.
Network dashboard data shows 25% of all rig checks fail on the first attempt; nearly all of them can be resolved with one specific change.
the most common failures
”latency too high”
What it means: your connection’s round-trip to the nearest YOM exchange is over 30 ms, or jitter (variation in latency) is too high.
What it usually is: Wi-Fi. Even fast Wi-Fi adds 10-30 ms of variable latency and noticeable jitter. The YOM network can’t reliably route real-time game streams over a connection with these characteristics.
How to fix:
- Plug a wired ethernet cable from your router to your PC
- Re-run the rig check
- If the network test still fails over wired ethernet, the bottleneck is your ISP or modem. Try a speed test (fast.com) and confirm latency to a nearby server is under 20 ms.
This single change (Wi-Fi → wired) resolves roughly 80% of network-related rig check failures.
”bandwidth too low”
What it means: your upload speed isn’t enough to sustain a streaming session at acceptable quality. Minimum is 25 Mbps upload.
How to fix:
- Stop any active uploads (cloud backup, video calls, Steam uploading game saves) and re-test
- Check if anyone else on your network is using bandwidth (4K video calls, large downloads)
- If your raw upload is genuinely under 25 Mbps even idle, your ISP plan needs upgrading
”GPU insufficient”
What it means: your GPU isn’t an NVIDIA RTX series, or it’s a pre-RTX card without the NVENC encoder block needed for low-latency streaming.
How to fix: there’s no fix for this on the hardware side. The minimum is RTX 2060 (any model: laptop GPUs are out, eGPU enclosures add latency). If you’re using a GTX-series or AMD card, the rig check can’t pass.
If you’re sure your GPU is RTX-series and the check still fails:
- Update to the latest NVIDIA driver via GeForce Experience or the standalone driver download
- Confirm the GPU is selected as the primary in Windows display settings (some hybrid laptops default to Intel iGPU)
“container runtime not available”
What it means: Docker + NVIDIA container toolkit can’t initialize on this machine.
This is usually a software-conflict issue. Common causes:
- Windows Subsystem for Linux (WSL) with conflicting GPU passthrough settings. Disable WSL’s GPU sharing.
- An existing Docker installation with non-default NVIDIA config. Reset to defaults or uninstall Docker before running rig check.
- VirtualBox or VMware Workstation reserving GPU resources. Close them before running the check.
”RAM insufficient”
What it means: you have less than 16 GB of system RAM, or available RAM at test time was below the threshold.
How to fix:
- If installed RAM is genuinely less than 16 GB: upgrade. There’s no software workaround.
- If installed RAM is 16+ GB but available is low: close memory-hungry applications (browsers with many tabs, Discord, Spotify) and rerun the check.
less common failures
”vulkan unsupported”
Update your GPU driver. Modern NVIDIA drivers include Vulkan support but very old (pre-2020) drivers may not.
”secure boot conflict”
Your BIOS has Secure Boot enabled in a configuration the rig check can’t handle. Two options:
- Disable Secure Boot temporarily for the check
- Add the YOM signing key to your trusted keys in BIOS
”internet speed inconsistent”
Your speed test shows the speed varying by more than 30% across multiple samples. This usually indicates ISP congestion (peak hours) or a problematic local network device.
Try the check again later, or replace your router/modem if the issue persists.
what to do if the failure reason isn’t clear
The rig check tool also exports a detailed result you can share with us. From the failure screen, click download report (or copy the share link). Send that with your message via contact and we can usually pinpoint the issue within a few hours.
one note on retrying
The rig check writes results to your wallet’s profile. Repeated failures don’t penalize you in any way: you can rerun as many times as needed. Each successful run also updates your node-capacity score, so re-running after a hardware upgrade is encouraged.