Mefioso utworzono 30 listopada 2009 utworzono 30 listopada 2009 (edytowane) Mam taki problem, że gdy uśpię komputer (lub nawet się wyloguję i chcę się zalogować po jakiejś godzinie) to wyskakuję BSOD. Screen: [URL=http://img171.imageshack.us/i/dsc00043ps.jpg/][IMG]http://img171.imageshack.us/img171/6079/dsc00043ps.th.jpg[/IMG][/URL] Mój sprzęt: C2D E8400 Gigabyte GA EP45 DS3L Geil Ultra 2x1gb Radeon HD4850 Samsung 640 GB Karta sieciowa D-Link DWL-520+ Zasiłka Chieftec GPS 450W Co/Jak/Gdzie zrobić aby uniknąć tych bluescreenów? Proszę o pomoc.
Mbroziak komentarz 1 grudnia 2009 komentarz 1 grudnia 2009 Wykonaj [url=http://www.forumpc.pl/index.php?showtopic=16074]>>TO<<[/url] i wstaw wynik na forum.
Mefioso komentarz 3 grudnia 2009 Autor komentarz 3 grudnia 2009 W WinDbg wyskoczyło coś takiego: [code] Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Windows\Minidump\112309-14679-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: E:\Symbols Executable search path is: 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 7 Kernel Version 7600 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0x82851000 PsLoadedModuleList = 0x82999810 Debug session time: Mon Nov 23 21:23:38.766 2009 (GMT+1) System Uptime: 0 days 2:20:39.280 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 ............ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {839fffec, 2, 1, 828ec168} *** WARNING: Unable to verify timestamp for cdd.dll Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for win32k.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 *** *** *** ************************************************************************* Probably caused by : cdd.dll ( cdd!CddAllocShadowSysMem+1da ) Followup: MachineOwner --------- [/code]
Mbroziak komentarz 3 grudnia 2009 komentarz 3 grudnia 2009 Wklej symbole. To co jest opisane na samym dole z poradnika dwa posty wyżej. I dopiero potem otwórz minidumpa i wklej z powrotem na forum.
Mefioso komentarz 3 grudnia 2009 Autor komentarz 3 grudnia 2009 Ok udało się. O to chodzi? [code]******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {839fffec, 2, 1, 828ec168} [/code]
Mbroziak komentarz 4 grudnia 2009 komentarz 4 grudnia 2009 Nie, nie o to. Zrób tak: [quote]Zamykamy Debuggera. Po ponownym jego uruchomieniu klikamy File -> Symbol File Path -> wpisujemy: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Następnie wciskamy [ctrl] + [D] i wskazujemy znów nasz plik minidump. Trzeba poczekać aż Debugger ściągnie sobie wszystkie symbole i przeanalizuje cały plik. Należy pamiętać że ten proces może nieco potrwać - symbole mogą ważyć nawet ponad 10MB, także trzeba uzbroić się w cierpliwość.[/quote] I potem wklej cały tekst na forum (tak jak to zrobiłeś 2 posty wyżej).
Mefioso komentarz 4 grudnia 2009 Autor komentarz 4 grudnia 2009 (edytowane) Zrobiłem dokładnie tak jak pisze w poradniku. [code] Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Windows\Minidump\112309-14679-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0x82851000 PsLoadedModuleList = 0x82999810 Debug session time: Mon Nov 23 21:23:38.766 2009 (GMT+1) System Uptime: 0 days 2:20:39.280 Loading Kernel Symbols ............................................................... ................................................................ ............... Loading User Symbols Loading unloaded module list ............ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {839fffec, 2, 1, 828ec168} Probably caused by : cdd.dll ( cdd!CddAllocShadowSysMem+1f6 ) Followup: MachineOwner --------- [/code]
Mbroziak komentarz 4 grudnia 2009 komentarz 4 grudnia 2009 Teraz tak. Ale wcześniej pisało ci [quote]Your debugger is not using the correct symbols[/quote] więc kazałem poprawić.
Mefioso komentarz 4 grudnia 2009 Autor komentarz 4 grudnia 2009 Aha rozumiem. Czyli w czym może leżeć problem? Dzięki za zainteresowanie.
Mbroziak komentarz 5 grudnia 2009 komentarz 5 grudnia 2009 No właśnie nie wiadomo. Ten plik co wykazał debugger to tak jakby nie wiadomo dlaczego powoduje bluescreena. A bluescreen wyskakuje tylko po uśpieniu kompa czy też podczas normalnej pracy?
ZooMpl komentarz 5 grudnia 2009 komentarz 5 grudnia 2009 Innym wyskakiwał taki błąd z przeglądarką zdjęc, IrfanView, Thumbnail viewer i inne
Mefioso komentarz 10 grudnia 2009 Autor komentarz 10 grudnia 2009 (edytowane) Podczas normalnego używania kompa nic się nie dzieje. OS jest stabilny. BSOD wyskakuje po wyjściu z uśpienia.Czy ktoś potrafi podać przyczynę tych bluescreenów? Z góry przepraszam za post pod postem.
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.