Stery ATI i problemz pliczekiem ati3duag.dll


(Samba1976) #1

Witam

Otóż włączyłem sobie dzisiaj Far Cry 2 i pojawiły się kłopoty.

Po pierwsze w lewym górnym rogu monitora mam coś takiego jakby licznik FPS i czegoś tam jeszcze.

Wygląda to tak ;

2r4sg06.jpg

Pomyślałem że zrestartuję grę i wszystko będzie O.K.

A tutaj nastąpił restart kompa samoistny i powtał plik Mini Dump który po analizie wygląda tak

http://wklejto.pl/18311

Microsoft ® Windows Debugger Version 6.10.0003.233 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C]

Mini Kernel Dump File: Only registers and stack trace are available

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:

*********************************************************************

* 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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

Debug session time: Thu Dec 11 16:44:28.125 2008 (GMT+1)

System Uptime: 0 days 6:07:42.827

*********************************************************************

* 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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Loading Kernel Symbols

...............................................................

................................................................

........

Loading User Symbols

Loading unloaded module list

................

Unable to load image ati3duag.dll, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ati3duag.dll

*** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf2c74d2, aa2a2160, 0}

***** Kernel 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: nt!_KPRCB ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** 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: nt!_KPRCB ***

*** ***

*************************************************************************

*********************************************************************

* 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 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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Probably caused by : ati3duag.dll ( ati3duag+e74d2 )

Followup: MachineOwner

---------

0: kd !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)

This is a very common bugcheck. Usually the exception address pinpoints

the driver/function that caused the problem. Always note this address

as well as the link date of the driver/image that contains this address.

Some common problems are exception code 0x80000003. This means a hard

coded breakpoint or assertion was hit, but this system was booted

/NODEBUG. This is not supposed to happen as developers should never have

hardcoded breakpoints in retail code, but ...

If this happens, make sure a debugger gets connected, and the

system is booted /DEBUG. This will let us see why this breakpoint is

happening.

Arguments:

Arg1: c0000005, The exception code that was not handled

Arg2: bf2c74d2, The address that the exception occurred at

Arg3: aa2a2160, Trap Frame

Arg4: 00000000

Debugging Details:

------------------

***** Kernel 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: nt!_KPRCB ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** 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: nt!_KPRCB ***

*** ***

*************************************************************************

*********************************************************************

* 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 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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4907c324

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwo

FAULTING_IP:

ati3duag+e74d2

bf2c74d2 83781c05 cmp dword ptr [eax+1Ch],5

TRAP_FRAME: aa2a2160 -- (.trap 0xffffffffaa2a2160)

ErrCode = 00000000

eax=00000000 ebx=e4479024 ecx=e4694124 edx=e3d088d0 esi=e29515f0 edi=e294e010

eip=bf2c74d2 esp=aa2a21d4 ebp=00000001 iopl=0 nv up ei pl zr na pe nc

cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246

ati3duag+0xe74d2:

bf2c74d2 83781c05 cmp dword ptr [eax+1Ch],5 ds:0023:0000001c=????????

Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from e294e010 to bf2c74d2

STACK_TEXT:

WARNING: Stack unwind information not available. Following frames may be wrong.

aa2a21d0 e294e010 e4479040 e29515f0 00000030 ati3duag+0xe74d2

aa2a21d4 e4479040 e29515f0 00000030 e294e010 0xe294e010

aa2a21d8 e29515f0 00000030 e294e010 e4479010 0xe4479040

aa2a21dc 00000000 e294e010 e4479010 e29515f0 0xe29515f0

STACK_COMMAND: kb

FOLLOWUP_IP:

ati3duag+e74d2

bf2c74d2 83781c05 cmp dword ptr [eax+1Ch],5

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ati3duag+e74d2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ati3duag

IMAGE_NAME: ati3duag.dll

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

---------

Pliczek powodujący błąd to ati3duag.dll.

Prawdopodobnie to coś ze sterownikami ATI które mam w najnowszej wersji.

A te zielone cyferki o których piszę wyżej to jakaś opcja w CCC ale nie mam pojęcia co zrobić.

Ratunku.

Pozdrawiam


(Spectatorx) #2

Podobno catalyst 8.12 sprawiają mnóstwo problemów... Osobiście nie spotkałem się z nimi. Najlepiej zainstaluj wcześniejsze sterowniki 8.11 lub far cry 2 ati hotfix.


(Samba1976) #3

Przepraszam może wprowadziłem Ciebie w błąd ale mam zainstalowane właśnie 8.11.

Prawdopodobnie jakaś opcja w CCC jest włączona stąd te FPS-y i ich liczenie.


(Spectatorx) #4

To zainstaluj najnowsze dostępne sterowniki, czyli catalyst 8.12. W CCC nie ma możliwości włączenia jakiejkolwiek opcji związanej z wyświetlaniem fps. Może frapsa używasz i on wyświetla fps albo w grze włączone wyświetlanie fps?