Debug Analyse:
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Dokumente und Einstellungen\Ilias\Desktop\Mini081008-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols\
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Sun Aug 10 00:49:50.593 2008 (GMT+2)
System Uptime: 0 days 0:05:03.157
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.................................................................................................................................................
Loading User Symbols
Loading unloaded module list
........
Unable to load image ati3duag.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ati3duag.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c000001d, e3652870, b8210890, 0}
Probably caused by : ati3duag.dll ( ati3duag!silWriteDst+33e8 )
Followup: MachineOwner
---------
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: c000001d, The exception code that was not handled
Arg2: e3652870, The address that the exception occurred at
Arg3: b8210890, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {AUSNAHME} Ung ltige Anweisung Es wurde versucht, eine ung ltige Anweisung auszuf hren.
FAULTING_IP:
+ffffffffe3652870
e3652870 f20fd6d0 movdq2q mm2,xmm0
TRAP_FRAME: b8210890 -- (.trap 0xffffffffb8210890)
ErrCode = 00000000
eax=e2ece150 ebx=e31b9040 ecx=00000082 edx=000000a0 esi=e32074c0 edi=b82109a0
eip=e3652870 esp=b8210904 ebp=b8210910 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
e3652870 f20fd6d0 movdq2q mm2,xmm0
Resetting default scope
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: sro_client.exe
LAST_CONTROL_TRANSFER: from bf2a68f8 to e3652870
FAILED_INSTRUCTION_ADDRESS:
+ffffffffe3652870
e3652870 f20fd6d0 movdq2q mm2,xmm0
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
b8210910 bf2a68f8 e32074c0 e319c418 bf2a6912 0xe3652870
b82109c0 b82109a0 e319c020 e319c260 e319c144 ati3duag!silWriteDst+0x33e8
b82109cc e319c144 e1336508 00000000 00000209 0xb82109a0
b82109d0 e1336508 00000000 00000209 00000001 0xe319c144
b82109d4 00000000 00000209 00000001 00000000 0xe1336508
STACK_COMMAND: kb
FOLLOWUP_IP:
ati3duag!silWriteDst+33e8
bf2a68f8 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: ati3duag!silWriteDst+33e8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ati3duag
IMAGE_NAME: ati3duag.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4844b372
FAILURE_BUCKET_ID: 0x8E_BAD_IP_ati3duag!silWriteDst+33e8
BUCKET_ID: 0x8E_BAD_IP_ati3duag!silWriteDst+33e8
Followup: MachineOwner
---------
kd> lmvm ati3duag
start end module name
bf18f000 bf4e5940 ati3duag M (pdb symbols) C:\WINDOWS\Symbols\dll\ati3duag.pdb
Loaded symbol image file: ati3duag.dll
Image path: ati3duag.dll
Image name: ati3duag.dll
Timestamp: Tue Jun 03 04:58:58 2008 (4844B372)
CheckSum: 003628BB
ImageSize: 00356940
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
kd> .trap 0xffffffffb8210890
ErrCode = 00000000
eax=e2ece150 ebx=e31b9040 ecx=00000082 edx=000000a0 esi=e32074c0 edi=b82109a0
eip=e3652870 esp=b8210904 ebp=b8210910 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
e3652870 f20fd6d0 movdq2q mm2,xmm0
kd> .trap 0xffffffffb8210890
ErrCode = 00000000
eax=e2ece150 ebx=e31b9040 ecx=00000082 edx=000000a0 esi=e32074c0 edi=b82109a0
eip=e3652870 esp=b8210904 ebp=b8210910 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
e3652870 f20fd6d0 movdq2q mm2,xmm0
