Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assault cube crashing at start. #465

Open
cartiace0d opened this issue Dec 16, 2022 · 11 comments
Open

Assault cube crashing at start. #465

cartiace0d opened this issue Dec 16, 2022 · 11 comments

Comments

@cartiace0d
Copy link

Assault Cube 1.2.0.2 crashing when I try to open it. It shows the loading screen then it crashes. PS: I've tried all other versions too and its the same.
Win32 Exception: 0xc0000005 [0x2367d0]
This is the error that shows.
I've tried turning off DEP, changed the values in the .bat file to lower the resolution, installed .net and direct x even did a fresh windows installation but nothing seems to work.
Will appreciate any help thanks.

@rpaugusto-eu
Copy link

rpaugusto-eu commented Dec 18, 2022

My current installation also started giving out this error a few days ago. I belive it might have been some Windows updated that caused this. Included is a screenshot of an instance of the error and the folder the error refers to. Not always mentions a folder or a file not being loaded, sometimes it only gives out the error number.

Already tried to reinstall, same error occurs. Sometimes it loads the game, it crashes joining a server or I can join a server and crashes leaving the server... all random events.

There was also another change, I recently bought a UHD monitor, the desktop resolution is now very high. But I have not changed the resolution in game, still FHD.

AC_error1

@Macintoshin
Copy link

Macintoshin commented Jan 1, 2023

Solution? -
I found if i set the resolution at 800 x 600 before launching it fixes this issue, but the game does not switch to 800 x 600 it stays at the default monitor resolution. Idk if this works with other setups but this works for me

UPDATE: as soon as i post this the issue returns. oops.

@HercFila
Copy link

HercFila commented Jan 4, 2023

Same issue on my end. I have Windows 11 as my main OS and seems like it is a problem with latest windows updates that cause this error. Tried installing latest version of the AC where the error is a bit different, sometimes it says it si missing a jpg file from for ladder top or bottom which I initially fixed with replacing all model textures with the previous version of AC. After fixing that problem the issue just loops back to Read Access Violation. Tried installing different version as different users and adding different permissions on all of these versions of AC... still didn't resolve the problem. What I found interesting is that rarely it would let me play the game (singplayer) mode also didn't matter but on certain maps I would get read access violation and on others I would play normally which leads me to believe that the jpg's are causing a problems. In the end its a weird rabbit hole of errors that I coulnd't figure out :)

@cartiace0d
Copy link
Author

I fixed the problem. It seems it was a problem with the recent Amd drivers update. I rollbacked to old version and the issue resolved.

@HercFila
Copy link

HercFila commented Jan 5, 2023

I fixed the problem. It seems it was a problem with the recent Amd drivers update. I rollbacked to old version and the issue resolved.

Interesting, which version of amd driver are you currently running on?

@adeliktas
Copy link

read #308

@rpaugusto-eu
Copy link

Previous working AMD driver for AssaultCube is Adrenalin 22.5.1 but this causes problems in WarThunder, GPU driver crashes.

Just installed latest Adrenalin 23.2.1, released yesterday 2023/02/14, and problem still occurs in AssaultCube.

@HercFila
Copy link

I managed to fix the issue on my side by also installing the 22.5.1 version of AMD Drivers. Although it didn't work for me from the beginning because I had to do a clean install of drivers, meaning I had to use the AMD's Cleanup Utility to uninstall everything as well as drivers and then when I installed the 22.5.1 version everything worked normally (didn't test compatiblity with other games but I would assume the drivers are super outdated for newer games.).

Also one more issue I had when the older drivers were successfully installed was that my Windows 11 automatically forced to updates to AMD drivers to fix this I had to disable the Windows updates for any kind of drivers in Group Policy Editor, so every driver update you will have to do manually.

@ac-jamz
Copy link
Contributor

ac-jamz commented Mar 9, 2023

For anyone suffering from this crash and using AMD drivers later than 22.6.1, please try installing the 64 bit client:
https://github.com/assaultcube/AC/archive/refs/heads/win-x64.zip
If you don't want to mess with your existing installation, you can simply copy the bin_win64 folder and assaultcube64.bat from the zip into your AC install folder (the same place you currently have bin_win32, probably c:\program files (x86)\AssaultCube 1.3.0.2).

@Macintoshin
Copy link

Thanks this worked 👍

@entr-py
Copy link

entr-py commented Apr 22, 2023

For anyone suffering from this crash and using AMD drivers later than 22.6.1, please try installing the 64 bit client: https://github.com/assaultcube/AC/archive/refs/heads/win-x64.zip If you don't want to mess with your existing installation, you can simply copy the bin_win64 folder and assaultcube64.bat from the zip into your AC install folder (the same place you currently have bin_win32, probably c:\program files (x86)\AssaultCube 1.3.0.2).

This seems to only work sporadically for me, sometimes the client launches and is fine, but other times it launches and my memory usage peaks out (task manager shows AC using 16gb of memory?!) causing my computer to freeze before the client inevitably crashes. Sometimes even when it seems to be working fine, launching into random maps will then break it again. Not sure if this is still a widespread issue for AMD users still but worth noting I guess.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants