Niebieski ekran (Blue Death)


(Kierka) #1

Proszę o pomoc w odnalezieniu przyczyn wystąpienia tego problemu.

Microsoft ® Windows Debugger Version 6.6.0003.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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 2

*** WARNING: Unable to verify timestamp for ntkrnlpa.exe

*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe

Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Kernel base = 0x81a1f000 PsLoadedModuleList = 0x81b36c70

Debug session time: Tue Apr 29 08:31:07.797 2008 (GMT+2)

System Uptime: 0 days 0:39:23.045

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

* 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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 2

*** WARNING: Unable to verify timestamp for ntkrnlpa.exe

*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe

Loading Kernel Symbols

................................................................................................................................................

Loading User Symbols

Loading unloaded module list

...

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 81c3946e, a2920adc, 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 ***

*** ***

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

Probably caused by : ntkrnlpa.exe ( nt+21a46e )

Followup: MachineOwner


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

Arg3: a2920adc, 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 ***

*** ***

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

MODULE_NAME: nt

FAULTING_MODULE: 81a1f000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b12

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

FAULTING_IP:

nt+21a46e

81c3946e 894204 mov [edx+0x4],eax

TRAP_FRAME: a2920adc -- (.trap ffffffffa2920adc)

ErrCode = 00000002

eax=85ffc4d8 ebx=b3aa9758 ecx=81ffc260 edx=00000000 esi=85ffc460 edi=00000000

eip=81c3946e esp=a2920b50 ebp=a2920b8c iopl=0 nv up ei ng nz ac po cy

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

nt+0x21a46e:

81c3946e 894204 mov [edx+0x4],eax ds:0023:00000004=????????

Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_BETA2

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 81c3aa34 to 81c3946e

STACK_TEXT:

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

a2920b8c 81c3aa34 a2920c70 00000000 00000000 nt+0x21a46e

a2920bc0 81c3a62f 5bcbd214 860b3c08 860b3c08 nt+0x21ba34

a2920c48 81c4b350 a2920c70 00433998 00000000 nt+0x21b62f

a2920cd0 81c4aabc 860b3c08 00020000 00433998 nt+0x22c350

a2920d3c 81a76a7a 0000014c 00020000 00433998 nt+0x22babc

a2920d64 777c9a94 badb0d00 0126eed8 00000000 nt+0x57a7a

a2920d68 badb0d00 0126eed8 00000000 00000000 0x777c9a94

a2920d6c 0126eed8 00000000 00000000 00000000 0xbadb0d00

a2920d70 00000000 00000000 00000000 00000000 0x126eed8

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:

nt+21a46e

81c3946e 894204 mov [edx+0x4],eax

FAULTING_SOURCE_CODE:

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt+21a46e

IMAGE_NAME: ntkrnlpa.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner



(Pan Ziombl) #2

jakiego masz firewalla? instalowales daemona toolsa?

zobacz to viewtopic.php?t=104417


(Kierka) #3

Nie, takiego programu nie mam, jedyne co ostatnio instalowałem to Nero, a firewall mam systemowy.

Ten problem wystąpił tylko raz i na razie cisza, wszystko jest ok.

Czy to może być wina pamięci ?

Może warto ją przetestować.

Czy windowsowe "Narzędzie diagnostyczne pamięci" będzie ok do tego celu ?


(Pan Ziombl) #4

sprawdź ram memtestem


(Kierka) #5

Test pamięci nie wykazał żadnych błędów.