Witam, mam problem znów z grafiką. Oddawałam z tego powodu już komputer do naprawy, naprawili i było ok, ale znów się to dzieje.
Chodzi mi generalnie o :
Address a problem with ATI Graphics Driver ATI Graphics Driver has stopped working properly. A driver update, if available, might prevent this problem from recurring. There are several ways of locating and installing driver updates, but it is best to let Windows do this for you. Try the first step below, which describes the process. If it doesn’t produce a driver update that solves the problem, then try the remaining steps in the order given. Check for optional third-party updates Even if all critical updates have been installed on your computer, optional updates might be available for ATI Graphics Driver that have yet to be installed. Here’s how to use Windows Update to check for and install optional driver updates: Click to go online to the Windows Update website.
i ekran :
Dodaję także informację z centrum rozwiązywania problemów :
oraz log z programu Debugging Tools for Windows :
Microsoft ® Windows Debugger Version 6.11.0001.404 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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0x83a3e000 PsLoadedModuleList = 0x83b55c70 Debug session time: Wed Mar 24 14:51:44.093 2010 (GMT+1) System Uptime: 0 days 0:01:48.217 ********************************************************************* * 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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Loading Kernel Symbols … … … Loading User Symbols Loading unloaded module list … Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for dxgkrnl.sys *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 100000EA, {88f9c580, 0, 0, 0} *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys ***** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 : dxgkrnl.sys ( dxgkrnl+6c1c ) Followup: MachineOwner ---------
Proszę o pomoc!
hubcio443
(Hubcio443)
24 Marzec 2010 15:23
#2
Spróbuj może reinstalkę sterowników, lub po prostu wgraj nowe… być może grafika się grzeje… Sterowniki ostatnio felerne wychodzą, piszę o Nvidii
Ja posiadam ATI Radeon HD 3600 Series i stery były wgrywane ze strony producenta…
– Dodane 24.03.2010 (Śr) 17:33 –
pomocy? miałam już jeden temat ale nikt nie pomógł : dziwny-ekran-jakby-zaklocen-restart-t350124.html
hubcio443
(Hubcio443)
24 Marzec 2010 18:20
#4
A sprawdzałaś połączenia monitora z komputerkiem???
– Dodane 24.03.2010 (Śr) 19:22 –
Jeżeli nie rozwiąże nikt tego problemu do jutra, to pójdę do takiego kolesia ze screenami twoimi on powinien coś doradzić.
– Dodane 24.03.2010 (Śr) 19:23 –
Dimatheus w w/w temacie doradził Tobie dobrze, jak rozwiązać ten problem.
Aha… no ja nic z tego nie rozumiem, jestem kompletnym laikiem jeśli chodzi o bawienie się sterowaniami… Aha i w rozwiązaniach pisze Błąd wideo…
hubcio443
(Hubcio443)
25 Marzec 2010 20:58
#6
,jest napisane, to tak na przyszłość. A sprawdzałaś połączenia monitora z komputerem? Podłącz komputer do innego monitora i zobacz czy problem występuje. I jakie sterowniki instalowałaś?? podaj mi konkretne oznaczenie, lub datę ich wydania.Zawsze podczas ściągania sterowników ze strony producenta, w tym przypadku Ati jest napisana data wydania.
Nie posiadam innego komputera żeby to sprawdzić, ale monitor jest wymieniany. Wcześniej z innymi 3 było tak samo.
Instalowałam inne, teraz w serwisie wymienili mi kartę z 2600 hd na 3600.
To screen sterownika :
Niestety nie. Komputer jest ciągle na gwarancji i niestety nie mogę go otworzyć. Spróbuje pobrać nowe stery i się odezwę co i jak.
– Dodane 27.03.2010 (So) 15:41 –
http://game.amd.com/us-en/drivers_catal … on-vista32 stąd wcześniej pobierałam stery i teraz pobieram
Czy to pomoże?
http://i42.tinypic.com/2iitsm0.jpg czy jeżeli doszedł nowy folder to znaczy że tamte stery były stare?
– Dodane 27.03.2010 (So) 16:11 –
No dobra, sterowniki są nowsze sprawdziłam, data też jest nowsza tylko… teraz komputer uruchamia się dłużej ;/ (wyłączyłam i włączyłam ponownie komputer)
wcześniej po 4 paskach diody na klawiaturze migaly i paski przeleciały jeszcze ze 3-6 razy i włączał się (szybko) a teraz… tragedia. mam włączoną usługę readyboost.
– Dodane 28.03.2010 (N) 12:24 –
dodam jeszcze, że po instalacji wyskakuje blue screen tylko przy uruchamianiu systemu i już poprawnie się wyświetla, podaje to co zapisałam :
– Dodane 28.03.2010 (N) 12:25 –
Microsoft ® Windows Debugger Version 6.11.0001.404 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] Kernel Summary Dump File: Only kernel address space is 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+ * ********************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe - Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 6002.18160.x86fre.vistasp2_gdr.091208-0542 Machine Name: Kernel base = 0x83a11000 PsLoadedModuleList = 0x83b28c70 Debug session time: Sun Mar 28 13:19:49.077 2010 (GMT+2) System Uptime: 0 days 0:01:19.811 ********************************************************************* * 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+ * ********************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe - Loading Kernel Symbols … … … Loading User Symbols Loading unloaded module list … *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {80c03510, 89920c4e, 0, 2} ***** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys ************************************************************************* *** *** *** *** *** 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 : atikmpag.sys ( atikmpag+4c4e ) Followup: MachineOwner ---------
hubcio443
(Hubcio443)
29 Marzec 2010 18:58
#10
Ciężka sprawa, mój znajomy też twierdzi, że to wina sterowników…A do deinstalacji użyłaś jakich narzędzi??? wyczyściłas pozostałości po nich w rejestrze?
Tak odinstalowywałam Driver Sweeperem, potem CCleaner, i nowe. Na razie jest ok, ale plik dalej siedzi i nie odinstalowywał się… coś by się stało jakbym go usunęła ręcznie?
– Dodane 30.03.2010 (Wt) 13:13 –
Dodam że zrobiłam podobny wątek tu : http://www.searchengines.pl/index.php?s … ntry594253 ale też nic konkretnego… dalej to się dzieje nawet po odinstalowaniu i instalacji od nowa…
hubcio443
(Hubcio443)
30 Marzec 2010 18:22
#12
Tak odinstalowywałam Driver Sweeperem, potem CCleaner, i nowe. Na razie jest ok, ale plik dalej siedzi i nie odinstalowywał się… coś by się stało jakbym go usunęła ręcznie? – Dodane 30.03.2010 (Wt) 13:13 – Dodam że zrobiłam podobny wątek tu : http://www.searchengines.pl/index.php?s … ntry594253 ale też nic konkretnego… dalej to się dzieje nawet po odinstalowaniu i instalacji od nowa…
Daj screen tego pliku, który chcesz usunąć oraz jego właściwości, chodzi mi o usadowienie.I mam rozumieć, że narazie jest wszystko okey ?
Niestety nie. BS dalej są … tam mi radzą już co innego… mam kiepski zasilacz Mode com FEEL i musze go wymienić, lecz komputer jest chyba na gwarancji jeszcze no i nie wiem co zrobić. Przeczytaj najnowsze posty.
hubcio443
(Hubcio443)
31 Marzec 2010 15:32
#14
A ja Tobie nie radzę zrywać plomb, ponieważ potem będziesz miała problemy z uznaniem gwarancji.I nie jestem pewien ale nie bedzie to zasilacz. Powodów może być wiele, przegrzewająca się karta, zły kabel łączący monitor ze stacjonarką, wadliwe sterowniki, błędy w rejestrze lub też wirusy. Zrób nowy temat i wrzuć log z gmer’a oraz otl. I niech ktoś kompetentny to sprawdzi.
to na pewno nie wirusy. ale ok zrobię tak. gmera nie będę używała, bo miała BS po nich, i na pewno nie posiadam żadnego rootkita :d
hubcio443
(Hubcio443)
1 Kwiecień 2010 19:03
#16
Jeżeli droga kolezanko masz po nich blue screeny, to jest wina gdzieś w systemie, być może również masz rootkita’a
Nie raczej nie. Skanowałam kompa MBAM i nic nie ma. to nie sprawa wirusowa. raczej hardware ale ciężko mi jest znaleźć przyczynę ;/
hubcio443
(Hubcio443)
2 Kwiecień 2010 06:50
#18
A komu nie jest ciężko:/ Słuchaj, pod viste nie wyszły sterowniki w pełni kompatybilne pod Twoją grafikę, może to dlatego, Odinstaluj w trybie awaryjnym sterowniki od grafiki, wyczyść rejestr http://www.dobreprogramy.pl/RegSeeker,P … 2055.html. . następnie znów zainstaluj sterowniki od grafiki, najlepiej, do tego użyj programu, który wyszuka najbardziej aktualne http://www.driver-soft.com/ co do keya to pisz do mnie prywatna wiadomość, jakbyś nie znalazła. Może to pomoże, trzeba próbować. Natomiast mam jedno pytanie, jak często występują te ,ekrany śmierci, i w jakich sytuacjach.
Jak włączam komputer. Tylko podczas włączania po pasku przelatującego. Już to robiłam no ale ok, spróbuje.
– Dodane 23.04.2010 (Pt) 14:53 –
Witajcie ponownie, otóż myślałam długo nad kupnem nowego zasilacza lecz niestety nie stać mnie na razie na nic ;/
więc zrobiłam po swojemu i przeniosłam plik atikmpag.sys na pulpit i BLUE SCREENA NIE MA. Komputer się szybciej uruchamia ale… ale… nie ma AERO GLASS, i okna strasznie się przycinają i nie mają płynności jak przy aero… co teraz mam zrobić? nie przywrócę tego pliku ;/