AAO25.com

Assist => Feedback & Suggestions => Bug Reports => Topic started by: Rapture on Wednesday, July 31, 2013, 22:44:25 PM

Title: critical error
Post by: Rapture on Wednesday, July 31, 2013, 22:44:25 PM
this just starting happening about 2 hours ago. I keep getting criticals whenever i try to join a server. I have tried probably 20 different times and even deleted everything and did a clean install and im still getting them when loding into a server. This is what it says


 Build AmericasArmy_Build_[2004-06-01_02.01.01]

OS: Windows NT 6.1 (Build: 7601)
CPU: GenuineIntel Unknown processor @ 3467 MHz with 2047MB RAM
Video: ATI Radeon HD 2400 Series (1129)

General protection fault!

History: UD3DRenderDevice::Unlock <- UViewport::Unlock <- UWindowsViewport::Unlock <- UGameEngine::Draw <- UWindowsViewport::Repaint <- UWindowsClient::Tick <- ClientTick <- UGameEngine::Tick <- Level Urban Assault <- UpdateWorld <- MainLoop <- FMallocWindows::Free <- FMallocWindows::Realloc <- 706D7564 0 FArray <- FArray::Realloc <- 0*2 <- FMallocWindows::Free

Title: Re: critical error
Post by: Rapture on Wednesday, July 31, 2013, 23:48:15 PM
n/m it seems it was a faulty ethernet wire. changed it to anew one and it works. somone in ts was telling me it was saying no packet flow. new cable and boom it works
Title: Re: critical error
Post by: Spanky on Thursday, August 01, 2013, 00:26:55 AM
That shouldn't be the issue. You'll time out and get kicked or just lag with a bad connection. I'd be surprised if this really does fix it.
Title: Re: critical error
Post by: Rapture on Thursday, August 01, 2013, 01:02:19 AM
i know i thought the same thing, usually a critical has something to do with a component in the cpu or the program itself. but i changed the cord after receiving this every time i joined a server for a few hours. And BAM it worked i was like wtf?
Title: Re: critical error
Post by: Rapture on Friday, August 02, 2013, 02:02:51 AM
while the cable did help me get back into a server right away I think I found the real problem. the new ts3 client that updated. It appears with ts3 up I get this error. but if I join a server first, then start ts then I don't have the prob