Happened again after 14 minutes of gameplay. I have it on video. I ran scr_kill_infinite_loops 1;developer 1 at the beginning of the game. This is the bottom of console_zm_log: DB_LoadGump async zm_transit_gump_town DB_LoadGump gump file zm_transit_gump_forest2 is loaded DB_FlushGump 0 Unloading fastfile zm_transit_gump_forest2 Sys_GumpFlushed set gumpFlushedEvent DB_LoadGump calling DB_LoadXAssets Loading fastfile zm_transit_gump_town DB_LoadGump end send gump_flushed notify to script Built adjacency info for IPaks 23ms Sys_GumpLoaded set gumpLoadedEvent send gump_flushed notify to script Writing stats... GScr_loadGump zm_transit_gump_busstation 0 DB_L

I have posted a separate post as this is a separate issue: https://forum.plutonium.pw/topic/42375/game-freezes-30-mins-into-zombies-mode

@wizard_pot I found a way to save mine I just did upload stats swapped fov then did msaa8x then it worked for me everytime I turned it off

@noah2soberr one time should be enough.

Hey, sorry you’re both running into this.@KOTEMAN123 @Craken83 That 0xC0000005 / INVALID_POINTER_READ crash basically means the Plutonium bootstrapper tried to access memory and Windows blocked it. It looks scary, but don’t worry, it’s usually down to something simple like antivirus, a broken cache, or missing runtimes. First thing to check is that you’re actually on Windows 8.1 or newer (64-bit) and that your GPU supports DirectX 11. Older builds or DX10-only cards will crash the launcher right away. Another really common cause is antivirus or Windows Defender blocking Plutonium. Make sure you add this folder to your exclusions: C:\Users<YourUser>\AppData\Local\Plutonium and also allow plutonium-bootstrapper-win32.exe through your firewall. If that doesn’t help, try clearing the cache. Close Plutonium completely, delete the %localappdata%\Plutonium folder, then download a fresh plutonium.exe from the official site and run it again. You might need to reselect your BO2 folder afterwards. It’s also worth reinstalling the required runtimes, even if you think you already have them. That means .NET Framework 4.7.2 or newer, the Visual C++ Redistributables (both x86 and x64), and DirectX (June 2010). When these are missing or corrupted, the bootstrapper will just fail instantly. If you own BO2 on Steam, run a verify of the game files to make sure nothing is corrupted before launching through Pluto. Don’t forget overlays either — tools like MSI Afterburner, RTSS, ReShade, or even certain screen recorders can cause this exact access violation. Closing them before launching often fixes it. And if the crash started right after you changed your video settings, try deleting the config files inside the players folder (plutonium_mp.cfg or plutonium_zm.cfg). That resets everything to default and can clear a bad setting. If you still can’t get it working after all that, it really helps to share a bit more info: your Windows version (press Win+R and type winver), your GPU model, confirm that you excluded Plutonium in Defender, and maybe upload the latest .dmp file from %localappdata%\Plutonium\crashdumps. With those details, people can dig deeper and figure out what’s making the bootstrapper crash.

Hey @Sam_826 Yeah, it is possible to get BO2 split-screen working with Plutonium through Nucleus Co-op, but since it’s not officially supported you’ll sometimes hit errors like the one you saw. That “proto input failed to startup inject” message just means that the input hook didn’t attach properly when the game launched. A few things you can try that usually fix it: Run Nucleus as admin and, if “startup inject” fails, switch the injection mode in ProtoInput (try EasyHook, runtime, or remote load instead). Whitelist the Nucleus folder in your antivirus/Defender Windows loves to block the ProtoInput DLLs and that alone can trigger this error. Re-install the basics: .NET Framework and the Visual C++ redistributables (both x86 and x64). Even if you think they’re installed, a fresh install often helps. In the Plutonium launcher, make sure you run the game in LAN mode (anti-cheat off) before trying split-screen, otherwise the injection won’t work. And finally, check that Nucleus is pointing to the right .exe (t6mp.exe or t6zm.exe) and keep the game in windowed mode so the handler can position everything. If none of that works right away, let us know your Windows version and which injection methods you’ve tried makes it a lot easier to narrow down. Hope that helps and good luck getting splitscreen running!

Open the console and enter use_localStats 1 in the console to have the game save your online stats locally instead of on Plutonium's servers. Beware that doing this makes LAN mode use the same stats as online mode and vice versa.

Did you try reading the instructions or watching a 5-minute YouTube tutorial?

Click the grey "Game Settings" text then click "select dir" and you can change the directory.

hey did you find a fix. im having the same problem but my game doesnt crash. Nothing happens at all. I can join Zombie Servers just fine tho

Legend! Thank you

If you're getting kicked from Black Ops 2 (BO2) Plutonium servers with the message: "You were kicked due to reason of VPN" ...but you are not using a VPN, then the issue is likely related to your IP address being misidentified as a VPN or proxy by the server's protection system.

Check my comment from here: https://forum.plutonium.pw/topic/39666/error-during-initialization-invalid-patch-fastfiles-please-verify-your-game-files-with-steam/

@Resxt I see.