Quantcast
Channel: Windows Server Forum
Viewing all articles
Browse latest Browse all 2531

Server 2003 BSOD ntkrpamp.exe 1000007E

$
0
0

Während dem Windows Update (lt. Kunden) kommt folgender BSOD:
(Server 2003 R2 Std. SP2)

---------------------------------------------------------------------------------------------------

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


Loading Dump File [Mini042713-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: Server, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_gdr.120821-0338
Machine Name:
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
Debug session time: Sat Apr 27 07:49:57.065 2013 (UTC + 2:00)
System Uptime: 0 days 20:39:51.265
Loading Kernel Symbols
...............................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 8080f759, f78cabc8, f78ca8c4}

Probably caused by : ntkrpamp.exe ( nt!CcFlushCache+1c9 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: 8080f759, The address that the exception occurred at
Arg3: f78cabc8, Exception Record Address
Arg4: f78ca8c4, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

FAULTING_IP:
nt!CcFlushCache+1c9
8080f759 f6400420        test    byte ptr [eax+4],20h

EXCEPTION_RECORD:  f78cabc8 -- (.exr 0xfffffffff78cabc8)
ExceptionAddress: 8080f759 (nt!CcFlushCache+0x000001c9)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000004
Attempt to read from address 00000004

CONTEXT:  f78ca8c4 -- (.cxr 0xfffffffff78ca8c4)
eax=00000000 ebx=00000000 ecx=808b4000 edx=00000000 esi=8ab4e008 edi=00000000
eip=8080f759 esp=f78cac90 ebp=f78cacfc 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!CcFlushCache+0x1c9:
8080f759 f6400420        test    byte ptr [eax+4],20h       ds:0023:00000004=00
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  00000004

READ_ADDRESS: GetUlongFromAddress: unable to read from 808ab6b8
 00000004

FOLLOWUP_IP:
nt!CcFlushCache+1c9
8080f759 f6400420        test    byte ptr [eax+4],20h

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

EXCEPTION_STR:  0x0

LAST_CONTROL_TRANSFER:  from 8080fcaf to 8080f759

STACK_TEXT: 
f78cacfc 8080fcaf 88c87a34 00000000 00000001 nt!CcFlushCache+0x1c9
f78cad40 808127fa 8b77d7a8 808ae5c0 8b7750d8 nt!CcWriteBehind+0x11b
f78cad80 808804eb 8b7750d8 00000000 8b77d7a8 nt!CcWorkerThread+0x15a
f78cadac 80949c7e 8b7750d8 00000000 00000000 nt!ExpWorkerThread+0xeb
f78caddc 8088e132 80880400 00000000 00000000 nt!PspSystemThreadStartup+0x2e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!CcFlushCache+1c9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  503382ff

STACK_COMMAND:  .cxr 0xfffffffff78ca8c4 ; kb

FAILURE_BUCKET_ID:  0x7E_nt!CcFlushCache+1c9

BUCKET_ID:  0x7E_nt!CcFlushCache+1c9

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

 


Viewing all articles
Browse latest Browse all 2531


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>