"General Protection Fault" Error help please!

[Mythelion]

http://filesmelt.com/Imagehosting/pics/2ce17f8c8fc63f046869903740dc0f5b.png

So, my friend recently bought Killing Floor for me, so I started it, it worked, I changed my graphics, exited ( It said I had to exit for change ) And it came up with an error ( See picture above ) please help me :(

System Specs:
Nvidia 8800 GTX
3GB RAM
Enough Disk Space
Windows vista 32-bit


I tried:
Deleting game cache files and redownload it.
Resetting steam.
Turning off Firewall.
Reseting PC.

[Mr. Darkness]

I had this exact same problem and all it took was messing with the Killing Floor.ini file a bit.


What you need to do is to edit the killingfloor.ini file which can be found in:

c:\....\steam\steamapps\common\killingfloor\system

Once you are in the killingfloor.ini file, search for a line that says [Engine.Engine]

Then need to edit it by just copy and pasting the following. See below:

;RenderDevice=PixoDrv.PixoRenderDevice
RenderDevice=D3D9Drv.D3D9RenderDevice
;RenderDevice=Engine.NullRenderDevice
;RenderDevice=OpenGLDrv.OpenGLRenderDevice
;RenderDevice=PixoDrv.PixoRenderDevice

If your files does not look like the same above, then you need to change it. Once done, save it, then close all windows down. Relaunch your game and presto, the game loads.

[Mythelion]

Will try, thanks.

[cairenn]

I also get that since this evening, never had it before.

Build KillingFloor_Build_[2009-02-09_10.82]

OS: Windows NT 6.1 (Build: 7100)
CPU: GenuineIntel PentiumPro-class processor @ 2401 MHz with 2046MB RAM
Video: NVIDIA GeForce 8800 GTX (8585)

General protection fault!

History: ResetDevice <- UD3D9RenderDevice::SetRes <- WM_SIZE <- UWindowsViewport::ViewportWndProc <- WWindow::StaticProc <- UWindowsViewport::ViewportWndProc <- WWindow::StaticProc <- MessagePump <- MainLoop <- FMallocWindows::Free <- FMallocWindows::Realloc <- 4C576C61 0 FArray <- FArray::Realloc <- 0*2 <- FMallocWindows::Free



That didn't work, Mr Darkness, unfortunately. :(

[Mythelion]

Reinstalled the game, Removed all steam files related with Killing floor ( Killing floor folder on Steamapps/Common ) and it worked perfect for me.

[Thegoodguy]

Is anyone else still getting this error? I've been playing lans with my friends, and I'll host. The majority of our games crash to the desktop with this error, probably around 75% of them. Sometimes on our last wave too, and it's very frustrating.

Any resolutions yet? I'm a bit weary about editing the .ini file. Thanks!

[CoDkiller]

Is anyone else still getting this error? I've been playing lans with my friends, and I'll host. The majority of our games crash to the desktop with this error, probably around 75% of them. Sometimes on our last wave too, and it's very frustrating.

Any resolutions yet? I'm a bit weary about editing the .ini file. Thanks!

Guys this is the fourth thread about the same problem. I have mailed devs in three ocassion already and didn't get any reply back so I guess they just decided to neglect this. It is sad because they were usually supportive but regarding this problem they just keep ignoring us so we're pretty screwed.

Please check these threads:

http://forums.steampowered.com/forums/showthread.php?t=872351

http://forums.steampowered.com/forums/showthread.php?t=873599

http://forums.steampowered.com/forums/showthread.php?t=879360

All threads are about the same problem, all of them reported and sent by mail to at least three tripwire staff and to date no word at all spoken from them about this issue which is related to the second patch.

[hzt23]

yea I mean I just bought it and I feel like someone who has just burned 18€ you see I have INSTALLED THIS GAME 3 TIMES AND IT HASN'T CHANGED A BIT and it worked on that free weekend for killing floor so I bet this is their problem:o

[Yoshiro]

Every general protection fault is different, and if you don't post it I can't begin to help you.

Secondly most of them are caused by a corrupt file/bad download from a steam content server. Best thing to do is to delete the system folder, change the steam download server, and verify cache in steam.

[hzt23]

I had this exact same problem and all it took was messing with the Killing Floor.ini file a bit.


What you need to do is to edit the killingfloor.ini file which can be found in:

c:\....\steam\steamapps\common\killingfloor\system

Once you are in the killingfloor.ini file, search for a line that says [Engine.Engine]

Then need to edit it by just copy and pasting the following. See below:

;RenderDevice=PixoDrv.PixoRenderDevice
RenderDevice=D3D9Drv.D3D9RenderDevice
;RenderDevice=Engine.NullRenderDevice
;RenderDevice=OpenGLDrv.OpenGLRenderDevice
;RenderDevice=PixoDrv.PixoRenderDevice

If your files does not look like the same above, then you need to change it. Once done, save it, then close all windows down. Relaunch your game and presto, the game loads.

Thanks so much dude

[MaltManMike]

Yoshiro, any tips on this one?

Build UT2004_Build_[2004-11-11_10.48]

OS: Windows NT 6.1 (Build: 7600)
CPU: GenuineIntel PentiumPro-class processor @ 3348 MHz with 4095MB RAM
Video: ATI Radeon HD 4800 Series (24)

General protection fault!

History: SkeletalMeshGet <- USpriteEmitter::UpdateParticles <- AEmitter::Tick <- TickAllActors <- ULevel::Tick <- (NetMode=2) <- TickLevel <- UGameEngine::Tick <- Level Wyre Forest <- UpdateWorld <- MainLoop <- FMallocWindows::Free <- FMallocWindows::Realloc <- 4C576C61 0 FArray <- FArray::Realloc <- 0*2 <- FMallocWindows::Free

I've crashed twice in the last week or so while hosting a friends game. Only saved one of the error reports though. I was playing firebug if it makes a difference. 1680x1050.

[Frydazz]

I had this exact same problem and all it took was messing with the Killing Floor.ini file a bit.


What you need to do is to edit the killingfloor.ini file which can be found in:

c:\....\steam\steamapps\common\killingfloor\system

Once you are in the killingfloor.ini file, search for a line that says [Engine.Engine]

Then need to edit it by just copy and pasting the following. See below:

;RenderDevice=PixoDrv.PixoRenderDevice
RenderDevice=D3D9Drv.D3D9RenderDevice
;RenderDevice=Engine.NullRenderDevice
;RenderDevice=OpenGLDrv.OpenGLRenderDevice
;RenderDevice=PixoDrv.PixoRenderDevice

If your files does not look like the same above, then you need to change it. Once done, save it, then close all windows down. Relaunch your game and presto, the game loads.

This is working solution of "General protection fault!" problem...
Thank you so much.

[wodniloc]

Tried pasting that in but to no avail.

This is what I'm getting:


Build UT2004_Build_[2004-11-11_10.48]

OS: Windows NT 6.1 (Build: 7601)
CPU: GenuineIntel PentiumPro-class processor @ 2718 MHz with 4095MB RAM
Video: NVIDIA GeForce GTX 560 Ti (8538)

General protection fault!

History: UD3D9RenderDevice::SetRes <- UWindowsViewport::TryRenderDevice <- UWindowsViewport::OpenWindow <- UGameEngine::Init <- InitEngine <- FMallocWindows::Free <- FMallocWindows::Realloc <- 3D93CE85 0 FArray <- FArray::Realloc <- 0*2 <- FMallocWindows::Free <- FMallocWindows::Free

[VinnyI82]

I had this exact same problem and all it took was messing with the Killing Floor.ini file a bit.


What you need to do is to edit the killingfloor.ini file which can be found in:

c:\....\steam\steamapps\common\killingfloor\system

Once you are in the killingfloor.ini file, search for a line that says [Engine.Engine]

Then need to edit it by just copy and pasting the following. See below:

;RenderDevice=PixoDrv.PixoRenderDevice
RenderDevice=D3D9Drv.D3D9RenderDevice
;RenderDevice=Engine.NullRenderDevice
;RenderDevice=OpenGLDrv.OpenGLRenderDevice
;RenderDevice=PixoDrv.PixoRenderDevice

If your files does not look like the same above, then you need to change it. Once done, save it, then close all windows down. Relaunch your game and presto, the game loads.

This has worked for me. I just purchased the game today. Played it once with my friends for about an hour and then I had this problem. Seriously, second time trying to play the game, and I reinstalled it two times, and this is allowed to happen? Come on STEAM lets be a bit more strict about shoddy a$$ programs being allowed here.

[Icedfate]

I had this exact same problem and all it took was messing with the Killing Floor.ini file a bit.


What you need to do is to edit the killingfloor.ini file which can be found in:

c:\....\steam\steamapps\common\killingfloor\system

Once you are in the killingfloor.ini file, search for a line that says [Engine.Engine]

Then need to edit it by just copy and pasting the following. See below:

;RenderDevice=PixoDrv.PixoRenderDevice
RenderDevice=D3D9Drv.D3D9RenderDevice
;RenderDevice=Engine.NullRenderDevice
;RenderDevice=OpenGLDrv.OpenGLRenderDevice
;RenderDevice=PixoDrv.PixoRenderDevice

If your files does not look like the same above, then you need to change it. Once done, save it, then close all windows down. Relaunch your game and presto, the game loads.

this is not working for me. this is bullcrap..I have a good computer and I keep giving these people money for games and can't play them.

first its mass effect now this



just for added info this is the error message





OS: Windows XP 5.1 (Build: 2600)
CPU: AuthenticAMD Unknown processor @ 3217 MHz with 2047MB RAM
Video: AMD Radeon HD 6700 Series (7246)

Error setting display mode: CreateDevice failed (D3DERR_INVALIDCALL). Please delete your KillingFloor.ini file if this error prevents you from starting the game.

History: UD3D9RenderDevice::UnSetRes <- CreateDevice <- UD3D9RenderDevice::SetRes <- UWindowsViewport::TryRenderDevice <- UWindowsViewport::OpenWindow <- UGameEngine::Init <- InitEngine <- FMallocWindows::Free <- FMallocWindows::Free

[Icedfate]

this is really odd but when I was trying to make the game work. I alt tabbed back to my internet browser while the splash screen was up and when the game loaded up, it launched it in "windowed mode" I don't know how I made it launch in windowed mode but it works in windowed mode but not in full screen. when I try to make it full screen from windowed mode, it crashes again but its fully playable in windowed mode. however..there is no option to make it launch in windowed mode all the time. I suspect it launched it in windowed mode because I alt tabbed out of it. this worked for me when all the other fixes did not.