XP - Restart systemu (minidump)

[adpawl]

Witajcie!

Ostatnio coś mnie prześladują dziwne problemy z kompem - pewnie dlatego że mam sporo pilnej roboty… :?

Ale do rzecz…

Co jakiś czas system mi się resetuje - moze ktoś podrzuci rozwiązanie?

Załączam log z debuggera:

Microsoft ® Windows Debugger Version 6.6.0007.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 (Service Pack 2) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420 Debug session time: Sun Feb 4 21:23:38.703 2007 (GMT+1) System Uptime: 0 days 4:50:48.293 ********************************************************************* * 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 … The call to LoadLibrary(ext) failed, Win32 error 2 “Nie można odnaleźć określonego pliku.” Please check your debugger configuration and/or network access. The call to LoadLibrary(kext) failed, Win32 error 2 “Nie można odnaleźć określonego pliku.” Please check your debugger configuration and/or network access. The call to LoadLibrary(ext) failed, Win32 error 2 “Nie można odnaleźć określonego pliku.” Please check your debugger configuration and/or network access. The call to LoadLibrary(kext) failed, Win32 error 2 “Nie można odnaleźć określonego pliku.” Please check your debugger configuration and/or network access. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Bugcheck code 100000D1 Arguments c51bc480 00000009 00000000 c51bc480 Unable to load image i8042prt.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for i8042prt.sys *** ERROR: Module load completed but symbols could not be loaded for i8042prt.sys ChildEBP RetAddr Args to Child WARNING: Frame IP not in any known module. Following frames may be wrong. fc4766b0 f98fd3f8 f9904dc6 00000002 fc4766db 0xc51bc480 fc4766dc 804da915 81c02510 81c518d8 00010009 i8042prt+0x3f8 fc476700 fc282bac badb0d00 ffffffbc fc282c3c nt+0x3915 fc476704 badb0d00 ffffffbc fc282c3c f8b9fd28 0xfc282bac fc476708 ffffffbc fc282c3c f8b9fd28 fc2e5f00 0xbadb0d00 fc47670c fc282c3c f8b9fd28 fc2e5f00 fc49b54f 0xffffffbc fc476710 f8b9fd28 fc2e5f00 fc49b54f fc498683 0xfc282c3c fc476714 fc2e5f00 fc49b54f fc498683 fc49b54f 0xf8b9fd28 fc476718 fc49b54f fc498683 fc49b54f fc2e5edc 0xfc2e5f00 fc47671c fc498683 fc49b54f fc2e5edc fc282bca 0xfc49b54f fc476720 fc49b54f fc2e5edc fc282bca fc490294 0xfc498683 fc476724 fc2e5edc fc282bca fc490294 fc490294 0xfc49b54f fc476728 fc282bca fc490294 fc490294 fc2e5dd8 0xfc2e5edc fc47672c fc490294 fc490294 fc2e5dd8 ffffffbc 0xfc282bca fc476730 fc490294 fc2e5dd8 ffffffbc 0000003c 0xfc490294 fc476734 fc2e5dd8 ffffffbc 0000003c 00000029 0xfc490294 fc476738 ffffffbc 0000003c 00000029 fc2e5e7c 0xfc2e5dd8 fc47673c 00000000 00000029 fc2e5e7c f8b9fd28 0xffffffbc

_____update_____

Widzę zadnej odpowedzi

No nic, całe szczęście dałem sobie radę sam :mrgreen:

-jak by co, to pomogły: deinstlka kilku zbytecznych programów, usunięcie walniętego PowerShella, przeczyszcenie rejestru (manual, potem auto) …na koniec reset biosu na dfaulta, scandisk, wreszcie defrag. ufff

Jak narazie się nie tnie, nie resetje - więc chyb spoczko …można wracać do pracy.