Wątek zamknięty

BlueScreen atikmdag.sys

 
$kubi
Nowy
Liczba postów: 8
Post: #1

BlueScreen atikmdag.sys


Witam!
Mam problem z moim PC... od jakiegoś czasu np. grając potrafi zgasnąć ekran, po czym dźwięk sieczkuje z głośników i komp chodził wentylatory i wszystko ale ciemność i ten dźwięk. No ewentualnie się resetował...

Oto zapis pliku MiniDump

Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C: \Windows\Minidump\122909-17078-01.dmp]
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 <symbol_path> 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 (2 procs) Free x64
Product:  WinNt, suite:  TerminalServer SingleUserTS
Built by:  7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e1e000 PsLoadedModuleList = 0xfffff800`03063670
Debug session time:  Thu Sep 29 10: 00: 07.450 2011 (UTC + 2: 00)
System Uptime:  0 days 0: 33: 30.856
*********************************************************************
* 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+                                    *
*********************************************************************
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
.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffffffffffffff, 2, 0, fffff80002e9ebb6}

***** 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                                     ***
***                                                                   ***
*************************************************************************
Probably caused by :  ntoskrnl.exe ( nt+80bb6 )

Followup:  MachineOwner
---------


Pomocy...
(Ten post był ostatnio modyfikowany: 29.09.2011 11:52 przez $kubi.)

29.09.2011 10:00

Znajdź wszystkie posty użytkownika
thermalfake
Ostatni Mohikanin

Liczba postów: 13.580
Post: #2

RE: BlueScreen ntoskrnl.exe


Ten zrzut jest nic nie warty bo nie załadowały się symbole.
Ustaw sobie ścieżkę dostępu na hdd - w momencie debugowania pobierane są przez internet.
SRV*c:\symbole*http://msdl.microsoft.com/download/symbols

[Obrazek: 2089620800_1406976151.png]

W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu.
Jak mądrze zadawać pytania? - przejrzyj poradnik na forum.
Nie udzielam porad via PW.

29.09.2011 10:56

Znajdź wszystkie posty użytkownika
jacek-placek
Młodszy specjalista

Liczba postów: 1.237
Post: #3

RE: BlueScreen ntoskrnl.exe


A odkręć pokrywę i spróbuj go oczyścić z kurzu, szczególnie radiator procesora.

[Obrazek: 04a55a03ba27.jpg]

29.09.2011 11:10

Znajdź wszystkie posty użytkownika
$kubi
Nowy
Liczba postów: 8
Post: #4

RE: BlueScreen ntoskrnl.exe


@jacek-placek Większego kurzu w obudowie nie ma.

@thermalfake Zrobiłem jak pisałeś i teraz plik dump wygląda tak po odczytaniu:

Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C: \Windows\Minidump\122909-17078-01.dmp]
Mini Kernel Dump File:  Only registers and stack trace are available

Symbol search path is:  SRV*c: \symbole*http: //msdl.microsoft.com/download/symbols
Executable search path is:  
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product:  WinNt, suite:  TerminalServer SingleUserTS
Built by:  7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e1e000 PsLoadedModuleList = 0xfffff800`03063670
Debug session time:  Thu Sep 29 10: 00: 07.450 2011 (UTC + 2: 00)
System Uptime:  0 days 0: 33: 30.856
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffffffffffffff, 2, 0, fffff80002e9ebb6}

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING:  Unable to verify timestamp for atikmdag.sys
*** ERROR:  Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by :  atikmdag.sys ( atikmdag+4d26c )

Followup:  MachineOwner
---------

a jeszcze inny jakiś większy gabarytowo z inną datą:

Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C: \Windows\Minidump\092311-16312-01.dmp]
Mini Kernel Dump File:  Only registers and stack trace are available

