Tweet
My First 1.4 CTD and how-to Analyze it
Hi, well, after 3 hours of playing, I have my first CTD with 1.4.
Battlefield 2, on every crash generates a DUMP file with the error that produces the crash. Here is the way to read those files.
First, you need the Windows Debuging tool, get it from here:
for 32 Bits:
http://www.microsoft.com/whdc/devtoo...nstallx86.mspx
For 64 Bits:
http://www.microsoft.com/whdc/devtoo...tall64bit.mspx
Install Windbg and then go to:
My Documents/Battlefield 2/dmp
Order the files by date and select the lastone.
Open WinDBG and drag & drop te .dmp file into the Windbg window.
Now you can see what's the cause of the CTD in your game. The next one is my first (y really dont know what it means):
D:\Aphrodite\BF2_1.4\Code\BF2\Game\Common\GhostMan ager.cpp(1350): Error: Common: state bits differs read:85 expected:78
[EOF]'
^^ That's the line.
Post yours so maybe we can get common causes to try to solve the problems.
Greetz.
Pepe.-
Battlefield 2, on every crash generates a DUMP file with the error that produces the crash. Here is the way to read those files.
First, you need the Windows Debuging tool, get it from here:
for 32 Bits:
http://www.microsoft.com/whdc/devtoo...nstallx86.mspx
For 64 Bits:
http://www.microsoft.com/whdc/devtoo...tall64bit.mspx
Install Windbg and then go to:
My Documents/Battlefield 2/dmp
Order the files by date and select the lastone.
Open WinDBG and drag & drop te .dmp file into the Windbg window.
Now you can see what's the cause of the CTD in your game. The next one is my first (y really dont know what it means):
Code:
Microsoft (R) Windows Debugger Version 6.6.0003.5 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [e:\Battlefield 2\Dmp\bf2_v1.1.2963-795.0_2006-09-06_02.06.26.dmp] User Mini Dump File: Only registers, stack and portions of memory are available Comment: 'Battlefield2 MiniDump. Address: 00448101 (In Windbg type: .ecxr) ASSERT INFORMATION: [...] D:\Aphrodite\BF2_1.4\Code\BF2\Game\Common\GhostManager.cpp(1350): Error: Common: state bits differs read:85 expected:78 [EOF]' Windows XP Version 2600 (Service Pack 2) UP Free x86 compatible Product: WinNt, suite: SingleUserTS Debug session time: Wed Sep 6 02:06:29.000 2006 (GMT-4) System Uptime: not available Process Uptime: 0 days 2:39:11.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. eax=00000006 ebx=00000000 ecx=0012f8b8 edx=4e14002c esi=000006d8 edi=00000000 eip=7c91eb94 esp=0012f400 ebp=0012f464 iopl=0 nv up ei pl zr na po 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: 7c91eb94 c3 ret
[EOF]'
^^ That's the line.
Post yours so maybe we can get common causes to try to solve the problems.
Greetz.
Pepe.-
Comment