Przymulony komputer - spadła wydajność

Witam spadła widocznie wydajność mojego komputera
Logi :
OTl : http://www.wklej.eu/index.php?id=2ede387207
OTL Extras : http://www.wklej.eu/index.php?id=c55e4b890d
GMER : http://www.wklej.eu/index.php?id=2a7050cba0

Wejdź w START URUCHOM Msconfig Usługi i odznacz tam usługę NVIDIA Display Driver Service Zastosuj.

Uruchom OTL w oknie Własne opcje skanowania/skrypt wklej:

:OTL

O4 - HKLM..\Run: [KernelFaultCheck] %systemroot%\system32\dumprep 0 -k File not found
O16 - DPF: {00000055-9980-0010-8000-00AA00389B71} http://download.microsoft.com/download/ ... BC/fhg.CAB (Reg Error: Key error.)
O16 - DPF: {E6F480FC-BD44-4CBA-B74A-89AF7842937D} http://content.systemrequirementslab.co ... 4.21.0.cab (Reg Error: Key error.)
@Alternate Data Stream - 99 bytes C:\Documents and Settings\All Users\Dane aplikacji\TEMP:0F8F5844

Files
C:\Documents and Settings\kaczka\Menu Start\Programy\Autostart\PowerReg Scheduler V3.exe
C:\Documents and Settings\kaczka\Menu Start\Programy\Autostart\PowerReg Scheduler.exe

:Reg
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run]
"NvCplDaemon"=-
"NvMediaCenter"=-
"nwiz"=-

:Commands
[clearallrestorepoints]
[emptytemp]

Klikasz Wykonaj skrypt. Dajesz log z usuwania. Następnie podajesz nowe logi z OTL.

log z usuwania : http://www.wklej.eu/index.php?id=24fd5b074a
OTL.txt : http://www.wklej.eu/index.php?id=e81f39b882
OTL extras : http://www.wklej.eu/index.php?id=b15586352b

Uruchom OTL w oknie Własne opcje skanowania/skrypt wklej:

:Processes
killallprocesses

:OTL

O4 - Startup: C:\Documents and Settings\kaczka\Menu Start\Programy\Autostart\PowerReg Scheduler V3.exe (Leader Technologies)
O4 - Startup: C:\Documents and Settings\kaczka\Menu Start\Programy\Autostart\PowerReg Scheduler.exe ()

:Files
C:\Documents and Settings\kaczka\Menu Start\Programy\Autostart\PowerReg Scheduler V3.exe
C:\Documents and Settings\kaczka\Menu Start\Programy\Autostart\PowerReg Scheduler.exe

:Reg
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run]
"NvCplDaemon"=-

:Commands
[clearallrestorepoints]
[emptytemp]

Klikasz Wykonaj skrypt. Dajesz log z usuwania. Następnie podajesz nowe logi z OTL.

log z usuwania : http://www.wklej.eu/index.php?id=ea2e1ee75b
otl.txt : http://www.wklej.eu/index.php?id=d52a44891a
otl extras : http://www.wklej.eu/index.php?id=fe78732759

Uruchom OTL w oknie Własne opcje skanowania/skrypt wklej:

:OTL

:Reg
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run]
"NvCplDaemon"=-
"NvMediaCenter"=-
"nwiz"=-

:Commands
[clearallrestorepoints]

Klikasz Wykonaj skrypt. Dajesz log z usuwania. W OTL Sprzątanie.

Zaktualizuj Internet Explorer do najnowszej wersji (nawet, jeśli Go nie używasz) http://www.instalki.pl/programy/downloa ... _8_XP.html).
Przeczyść dysk i rejestr CCleaner`em https://www.instalki.pl/download/programy/windows/narzedzia/narzedzia-systemowe/ccleaner/.
Wykonaj pełne skanowanie Malwarebytes`em Anti-Malware https://www.instalki.pl/download/programy/windows/bezpieczenstwo/antyspyware/malwarebytes/, jeśli coś znajdzie usuń i daj raport.
Odinstaluj starą wersję programu do odczytu .PDF Adobe Acrobat 7.0 Professional i zainstaluj najnowszą http://www.instalki.pl/programy/downloa ... eader.html.
Odinstaluj starą wersję Java`y Java(TM) 6 Update 22 i zainstaluj najnowszą http://www.instalki.pl/programy/downloa ... %29_6.html.

Po wykonaniu tego wszystkiego napisz, jak wygląda sytuacja.

Uruchom OTL w oknie Własne opcje skanowania/skrypt wklej:

:OTL

:Reg
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run]
"NvCplDaemon"=-
"NvMediaCenter"=-
"nwiz"=-

:Commands
[clearallrestorepoints]

czy mógł bym nie robić tego punktu bo jak się orientuje usuwa on ustawienia NVIDI z paska zadań a często z tego korzystam

To wpisy autostartu, jednak skoro z tego korzystasz to możesz nie wykonywać tego podpunktu. W takim razie wykona resztę.

W OTL Sprzątanie.

Zaktualizuj Internet Explorer do najnowszej wersji (nawet, jeśli Go nie używasz) http://www.instalki.pl/programy/downloa ... _8_XP.html).
Przeczyść dysk i rejestr CCleaner`em https://www.instalki.pl/download/programy/windows/narzedzia/narzedzia-systemowe/ccleaner/.
Wykonaj pełne skanowanie Malwarebytes`em Anti-Malware https://www.instalki.pl/download/programy/windows/bezpieczenstwo/antyspyware/malwarebytes/, jeśli coś znajdzie usuń i daj raport.
Odinstaluj starą wersję programu do odczytu .PDF Adobe Acrobat 7.0 Professional i zainstaluj najnowszą http://www.instalki.pl/programy/downloa ... eader.html.
Odinstaluj starą wersję Java`y Java(TM) 6 Update 22 i zainstaluj najnowszą http://www.instalki.pl/programy/downloa ... %29_6.html.

Po wykonaniu tego wszystkiego napisz, jak wygląda sytuacja.

ok zostało mi jeszcze skanowanie Malwarebytes`em Anti-Malware a komputer już tak nie muli.
Dziękuje za pomoc

niestety ale podczas przeglądania internetu wyskoczył mi BSOD z wiązany z atapi.sys a po restarcie kompa windows nie chciał się wczytać.
czyżby dysk padał ?

Podaj odczyt minidump viewtopic.php?t=15501. Podaj również screenshoty z HD Tune http://www.instalki.pl/programy/downloa ... _Tune.html z zakładek Health i Error Scan. To albo dysk, albo porty USB.

dysk bad sectorów nie ma
HD Tune Pro: WDC WD1600AAJS-07PSA0 Health

ID Current Worst ThresholdData Status
(01) Raw Read Error Rate 200 200 51 0 ok
(03) Spin Up Time 160 155 21 2991 ok
(04) Start/Stop Count 98 98 0 2419 ok
(05) Reallocated Sector Count 200 200 140 0 ok
(07) Seek Error Rate 200 200 51 0 ok
(09) Power On Hours Count 96 96 0 3337 ok
(0A) Spin Retry Count 100 100 51 0 ok
(0B) Calibration Retry Count 100 100 51 0 ok
(0C) Power Cycle Count 98 98 0 2393 ok
(C0) Unsafe Shutdown Count 200 200 0 153 ok
(C1) Load Cycle Count 200 200 0 2419 ok
(C2) Temperature 110 101 0 33 ok
(C4) Reallocated Event Count 200 200 0 0 ok
(C5) Current Pending Sector 200 200 0 0 ok
(C6) Offline Uncorrectable 200 200 0 0 ok
(C7) Ultra DMA CRC Error Count 200 200 0 1 warning
(C8) Write Error Rate 200 200 51 0 ok

Health Status : warning
kabel sata wymieniałem już dawno z powodu ultra dma crc

odczytany dump

Loading Dump File [C:\WINDOWS\Minidump\Mini101311-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) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Thu Oct 13 19:39:14.765 2011 (GMT+2)
System Uptime: 0 days 0:09:58.482
*********************************************************************
* 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 atapi.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atapi.sys
*** ERROR: Module load completed but symbols could not be loaded for atapi.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {c, 7, 1, f72f15f7}

***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 : atapi.sys ( atapi+85f7 )

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

Jeśli możesz to chciałbym zobaczyć obszar Error Scan, oczywiście z odznaczoną opcją Quick Scan . Pamiętaj o skanie Malwarebytes`em.

ok zaraz zrobie

Ponadto, czy zauważyłeś frazę Ultra DMA? Dyski SATA nie pracują w tym trybie poprawnie, bo to tryb dla 80 żyłowych kabli ATA. Stąd prawdopodobnie ten błąd. Nie mniej jednak trzeba dysk monitorować i dane pozgrywać w bezpieczniejsze miejsca, bo nigdy nic nie wiadomo. Jeśli do systemu zainstalujesz sterownik kontrolera SATA (z płytki dołączonej do) to możesz zmienić tryb kontrolera w BIOS`IE sekcja Standard CMOS Features lub Advanced BIOS Features (zależy od układu) tryb kontrolera SATA z Native IDE na AHCI. Nie możesz tego zrobić bez instalacji sterowników, bo system nie uruchomi się poprawnie (zobaczysz BSOD). Jeśli zmiana trybu nie rozwiąże problemu, to należy bacznie obserwować dysk.