Problem z Kompem?

Autor: Azi <azazell.civ_at_gmail.com>
Data: Tue 25 Sep 2007 - 19:11:09 MET DST
Message-ID: <fdbfgs$i31$1@atlantis.news.tpi.pl>
Content-Type: text/plain; charset=ISO-8859-2; format=flowed

Nagle gram sobie w Settlers i tu ciach ostry reset .. włączyłem windows
i za pomocą programu odczytałem zapisany błąd w Minidump

o to on:
-------------------------

Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini092507-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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Tue Sep 25 18:32:33.390 2007 (GMT+2)
System Uptime: 0 days 10:48:25.980
*********************************************************************
* 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
............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {bad0b148, 0, 805af54f, 3}

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

Probably caused by : ntoskrnl.exe ( nt+d854f )

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

co jest grane ? wczoraj kupiłem nowe pamięci ze sklepu nowe ale mam
nadzieję, że to nie wina pamięci .. bo wczoraj grałem sporo i dziś i nie
było problemów .. Co jest grane?
Received on Tue Sep 25 19:15:06 2007

To archiwum zostało wygenerowane przez hypermail 2.1.8 : Tue 25 Sep 2007 - 19:51:15 MET DST