Bluescreen while playing - what is the cause?

[MadManniMan]

Hello there!

I am enjoying KF for quiet a while now but recently I started to get really serious crashes - sometimes it just shoots me back to desktop but more often I get a complete bluescreen ("dumping memory to disc...").

I HAVE overclocked my CPU but never received any stability problems before - every application runs smooth and without any problem. If Maya, InDesign, Photoshop, video processing or games like Crysis, Left 4 Dead, Shattered Horizon ... no prob at all!

Only KF still crashes...

Are there any other know causes in spite of an overclocked CPU for that?

 

[Zetsumei]

Why dont you try for a moment running your processor at stock speed and check if the same issues happen.

It might sound weird but unlike crysis etc, KF runs on a single thread and on pretty much all computers is bottlenecked by the cpu rather than the gpu as is the case for the games you used as your example.

 

[MadManniMan]

Yeah, I will do so! But it seems that the problems are "especially for" the newer maps like bedlam. To be honest: 90% of all bluescreens have been on bedlam - is that map more demanding then other ones?

But it is good to know that KF can be used nicely as a stability benchmark

Ill report when I get time to play again.

 

[anthracy]

Run prime95 for a while on all cores @ small ffts:
http://files.extremeoverclocking.com/file.php?f=103

That will let you know if its the RAM/CPU

 

[zYnthetic]

Can you copy down the error codes? These would provide more insight into what may actually be the problem.

 

[MadManniMan]

Allright...

Ive clocked my Core 2 Duo E6300 (standard clock 1.86 GHz) from 3 GHz down to 2.8 -> bluescreen. Ive clocked it down to 2.33 -> bluescreen. And Ive finally clocked it down to 1.86 GHz -> bluescreen.

Happens on all maps: Manor, Foundry, Farm, Bedlam, ...

Then I assigned Killing Floor to only one CPU core via the task manager - and there have been no bluescreens for at least 20 minutes; I couldnt test longer.

Run prime95 for a while on all cores @ small ffts:
http://files.extremeoverclocking.com/file.php?f=103

That will let you know if its the RAM/CPU

THX, but I know that program. Everything rockstable

Can you copy down the error codes? These would provide more insight into what may actually be the problem.

Its just an ordinary bluescreen

Running Vista64...

 

[MadManniMan]

Ive posted a reply this morning - has it been so bad, that it hasnt been unlocked yet?

 

[Morello]

You really need to either copy down the error reason and code, or better, provide us with minidumps, because without those there is no way to see what is causing the problem.

 

[therajuncajun]

It could just be that your system is trying to multicore render KF, and KF doesn't support multicore rendering on such an old engine. It gets confused and dumps itself. Try clocking back up to your max clock and run it on a separate core from the rest of your applications, and let us know if you get any crashes from there on.

 

[MadManniMan]

Morello,

I would really like to, but copying wont be possible as its just a bluescreen - but what is a minidump?


therajuncajun,
Seems to be possible, yeah! I will watch KF's behaviour whilst just using one dedicated core - and post it!

 

[Nekomancer]

Then copy it the old fashioned way. Pen & Paper.

 

[MadManniMan]

Ive got about 2 seconds until memory is dumped to disc:

1) Stuttering - happens often, nothing special
2) Graphics glitches - uh oh, not the ordinary stuttering...
3) Sound freezes
4) Bluescreen ... Off

No time left to react

 

[Zetsumei]

try to change the ingame audio driver.

so open killingfloor.ini

and under the sound section look for use local driver (or something like that) and switch that to false if its on true or true if its on false.

or read this thread:http://forums.tripwireinteractive.com/showthread.php?t=32443

----
So do you have a creative soundcard?

 

[vempajor]

Use a camera and shoot a pic on bluescreen.

 

[therajuncajun]

He's yet to say if his game has continued crashing since using a single core.

 

[Bio666]

lol'd

It's a BSOD, and you guys run from "pen'n'paper" and "camera" lol'd

After BSOD, the system on next restart will have an error message say "windows just recovered from a error" with error type BSOD. Expand the message, screenshot, done

And this is memory dump:
-start -> right click My computer
-Select Advance system settings in the left hand
-Tab Advanced -> on Startup and recovery, click setting
-remove check on automatically restart (if you can not see the message after reboot, it'll stay at BSOD for you to camera or pen'n'paper)
-On write debug infor, select kener memory dump (some even have option to write full memory, select it if you have enough space and nothing afraid others to see)
-Dump file often is "%SystemRoot%\MEMORY.DMP". After reboot, upload the file.
-Tadaa