🔴Common Errors & Fixes

This is a developing page, as more customers provide errors it will be updated accordingly

Table of contents

  • Quick tips (before you inject)

  • Error codes — client / injector

    • 0x399 — Invalid / empty process name

    • 0x400 — Process ID not found / no PID

    • 0x402 — Mapped payload handle missing (driver not mapped)

    • 0x403 — Payload handle present but no communication

    • 0x406 — Render / module initialization failure

    • 0x407 — Failed to get HWND for PID

    • 0x408 — Overlay failed to initialize

    • 0x409 — DirectX / Direct3D initialization failed

  • Error codes — kernel / memory / loader

    • 0x601 — DTB (Directory Table Base) not found

    • 0x602 — Failed to get image base address

    • 0x603 — Module not found in target process (e.g., GameAssembly.dll)

  • Extra troubleshooting & common scenarios

    • Blue screen on inject

    • “Axon service failed. (L: 1, C: 10)”

    • Registry tweak: VulnerableDriverBlocklistEnable (when required)

    • Standard inject checklist / Exploit Protection (Windows Defender)

    • Session timeout when booting Fortnite (EFI checks)

  • When to open a support ticket

  • Support ticket template (copy & paste)

Quick tips (before you inject)

  1. Run the loader and the game as Administrator.

  2. Make sure the game is fully launched and stable before injecting (wait 5–10s if needed).

  3. Disable any security tools temporarily only for testing. Re-enable after troubleshooting.

  4. Create a Windows restore point or backup before changing registry settings.

  5. If unsure, open a support ticket and include logs/screenshots and the exact error code.

Error codes — client / injector

0x399 — Invalid / empty process name

What it means The injector did not receive a valid process name, or the name is empty.

Quick fixes

  • Make sure the game is running before injecting.

  • Launch both loader and game as Administrator.

  • Temporarily disable antivirus / EDR and test.

  • Reinstall the injector if files appear corrupt.

0x400 — Process ID (PID) not found

What it means The specified process name doesn't map to a valid PID — the loader couldn't find the running process.

Possible causes & steps

  • Game not running: Start the game, wait a few seconds, then inject.

  • Game crashed / closed: Relaunch the game and retry.

  • Delayed detection: Wait (~5–10s) after launch before injecting.

  • Restart & retry: Fully close the game (check Task Manager), restart, then inject.

0x402 — Mapped payload handle missing (driver not mapped)

What it means The loader expects a mapped driver handle that isn’t present — driver mapping failed.

Fixes

  • Ensure the driver was mapped successfully before injecting (restart the loader).

  • Run the loader as Administrator.

  • Temporarily disable security software that may block driver mapping.

  • If the driver crashed or unloaded, reboot and remap it.

  • Reinstall the loader if files are missing or corrupt.

0x403 — Payload handle exists but no communication

What it means Driver handle is present but communication between userland and kernel driver failed.

Fixes

  • Check for kernel-level protection or security software blocking comms; temporarily disable them for testing.

  • Reboot the system to reset the driver state and try again.

  • If persistent, collect logs and open a support ticket.

0x406 — Render / module initialization failure

What it means A required module failed during initialization, usually affecting UI/windowing/rendering.

Fixes

  • Run sfc /scannow to verify and repair system files.

  • Ensure system environment variables and dependencies are correct.

  • Verify required runtime components (DirectX, Visual C++ redistributables, etc.).

  • Temporarily disable security software that may block module loading.

  • Reboot and try again.

Example

# Run in elevated command prompt
sfc /scannow

0x407 — Failed to get HWND for PID

What it means The loader couldn't get the window handle (HWND) for the target process — prevents window interactions.

Fixes

  • Make sure the game window is active and not minimized.

  • Wait for the game window to finish initializing (don’t inject immediately).

  • If problem persists, re-inject (restart loader + game).

0x408 — Overlay failed to initialize

What it means The overlay component failed to start — overlay won't display or interact with the game.

Fix

  • If this persists after basic troubleshooting (restart, permissions, updating GPU drivers), please open a support ticket so the team can inspect logs and environment details.

0x409 — DirectX / Direct3D initialization failed

What it means DirectX failed to initialize; rendering cannot start.

