Announcement

Collapse
No announcement yet.

My First 1.4 CTD and how-to Analyze it

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    Re: My First 1.4 CTD and how-to Analyze it

    is bf2 written in C++ because i think files with .cpp extension is C++

    Comment


    • #32
      Re: My First 1.4 CTD and how-to Analyze it

      I went for several months without playing BF2. I just started playing again last week with the 1.4 update. I've experienced numerous freezes, usually within the first 15 minutes of gameplay. I've had 3 CTD's, the latest of which yielding the following dump info:
      Comment: 'Battlefield2 MiniDump. Address: 006A2F2E (In Windbg type: .ecxr)
      ASSERT INFORMATION:
      [...]
      [EOF]'
      Windows XP Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
      Product: WinNt, suite: SingleUserTS
      Debug session time: Wed Oct 11 13:59:16.000 2006 (GMT-5)
      System Uptime: not available
      Process Uptime: 0 days 0:02:09.000
      Symbol search path is: *** Invalid ***
      ************************************************** **************************
      * Symbol loading may be unreliable without a symbol search path. *
      * Use .symfix to have the debugger choose a symbol path. *
      * After setting your symbol path, use .reload to refresh symbol locations. *
      ************************************************** **************************
      Executable search path is:
      .................................................. ..........................................
      This dump file has an exception of interest stored in it.
      The stored exception information can be accessed via .ecxr.
      (868.47c): Access violation - code c0000005 (first/second chance not available)
      eax=00000000 ebx=00000000 ecx=0012f5e4 edx=0012f64b esi=000005e0 edi=00000000
      eip=7c90eb94 esp=0012f108 ebp=0012f16c iopl=0 nv up ei pl zr na pe nc
      cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00200246
      *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
      ntdll!KiFastSystemCallRet:
      7c90eb94 c3 ret
      BF2 is unplayable now, so far as I'm concerned. Bummer. It was a great game.

      Playing BF2 1.4 online at 1600x1200x32@85Hz
      Special Forces, Armored Fury, Euro Force

      Intel Pentium 4 640 HT 3.20 GHz
      Windows XP Pro SP2
      2GB Dual Channel DDR2 SDRAM at 533MHz (2x512M)
      256MB PCI Express x16 ATI Radeon X850 XT PE
      Catalyst 6.9 drivers for Windows XP
      DirectX 9.0c
      ViewSonic P95f+ 19 inch Ultrabrite CRT Monitor
      Sound Blaster Audigy2 ZS
      Creative I-Trigue 2.1 3300 Speakers
      Logitech MX 518 Optical Mouse
      Saitek Gamers Keyboard USB
      Thrustmaster Top Gun Fox 2 Pro USB joystick

      For what it's worth, this CTD happened immediately after playing about 40 minutes of Ghost Town, while the game was loading resources for the next map (map unknown):
      Comment: 'Battlefield2 MiniDump. Address: 04965D69 (In Windbg type: .ecxr)
      ASSERT INFORMATION:
      [...]
      [EOF]'
      Windows XP Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
      Product: WinNt, suite: SingleUserTS
      Debug session time: Thu Oct 12 11:00:49.000 2006 (GMT-5)
      System Uptime: not available
      Process Uptime: 0 days 0:54:53.000
      Symbol search path is: *** Invalid ***
      ************************************************** **************************
      * Symbol loading may be unreliable without a symbol search path. *
      * Use .symfix to have the debugger choose a symbol path. *
      * After setting your symbol path, use .reload to refresh symbol locations. *
      ************************************************** **************************
      Executable search path is:
      .................................................. ............................................
      This dump file has an exception of interest stored in it.
      The stored exception information can be accessed via .ecxr.
      (b3c.cac): Access violation - code c0000005 (first/second chance not available)
      eax=00000000 ebx=00000000 ecx=2418880c edx=00000000 esi=00000a78 edi=00000000
      eip=7c90eb94 esp=0012ead8 ebp=0012eb3c iopl=0 nv up ei pl zr na pe nc
      cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00200246
      *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
      ntdll!KiFastSystemCallRet:
      7c90eb94 c3 ret

      Comment


      • #33
        Re: My First 1.4 CTD and how-to Analyze it

        Well I played Karkland for 2 hours yesterday with no crashes but today I was on Dalian plant for about 5 minutes then CTD. I hope EA checks these forums.

        Toshiba Satellite Laptop
        Intel Core Duo T2400 @ 1.83ghz
        1GB 533mhz DDR2
        Nvidia Go 7300 256mb

        BF2 @ 800x600 all settings at medium and getting around 50-60fps

        Comment


        • #34
          Re: My First 1.4 CTD and how-to Analyze it

          fwiw, i have up'd my settings from 800x600 to 1024x768, and i lowered textures to low, the game is cleaner and so far only 2 CTDs in two days or about 8+ hrs of playing.

          Comment


          • #35
            Re: My First 1.4 CTD and how-to Analyze it

            this is for a ctd at startup-
            d:\Aphrodite\BF2_1.4\Code\BF2\RendDX9\RendDX9Inin. cpp(468) : Error: RendDX9: Failed to create d3d device. Unknown cause. Invalid call [EOF]'

            I had this same problem a few months ago- I would click BF2, there would be a black screen as if the program was starting normally, then the black screen would go away and id be looking at my desktop again. I took a break from bf2 for a few months after i could not once start the program, then I decided to completely uninstall and reinstall bf2 once 1.4 came out. It worked fine after this, until just today, when I started having this problem again. My video card is almost new, my computer is pretty good, I have just over a gig of ram, and bf2 ran perfectly before this. I suppose this is something wrong with DirectX, but I reinstalled DirectX and ran dxdiag-still crashes to desktop. I dont want to reinstall the whole program just to experience this problem again. This is also the first and only problem I've had with 1.4.


            EDIT: Yes it was directX! For some reason my directX was screwed up, and when I upgraded it to the latest directX (9.0c i think) , for some reason it didnt work. But when I installed the previous version (9.0b) and restarted, it started up again perfectly! Hope this helps.

            Comment


            • #36
              Re: My First 1.4 CTD and how-to Analyze it

              Originally posted by rsgx

              EDIT: Yes it was directX! For some reason my directX was screwed up, and when I upgraded it to the latest directX (9.0c i think) , for some reason it didnt work. But when I installed the previous version (9.0b) and restarted, it started up again perfectly! Hope this helps.
              How did you downgrade DirectX??? My problems also started after installing 9.0c.

              Comment


              • #37
                Re: My First 1.4 CTD and how-to Analyze it

                I am desolate, i just spent nearly two grand on an Alienware rig, this thing is a monster, 2 gig RAM, 2x Intel 2.16 dual core processor, 2 x GeForce 7900GT, 250 gig hard drive, Nvidia motherboard, this thing is brand new, and in theory should eat alive any games graphics requirements out there today.

                However, BF2 crashed to desktop after about 5 minutes of game time, and this happens every time, even with graphic options scaled down!!!!!!!

                I am horrified, and emotionally unstable as a result of this travesty, someone please help.

                I have latest Nvidia drivers, 1.4 full patch, it used to run fine on my old machine (at low graphic settings) and on this new machine, which i have forked out serious cash for only a few weeks ago, the damn thing is crashing every time!!!

                Someone please please help!!!!!!!

                Comment


                • #38
                  Re: My First 1.4 CTD and how-to Analyze it

                  heh lol

                  Comment


                  • #39
                    Re: My First 1.4 CTD and how-to Analyze it

                    I can recreate the problem in the original post exactly, by starting off as USA, playing for a while, then when dying, succesfully switching to MEC/PLA. The second you switch teams, it CTDs. It even happens if the server autobalances you, which is pretty annoying. It never used to happen, that's what I don't get.

                    Comment


                    • #40
                      Re: My First 1.4 CTD and how-to Analyze it

                      1.41 has yet to show me any errors.

                      Which means that I haven't got any major errors other than a few CTD's in 1.41

                      Comment


                      • #41
                        Re: My First 1.4 CTD and how-to Analyze it

                        Mine CTDs at 14%, what the hell is wrong?

                        Comment


                        • #42
                          Re: My First 1.4 CTD and how-to Analyze it

                          Loading Dump File [D:\Documents and Settings\Simon\My Documents\Battlefield 2\dmp\bf2_v1.1.2965-797.0_2007-02-13_22.20.59.dmp]
                          User Mini Dump File: Only registers, stack and portions of memory are available

                          Comment: 'Battlefield2 MiniDump. Address: 03A14371 (In Windbg type: .ecxr)
                          ASSERT INFORMATION:
                          [...]
                          D:\Aphrodite\BF2_1.4\Code\BF2\Geom\BundledMeshTemp late.cpp(269): Error: Geom: Cannot load BundledMesh Objects/weapons/handheld/eurif_fnp90/Meshes/eurif_fnp90.bundledMesh Please make sure it exists!
                          [EOF]'

                          The game is unplayable. this is the end for me.

                          Comment

                          Working...
                          X