Częsty Blue Screen

Zaloguj się Zarejestruj się

Całe forum

Przeszukaj

Całe forum

Użytkownicy

Odpowiedz

Tryb drzewa \| Tryb normalny Częsty Blue Screen
vmisa Nowy Liczba postów: 2	Post: #1 Częsty Blue Screen Witam! Od momentu wgrania Windows 7 na mój komputer często zaczął się pojawiać Blue Screen. Czasami wyskakuje podczas oglądania stron, lecz bywają sytuacje, kiedy komputer już przy włączaniu pokazuje niebieski ekran śmierci. Prawie zawsze Blue Screen jest z takim samym problemem.Gdy się wyświetla, prawie zawsze jest linijka tcpip.sys. Skorzystałam z progamu Windows Debbuger i tutaj zamieszczam dwa pliki bmp. Kod: Microsoft ® Windows Debugger Version 6.12.0002.633 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C: \Windows\Minidump\102911-14086-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\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 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850 Machine Name: Kernel base = 0x82812000 PsLoadedModuleList = 0x8295c850 Debug session time: Sat Oct 29 14: 19: 57.389 2011 (UTC + 1: 00) System Uptime: 0 days 0: 00: 30.543 ******************************************************************* * 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\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\tcpip.sys, Win32 error 0n2 * WARNING: Unable to verify timestamp for tcpip.sys * ERROR: Module load completed but symbols could not be loaded for tcpip.sys ***************************************************************************** * * * Bugcheck Analysis * * * ***************************************************************************** Use !analyze -v to get detailed debugging information. BugCheck D1, {18, 2, 1, 8b06e628} * WARNING: Unable to verify timestamp for afd.sys * ERROR: Module load completed but symbols could not be loaded for afd.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 : tcpip.sys ( tcpip+5f628 ) Followup: MachineOwner --------- Microsoft ® Windows Debugger Version 6.12.0002.633 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C: \Windows\Minidump\110311-15366-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\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 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850 Machine Name: Kernel base = 0x82851000 PsLoadedModuleList = 0x8299b850 Debug session time: Thu Nov 3 16: 07: 20.961 2011 (UTC + 1: 00) System Uptime: 0 days 0: 00: 16.114 ******************************************************************* * 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\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 .... Specyfikacja komputera : ------------------ System Information ------------------ Operating System: Windows 7 Professional 32-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_rtm.101119-1850) Language: Polish (Regional Setting: Polish) System Manufacturer: VOBIS System Model: System Product Name BIOS: Phoenix - AwardBIOS v6.00PG Processor: Intel® Core™2 CPU 4400 @ 2.00GHz (2 CPUs), ~2.0GHz Memory: 3072MB RAM Available OS Memory: 3070MB RAM Page File: 982MB used, 5156MB available Windows Dir: C: \Windows DirectX Version: DirectX 11 DX Setup Parameters: Not found User DPI Setting: Using System DPI System DPI Setting: 96 DPI (100 percent) DWM DPI Scaling: Disabled Notatka została dodana nie znane. Ostatnia edycja dokonana 03.11.2011 20:12 przez peciaq**: Logi oraz inne tym podobne zamykamy w [code]. Zapoznaj się z: Jak poprawnie tytułować wątki? i popraw tytuł. Ma być streszczeniem twojego problemu. 03.11.2011 19:44
Podziękowania od:

thermalfake Ostatni Mohikanin Liczba postów: 13.580	Post: #2 RE: Częsty Blue Screen Z minidumpa nic nie wynika bo źle jest "obrobiony". Spakuj te pliki i podrzuć na forum to sobie przejrzę. Pobierz najnowsze sterowniki do sieciówek wifi/lan. W trybie awaryjnym ręcznie usuń sterowniki do wszystkich urządzeń sieciowych i zainstaluj wskazując lokalizację (nie instaluj domyślnie bo znów zainstaluje stare). W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu. Jak mądrze zadawać pytania? - przejrzyj poradnik na forum. Nie udzielam porad via PW. 03.11.2011 20:30
Podziękowania od:

vmisa Nowy Liczba postów: 2	Post: #3 RE: Częsty Blue Screen Witam. Próbowałam zastosować się do zaleceń ale to nie przyniosło efektu.Wrzucam tutaj ostatni plik , ponieważ reszta usunęła się z powodu CCleanera.Ten Blue Screen wystąpił dzisiaj rano.Dziękuję za wszelką pomoc i pozdrawiam. EDIT : 07.11.2011 Witam Problem nadal występuje a dzisiaj kolejno po sobie wystąpiły trzy BSODY. Pliki wrzuciłam na serwer i razem z tym starszym podaje w jednym pliku : http://hostuje.net/file.php?id=c4d15d487...1064fda25e Dziękuję za wszelką pomoc i pozdrawiam. (Ten post był ostatnio modyfikowany: 07.11.2011 19:40 przez vmisa.) 05.11.2011 12:18
Podziękowania od:

Odpowiedz

Podobne wątki
Wątek:	Autor	Odpowiedzi:	Wyświetleń:	Ostatni post
Windows 7 64bit Blue Screen 116	MisterDui	5	2.154	02.03.2017 16:24 Ostatni post: thermalfake
Częsty blue screen - ASUS	viOoluSkAaa	3	1.595	20.12.2016 18:29 Ostatni post: dyzio2
błąd 124 blue screen podczas grania w wymagające gry	paczkaxd	1	1.444	05.12.2016 18:57 Ostatni post: supcio12343
Częsty ekrad BSOD	kubajed	0	1.274	03.10.2016 17:46 Ostatni post: kubajed
Blue screen podczas zamykania systemu	Gasiu93	0	1.136	30.08.2016 23:06 Ostatni post: Gasiu93
Problem Blue Screen - Driver irql not less or equal	Danielkg	1	2.025	19.07.2016 21:22 Ostatni post: thermalfake

« Starszy wątek | Nowszy wątek »

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

Regulamin for | Polityka Prywatności | Oznacz wszystkie działy jako przeczytane | Ekipa forum | Statystyki | Wersja mobilna | Użytkownicy | Wersja Lo-Fi | Mapa strony |

Copyright © Windows 7 Forum