Microsoft (R) Windows Debugger  Version 6.7.0005.1
Copyright (C) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini072307-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Jul 23 20:59:04.703 2007 (GMT+8)
System Uptime: 0 days 0:48:49.409
Loading Kernel Symbols
......................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
Unable to load image RtkHDAud.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RtkHDAud.sys
*** ERROR: Module load completed but symbols could not be loaded for RtkHDAud.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, aec49bee, ab49e71c, 0}

Probably caused by : RtkHDAud.sys ( RtkHDAud+148bee )

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: aec49bee, The address that the exception occurred at
Arg3: ab49e71c, 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:
RtkHDAud+148bee
aec49bee 8982bc000000    mov     dword ptr [edx+0BCh],eax

TRAP_FRAME:  ab49e71c -- (.trap 0xffffffffab49e71c)
ErrCode = 00000002
eax=00000001 ebx=85539d98 ecx=84d19a10 edx=00000000 esi=aece9d08 edi=aece9d08
eip=aec49bee esp=ab49e790 ebp=ab49e794 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
RtkHDAud+0x148bee:
aec49bee 8982bc000000    mov     dword ptr [edx+0BCh],eax ds:0023:000000bc=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  war3.exe

LAST_CONTROL_TRANSFER:  from aec1ce6a to aec49bee

STACK_TEXT: 
WARNING: Stack unwind information not available. Following frames may be wrong.
ab49e794 aec1ce6a 00000000 844d6ee0 85539d98 RtkHDAud+0x148bee
ab49e9fc aeaf002c 85539d98 0000000c 849844f8 RtkHDAud+0x11be6a
ab49ea14 aeaf011c 849844f8 844d6ee0 e194d364 portcls!PcDispatchProperty+0x12e
ab49ea3c f6eb1f4c 00000004 84b341b8 84b341b0 portcls!PropertyItemPropertyHandler+0x29
ab49eaa0 f6eb1ec9 849844f8 0000000c e194d364 ks!KspPropertyHandler+0x616
ab49eac4 aeaee1bd 849844f8 0000000c e194d2d8 ks!KsPropertyHandler+0x19
ab49ead4 aeaef753 849844f8 0000000c e194d2d8 portcls!PcHandlePropertyWithTable+0x1a
ab49eb0c aeaee148 844d6e60 862fa5d0 849844f8 portcls!CPortPinWaveCyclic::DeviceIoControl+0x1e3
ab49eb24 f6eb1f0f 862fa5d0 849844f8 ab49eb78 portcls!DispatchDeviceIoControl+0x44
ab49eb34 aeaf5b75 862fa5d0 849844f8 862fa688 ks!KsDispatchIrp+0x126
ab49eb48 aeaf5dd8 862fa5d0 849844f8 aeec908e portcls!KsoDispatchIrp+0x40
ab49eb54 aeec908e 862fa5d0 849844f8 00000000 portcls!PcDispatchIrp+0x2a
ab49eb78 804ef095 862fa5d0 00000004 849844f8 RtkHDAud+0x3c808e
ab49eb88 ac52f774 e17f2d18 00000000 849844f8 nt!IopfCallDriver+0x31
ab49ebd8 ac5322a2 849844f8 84b341b8 e3951b80 sysaudio!ForwardIrpNode+0x1b2
ab49ec30 f6eb1f85 863a8d80 849844f8 ab49ec64 sysaudio!CPinInstance::PinDispatchIoControl+0x153
ab49ec40 804ef095 863a8d80 849844f8 806e4410 ks!DispatchDeviceIoControl+0x28
ab49ec50 8057e70a 84984640 85245370 849844f8 nt!IopfCallDriver+0x31
ab49ec64 8057f56d 863a8d80 849844f8 85245370 nt!IopSynchronousServiceTail+0x60
ab49ed00 805780c2 00002c28 00002370 00000000 nt!IopXxxControlFile+0x5c5
ab49ed34 8054086c 00002c28 00002370 00000000 nt!NtDeviceIoControlFile+0x2a
ab49ed34 7c90eb94 00002c28 00002370 00000000 nt!KiFastCallEntry+0xfc
0012f0f4 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND:  kb

FOLLOWUP_IP:
RtkHDAud+148bee
aec49bee 8982bc000000    mov     dword ptr [edx+0BCh],eax

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  RtkHDAud+148bee

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RtkHDAud

IMAGE_NAME:  RtkHDAud.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  467ba10a

FAILURE_BUCKET_ID:  0x8E_RtkHDAud+148bee

BUCKET_ID:  0x8E_RtkHDAud+148bee

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