Fixes

  • Update GPU drivers:

    • NVIDIA — visit NVIDIA driver downloads

    • AMD — visit AMD driver downloads

    • Intel — visit Intel driver downloads

  • Reinstall/repair DirectX:

    • Use the DirectX End-User Runtime (Microsoft).

  • Ensure your hardware meets DirectX requirements.

  • Verify there are sufficient system resources (RAM, GPU memory).

  • Reinject after updating drivers / DirectX.

Error codes — kernel / memory / loader

0x601 — DTB (Directory Table Base) not found

What it means The loader could not locate the DTB for translating kernel memory — memory access failed.

Fixes

  • Security software may block kernel access — temporarily disable it for testing.

  • Windows updates can change internal structures; check compatibility with the loader/driver version.

  • Try a system reboot and then reinject.

  • If the OS is unsupported or recently updated, consult support/tickets for compatibility patches.

0x602 — Failed to get image base address

What it means The loader could not read the target process’ image base address (needed for memory offsets).

Fixes

  • Wait for the process to be fully loaded before injecting; some modules load later.

  • Re-inject (restart loader + process) and try again.

0x603 — Module not found in target process (e.g., GameAssembly.dll)

What it means Required module is not present in memory for the target process.

Fixes

  • Ensure the game is fully launched — some modules load after initial start.

  • Verify game files (use the game launcher/repair).

  • Restart the game and retry injection.

Extra troubleshooting & common scenarios

Blue screen on inject

Immediate actions

  1. Reboot into Safe Mode if needed and collect crash dump if possible.

  2. Run sfc /scannow and chkdsk to check system integrity.

  3. Try mapping a different driver build or rollback recent driver/Windows updates.

Run Sordum

  • If instructed to use Sordum utilities, the provided password is: sordum.

Security note: Only run trusted utilities from known sources. Verify file integrity.

Disable Windows Defender (testing only)

  • Strong caution: Disabling Defender or real-time protection exposes the system. Only do this temporarily for testing and re-enable afterward. Always explain the risk to end users and recommend a backup/restore point.

Axon service failed. (L: 1, C: 10)

  • Typical immediate step: reinstall or repair the Axon service component. If failure persists, collect the Axon logs and open a support ticket with the log attached.

Downgrade / Registry tweak for vulnerable driver blocklist

When to consider If OS version or specific Windows update blocks driver loading, vendors sometimes recommend either a supported OS version or a registry tweak.

Registry edit (make a system restore point first)

  1. Press Win + R, type regedit, press Enter.

  2. Navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CI\Config

  1. If VulnerableDriverBlocklistEnable (DWORD) doesn't exist, create it and set value to 0.

  2. Reboot.

Power-user caution: editing the registry is risky. Back up the key and create a restore point before proceeding.

Standard Inject Checklist — Exploit Protection (Windows Defender)

Before loading the product (example: R6), verify Exploit Protection settings. Each setting should be explicitly set to On by default or Off by default — not to “Use default (On)”.

Recommended settings (verify in Windows Security → App & browser control → Exploit protection → Program settings):

  • Control Flow Guard (CFG): On by default

  • Data Execution Prevention (DEP): On by default

  • Force randomization for images (Mandatory ASLR): On by default

  • Randomize memory allocations (Bottom-up ASLR): On by default

  • High-entropy ASLR: Off by default

  • Validate exception chains (SEHOP): On by default

  • Validate heap integrity: On by default

Injection starts game but cheat overlay doesn’t show

  • If you see the loader/game message (e.g., a prompt image) keep it open until the cheat fully loads, then click OK.

  • If overlay still doesn’t appear, check GPU overlays (e.g., NVIDIA/AMD/Steam) which can conflict, and try switching rendering mode or running the loader with admin rights.

Session timeout with booting Fortnite

  • Check if the user is booting EFI.

  • If using an external Fortnite build, advise the user to boot without EFI (external builds often need non-EFI mode). Provide exact environment details when opening a ticket.

When to open a support ticket

Open a ticket when:

  • You see persistent errors after trying all listed fixes (reboot, run as admin, reinstall, update drivers).

  • Kernel/DTB/driver mapping errors (0x402, 0x403, 0x601) persist — attach logs.

  • Blue screen (BSOD) occurs on inject — include mini-dump and exact Windows build.

  • Overlay or DirectX initialization fails after driver and system updates.

Last updated