jedi knight ii: crashing woes

Discussion in 'Games' started by obi wan jonobi, Sep 24, 2003.

  1. obi wan jonobi macrumors newbie

    Sep 24, 2003
    I am experiencing erratic and unpredictable crashes in Jedi Knight II. I have had trouble getting the game to run stably from first installation.

    I am using:
    Power Mac G4
    Dual 1.25 ghz
    768 mb RAM
    Radeon 9000 Pro
    Mac OS X 10.2.6

    I installed the game, and have found that it crashes at random times during gameplay. It does so in one of two ways:
    1) it simply closes up inexplicably and returns me to the desktop
    2) it crashes the computer completely: the screen freezes and I am forced to turn my computer off altogether in order to reboot.

    I have tried:
    Reinstalling the Game
    Deleting the config files from my library
    Deleting the preferences files from my library
    Reducing the graphics settings/detail greatly
    Disabling Norton Antivirus Autoprotect
    Upgrading to Mac OS X 10.2.8

    All to no avail.
    I am greatly enjoying the game thus far, and have persisted playing it despite facing 10-12 crashes a day. I do not think it would be system software related as my power mac is brand new, and Jedi Knight II was one of the first pieces of software that I installed on it.
    Any assistance in how to resolve this issue would be greatly appreciated. I have attached below copies of a few of the crash logs in case they are of any help.


    Date/Time: 2003-09-22 23:23:56 +0800
    OS Version: 10.2.6 (Build 6L60)

    Command: Jedi Knight II
    PID: 653

    Exception: EXC_BAD_INSTRUCTION (0x0002)
    Code[0]: 0x00000002Code[1]: 0x0021c80c

    Thread 0 Crashed:
    #0 0x0021c80c in R_RenderView__FP11viewParms_t
    #1 0x00212ac8 in RE_RenderScene__FPC8refdef_t
    #2 0x00273ba4 in 0x273ba4
    #3 0x00272414 in VM_DllSyscall__Fie
    #4 0x06253440 in cgi_R_RenderScene__FPC8refdef_t
    #5 0x06227694 in CG_DrawActive__F13stereoFrame_t
    #6 0x06259190 in CG_DrawActiveFrame__Fi13stereoFrame_t
    #7 0x06232310 in vmMain
    #8 0x002723a4 in VM_Call__Fie
    #9 0x00274370 in CL_CGameRendering__F13stereoFrame_t
    #10 0x0027d268 in SCR_DrawScreenField__F13stereoFrame_t
    #11 0x0027d380 in SCR_UpdateScreen__Fv
    #12 0x0027ffa0 in CL_Frame__Fif
    #13 0x001e35a0 in Com_Frame__Fv
    #14 0x002512d8 in carbonTimerCallback
    #15 0x90163230 in __CFRunLoopDoTimer
    #16 0x90148d28 in __CFRunLoopRun
    #17 0x90180f58 in CFRunLoopRunSpecific
    #18 0x969a3b70 in RunCurrentEventLoopInMode
    #19 0x969b3b00 in ReceiveNextEventCommon
    #20 0x969f2b5c in _AcquireNextEvent
    #21 0x96ab4cf8 in RunApplicationEventLoop
    #22 0x002571bc in main

    Thread 1:
    #0 0x90073c08 in mach_msg_trap
    #1 0x90005ed0 in mach_msg
    #2 0x901489f0 in __CFRunLoopRun
    #3 0x90180f58 in CFRunLoopRunSpecific
    #4 0x94d9c1c0 in _ZN10HALRunLoop9OwnThreadEPv
    #5 0x94d911b0 in _ZN9CAPThread5EntryEPS_
    #6 0x90020c88 in _pthread_body

    Thread 2:
    #0 0x900425e8 in semaphore_timedwait_signal_trap
    #1 0x9003e814 in _pthread_cond_wait
    #2 0x94d83ac4 in _ZN7CAGuard7WaitForEy
    #3 0x94d832b0 in _ZN7CAGuard9WaitUntilEy
    #4 0x94d822e0 in _ZN15XThreadedDevice8IOThreadEv
    #5 0x94d95a24 in _ZN15XThreadedDevice13IOThreadEntryEPv
    #6 0x94d911b0 in _ZN9CAPThread5EntryEPS_
    #7 0x90020c88 in _pthread_body

    PPC Thread State:
    srr0: 0x0021c80c srr1: 0x0208f030 vrsave: 0x00000000
    xer: 0x20000000 lr: 0x00212ac8 ctr: 0x00000000 mq: 0x00000000
    r0: 0x0000000f r1: 0xbfffd5a0 r2: 0x00405000 r3: 0x00000000
    r4: 0xbfffd6b4 r5: 0x006b81dc r6: 0x00000000 r7: 0x00000000
    r8: 0x00000258 r9: 0x0d2e3034 r10: 0x00000000 r11: 0x0d2e3534
    r12: 0x0000003b r13: 0x00424338 r14: 0x0042432c r15: 0x00424330
    r16: 0x00000000 r17: 0x00000000 r18: 0x24002282 r19: 0x00000000
    r20: 0x006b7b40 r21: 0x006b569c r22: 0x006b56a0 r23: 0x006b56a4
    r24: 0x006b56a8 r25: 0x006b56ac r26: 0x006b56b0 r27: 0x006b56b4
    r28: 0x006b5690 r29: 0x006b488c r30: 0xbfffd640 r31: 0x006b7bac


    Date/Time: 2003-09-22 23:18:44 +0800
    OS Version: 10.2.6 (Build 6L60)

    Command: Jedi Knight II
    PID: 648

    Exception: EXC_BAD_ACCESS (0x0001)
    Codes: KERN_INVALID_ADDRESS (0x0001) at 0x80c60d50


    Date/Time: 2003-09-22 23:08:28 +0800
    OS Version: 10.2.6 (Build 6L60)

    Command: Jedi Knight II
    PID: 643

    Exception: EXC_BAD_ACCESS (0x0001)
    Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000088


    (I have ommitted the 'threads' for the second two for want of space saving...)
  2. alphaone macrumors 6502

    Aug 12, 2003
    I don't know. It works fine for me on my dual 867 w/geforce 4 mx.

    I can venture a guess that it is having trouble rendering something and then it gets stuck in a loop. I'm no expert at reading crash logs though. A problem with the video card maybe? Do other games/things run ok?
  3. Nermal Moderator


    Staff Member

    Dec 7, 2002
    New Zealand
    Welcome to the forums, and what a descriptive first post!

    I'm having a similar problem with Neverwinter Nights. Unfortunately I haven't figured it out yet, but I'll let you know if I solve it (and if I remember to tell you!)
  4. obi wan jonobi thread starter macrumors newbie

    Sep 24, 2003
    thanks for the welcome.

    yea, i am an experienced wintel user who just made the switch, this is my first mac. im used to having to troubleshoot pc's,etc which is why i provided the detailed run down :)

    unfortunately ive had a run of bad luck with my mac- the power source or motherboard blew within a week of purchase (they weren't sure which), and now im having these instability issues :(

    as you suggested, i worry that it could be hardware related since everything else seems to work fine. i particularly worry over possible damage when the mboard/ power source blew. since its the first game/piece of 3d intensive software ive run i couldn't be sure though. i dont suppose anybody knows if there is any 3d card test available for mac os? something that could put my radeon card through its paces just to see if its working properly? id rather not have to wait till i get another hundred bucks together to test another game out.

    i will probably try reformatting my hd and reinstalling everything if i cant solve it within a week or two. but i just cringe at the thought of already having to deal with a potential reformat so early in the piece. *sigh* oh well, i guess all computers share common weaknesses :p
  5. obi wan jonobi thread starter macrumors newbie

    Sep 24, 2003
    just an update in case anybody else experiences the same problems I was having.

    I zeroed my harddrive and reinstalled everything from scratch- I tried jkii installed on os x 10.2.3 straight out, no other programs. the crashes persisted.

    My local applecentre then tried replacing both the RAM and the videocard. Since then the crashes have stopped!!

    I am not sure which of the two was the exact problem, but i guess the lesson is never rule out hardware issues causing persistent crashes (i had :)

    hope this might reduce the stress on anybody out there befuddled by similar problems.

  6. K.B. macrumors member


    Jul 8, 2003
    East Coast
    so you haven't had this kind of crash since the change out of your RAM and the graphics card??

    I checked my RAM with an assortment of programs and methods (shut down, take out one DIMM, restart, try run program.... repeat) and have checked my graphics card (RADEON 8500) every way I can and reloaded the drivers plenty of times.

    This first started happening to me in RTC Wolfenstein but then I noticed a Finder crash report with the infamous
    kern_invalid_address" as the problem.

    I tried another game and it crashed right off with the same primary reasons.

    With Wolfenstein I could go back to earlier saved games and play from there and it was fine but when I tried to advance from where I last left off (at a cutscene before the next mission) it crashes right after the cutscene.

    I've run every possible mainenence and premissions fix I can find, as I said I've checked the RAM---- I'm at a loss and would hate to have to replace the graphics card on a whim.

    Any and all suggestions or help on this would be appreciated!!!
  7. obi wan jonobi thread starter macrumors newbie

    Sep 24, 2003
    nup, crashes have gone (touchwood). I mean there is the occasional crash maybe once a week, but nothing that one would not be prepared to ignore. but crashes that were affecting my other programs stopped as well...

    Hmmm...ok, perhaps some more detail on my own experience might shed some light on your troubles. I had just purchased my powermac less than a month before this problem occurred. Upon installing an extra 512 ram, either my power supply or motherboard blew. I then had the motherboard replaced, and new RAM dimms put in.

    Everything seemed ok, except then I tried JKii and suffered all of that frustration. However, my problems with jkii were not isolated- they soon crept in to affect all of my other programs with random crashes. Because of this i took my mac back to my applecentre for examination.

    Point 1) It is very difficult to actually detect a defect in RAM. Often it might be that most of the 'sectors' are ok, except one and you only find this out as the RAM is filled up. This explains why games,etc might bring this problem to the fore- very memory intensive apps.

    Point 2) The same could be said equally about a video card. Especially since most programs do not use the full features of your graphics card (3d,etc).

    Do you have troubles with any other programs? If these problems are affecting you as persistently as they did I, and also across other programs/games, then I would definitely recommend testing the system out with replaced video card and ram parts.

    problem is...if it is a hardware related prob- then it cold be any one of a number of parts causing your trouble (perhaps m/board or cpu?). however, with these particular problems/crashes most likely ram/video card.

    Maybe try talking to your applecentre about testing with replacement parts with no obligaton to purchase? or better yet under warranty?
  8. K.B. macrumors member


    Jul 8, 2003
    East Coast
    No warrantee coverage.

    I took all the ram out of the machine and changed out my card, the 8500, for the original card the Rage 128.

    I put one DIMM of the memory in and booted up and tried the applications that were crashing and they all crashed with each piece of memory identically as they did with them all installed.

    I did a clean OS install and the problem still occurs.

    I've asked around all over the place on this error and no one has yet to come up with an explanation or suggestions that correct it.

    This is really annoying

Share This Page