"Sterownik ekranu przestał odpowiadać[...]" bluescreen


(Radzio107) #1

Witam.

Otóż dzis pojawił się problem z komputerem a dokładniej z grafiką. Podczas grania w Fife 13 wyskoczyło takie cos: http://imageshack.us/photo/my-images/34 ... 520001.jpg

http://imageshack.us/photo/my-images/94 ... 540001.jpg

A po tym jeszcze w tle bluescreen i reset kompa . Raz udało mi sie jeszcze wyłączyć aplikacje Alt+F4 i wyskoczyło powiadomienie "Sterownik ekranu AMD Driver przestał odpowiadać ale odzyskał sprawność."

Przy użytkowaniu normalnym nic sie nie dzieje i jest w porządku.

A to Minidump:

Microsoft (R) Windows Debugger Version 6.11.0001.402 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 \SystemRoot\system32\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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431

Machine Name:

Kernel base = 0xfffff800`02c5c000 PsLoadedModuleList = 0xfffff800`02ea0670

Debug session time: Wed Mar 13 15:04:34.252 2013 (GMT+1)

System Uptime: 0 days 0:59:34.969

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

* 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\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 \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 116, {fffffa80045b7010, fffff880044fcefc, 0, 2}


Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for atikmpag.sys

*** ERROR: Module load completed but symbols could not be loaded for atikmpag.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***

******

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

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

* 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+8efc )


Followup: MachineOwner

---------

Mój sprzęt:

Microsoft Windows 7 Ultimate 64 bit

ATI Radeon HD 4800 Series Wersja sterownika 8.970.100.3000 temp w spoczynku 40 st. w stresie 60-70 st.

Procesor AMD Athlon II X4 631 Quad-Core Processor

4 GB RAM

Proszę o pomoc w znalezieniu rozwiązania tego problemu . Pozdrawiam.


(Sebastian Semmerling) #2

Przywróć system i daj znać czy pomogło? :wink:


(Radzio107) #3

CHciałem zrobić reinstal i Odinstalowałem sterowniki a po 30 sek od włączenia kompa robi się coraz więcej pasków az nic nie widac i komp sie resetuje. Przywracanie nie pomogło. Wychodzi na to ze bede musiał wysłac karte na gwarancje?


(falcon89) #4

Sprawdź kartę graficzną na innym komputerze, ale to wskazuje na uszkodzoną kartę.


(Switu95) #5

Może przegrzała Ci się po prostu i powstały 'zimne luty', spróbuj suszarką przez 5 min podgrzać procesor, dać mu ostygnąć i sprawdź, ale jak wyrzej wygląda na uszkodzenie.