BO2 crashes when I open the game
-
Just looked at the cmd prompt for the error and it was a plutonium bootstrapper problem. Hope that helps as well. Not sure what to do still.
-
Wannyyy Upload the dump file to google drive. Here's some fixes for common issues:
- playing pluto in virtual machines doesn't work incase you're using one
- make sure you are using windows 10 version 1607 or later
- try closing steam and removing steam_api from your game folder
- try closing all programs that are running in the background (especially steam, msi afterburner and rivatuner if you have them)
- try excluding pluto from scanning in your av software: https://plutonium.pw/docs/antivirus/#how-do-i-fix-this-windows-defender
- update your graphics drivers
- if you have a vr headset plugged in unplug it
- verify the integrity of your system files:
- open the start menu and search for "cmd"
- run cmd as admin
- execute the following command
dism /online /cleanup-image /restorehealth
- after dism has finished repairing your system restart your pc
-
This post is deleted!
-
-
Dss0 said in BO2 crashes when I open the game:
- playing pluto in virtual machines doesn't work incase you're using one
Also what is a "virtual machine"? All I have is a desktop PC.
-
Wannyyy need a password to download the file. don't worry about virtual machines if you just have a pc running windows, virtual machine would be for example you running a virtual installation of windows on top of mac os or linux.
-
Dss0 You should be able to view it now.
-
Wannyyy By the way this is exactly what I see in the cmd thing
A critical exception occured!
Exception Code: 0xC0000005
Exception Address: 0x005769BA (plutonium-bootstrapper-win32.exe) -
Seems like that file is damaged.
Anyways RektInator (or any other dev) will have to take a look at it.
-
The error code 0xC0000005 (Access violation) could be caused by a lot of reasons like: damaged windows installation/old version or corrupted kernel driver/missing or corrupted dll. If this error occur with any other application I suggest you to run a scan for the system by opening command prompt then execute: sfc /scannow
-
coder x64 I just finished the scan and it said there was nothing wrong.
-
Wannyyy I haven't gotten any responses and I still don't know how to fix it can someone help me?
-
Wannyyy i don't think they care tbh bro bc not that many people have had this issue. I do as well but i usually just keep restarting my pc til it finally works