Critical Error


(BK201) #1

Every game about 5 minutes in i get DC to menu saying critical error, just started happening today. Has anyone been able too fix the issue I can not afford to DC during MM or COMP games resulting in forfeit.


(Eox) #2

That’s fun, it reminds the the bug I kept undergoing before the hotfix.

I did something before the update that seemed to make the game more stable : go to the Documents\My Games\UnrealEngine3\ShooterGame\Config directory, and remove all the file in it. Then make a steam cache verification for Dirty Bomb. It seemed to have fixed my problem until the hotfix came back.


(hyphe) #3

karma ?


(BK201) #4

[quote=“Eox;14339”]That’s fun, it reminds the the bug I kept undergoing before the hotfix.

I did something before the update that seemed to make the game more stable : go to the Documents\My Games\UnrealEngine3\ShooterGame\Config directory, and remove all the file in it. Then make a steam cache verification for Dirty Bomb. It seemed to have fixed my problem until the hotfix came back.[/quote]

Gave it a shot no dice. And you said until the hotfix came back, does that mean its not working for you now?


(Eox) #5

[quote=“BK201;14342”][quote=“Eox;14339”]That’s fun, it reminds the the bug I kept undergoing before the hotfix.

I did something before the update that seemed to make the game more stable : go to the Documents\My Games\UnrealEngine3\ShooterGame\Config directory, and remove all the file in it. Then make a steam cache verification for Dirty Bomb. It seemed to have fixed my problem until the hotfix came back.[/quote]

Gave it a shot no dice. And you said until the hotfix came back, does that mean its not working for you now?

[/quote]

Ah, no sorry. My words were poorly chosen. I have no issues since the update so far, so I guess it worked for me.

I read somewhere that it would be an issue with your antivirus software, check if you find some files blocked by it, and declare some exceptions if needed. You may also check your quarantine.


(fluxay) #6

I would receive the error rather sparingly until last night. During a 2 hour session I probably had the error 5 times. Sometimes at the immediate start of a round other times at the very end of 15 minutes of stop watch.

I’ll try the Steam verification and see if that helps. Most of the searching I’ve done is stating that this error results from a Xigncode issue, so I’ll be checking my running processes as well.