fatal error !!!
in [Windows XP]
|
From: MarckUchiha on 12 Aug 2010 00:01 well... recently i have been a problem with a game... every time that i play windows displays a window... the game create an error code... i install windbg to know more about the problem and this is the result: ******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* ***** OS symbols are WRONG. Please fix symbols to do analysis. ***** OS symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: ntdll!_PEB *** *** *** ************************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for Storm.dll - ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for userenv.dll - ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for wdmaud.drv - ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for dsound.dll - ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for Mss32.dll - ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for msvcr80.dll - ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for mswsock.dll - *** ERROR: Symbol file could not be found. Defaulted to export symbols for ws2_32.dll - ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* FAULTING_IP: +646c6975 646c6975 ?? ??? EXCEPTION_RECORD: ffffffff -- (.exr ffffffffffffffff) ExceptionAddress: 646c6975 ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 646c6975 Attempt to read from address 646c6975 PROCESS_NAME: War3.exe MODULE_NAME: Game FAULTING_MODULE: 7c910000 ntdll DEBUG_FLR_IMAGE_TIMESTAMP: 4a7c7eed ERROR_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en "0x%08lx" hace referencia a la memoria en "0x%08lx". La memoria no se puede "%s". READ_ADDRESS: 646c6975 BUGCHECK_STR: ACCESS_VIOLATION LAST_CONTROL_TRANSFER: from 6f3a893a to 646c6975 FAILED_INSTRUCTION_ADDRESS: +646c6975 646c6975 ?? ??? STACK_TEXT: WARNING: Frame IP not in any known module. Following frames may be wrong. 0012fc60 6f3a893a 00000001 32f3262e 00000000 0x646c6975 0012fc88 6f3a9768 01300088 6f3a45a6 00000001 Game!GameMain+0x39f0ca 0012fc90 6f3a45a6 00000001 00000000 00000000 Game!GameMain+0x39fef8 0012fca4 6f3a50e4 00000000 00000001 012400a8 Game!GameMain+0x39ad36 0012fcb4 6f006715 6f007a6a 012400a8 6f632c2d Game!GameMain+0x39b874 0012fcb8 6f007a6a 012400a8 6f632c2d 32f32692 Game+0x6715 0012fcc0 6f632c2d 32f32692 01220098 01220088 Game+0x7a6a 0012fce4 7c92b289 00000004 00000001 0012ffb0 Game!GameMain+0x6293bd 0012fcfc 6f62f4f3 00000000 01220098 6fab1518 ntdll!RtlpUnWaitCriticalSection+0x22 00000000 00000000 00000000 00000000 00000000 Game!GameMain+0x625c83 STACK_COMMAND: ~0s; .ecxr ; kb FAULTING_THREAD: 00000a38 FOLLOWUP_IP: Game!GameMain+39f0ca 6f3a893a 8b7e30 mov edi,dword ptr [esi+30h] SYMBOL_STACK_INDEX: 1 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: Game.dll SYMBOL_NAME: Game!GameMain+39f0ca DEFAULT_BUCKET_ID: WRONG_SYMBOLS BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- i need help please contact me if you know the solution to this problem ... thanks
From: Paul on 12 Aug 2010 03:01 MarckUchiha wrote: > well... recently i have been a problem with a game... every time that i play > windows displays a window... the game create an error code... i install > windbg to know more about the problem and this is the result: > > ******************************************************************************* > * > * > * Exception Analysis > * > * > * > ******************************************************************************* > > ***** OS symbols are WRONG. Please fix symbols to do analysis. > > ***** OS symbols are WRONG. Please fix symbols to do analysis. > > ************************************************************************* > *** *** > *** *** > *** Your debugger is not using the correct symbols *** > *** *** > *** In order for this command to work properly, your symbol path *** > *** must point to .pdb files that have full type information. *** > *** *** > *** Certain .pdb files (such as the public OS symbols) do not *** > *** contain the required information. Contact the group that *** > *** provided you with these symbols if you need this command to *** > *** work. *** > *** *** > *** Type referenced: ntdll!_PEB *** > *** *** > ************************************************************************* > Storm.dll - > userenv.dll - > wdmaud.drv - > dsound.dll - > Mss32.dll - > msvcr80.dll - > mswsock.dll - > ws2_32.dll - > > FAULTING_IP: > +646c6975 > 646c6975 ?? ??? > > EXCEPTION_RECORD: ffffffff -- (.exr ffffffffffffffff) > ExceptionAddress: 646c6975 > ExceptionCode: c0000005 (Access violation) > ExceptionFlags: 00000000 > NumberParameters: 2 > Parameter[0]: 00000000 > Parameter[1]: 646c6975 > Attempt to read from address 646c6975 > > PROCESS_NAME: War3.exe > > MODULE_NAME: Game > > FAULTING_MODULE: 7c910000 ntdll > > DEBUG_FLR_IMAGE_TIMESTAMP: 4a7c7eed > > ERROR_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en "0x%08lx" hace > referencia a la memoria en "0x%08lx". La memoria no se puede "%s". > > READ_ADDRESS: 646c6975 > > BUGCHECK_STR: ACCESS_VIOLATION > > LAST_CONTROL_TRANSFER: from 6f3a893a to 646c6975 > > FAILED_INSTRUCTION_ADDRESS: > +646c6975 > 646c6975 ?? ??? > > STACK_TEXT: > WARNING: Frame IP not in any known module. Following frames may be wrong. > 0012fc60 6f3a893a 00000001 32f3262e 00000000 0x646c6975 > 0012fc88 6f3a9768 01300088 6f3a45a6 00000001 Game!GameMain+0x39f0ca > 0012fc90 6f3a45a6 00000001 00000000 00000000 Game!GameMain+0x39fef8 > 0012fca4 6f3a50e4 00000000 00000001 012400a8 Game!GameMain+0x39ad36 > 0012fcb4 6f006715 6f007a6a 012400a8 6f632c2d Game!GameMain+0x39b874 > 0012fcb8 6f007a6a 012400a8 6f632c2d 32f32692 Game+0x6715 > 0012fcc0 6f632c2d 32f32692 01220098 01220088 Game+0x7a6a > 0012fce4 7c92b289 00000004 00000001 0012ffb0 Game!GameMain+0x6293bd > 0012fcfc 6f62f4f3 00000000 01220098 6fab1518 > ntdll!RtlpUnWaitCriticalSection+0x22 > 00000000 00000000 00000000 00000000 00000000 Game!GameMain+0x625c83 > > > STACK_COMMAND: ~0s; .ecxr ; kb > > FAULTING_THREAD: 00000a38 > > FOLLOWUP_IP: > Game!GameMain+39f0ca > 6f3a893a 8b7e30 mov edi,dword ptr [esi+30h] > > SYMBOL_STACK_INDEX: 1 > > FOLLOWUP_NAME: MachineOwner > > IMAGE_NAME: Game.dll > > SYMBOL_NAME: Game!GameMain+39f0ca > > DEFAULT_BUCKET_ID: WRONG_SYMBOLS > > BUCKET_ID: WRONG_SYMBOLS > > Followup: MachineOwner > --------- > > > i need help please contact me if you know the solution to this problem ... > thanks Symbols allows the debugger to print more information about what routine you're in. But the thing is, you're not going to have symbols for war3.exe (Warcraft III). And chances are, the error is in the game itself. Adding the Symbols folder to your system, would only help you (in a limited way), if the error was in a Windows code module. If you want symbols, you can do things such as: 1) System environment variable ==> _NT_SYMBOL_PATH Value ==> SRV*C:\WINDOWS\Symbols*http://msdl.microsoft.com/download/symbols 2) Create a folder C:\WINDOWS\Symbols to hold your symbols 3) Run SYMCHK (symchk.exe is in the same folder as windbg.exe) symchk -v /r c:\windows\system32 That will return results such as - SYMCHK: FAILED files = 360 SYMCHK: PASSED + IGNORED files = 6869 It will take quite a while to run symchk. My Symbol folder is now about 1.5GB in size, so you'll need a high speed Internet connection to do "symchk" in reasonable time. In the above command example, symchk will download a file from Microsoft, for each code file in the system32 folder. So it is going to download 6000+ files, and chew up disk space. As an example of one entry in the Symbols folder C:\WINDOWS\Symbols userenv.pdb 9FEE774E547347799689D6BAF9DAB4102 userenv.pdb 1395 KB 4/15/2008 userenv.pdb would be used to resolve symbols for subroutines running in userenv.dll . And userenv.dll is part of Windows. ******* I recommend, instead of using windbg, you use your favorite search engine, to look for Warcraft 0xC0000005 errors or war3.exe 0xC0000005 and see what some of the popular reasons are for that error. It could be bad memory or an overclocked CPU, the game needs a patch, or the game is crashing due to some anti-piracy check. You would need "symbols" from the game manufacturer, to turn Game!GameMain+0x39f0ca into useful information. Just a guess, Paul
|
Pages: 1 Prev: MIE 8 Next: How to pass a dragged filename as parameter in a WinXP shortcut? |