AssaultCube Reloaded Forums
ACR Fatal Error - Printable Version

+- AssaultCube Reloaded Forums (https://acrf.victorz.ca)
+-- Forum: Gameplay (https://acrf.victorz.ca/forum-3.html)
+--- Forum: Help (https://acrf.victorz.ca/forum-6.html)
+--- Thread: ACR Fatal Error (/thread-403.html)



ACR Fatal Error - GoldenWolf - 2012-08-13

So today I decided to play ACR. When I had launched the game last week, it loaded fine. This morning when I launched it, I got an error stating:
Win32 Execption: 0xc0000005 [0x0] ()
I am not sure what is causing this problem. I have a quite old PC I use to run these games and here are the specs:
Intel Duo 2.20
Intel G33/G331 GPU
6 GB of DDR2 RAM
I also wasn't able to launch Counter Strike (CZ and DS as well)[Paid on Steam], Battlefield 2, or AssaultCube because I get either this error or a GPU driver error, even though my drivers are all updated.
Any help at all is appreciated!

EDIT 1 (08/13/12): Well it seems my drivers were acting funny after reinstalling a game. I tried to uninstall the driver and reinstall the driver. The game launches, but even at horrible, the framerate is running at about 3 FPS. I was also to run at High previously. Interestingly Nightmare that you had this problem on the server, so it must be either a memory problem or driver problem.


RE: ACR Fatal Error - Nightmare - 2012-08-13

I have got the same thing but with the server.
[Image: wKp0DjYt.png]

Admin Edit: "un-expected crash.png" was moved to imgur


RE: ACR Fatal Error - Victor - 2012-08-13

Those crashes don't show the debug data. *sigh*

Those are segmentation faults. They are probably different, but the same type of crash.

If they had more data, it should go to the Issue Tracker, but they don't, so I can't do anything about it, until I find that crash on my server.


RE: ACR Fatal Error - THESOUNDOFRAP - 2012-08-14

i had tha same problems, like NightMare showed,
#NukeCrash

*** Post on PS3


RE: ACR Fatal Error - Victor - 2012-08-15

I already fixed 1 faulty segfault sanity check in the client, and 1 overread in the server, both of which cause segmentation faults.

Just wait for the 2.5.3 patch to fix those bugs.