TheRealKC

Thanks for your reply. Yes, I already tried loading GTA V normally into Story Mode first, then starting RAGE Plugin Hook; it still hung/crashed. GTA works normally by itself. Attached is the latest RagePluginHook.log currently in the main game folder, from October 11 at 9:23 PM, after the AMD 26.9.2 update and reboot. This last test used only -nobattleye in commandline.txt, with -nodx removed. It again ends at "Initializing texture system; phase 14" after "Steam hook detected". The Windows username in the log has been replaced with USER. Understood about -nodx. It was only a diagnostic test and has been removed; it was not a usable fix because the LSPDFR interactions did not respond. Is there a specific next diagnostic step or trace you would like me to capture? RagePluginHook-latest-2026-10-11-2123.log

GTA V Legacy runs normally alone, but RAGE Plugin Hook hangs, becomes Not Responding and then crashes during startup, before LSPDFR loads. Versions: Windows 11 Home build 26200 AMD Radeon RX 9060 AMD Adrenalin 26.9.2 / driver 32.0.32015.2008 (updated and rebooted; same failure) Steam GTA V Legacy 1.0.3889.0 RPH 1.131.1424.17745 LSPDFR 0.4.9695.26411 The RPH log reports “Failed to retrieve D3D call in reasonable time, changing hooking mode”, then “Steam hook detected”. It initializes the D3D11 renderer and stops at “Initializing texture system; phase 14”. The attached log is from the failed test after updating the driver. A full user-mode dump from the earlier driver was analyzed locally with WinDbg. It shows an execute access violation (0xc0000005), target 0xffffffffed91048a. The caller is socialclub_tmp.dll+0x2479e. Version resources identify this temporary DLL as RAGE Plugin Hook 1.131.1424.17745 by MulleDK19 / LMS. Disassembly shows an indirect call through a pointer loaded from socialclub_tmp+0x4b9ef0. The main GTA thread is waiting in SleepEx. This identifies a failing RPH hook path; the underlying reason for the invalid pointer is not established. No new dump has been captured after the driver update. Already tried without resolving startup: Overlay changes; reinstall; no-plugin startup; DX11; windowed 1280x720; launching GTA first and attaching RPH after Story Mode loads; DX10.1; correcting malformed commandline arguments; AMD driver update and reboot. Diagnostic bypass: adding -nodx allows GTA and LSPDFR to load. However, LSPDFR station/locker/duty interaction keys and in-game key capture do not respond. GTA walking and native pause-menu keyboard navigation do work. Rebinding Toggle Duty from E to F7 and the in-game binding menu did not fix it. No controller is available. Therefore -nodx is not a usable resolution. Current commandline.txt: -DX11 -disableCustomLoadingScreen -nobattleye The log warns that nobattleye is supplied twice (also supplied elsewhere). Could you advise on diagnosing the invalid RPH hook target or a supported way to restore rendering and input? Is a diagnostic build or specific additional trace available? The full memory dump is retained locally and has not been uploaded. Thank you. RagePluginHook-amd2692-failure.log