![]() |
![]() |
|
#1
|
|||
|
|||
|
No fixes worked for this one, not even deleting killingfloor.ini and killingfloor.exe then redownloading:
Build UT2004_Build_[2004-11-11_10.48] OS: Windows NT 6.1 (Build: 7601) CPU: GenuineIntel PentiumPro-class processor @ 2262 MHz with 3893MB RAM Video: Intel(R) HD Graphics General protection fault! History: FOpenGLRenderInterface::SetMaterial <- USkeletalMeshInstance::Render <- FDynamicActor::Render <- RenderLevel <- KF-Deck16][-fix.myLevel <- FLevelSceneNode::Render <- FPlayerSceneNode::Render <- UGameEngine: raw <- UWindowsViewport::Repaint <- UWindowsClient::Tick <- ClientTick <- UGameEngine::Tick <- Level Deck16 <- UpdateWorld <- MainLoop <- FMallocWindows::Free <- FMallocWindows::Realloc <- 4C576C61 0 FArray <- FArray::Realloc <- 0*2 <- FMallocWindows::FreeHappens during multiplayer. |
|
#2
|
|||
|
|||
|
It may sound weird, but I have exactly same problem, mostly happens at RE1 Mansion Story though
|
|
#3
|
||||
|
||||
|
Quote:
|
|
#4
|
|||
|
|||
|
Yeah, Direct3D doesn't even let the game start.
|
|
#5
|
|||
|
|||
|
I have a similar problem. Although it only occurs when playing on a fun server with perks from lvl 6 to lvl 25, Doom mobs and other modified stuff.
|
|
#6
|
|||
|
|||
|
people have been getting alot of critical errors on my server.
**Edit A window doesn't even pop up saying critical error the game just crashes and pops up a windows error insted Last edited by dangercake; 06-01-2012 at 11:27 PM. |
|
#7
|
|||
|
|||
|
Quote:
Code:
Build UT2004_Build_[2004-11-11_10.48] OS: Windows NT 6.1 (Build: 7601) CPU: GenuineIntel PentiumPro-class processor @ 4000 MHz with 4095MB RAM Video: NVIDIA GeForce GTX 460 (9610) General protection fault! History: KBodyGetActor <- BodyGetDoubleRate <- KBuildPartitions <- KWorldStepSafeTime <- KTickLevelKarma <- TickAllActors <- ULevel::Tick <- (NetMode=3) <- TickLevel <- UGameEngine::Tick <- Level KF-Canville <- UpdateWorld <- MainLoop <- FMallocWindows::Free <- FMallocWindows::Realloc <- 4C576C61 0 FArray <- FArray::Realloc <- 0*2 <- FMallocWindows::Free |
|
#8
|
|||
|
|||
|
did this just start happening after the update? looks like a specimen problem, are you running custom zeds?
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|