Windows 2003 Memory Dump - Bug check Analysis attached

Question

Hi all
I recently have had a Windows 2003 Standard with SP2 server crash with a memory dump
 I have used WinDBG to read the file and output below
can anyone shed any light on the faults, or point me in the right direction?
*                        Bugcheck Analysis                                   
KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
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: 8081c630, The address that the exception occurred at
Arg3: b7487c30, Trap Frame
Arg4: 00000000
Debugging Details:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!IoGetAttachedDevice+c
8081c630 8b4810          mov     ecx,dword ptr [eax+10h]
TRAP_FRAME:  b7487c30 -- (.trap 0xffffffffb7487c30)
ErrCode = 00000000
eax=000007f6 ebx=85e76068 ecx=000007f6 edx=00000000 esi=85e76068 edi=89d42020
eip=8081c630 esp=b7487ca4 ebp=b7487ca4 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
nt!IoGetAttachedDevice+0xc:
8081c630 8b4810          mov     ecx,dword ptr [eax+10h] ds:0023:00000806=????????
Resetting default scope
DEFAULT_BUCKET_ID:  DRIVER_FAULT
BUGCHECK_STR:  0x8E
PROCESS_NAME:  DocTransport.ex
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre
LAST_CONTROL_TRANSFER:  from 8082db20 to 80827f7d
STACK_TEXT: 
b74877fc 8082db20 0000008e c0000005 8081c630 nt!KeBugCheckEx+0x1b
b7487bc0 8088c12a b7487bdc 00000000 b7487c30 nt!KiDispatchException+0x3a2
b7487c28 8088c0de b7487ca4 8081c630 badb0d00 nt!CommonDispatchException+0x4a
b7487ca4 8081c7e1 89d42020 b7487d64 00000000 nt!KiExceptionExit+0x186
b7487cb8 808f44c7 85e76068 b7487d64 08a9ea50 nt!IoGetRelatedDeviceObject+0x63
b7487d38 8088b658 00001e20 00000000 00000000 nt!NtReadFile+0x55
b7487d38 7c82845c 00001e20 00000000 00000000 nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
08a9ea8c 00000000 00000000 00000000 00000000 0x7c82845c
STACK_COMMAND:  kb
FOLLOWUP_IP:
nt!IoGetAttachedDevice+c
8081c630 8b4810          mov     ecx,dword ptr [eax+10h]
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!IoGetAttachedDevice+c
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  51d4c567
IMAGE_VERSION:  5.2.3790.5190
FAILURE_BUCKET_ID:  0x8E_nt!IoGetAttachedDevice+c
BUCKET_ID:  0x8E_nt!IoGetAttachedDevice+c
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:0x8e_nt!iogetattacheddevice+c
FAILURE_ID_HASH:  {22c1c728-5bf3-efb9-fff4-40d5ae0d47e2}
Followup: MachineOwner

Answer 1

Hi,
For Bug Check 0x8E, it
indicates that a kernel-mode application generated an exception that the error handler did not catch. For more details, please refer to following article and check if can help you.
Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Did you remember that which operation (or any change) you do before this issue occurred? Or just the server
crashed suddenly?
Please check if all necessary updates were installed and drivers were updated.
à
PROCESS_NAME: 
DocTransport.exe
Did you install any third-party application on the server? Please
perform a clean boot and monitor the result.
By the way, as you know, troubleshoot this kind of kernel crash issue, we need to analyze the crash dump file to narrow down the root cause of the issue. However, it is not
effective for us to debug the crash dump file here in the forum. If this issues is a state of emergency for you. Please contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.
To obtain the phone numbers for specific technology request, please refer to the web site listed below:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
Hope this helps.
Best regards,
Justin Gu