> For the complete documentation index, see [llms.txt](https://docs.lmarket.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lmarket.fr/valorant/onyx/common-bugs-and-fixes.md). # Common bugs & fixes ### ERROR 401 * Sync Time and date ### ERROR 404 * Key expired or Wrong Hwid , make a ticket in the server ### WIN 11 2H24 users * Switch to WIN10 or downgrade to WIN11 24h2. ### Driver didnt load correctly * Disable hvci and open onyx again. ### CrosshairX not found : Download for overlay. 1. Esp doesnt shows : Restart PC. ### BSOD If you are bluescreening, it is usually because of one of two issues. * The driver was loaded twice, if the driver is loaded twice, restart your pc and type your key in again. It wont blue screen again. DO NOT TRY AND LOAD A SAVED KEY AFTER A BLUESCREEN! it will not work, you need to type it again. * If you are still bluescreening, you need to uninstall the recent windows security update.​ --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.lmarket.fr/valorant/onyx/common-bugs-and-fixes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.