+- Windows 7 Forum: konfiguracja, optymalizacja, porady, gadżety • (https://windows7forum.pl)
+-- Dział: Pomoc i wsparcie, Windows 7 (/pomoc-i-wsparcie-windows-7-26-f)
+--- Dział: Software (/software-27-f)
+--- Wątek: Ciągły problem z Win7 Ultimate (/ciagly-problem-z-win7-ultimate-10620-t)
Ciągły problem z Win7 Ultimate - Dylan - 20.10.2010 20:45
Witam!
Chciałbym prosić was o pomoc. Otóż po zainstalowaniu win7, i wgraniu sterowników, system nie zachowywał się stabilnie. Już po dwóch czy trzech dniach, zaczął się restartować oraz jak by "zatrzymywał się"(czyli sam musiałem go restartować) było to denerwujące szczególnie kiedy słuchałem muzyki i nagle, muzyka się "zacinała". Przywróciłem stare sterowniki od karty sieciowej, ale zaraz przekonałem się, że to nie w tym leży problem. Nie miałem czegoś takiego na XP. Nawet podczas pisania tego posta, miałem z 3 resety... By trochę przyspieszyć sprawę, ściągnąłem program Debugger tools for windows, i otworzyłem nim jeden z plików minidump.
Oto on:
Kod PHP:
<?php
Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Windows\Minidump\102010-15256-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 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`02a50000 PsLoadedModuleList = 0xfffff800`02c8de50
Debug session time: Wed Oct 20 20: 10: 14.254 2010 (GMT+2)
System Uptime: 0 days 0: 00: 07.846
*********************************************************************
* 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
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8004c4e8f8, 0, 0}
***** 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!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
Unable to load image PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : hardware
Followup: MachineOwner
Kodu z BD nie udało mi się spisać, ponieważ komputer się zawiesza na amen. Moją konfiguracja sprzętowa:
AMD Athlon II X2 255 3,1 GHz, 4 GB Ram, NVIDIA with CUDA GeForce 9800 GT 1 GB, płyta gł. ASUS M4A77TD PRO.
Za pomoc z góry dziękuję.
Dylan
RE: Ciągły problem z Win7 Ultimate - LadyInBlue - 20.10.2010 21:12
Spróbuj zaktualizować BIOS, może tu jest błąd.
RE: Ciągły problem z Win7 Ultimate - trefl - 20.10.2010 21:48
Było by dobrze gdybyś podał z Narzędzia administracyjne => Podgląd zdarzenie => aplikacje które wywołują błędy.
Czy pobrałeś wszystkie uaktualnienia z Microsoft. Skąd pobrałeś sterowniki - jakim programem?
RE: Ciągły problem z Win7 Ultimate - Dylan - 20.10.2010 22:10
(20.10.2010 21:12)LadyInBlue napisał(a): Spróbuj zaktualizować BIOS, może tu jest błąd.
Na płytce od asusa powinienem mieć programik do update'u biosa. Wezmę się jak już nic nie zadziała.
(20.10.2010 21:48)trefl napisał(a): Było by dobrze gdybyś podał z Narzędzia administracyjne => Podgląd zdarzenie => aplikacje które wywołują błędy.
Czy pobrałeś wszystkie uaktualnienia z Microsoft. Skąd pobrałeś sterowniki - jakim programem?
Do geforce'a ściągałem ze strony nvidii, a do reszty podzespołów używałem programu DriverMax. A te wydarzenia to chodzi ci z kategorii "dzienniki sys. Windows/Aplikacja" czy "dziennik aplikacji i usług"? W każdym razie zapisałem z tego pierwszego i dołączam plik dziennika zdarzeń, na początku widziałem błędy od agent.exe, ale niżej jak zjechałem jest ich też trochę. A uaktualnienia, to najważniejsze pobieram, a czy wszystkie nie wiem, ciągle mi wyskakuje że aktualizacja do pobrania, więc myślę że jestem na bieżąco.
Dylan
[attachment=1671]
RE: Ciągły problem z Win7 Ultimate - trefl - 20.10.2010 22:35
DriverMax potrafi zrobić "cuda" pobiera sterowniki "ogólne" a nie od producenta danego sprzętu. Karty graficzne są produkowane przez różne firmy. Chipset maja niby ten sam ale interfejs różny.Co za tym idzie występują różnice w sterownikach.Podobnie jest z innymi urządzeniami. Odinstaluj sterowniki programem http://www.programosy.pl/program,driver-sweeper.html , a następnie zainstaluj ze strony producenta.
Przeczytaj to http://www.spycheck.pl/genera.php?processfile=agent.exe&dir=a&pag=27
Wyłącz łotra w procesach i przeskanuj system antywirusem i programem anty malware