⚠️Common bugs & fixes
Menu disappears after joining a server (Rust)
If the menu disappears after joining the server. Instead of clicking OK from the pop up box while in the main menu, click it only after you have connected to a server.
Axon Service Failed L1 C2
Downgrade from Winver 24h2 or higher (Guide)
Disable core isolation (Guide)
Delete your VulnerableDriverBlocklist in regedit (download file to do it automatically)
Blue screen on inject
Download Defender Control (password:
sordum)Download Winrar
Unpack Defender Control into a folder on your desktop
Disable the defender control using the application
No "press ok" pop up
Install Visual C++ (download)
Install .Net (download)
DYT2 / YT2
This error indicates that the server is either down or something went wrong during the request.
Solution
Restart the Loader – In most cases, simply restarting the loader will resolve the issue.
Check for Widespread Issues – If this error is affecting everyone, it may be a server-side issue. Please open a support ticket for further assistance.
Launch with warp vpn on. (free)
0x304
Restart your PC.
0x399
This error occurs when the game injection process fails due to an invalid or empty process name. Ensure that you have the game is running before attempting to inject
Possible Causes & Solutions
Game Not Running – Ensure the game is launched before injecting.
Permissions Issue – Try running the game as an administrator.
Antivirus Interference – Some security software may block the injection process. Temporarily disable it to test.
Corrupt or Missing Files – Reinstall the injector or verify game files.
0x400
This error occurs when the specified process name does not have a valid process ID, meaning the game may not be running or was not detected.
Possible Causes & Solutions
Game Not Running – Ensure the game is launched before injecting.
Game Crashed or Closed – If the game closed unexpectedly, restart it and try again.
Delayed Process Detection – Wait a few seconds after launching the game, then attempt injection again.
Restart & Retry – Close the game completely, restart it, and attempt injection again.
0x402
This error occurs when the mapped payload handle is missing, indicating that the driver was not successfully mapped in the loader before attempting injection.
Possible Causes & Solutions
Driver Not Loaded – Ensure that the driver was properly mapped before injecting. Restart the loader and try again.
Insufficient Permissions – Run the loader with administrator privileges.
Antivirus or Security Software – Some security programs may block the driver from being mapped. Temporarily disable them to test.
Driver Crash or Unload – If the driver was unloaded unexpectedly, restart the system and reload the driver before injecting.
Corrupt or Missing Loader Files – Reinstall the loader to ensure all necessary files are present.
0x403
This error occurs when the payload handle exists, but no communication is received from it, indicating a failure in establishing a connection between the cheat and the driver.
Possible Causes & Solutions
Communication Blocked – Security software or Windows Kernel protections may be interfering. Temporarily disable them to test.
Reboot & Retry – Restart the system to reload necessary modules and try again.
0x406
This error occurs when there is an issue in the render setup, causing a common failure in the rendering process.
This error occurs when the system fails to load a required module during the initialization process. This prevents certain features from functioning correctly, typically affecting windowing and user interface operations.
Possible Causes & Solutions
Corrupt System Files – Verify and repair the integrity of your system files through tools like
sfc /scannowto ensure no system files are missing or corrupt.Incorrect System Configuration – Check that your system’s environment variables and settings are correctly configured.
Missing or Blocked System Dependencies – Ensure all required system dependencies are available and not blocked by security software or other restrictions.
Reboot & Retry – Restart the system to reload necessary modules and try again.
0x407
This error occurs when the system is unable to retrieve the window handle (HWND) from the given process ID, preventing interactions with the game’s window.
Possible Causes & Solutions
Game Window Not Active – Ensure that the game window is active and not minimized when attempting to retrieve the handle.
Window Not Initialized – If the game window is still initializing, wait for it to fully load before attempting again.
Reinject & Retry – If the issue persists, try reinjecting the loader and retrying the operation.
0x408
This error occurs when the overlay fails to initialize, preventing it from displaying or interacting with the game properly.
Solution
If this issue persists, please open a support ticket for further assistance. Our support team will help resolve the problem.
0x409
This error occurs when DirectX fails, preventing the system from initializing DirectX for rendering. This typically indicates issues with graphics configuration or system compatibility.
Possible Causes & Solutions
Outdated Graphics Drivers – Ensure your graphics drivers are up to date. Visit your GPU manufacturer’s website to download the latest drivers:
AMD Drivers
Intel Drivers
DirectX Installation Issue – Verify that DirectX is correctly installed and up to date. You can reinstall or update it from Microsoft’s website:
Insufficient System Resources – Check if the system has enough resources (memory, GPU power) available for Direct3D to initialize properly.
Graphics Hardware Compatibility – Ensure your hardware meets the minimum requirements for DirectX. Older or unsupported GPUs may cause issues.
Reinject & Retry – Try reinjecting the loader and retry the operation after updating drivers or DirectX.
0x500/0x501/0x502
Install both the game and steam on the same disk.
If it doesnt work try downloading both on C: Drive.
0x600
This error means that the server is down for auto updating. It will be back in a few minutes after its done updating.
0x601
This error occurs when the Directory Table Base (DTB) could not be found, preventing proper memory translation and access.
Possible Causes & Solutions
Kernel Access Blocked – Security software may prevent access to DTB. Temporarily disable it to test.
Unsupported or Updated System – Some Windows updates may change structures. Check for compatibility with your OS version in the tickets.
Memory Corruption – If DTB cannot be located, try restarting the system and reinjecting
0x602
This error occurs when the loader fails to retrieve the image base address of the target process, which is necessary for further memory operations.
Possible Causes & Solutions
Process Is Not Fully Loaded – If the process is still starting up, the image base may not be available. Wait for the game to fully load before retrying.
Reinject & Retry – If the issue persists, reinject the loader and retry the operation.
0x603
This error occurs when the specified module (e.g., GameAssembly.dll) could not be found in the target process, preventing further operations.
Possible Causes & Solutions
Game Not Fully Loaded – Ensure the game is fully launched before injecting. Some modules load after the initial startup.
Corrupt or Missing Game Files – Verify the integrity of game files through the launcher or reinstall the game.
Restart & Retry – Close the game, restart it, and attempt injection again.
Last updated