Reset komputera

Parę razy podczas używania przeglądarek internetowych resetował mi się komputer z niebieskim ekranem w tle. Umieszczam zawartość katalogu: C:\WINDOWS\Minidump.

Kod:

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


Loading Dump File [C:\WINDOWS\Minidump\Mini070114-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: Tue Jul  1 08:27:21.453 2014 (GMT+2)
System Uptime: 0 days 0:10:45.074
*********************************************************************
* 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 win32k.sys, Win32 error 0n2
*** 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, bf85fcb0, b0a20ae4, 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!_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 : win32k.sys ( win32k+5fcb0 )

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



Nie wiem jak to zinterpretować.
System to windows xp sp3, przegladarki to mozilla firefox i google chrome.

Niestety ten odczyt nic nam nie mówi. Podaj jeszcze odczyty innych plików .dmp, może w którymś będą jakieś "konkrety".

Tylko powiedz czym to można jeszcze odczytać. Żeby odczytać tego *.dmp ściągnąłem - Debbuging Tools for Windows (x86) i to jest to co zamieściłem w poście wyżej.

A sprawdź, czy masz więcej plików .dmp w folderze Minidump

Niestety mam kilka tych plików. Sądzę jednak że zapis ich będzie teraz czytelniejszy, ponieważ zainstalowałem Windows Symbol Packages.

Kod:

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


Loading Dump File [C:\WINDOWS\Minidump\Mini070114-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp 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: Tue Jul  1 08:27:21.453 2014 (GMT+2)
System Uptime: 0 days 0:10:45.074
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................

Loading User Symbols
Loading unloaded module list
.............
Unable to load image win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf85fcb0, b0a20ae4, 0}

Probably caused by : win32k.sys ( win32k!sfac_ReadOutlineData+2af )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf85fcb0, The address that the exception occurred at
Arg3: b0a20ae4, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwo

FAULTING_IP:
win32k!sfac_ReadOutlineData+2af
bf85fcb0 80792c02        cmp     byte ptr [ecx+2Ch],2

TRAP_FRAME:  b0a20ae4 -- (.trap 0xffffffffb0a20ae4)
ErrCode = 00000000
eax=e3cbd198 ebx=00000000 ecx=00000000 edx=00000000 esi=b0a20b80 edi=e1446c28
eip=bf85fcb0 esp=b0a20b58 ebp=b0a20b68 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
win32k!sfac_ReadOutlineData+0x2af:
bf85fcb0 80792c02        cmp     byte ptr [ecx+2Ch],2       ds:0023:0000002c=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  chrome.exe

LAST_CONTROL_TRANSFER:  from bf85fd72 to bf85fcb0

STACK_TEXT: 
b0a20b68 bf85fd72 e3e07528 00000000 b0a20bdc win32k!sfac_ReadOutlineData+0x2af
b0a20b88 bf8e0a88 00000000 00000000 00000000 win32k!sfac_ReadOutlineData+0x173
b0a20bac bf8e0f80 b0a20bdc 00000000 e113cee8 win32k!HT_CreateDeviceHalftoneInfo+0x2dc
b0a20bd4 bf8beb9b e12eec08 e113cee8 00000000 win32k!HT_CreateDeviceHalftoneInfo+0x681
b0a20c00 bf8be82e e113dc38 00000000 00000000 win32k!InternalScrollDC+0x330
b0a20c18 bf8bcede e113dc38 00000000 00000000 win32k!xxxCreateThreadInfo+0x6f6
b0a20c30 bf8ba08f e113dc38 00000000 8a317da0 win32k!RtlGetExpWinVer+0x86
b0a20c4c 805d1e6b 89517578 00000000 88e55790 win32k!EngAlphaBlend+0x179
b0a20cf0 805d2153 00000000 b0a20d4c 804ff99b nt!IoReportDetectedDevice+0x55
b0a20cfc 804ff99b 88e55790 b0a20d48 b0a20d3c nt!IoReportDetectedDevice+0x678
b0a20d4c 80541853 00000001 00000000 b0a20d64 nt!CcScheduleReadAhead+0x1ab
b0a20d5c 00000000 01bdffb4 7c90e514 badb0d00 nt!RtlSecondsSince1980ToTime+0x3


STACK_COMMAND:  kb

FOLLOWUP_IP:
win32k!sfac_ReadOutlineData+2af
bf85fcb0 80792c02        cmp     byte ptr [ecx+2Ch],2

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!sfac_ReadOutlineData+2af

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52f43e77

FAILURE_BUCKET_ID:  0x8E_win32k!sfac_ReadOutlineData+2af

BUCKET_ID:  0x8E_win32k!sfac_ReadOutlineData+2af

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




Czy teraz ktoś może mi powiedzieć co powoduje te resety.

Niestety nadal nam to nic nie mówi. Sprawdź na początek pamięć http://www.instalki.pl/programy/downloa ... mTest.html