Re: Uporczywe Rebootowanie

Użytkownik "JacFef" <jacfef@DELETE.o2.pl> napisał w wiadomości
news:MPG.1fe603ce15503fc59896c5@news.onet.pl...
AnkaS napisał(a):
> prawie codziennie ze razy sam sie rebootuje.
> Czesto, ale nie zawsze jest to zwiazane z dzialaniem aplikacji do obrobki
> dzwieku np. GoldWave, albo systemu przetwarzajacego tekxt na mowe.
>

Zrób to: http://gusioo.ovh.org/?page_id=20 i podaj wyniki.
Masz tam opisane krok po kroku co i jak ;)

-- 
/^~Pozdrawiam^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~\
|               Jacek 'Gusioo' F                   |
|             http://gusioo.ovh.org                |
\^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~/
Przesylam
Z niedzieli:
Mini121006-01.dmp
=========================================================
Microsoft (R) Windows Debugger  Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini121006-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 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 Dec 10 00:26:53.049 2006 (GMT+1)
System Uptime: 0 days 0:42:59.616
*********************************************************************
* 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 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
..........
Unable to load image win32k.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for 
win32k.sys
*******************************************************************************
* 
*
*                        Bugcheck Analysis 
*
* 
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, bf81007f, ecf0bf84, 0}
ANALYSIS: Kernel with unknown size. Will force reload symbols with known 
size.
ANALYSIS: Force reload command: .reload /f 
ntoskrnl.exe=FFFFFFFF804D7000,213F80,42250FF9
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Probably caused by : win32k.sys ( win32k+1007f )
Followup: MachineOwner
==================================
1. Czy mam zadać lepszą analizę
2. Czy to oznacza np. ze  mam z linni poleceń, albo okna terminala dać
 .reload/f ntoskrnl.exe=FFFFFFFF804D7000,213F80,42250FF9
czy co  mam zrobic
Pozdrawiam Anka