Adir.dll i pare innych!

Log z HJT

Niedlugo zamiescze z Silent Runners aktualnie sie robi.

Log czysty.

Wrzuć log z ComboFix. Aby zrobić w nim log należy go uruchomić => nacisnąć klawisz Y => czekać cierpliwie i log powinien być w formie pliku .txt o nazwie combofix na partycji C.

Dlaczego nie masz aktualizacji SP2…?:slight_smile: polecam…

Silent Runners

@Fafik

A skad to sciagnac? :wink:

@adam

ComboFix juz sie robi, zamieszcze w nastepnym poscie.

@Edit

Adam po 2minutach od uruchomienia ComboFixa komputer resetuje sie, co jest grane? ;<

OT - KOSZ

Log z silenta Ok

Uwaga: Jak wklejasz loga to obejmuj go znacznikiem (tagiem) CODE lub QUOTE - popraw.

Pozdrawiam Gutek2222

Dziwne, a wiecie czym moze byc resetowanie sie komputera?

Jeśli komputer restartuje się z powodu jakiś nieoczekiwanych błędów krytycznych możemy ustawić w systemie pokazywanie blue screena z sygnatura i opisem błędu

W tym celu w: PPM na Moj komputer » zakładka Zaawansowane » Uruchamianie i odzyskiwanie » Ustawienia » Automatycznie uruchom ponownie (odznaczyć)

wtedy podaj błąd Stop jak się pojawi niebieski ekran

Komputer znowu sie zresetowal! Pisalo tam wskazowki itp. oraz PAGE_FAULT_NONPAGED_AREA. Co to moze znaczyc ?

Chodzi o dokładny kod błędu. Ten który jest podany tuż przy STOP.

Sprawdź czy masz jakieś minidump’y, a jeśli tak to wklej zawartość np. dwóch.

http://forum.dobreprogramy.pl/viewtopic … 327#797327

Microsoft ® Windows Debugger Version 6.6.0003.5

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 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 XP Kernel Version 2600 MP (2 procs) Free x86 compatible

Product: WinNt

Kernel base = 0x804d0000 PsLoadedModuleList = 0x8054ae28

Debug session time: Thu Feb 8 21:56:55.592 2007 (GMT+1)

System Uptime: 0 days 0:26:04.306

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

* 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 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 50, {e2e05000, 0, 804ef000, 1}

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

Probably caused by : ntoskrnl.exe ( nt+1f000 )

Followup: MachineOwner


Oraz

Microsoft ® Windows Debugger Version 6.6.0003.5

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 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 XP Kernel Version 2600 MP (2 procs) Free x86 compatible

Product: WinNt

Kernel base = 0x804d0000 PsLoadedModuleList = 0x8054ae28

Debug session time: Mon Feb 5 22:54:23.827 2007 (GMT+1)

System Uptime: 0 days 4:30:22.534

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

* 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 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 50, {e3273000, 0, 804ef000, 1}

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

Probably caused by : ntoskrnl.exe ( nt+1f000 )

Followup: MachineOwner


Włóż płytę CD XP do napędu:

Start >>> Uruchom >>> cmd i wpisz

expand X:\i386\ntoskrnl.ex_ C:\WINDOWS\system32\ntoskrnl.exe (X - literka CD-ROMu, a ta pozioma kreseczka “_” w pierwszej części komendy ma być!)