Blue screen błąd win 7 64 bit


(Malcek 94) #1

witam otóż co jakiś czas wyskakuje mi BS nie denerwowało mnie to ale jak już przy prezentacji mi wyskoczył i usunął mi wsio to się zdenerwowałem...

Bardzo proszę o pomoc

Microsoft ® Windows Debugger Version 6.11.0001.404 X86

Copyright © 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 7600 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Machine Name:

Kernel base = 0xfffff80002e52000 PsLoadedModuleList = 0xfffff8000308fe50

Debug session time: Sun Dec 19 09:46:22.120 2010 (GMT+1)

System Uptime: 0 days 1:24:34.946

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

* 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

......

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff88001a5d412}

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

***** 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 : tcpip.sys ( tcpip+5b412 )

Followup: MachineOwner



(Chamlet) #2

Przetestuj ram narzędziem które znajduje się w narzędziach administracyjnych Diagnostyka pamięci systemu Windows


(Malcek 94) #3

z pamięcią ram wsio dobrze... :smiley:


(Chamlet) #4

Proponowałbym może ściągnąć najnowszy sterownik od karty sieciowej , a ten co masz odinstalować z poziomu menadżera urządzeń.


(Malcek 94) #5

od sieciowej ? a skąd mogę wiedzieć jakie sterowniki mam ściągnąć


(Chamlet) #6

Nie wiem jaki masz komputer ? Czy masz kartę sieciową z integrowaną? jeśli tak to łatwo stwierdzić , to patrzysz jaką masz płytę główną, wchodzisz na stronę producenta na dany model i tam masz sterowniki.


(Malcek 94) #7

i nic dalej ten sam problem.


(Xemidra) #8

Powiedź jakie masz "bebechy" na początek i powiedź jakiego masz antywira, co robisz gdy BSOD wyskakuje ?