Bluescreen w Win 7


(Kuba Jam) #1

Witam,

Od wczoraj borykam się z problemem w postaci bluescreen. Poczytałem troche w sieci, ale niestety nie jestem sam sobie w stanie pomoc.

Pierwszy raz problem pojawił się wczoraj w nocy, później po kolejnych 10 minutach, następny po godzinie. Po tym ostatnim odpaliłem Windowsa w trybie awaryjnym i uruchomiłem ściąganie plików (tak, żeby sprawdzić czy mały wysiłek dla dysku tego czasami nie powoduje), aby wykluczyć albo raczej prawie wykluczyć uszkodzenie sprzętu. W trybie awaryjnym działał bez problemów przez dobre 12h i nic.

Załączam raporty z WinDbg od najstarszego do najnowszego:

Pierwszy z 03:37 w nocy

Microsoft (R) Windows Debugger Version 6.6.0003.5

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 2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows Vista Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333

Kernel base = 0xfffff800`03418000 PsLoadedModuleList = 0xfffff800`0365c670

Debug session time: Sun Nov 4 03:36:01.300 2012 (GMT+0)

System Uptime: 0 days 0:09:01.159

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

* 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 2

*** 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 D1, {28, 2, 0, fffff88001aa86fd}


***** Kernel symbols are WRONG. Please fix symbols to do analysis.


Unable to load image \SystemRoot\system32\drivers\NETIO.SYS, Win32 error 2

*** WARNING: Unable to verify timestamp for NETIO.SYS

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

******

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

Unable to load image \SystemRoot\System32\drivers\tcpip.sys, Win32 error 2

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

*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys

Unable to load image \SystemRoot\system32\DRIVERS\tdx.sys, Win32 error 2

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

*** ERROR: Module load completed but symbols could not be loaded for tdx.sys

Probably caused by : NETIO.SYS ( NETIO+106fd )


Followup: MachineOwner

---------

Drugi z 03:56 w nocy

Microsoft (R) Windows Debugger Version 6.6.0003.5

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 2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows Vista Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333

Kernel base = 0xfffff800`03459000 PsLoadedModuleList = 0xfffff800`0369d670

Debug session time: Sun Nov 4 03:55:35.561 2012 (GMT+0)

System Uptime: 0 days 0:19:08.420

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

* 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 2

*** 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 D1, {28, 2, 0, fffff880019986fd}


***** Kernel symbols are WRONG. Please fix symbols to do analysis.


Unable to load image \SystemRoot\system32\drivers\NETIO.SYS, Win32 error 2

*** WARNING: Unable to verify timestamp for NETIO.SYS

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

******

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

Unable to load image \SystemRoot\system32\DRIVERS\NETwNs64.sys, Win32 error 2

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

*** ERROR: Module load completed but symbols could not be loaded for NETwNs64.sys

Probably caused by : NETIO.SYS ( NETIO+106fd )


Followup: MachineOwner

---------

Trzeci z 05:06 w nocy

Microsoft (R) Windows Debugger Version 6.6.0003.5

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 2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows Vista Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333

Kernel base = 0xfffff800`03414000 PsLoadedModuleList = 0xfffff800`03658670

Debug session time: Sun Nov 4 04:57:09.779 2012 (GMT+0)

System Uptime: 0 days 0:41:00.527

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

* 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 2

*** 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 D1, {28, 2, 0, fffff88001a106fd}


***** Kernel symbols are WRONG. Please fix symbols to do analysis.


Unable to load image \SystemRoot\system32\drivers\NETIO.SYS, Win32 error 2

*** WARNING: Unable to verify timestamp for NETIO.SYS

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

******

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

Unable to load image \SystemRoot\system32\DRIVERS\NETwNs64.sys, Win32 error 2

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

*** ERROR: Module load completed but symbols could not be loaded for NETwNs64.sys

Unable to load image \SystemRoot\System32\drivers\tcpip.sys, Win32 error 2

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

*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys

Probably caused by : NETIO.SYS ( NETIO+106fd )


Followup: MachineOwner

---------

W razie gdyby ktoś byłby mi w stanie powiedzieć co i jak mam naprawić w systemie to byłbym bardzo wdzięczny.

Gdyby potrzebne były jakieś dodatkowe skany czymkolwiek to proszę powiedzieć, postaram się znaleźć instrukcję w sieci i wrzucić takowy skan jak najszybciej się da.

Pozdrawiam Serdecznie, Jakub.


(adam9870) #2

Używasz karty sieciowej Wi-Fi Intela?

Problem dotyczy sterownika bezprzewodowej karty sieciowej Wi-Fi Intela.

Rozwiązanie - albo aktualizacja sterownika do Wi-Fi Intela do nowszej wersji albo powrót do starszej, ale stabilnej i dopilnowanie, żeby system nie aktualizował automatycznie sterowników (ustawienia aktualizacji automatycznych).

Widziałem sytuacje ze sterownikiem do Wi-Fi Intela - system automatycznie zaktualizował sterownik do nowszej wersji, nowsza wersja sterownika powodowała problem, powrót do starszej wersji rozwiązał problem.

Jak szukać sterowników? sterowniki-windows-7do-karty-sieciowej-t508073.html#p3191454


(Kuba Jam) #3

Dziękuję Ci bardzo za odpowiedź.

Faktycznie w systemie miałem włączone aktualizacje automatyczne bez informowania mnie, zmieniłem to na opcje, w której system może pobrać aktualizacje ale ma mnie informować czy chce je zainstalować.

Co do samej karty sieciowej - wywaliłem stare sterowniki (styczeń 2012) i zainstalowałem nowe (marzec 2012). Zobaczymy czy to w jakiś sposób mi pomoże - mam taką nadzieje.

Nurtuje mnie jednak jedna rzecz - jeżeli jest to problem ze sterownikiem karty sieciowej, to czy w trybie awaryjnym karta sieciowa działałaby normalnie? Chodzi mi o to, że po wystąpienie 3 bluescreena, uruchomiłem Windowsa w trybie awaryjnym, oraz odpaliłem ściąganie plików na 12h i wszystko było OK.

Jeszcze dzisiaj napiszę czy problem się rozwiązał, ewentualnie będę pisał gdy problem znowu się pojawi.

Dzięki i Pozdrawiam, Jakub.

-- Dodane 05.11.2012 (Pn) 9:51 --

I po paru godzinach używania, kiedy już byłem zadowolony, że wszystko jest OK i komputer działa - pojawił się bluescreen. Przedstawiam raport z WinDbg:

-


(adam9870) #4

Spróbuj starszej wersji sterowników, może będzie stabilna, poczytaj opinie na internecie co do konkretnych wersji sterowników, metoda prób i błędów.

Podobny temat: bluescreen-windows-t489660.html