WARNING - KILLING FLOOR POTENTIALLY UNSTABLE

[SerFox]

Okay you may think I am over-exaggerating here but I'm not. My heart is still literally pounding. I decided to boot up Killing Floor and play some, and I get into the Bioticslab map, and I've noticed a glitch with some of the textures being loaded incorrectly and graphical glitches, tearing and all sorts of funky stuff.

Then my Macbook Pro all-out bricks. Screen flashes white for a millisecond (Which is what you see if you hard reset it) but remains on, screen dead. I hard reset it, wait a few seconds and turn it back on. Fails to boot. I thought it was dead.

Next step for me in these situations is a battery pull+SMC reset. Thankfully this worked, and I managed to get back into the computer and the screen appears to be fine. Will be running a couple of OpenGL games in a few to see if the GFX chipset is still alright.


Upon re-entering the OS, this is the error log I got (Sent to Apple):

Interval Since Last Panic Report: 4243320 sec
Panics Since Last Report: 1
Anonymous UUID: FFF54435-585F-4E6A-9F90-DCC06416C892

Thu May 20 23:20:29 2010
panic(cpu 0 caller 0x00C9A6A4): NVRM[0]: Read Error 0x00009410: BAR0 0xd4000000 0x62b7d000 0x096380c1 D0 P3/4
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x56f8e4c8 : 0x12b4c6 (0x45f91c 0x56f8e4fc 0x13355c 0x0)
0x56f8e518 : 0xc9a6a4 (0xecae80 0xecae80 0xe8f6d4 0x0)
0x56f8e578 : 0xf53df0 (0x7c6c404 0x7981004 0x9410 0xcd6d06)
0x56f8e5b8 : 0xf7e57d (0x7981004 0x9410 0x5c00 0x9)
0x56f8e5f8 : 0xd9c14f (0x7981004 0x6fb0004 0x0 0x0)
0x56f8e618 : 0xcdc3f1 (0x6fb0004 0x56f8e6a4 0x0 0x0)
0x56f8e658 : 0xeefdb8 (0x7981004 0x3d0900 0x56f8e6a4 0x0)
0x56f8e6d8 : 0xf26420 (0x7981004 0x7cc6004 0x3 0x3)
0x56f8e798 : 0xce6736 (0x7981004 0x7ccac04 0x0 0xf7ad004)
0x56f8e818 : 0xca7c49 (0xc1d0004f 0xbeef0003 0xcafec76a 0x10da8480)
0x56f8e858 : 0xc98804 (0x56f8e9e8 0x6 0x0 0x0)
0x56f8e9b8 : 0xc8a36c (0x0 0x600d600d 0x7058 0x56f8e9e8)
0x56f8ea78 : 0x1187917 (0xc1d0004f 0xbeef0003 0xcafec76a 0x10da8480)
0x56f8eab8 : 0x1187aee (0x42d6c000 0x10da8480 0x90dfe000 0x0)
0x56f8eaf8 : 0x11a76df (0x42d6c000 0xdeea000 0x56f8eb34 0x0)
0x56f8eb28 : 0x4425e5 (0x4308f000 0x56f8ed9c 0x56f8ec54 0x0)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(5.4.8)@0x1134000->0x11cbfff
dependency: com.apple.NVDAResman(5.4.8)@0xc81000
dependency: com.apple.iokit.IONDRVSupport(1.7.3)@0xc73000
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x601000
dependency: com.apple.iokit.IOGraphicsFamily(1.7.3)@0x78e000
com.apple.nvidia.nv50hal(5.4.8)@0xee0000->0x1133fff
dependency: com.apple.NVDAResman(5.4.8)@0xc81000
com.apple.NVDAResman(5.4.8)@0xc81000->0xedffff
dependency: com.apple.iokit.IONDRVSupport(1.7.3)@0xc73000
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x601000
dependency: com.apple.iokit.IOGraphicsFamily(1.7.3)@0x78e000

BSD process name corresponding to current thread: Killing Floor

Mac OS version:
9L31a

Kernel version:
Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386
System model name: MacBookPro5,1 (Mac-F42D86C8)

System uptime in nanoseconds: 83823383288907
unloaded kexts:
com.apple.driver.InternalModemSupport 2.4.0 - last unloaded 104774519806
loaded kexts:
com.Logitech.Control Center.HID Driver 3.1.0
com.paceap.kext.pacesupport.leopard 5.7
com.Cycling74.driver.Soundflower 1.5.1
com.manycamllc.driver.ManyCamDriver 0.0.9
com.apple.filesystems.cddafs 2.3.0 - last loaded 66746384138487
com.apple.driver.AppleHWSensor 1.9d0
com.apple.filesystems.autofs 2.0.2
com.apple.driver.IOBluetoothBNEPDriver 2.1.9f10
com.apple.driver.AppleUpstreamUserClient 2.7.5
com.apple.driver.AppleMikeyHIDDriver


This seems to indicate a rather hefty kernel panic/crash.