Symbol search path is:  SRV*c: \symbole*http: //msdl.microsoft.com/download/symbols
Executable search path is:  
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product:  WinNt, suite:  TerminalServer SingleUserTS
Built by:  7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e13000 PsLoadedModuleList = 0xfffff800`03058670
Debug session time:  Fri Sep 23 19: 34: 59.702 2011 (UTC + 2: 00)
System Uptime:  0 days 4: 27: 10.014
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800471a4e0, fffff880040949c8, 0, 2}

*** WARNING:  Unable to verify timestamp for atikmpag.sys
*** ERROR:  Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by :  atikmpag.sys ( atikmpag+79c8 )

Followup:  MachineOwner
---------

Ewidentnie coś z grafiką - ale co poradzić?

Konfig mojego komputera:
Procesor: Intel C2D E6750 @ Scythe Infinity & S-Flex 120
Płyta: MSI P35 Neo2 FIR @ Bios 1.C
Pamięć: G.Skill DDR2 2x2GB 800MHz CL5
Grafika: Gigabyte Radeon HD4850 512MB Zalman Edition
Dysk: Western Digital Caviar 640GB 16MB Sata II
Zasilacz: Tagan Below Zero 500w
Obudowa: Sharkoon Rebel 9 Eco & Fander 2x120mm
OS: Windows 7 Pro x64 MSDNAA

29.09.2011 11:46

Znajdź wszystkie posty użytkownika
jacek-placek
Młodszy specjalista

Liczba postów: 1.237
Post: #5

RE: BlueScreen atikmdag.sys


Próbowałeś pobrać i zainstalować najnowsze sterowniki do karty graficznej ze strony producenta?

[Obrazek: 04a55a03ba27.jpg]

29.09.2011 12:16

Znajdź wszystkie posty użytkownika
$kubi
Nowy
Liczba postów: 8
Post: #6

RE: BlueScreen atikmdag.sys


Przeskanowałem dysk chkdsk + HD Tune PRO i jest bez błędów.

Sterowniki instalowałem nowe ( zawsze tak robię ) po reinstalacji systemu która była niedawno bo w sierpniu.
Ale widzę, że są o 2 oczka nowsze stery więc ściągam.

Mam je nainstalować na te istniejące czy kasować poprzednie i dopiero wtedy instalacja nowych?

29.09.2011 12:32

Znajdź wszystkie posty użytkownika
jacek-placek
Młodszy specjalista

Liczba postów: 1.237
Post: #7

RE: BlueScreen atikmdag.sys


(29.09.2011 12:32)$kubi napisał(a):  Przeskanowałem dysk chkdsk + HD Tune PRO i jest bez błędów.

Sterowniki instalowałem nowe ( zawsze tak robię ) po reinstalacji systemu która była niedawno bo w sierpniu.
Mam je nainstalować na te istniejące czy kasować poprzednie i dopiero wtedy instalacja nowych?

Jeśli instalowałeś, to przecież wieszUśmiechnięty Mam Nividię i nie odinstalowuję, instalator sam to robi.

[Obrazek: 04a55a03ba27.jpg]

29.09.2011 12:43

Znajdź wszystkie posty użytkownika
$kubi
Nowy
Liczba postów: 8
Post: #8

RE: BlueScreen atikmdag.sys


(29.09.2011 12:43)jacek-placek napisał(a):  
(29.09.2011 12:32)$kubi napisał(a):  Przeskanowałem dysk chkdsk + HD Tune PRO i jest bez błędów.

Sterowniki instalowałem nowe ( zawsze tak robię ) po reinstalacji systemu która była niedawno bo w sierpniu.
Mam je nainstalować na te istniejące czy kasować poprzednie i dopiero wtedy instalacja nowych?

Jeśli instalowałeś, to przecież wieszUśmiechnięty Mam Nividię i nie odinstalowuję, instalator sam to robi.

Tak instalowałem - na świeżym systemie o czym zaznaczyłem wyżej.


EDIT:
Zainstalowałem nowe sterowniki. W razie gdyby problem się powtórzył z jakimś BSODem wrócę Cwaniak
(Ten post był ostatnio modyfikowany: 29.09.2011 12:53 przez $kubi.)

29.09.2011 12:47

Znajdź wszystkie posty użytkownika
thermalfake
Ostatni Mohikanin

Liczba postów: 13.580
Post: #9

RE: BlueScreen atikmdag.sys


Folder symbole na dysku C: musisz sobie utworzyć.

Jeden z błędów
http://forums.amd.com/game/messageview.c...erthread=y

[Obrazek: 2089620800_1406976151.png]

W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu.
Jak mądrze zadawać pytania? - przejrzyj poradnik na forum.
Nie udzielam porad via PW.
(Ten post był ostatnio modyfikowany: 29.09.2011 13:36 przez thermalfake.)

29.09.2011 13:34

Znajdź wszystkie posty użytkownika
Wątek zamknięty

Podobne wątki
Wątek: Autor Odpowiedzi: Wyświetleń: Ostatni post
Błędy Windows 7 Bluescreen gumi112198787 3 2.133 27.01.2023 20:49
Ostatni post: LadyInBlue
Bluescreen przy restarcie/zamknięciu systemu. nulus 0 1.596 25.02.2018 13:50
Ostatni post: nulus
problem z instalacja Windowsa bluescreen bartek07klapa 1 2.300 16.03.2017 21:23
Ostatni post: thermalfake
Problem z powrotem do windows7 z windows10 (bluescreen) kajakaja 2 1.706 10.08.2016 09:31
Ostatni post: kajakaja
Rozwiązany Bluescreen pod koniec instalacji Windows 7 na laptopie vales1 9 1.685 27.06.2015 17:38
Ostatni post: vales1
Rozwiązany Problem bluescreen tylko po instalacji SP1 w Windows 7 prof voltcraft 17 3.072 21.06.2015 16:52
Ostatni post: GamerPL
« Starszy wątek | Nowszy wątek »

Temat został oceniony na 0 w skali 1-5 gwiazdek.
Zebrano 0 głosów.