blue screen - raport do analizy :)

Wszystko co dotyczy systemów operacyjnych Windows, Unix, Mac OS i innych
falcoo

Użytkownik
Posty: 12
Rejestracja: 16 lip 2009, 12:08

blue screen - raport do analizy :)

Post16 lip 2009, 17:33

prosil bym Was o analize raportu :)
cos ten moj komp sie rozlatuje... :)
dziekuje za pomoc przy karcie graficznej, jednak problem nie zniknal :( tym razem jest cos takiego


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini071609-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 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 XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Thu Jul 16 17:16:27.359 2009 (GMT+2)
System Uptime: 0 days 0:09:44.936
*********************************************************************
* 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 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
.........
Unable to load image 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 C2, {3, 853470d8, 861732c0, 86173280}

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

*** WARNING: Unable to verify timestamp for NDIS.sys
*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys
*** WARNING: Unable to verify timestamp for psched.sys
*** ERROR: Module load completed but symbols could not be loaded for psched.sys
*** WARNING: Unable to verify timestamp for SymIM.sys
*** ERROR: Module load completed but symbols could not be loaded for SymIM.sys
*** WARNING: Unable to verify timestamp for RT61.sys
*** ERROR: Module load completed but symbols could not be loaded for RT61.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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
Probably caused by : SymIM.sys ( SymIM+c40 )

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

widze ze odwalacie tu kupe dobrej roboty pomagajac ludza ;)) hehe xD

Awatar użytkownika
seba86mu

VIP+
Posty: 9744
Rejestracja: 13 lis 2008, 18:07
Lokalizacja: Sosnowiec

blue screen - raport do analizy :)

Post16 lip 2009, 17:52

falcoo, czy posiadasz program antywirusowy firmy Symantec ?
Jeżeli tak to aktualizuj go, ja jeżeli to nie pomoże, to przeinstaluj.

falcoo

Użytkownik
Posty: 12
Rejestracja: 16 lip 2009, 12:08

Re: blue screen - raport do analizy :)

Post16 lip 2009, 17:57

tak :) mam symantec'a ale tylko wersje trial...
rozumiem ze to on mi sprawia takie `kloppoty? :/

Awatar użytkownika
seba86mu

VIP+
Posty: 9744
Rejestracja: 13 lis 2008, 18:07
Lokalizacja: Sosnowiec

blue screen - raport do analizy :)

Post16 lip 2009, 17:58

falcoo pisze:rozumiem ze to on mi sprawia takie `kloppoty? :/

W tym przypadku tak.

Awatar użytkownika
XMan

Globalny Moderator
Posty: 13385
Rejestracja: 30 lis 2008, 00:40

Re: blue screen - raport do analizy :)

Post16 lip 2009, 18:49

mam symantec'a ale tylko wersje trial...

Trial jest tylko do pewnego czasu a później zaczynają się problemy.
Może warto zmienić na inny za free i do tego PL :?:
Kto pyta - nie błądzi, kto szuka - znajduje.
Obrazek
Dostępne tylko dla zarejestrowanych użytkowników

falcoo

Użytkownik
Posty: 12
Rejestracja: 16 lip 2009, 12:08

Re: blue screen - raport do analizy :)

Post16 lip 2009, 21:09

no wlasnie szukam jakiegos dobrego za free :)
moze cos polecacie>?
hehe xD

Awatar użytkownika
seba86mu

VIP+
Posty: 9744
Rejestracja: 13 lis 2008, 18:07
Lokalizacja: Sosnowiec

blue screen - raport do analizy :)

Post16 lip 2009, 21:18

Z wersji polskich, np. avast! Home Edition.
Z wersji niespolonizowanych, np. Dostępne tylko dla zarejestrowanych użytkowników.



  • Reklama

Wróć do „Systemy operacyjne”



Kto jest online

Użytkownicy przeglądający to forum: Obecnie na forum nie ma żadnego zarejestrowanego użytkownika i 3 gości