» »

BlueScreen - 1000008e

BlueScreen - 1000008e

Tammih ::

Zdravo.

Imam težave, saj se mi vsakih par dni pojavi bluescreen. Prosil bi za pomoč, saj mi napake ne uspe odpraviti. Naložil sem gonilnike iz uradne strani Lenovo, najnovejše gonilnike za grafično, ...

NAPAKA:
Loading Dump File [C:\Users\mihaj\Desktop\040610-18796-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x8280b000 PsLoadedModuleList = 0x82953810
Debug session time: Tue Apr 6 12:00:07.749 2010 (GMT+2)
System Uptime: 4 days 0:14:42.811

Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** 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, 82a50593, 9c4b5c2c, 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 ***
*** ***
*************************************************************************


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: 82a50593, The address that the exception occurred at
Arg3: 9c4b5c2c, Trap Frame
Arg4: 00000000

Debugging Details:
------------------
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: 8280b000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4b1e090a

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt+245593
82a50593 837b7400 cmp dword ptr [ebx+74h],0

TRAP_FRAME: 9c4b5c2c -- (.trap 0xffffffff9c4b5c2c)
ErrCode = 00000000
eax=9e9b2818 ebx=00000000 ecx=00000000 edx=85600020 esi=85600020 edi=87073cb8
eip=82a50593 esp=9c4b5ca0 ebp=9c4b5cdc iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
nt+0x245593:
82a50593 837b7400 cmp dword ptr [ebx+74h],0 ds:0023:00000074=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 82a51f72 to 82a50593

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
9c4b5cdc 82a51f72 9af9f968 9e9b2818 86f5dd40 nt+0x245593
9c4b5d0c 82a520ea 86f5dd40 87073c01 03d78d2c nt+0x246f72
9c4b5d28 8284e47a 00000c0c 03d78d30 777064f4 nt+0x2470ea
9c4b5d34 777064f4 badb0d00 03d78d28 00000000 nt+0x4347a
9c4b5d38 badb0d00 03d78d28 00000000 00000000 0x777064f4
9c4b5d3c 03d78d28 00000000 00000000 00000000 0xbadb0d00
9c4b5d40 00000000 00000000 00000000 00000000 0x3d78d28


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+245593
82a50593 837b7400 cmp dword ptr [ebx+74h],0

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+245593

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrnlpa.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
{code}

MIHAc27 ::

Mogoče kak memtest odkrije da je težava v ramu, če si gonilnike že posodobil.

Zgodovina sprememb…

  • spremenil: MIHAc27 ()

Tammih ::

memtest ni našel napak... :(

Zdaj že nova napaka
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.4
Locale ID: 1060

Additional information about the problem:
BCCode: c2
BCP1: 00000099
BCP2: 85600008
BCP3: 00000000
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\040810-16875-01.dmp
C:\Users\mihaj\AppData\Local\Temp\WER-36234-0.sysdata.xml


Vredno ogleda ...

TemaSporočilaOglediZadnje sporočilo
TemaSporočilaOglediZadnje sporočilo
»

BSOD problem

Oddelek: Pomoč in nasveti
91758 (1416) Oktan
»

Windows XP Black screen

Oddelek: Pomoč in nasveti
123537 (3277) Twix
»

Win 7 blue screen in restart

Oddelek: Operacijski sistemi
132398 (2137) Duhec
»

Bluescreen

Oddelek: Pomoč in nasveti
101987 (1689) slickerSLO
»

BSOD pri Remote Desktopu v Win 2003 Server R2 Enterprise SP2

Oddelek: Pomoč in nasveti
211888 (1715) ender

Več podobnih tem