Od czego pojawia się błąd krytyczny - blue screen


(Granulka1) #1

Podczas normalnej pracy z komputerem nagle wyskoczył mi niebieski ekran z komunikatem, że jeśli pojawiło się to po raz pierwszy żeby uruchomić ponownie komputer a jeśli dalej będzie problem to sprawdzić wersję biosu - mniej więcej - coś tam było jeszcze o zrzucie pamięci.

Kod błędu: 1000008e parametr 1 c0000005, parametr 2 bf806980, parametr 3 b64df260, parametr 4 00000000.

Użyłem narzędzia do debugowania dla xp i oto co wyszło:

Microsoft ® Windows Debugger Version 6.8.0004.0 X86

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 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) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700

Debug session time: Thu Nov 8 07:29:11.062 2007 (GMT+1)

System Uptime: 0 days 0:10:00.794

*********************************************************************

* 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 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, bf806980, b64df260, 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 ***

*** ***

*************************************************************************

*********************************************************************

* 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+ *

*********************************************************************

*********************************************************************

* 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+ *

*********************************************************************

Probably caused by : win32k.sys ( win32k+6980 )

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: bf806980, The address that the exception occurred at

Arg3: b64df260, Trap Frame

Arg4: 00000000

Debugging Details:


***** 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 ***

*** ***

*************************************************************************

*********************************************************************

* 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+ *

*********************************************************************

*********************************************************************

* 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+ *

*********************************************************************

MODULE_NAME: win32k

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 45f013f6

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

FAULTING_IP:

win32k+6980

bf806980 f60702 test byte ptr [edi],2

TRAP_FRAME: b64df260 -- (.trap 0xffffffffb64df260)

ErrCode = 00000000

eax=00000001 ebx=b64df30c ecx=e2ae6318 edx=e2ae6318 esi=0000ffff edi=00390cc0

eip=bf806980 esp=b64df2d4 ebp=b64df2fc iopl=0 nv up ei pl zr na pe nc

cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246

win32k+0x6980:

bf806980 f60702 test byte ptr [edi],2 ds:0023:00390cc0=??

Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from bf80681f to bf806980

STACK_TEXT:

WARNING: Stack unwind information not available. Following frames may be wrong.

b64df2fc bf80681f b64df31c bf803e27 e20e6618 win32k+0x6980

b64df304 bf803e27 e20e6618 90010a5c bc66e5c0 win32k+0x681f

b64df31c bf803eb0 90010a5c 00000000 b64df384 win32k+0x3e27

b64df32c bf80ac07 90010a5c b64df414 bf80efa5 win32k+0x3eb0

b64df384 bf80edc6 bc66e5c0 00000085 00000001 win32k+0xac07

b64df39c bf823be3 bc66e5c0 00000085 00000001 win32k+0xedc6

b64df3b8 bf80f00d bc66e5c0 00000085 00000001 win32k+0x23be3

b64df3f0 8054086c 000e02a2 00000085 00000001 win32k+0xf00d

b64df414 7c90eb94 badb0d00 0012f478 e14e3018 nt+0x6986c

b64df418 badb0d00 0012f478 e14e3018 00001fa0 0x7c90eb94

b64df41c 0012f478 e14e3018 00001fa0 00000010 0xbadb0d00

b64df420 e14e3018 00001fa0 00000010 00000001 0x12f478

b64df424 00000000 00000010 00000001 bfa161c0 0xe14e3018

STACK_COMMAND: kb

FOLLOWUP_IP:

win32k+6980

bf806980 f60702 test byte ptr [edi],2

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k+6980

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: win32k.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner


Może ktoś wie o co chodzi i jak to interpretować?


(JNJN) #2

Proszę zmienić temat postu na konkretny, opcja zmień i popraw, poczytaj tematy przyklejone w tym dziale i wklej loga, sprawdź pamięć na błędy.


(Kuba Windows) #3

Windows to kiepski system. To nie twoja wina że miałeś bluesceen, ale wina Microsoftu. Mi też wyskakują Bluescreeny choć nic nie robiłem.