Forum

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?

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

as silly as it sounds, it does sound like a good idea. gives all the noobs a chance at weapon selection instead of always being stuck with a gun that no one else wanted

I was having the same prob of not being able to set the priority (even logged in as administrator). to fix it click show process for all users then set the priority higher


***This actually was suppose to go in the lagspike thread, can someone please move it 

this worked http://www.dll-files.com/dllindex/dll-files.shtml?msvcr100

i can CONFIRM!!! This does work. I did this on my wifes cpu and shes no longer getting the .dll error. Shes been on playing for almost 45 mins with no error.

he came in again and I just let him play, no use trying to ban 754,890 accts. just said please no aim bots, guess if u ask nice he listens. he went 4-2 before leaving

-_- how dare u speak of breakout in that way -_-

we was all excites that breakout was gonna be updated :/ lol. shoulda heard us on ts. lmao. thanks for the heads up, we was wondering what was fixed