Microsoft ® Windows Debugger Version 6.10.0003.233 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C]
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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Tue Dec 9 18:48:54.656 2008 (GMT+1)
System Uptime: 0 days 0:29:34.242
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
*** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c000001d, e3cdd870, f765688c, 0}
Probably caused by : ati3duag.dll ( ati3duag+11a5c8 )
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: e3cdd870, The address that the exception occurred at
Arg3: f765688c, 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:
+ffffffffe3cdd870
e3cdd870 f20fd6d4 movdq2q mm2,xmm4
TRAP_FRAME: f765688c – (.trap 0xfffffffff765688c)
ErrCode = 00000000
eax=e3f37150 ebx=e448d040 ecx=000000e3 edx=000000a0 esi=e44dba40 edi=e44dba40
eip=e3cdd870 esp=f7656900 ebp=f765690c iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
e3cdd870 f20fd6d4 movdq2q mm2,xmm4
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: sro_client.exe
LAST_CONTROL_TRANSFER: from bf2b45c8 to e3cdd870
FAILED_INSTRUCTION_ADDRESS:
+ffffffffe3cdd870
e3cdd870 f20fd6d4 movdq2q mm2,xmm4
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f765690c bf2b45c8 e44dba40 f76569a0 e442e420 0xe3cdd870
f7656910 e44dba40 f76569a0 e442e420 bf2b45f2 ati3duag+0x11a5c8
f7656914 f76569a0 e442e420 bf2b45f2 e442e42c 0xe44dba40
f7656918 e442e420 bf2b45f2 e442e42c e442e2e0 0xf76569a0
f76569a0 00000000 7dccccce 7dccccce 7dccccce 0xe442e420
STACK_COMMAND: kb
FOLLOWUP_IP:
ati3duag+11a5c8
bf2b45c8 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: ati3duag+11a5c8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ati3duag
IMAGE_NAME: ati3duag.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 48928cc0
FAILURE_BUCKET_ID: 0x8E_BAD_IP_ati3duag+11a5c8
BUCKET_ID: 0x8E_BAD_IP_ati3duag+11a5c8
Followup: MachineOwner
i
BugCheck 1000008E, {c000001d, e3cdd870, f765688c, 0}
Probably caused by : ati3duag.dll ( ati3duag+11a5c8 )
Tyle wyczytalem tylko niewiem ktory to blad z tych tabelek 
