Permanent Crash To Desktop

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • nonexistentuser

    #1

    Permanent Crash To Desktop

    ok... i have read the BF2 Community Tech FAQ and done everything in it relating to CTD exept reinstalling the game (i dont have my cdkey, lost my manual... what a sheettay place to put it). It used to be that if i logged on to server, it would load and when kit the kit selection screen came up i would CTD. Now i cant even start to load a map that i chose before the CTD. It doesnt have anything to do with my drivers or anything since i played for a while with them as thay are. I made no changes to the computer, this just happened randomly I cant live with out my BF2 despite the glitches:cry: :cry: HELP PLEASE!!!
  • hemimotorz

    #2
    Re: Permanent Crash To Desktop

    Post your dump file.

    Akses VIRUS88 sebagai agen Slot88 resmi dan terpercaya 2026 dengan game gacor terbaru, proses praktis, promo harian menarik, serta layanan online 24 jam.

    Comment

    • nonexistentuser

      #3
      Re: Permanent Crash To Desktop

      Microsoft (R) Windows Debugger Version 6.6.0007.5
      Copyright (c) Microsoft Corporation. All rights reserved.


      Loading Dump File [C:\Documents and Settings\Avinash K. Nayar\My Documents\Battlefield 2\dmp\bf2_v1.1.2963-795.0_2006-09-13_18.38.51.dmp]
      User Mini Dump File: Only registers, stack and portions of memory are available

      Comment: 'Battlefield2 MiniDump. Address: 0058B80B (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 Sep 13 18:38:51.000 2006 (GMT-4)
      System Uptime: not available
      Process Uptime: 0 days 0:00:44.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.
      (978.db0): Access violation - code c0000005 (first/second chance not available)
      eax=00000000 ebx=00000000 ecx=00000000 edx=0012f9bc esi=00000550 edi=00000000
      eip=7c90eb94 esp=0012f4f4 ebp=0012f558 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



      THIS IS WHAT I GET

      Comment

      Working...