BSOD wywołany przez sterowniki ATI


(Marjaan) #1

Witam, mam poważny problem,

Podkręciłem procesor z 1,6~ na 2,0 Ghz samą zworką, zwiększyłem timingi, wszystko jest idealnie, gdyby nie jedno, z grafiką nic nie robiłem oprócz instalacji nowych sterowników, Catalystów 8.8 [moja grafa to radeon x1600pro] i teraz mam problem, w 3dmarku03 wyskakuje mi BSOD [treści nie znam bo nie miałem zaznaczonego tego w opcjach, bo nie pamietam gdzie :?] a o to treść pliku minidump

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86

Copyright (c) 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 2) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620

Debug session time: Wed Aug 27 11:40:02.500 2008 (GMT+1)

System Uptime: 0 days 0:03:21.053

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

* 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, {c000001d, e2e1d8fc, a77c288c, 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+11a5c8 )


Followup: MachineOwner

---------

Co zrobić by BSOD nie wyskakiwał?


(Seba86mu) #2

Odinstaluj sterowniki karty graficznej (START -> Panel sterowania -> Dodaj/Usuń programy -> ATI DISPLAY DRIVERS /usuń/). Dodatkowo użyj programu Driver Cleaner, aby usunąć pozostałości po sterownikach.

Zainstaluj inną wersję ATI CATALYST - spróbuj starszą. To, że sterowniki są najnowsze nie znaczy, że są najlepsze dla Twojej karty graficznej.

Po instalacji sterownika i ponownym uruchomieniu komputera, zainstaluj koniecznie najnowsze biblioteki DirectX 9.0c (Instrukcja instalacji bibliotek DirectX 9.0c).


(Marjaan) #3

Przepraszam, że nie odpisałem wcześniej.

nie pomogło...

Czy to może być wina podkręconego procesora? :expressionless:


(Seba86mu) #4

Przywróć procesorowi domyślną częstotliwość taktowania i sprawdź, czy problem nadal występuje.