Needless to say I am not opening Killing Floor ever again until this is fully looked into. I trust the Tripwire guys to take this seriously, as this could be potentially fatal to someone's system if I had to do an SMC reset to get this up and running again.


Thanks. I'm going to post this on the TW forums now...

...and pour myself a stiff drink... :(

[SerFox]

Sorry for double post but this'll be more noticeable than an edit.

Gfx card seems fine. Altitude and Urban Terror working fine.

Reposted this on the Tripwire forums.


Keep up with the progress here: http://forums.tripwireinteractive.com/forumdisplay.php?f=94

[Yoshiro]

I've replied to your thread in the tripwire forum.

[gitano]

Hey SerFox,


Thanks. I'm going to post this on the TW forums now...


Yep, thats always a good idea, as it is easier for the TWI guys to keep track of potential bugs/ problems. And to get one quick help from experienced KF users.


Kernel version:
Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386
System model name: MacBookPro5,1 (Mac-F42D86C8)


So, i bet You're running 10.5.x on Your MacbookPro5,1? Heard quite some issues from Leopard users with this game now, maybe this is related.

Other than that, i can only think of some hardware issue, especially overheating. Do the fans spin up/ whats the temps on your hardware (GPU/CPU/HDD) when running the game?

greetz,
gitano

[SerFox]

Hey SerFox,



Yep, thats always a good idea, as it is easier for the TWI guys to keep track of potential bugs/ problems. And to get one quick help from experienced KF users.



So, i bet You're running 10.5.x on Your MacbookPro5,1? Heard quite some issues from Leopard users with this game now, maybe this is related.

Other than that, i can only think of some hardware issue, especially overheating. Do the fans spin up/ whats the temps on your hardware (GPU/CPU/HDD) when running the game?

greetz,
gitano

Yes I'm running 10.5.8

Fans span up a bit, but I also run a cooling fan pad underneath, and I've ran more intensive games over emulation/bootcamp without issue. I also ran KF on my Windows partition absolutely fine.

And I'm sorry but unless you guys promise to buy me a new computer if this one burns out, I'm not launching Killing Floor until this is resolved, and I have no other way of finding out the temp info.

[Zetsumei]

What kind of coolingpad do you run? As third party active cooling pads can actually have a negative effect on cooling performance of a lappy.

Different games stress different sections, and from your story so far it seemed like overheating. Can you tell in a bit more detail about what sort of visuals you saw before it went out.

[SerFox]

What kind of coolingpad do you run? As third party active cooling pads can actually have a negative effect on cooling performance of a lappy.

Different games stress different sections, and from your story so far it seemed like overheating. Can you tell in a bit more detail about what sort of visuals you saw before it went out.

Its a standard sit on top plastic three fan affair, and trust me this does a good job. The fans do not have to come on nearly as much, and after doing something intensive, cooldown is 60% faster.

I have done some research, and the Biotics Lab glitch is well known, I didn't know that was a documented bug. So basically, my screen went off, not black, off.

[stone man]

I really doubt this is related to Killing Floor. There is no way "unstable" userland software can break your hardware. In order to experience hardware trouble, either a) your OS must have a very serious bug, or b) there must have already been a hardware problem that just got bad enough for you to notice it. In this case, it sounds like your video card is either defective or overheated. The Nvidia cards used in Macs for several years had a very high defect rate (though people often didn't notice it at first and would wind up blaming it on whatever software they were running when it first got exposed), so it's quite likely you have one of those.

[Yoshiro]

Qouting my reply on our forums:

Our mac guy looked at the issue and this is what he said

"If it's a kernel panic, it's not our fault (this is the equivalent of a Blue Screen of Death on Windows)...we can crash, but if we crash the whole system, it's not our bug. Especially if it was so traumatic that the system wouldn't boot afterwards.

It sort of sounds like he might have gotten a MacBook with one of the defective ("bad bumps") Nvidia chips in it. That's the model that allegedly had them (first generation of the "unibody" macbook pros: model id "MacBook5,1"). If the chip was overheating, I wouldn't be surprised if it refused to boot for a few minutes afterwards.

It also might just be bad luck; that's the exact model I did the Killing Floor port on, though."

[d10sfan]

I believe I have that model or a similar one and my graphics card overheated once. If it fails completely, Apple should repair it free of charge, whether or not you are under warranty, as its a defective card. They repaired it for free when my card died.

[SerFox]

Right, I'm gonna get on the phone with Apple. I've had this laptop for a while, and I think my 9400 is defective, I get black flicks every few minutes but I never use it. But if both cards are faulty... fml.. x.x

[azrael_666]

i haven't had a problem THAT bad with killing floor. my problem is that when i'm done with a level and the next in the playlist starts loading, it freezes. i have to force quit EVERYTIME.

[Tararabbit11127]

Are you playing on a laptop? It looks like a Kernel panic or something. However if you are on a laptop and having cooling issues, high temps will cause damage to your hardware over time, which can also result in errors. I would suggest using a fan control program to monitor temps.