Windows Debug Kulla...
 
Bildirimler
Hepsini Temizle

Windows Debug Kullanımı Hk.  

Alper Aykut
(@alperaykut)
Üye

Selam arkadaslar, Client pclerde çıkan minidumpları Windebug programı ile analiz edilebiliyor.Şu Şekilde bir hata mesajı çıkıyor;Esas Mrk ettiğim Windebug programı ile baktıgım minidumplarda nelere dikkat etmem gerekli ki sorunun kaynagıonı bululayım.Ve bu bitp surucu hatalarında ne yapmalıyım ? Bu Hatanın sebebi tam olarak nedir ? Teşekkurler.


 


: 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: 80000004, The exception code that was not handled
Arg2: 806ecae1, The address that the exception occurred at
Arg3: a90bb540, Trap Frame
Arg4: 00000000


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



EXCEPTION_CODE: (HRESULT) 0x80000004 (2147483652) - No such interface supported


FAULTING_IP:
hal!HalpMovntiCopyBuffer+1d5
806ecae1 c20800          ret     8


TRAP_FRAME:  a90bb540 -- (.trap 0xffffffffa90bb540)
ErrCode = 00000000
eax=80001090 ebx=00000090 ecx=00000090 edx=00000cf8 esi=806f1420 edi=a90bb63c
eip=806ecae1 esp=a90bb5b4 ebp=a90bb5c4 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000286
hal!HalpMovntiCopyBuffer+0x1d5:
806ecae1 c20800          ret     8
Resetting default scope


CUSTOMER_CRASH_COUNT:  4


DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT


BUGCHECK_STR:  0x8E


PROCESS_NAME:  OUTLOOK.EXE


LAST_CONTROL_TRANSFER:  from 806e9f0f to 806ecae1


STACK_TEXT: 
a90bb5c4 806e9f0f 806f1420 a90bb5e4 a90bb710 hal!HalpMovntiCopyBuffer+0x1d5
a90bb5c8 806f1420 a90bb5e4 a90bb710 00000090 hal!VESUVIUSGetTrigger+0x4
a90bb5f8 806ea337 a90bb600 00000002 a90bb710 hal!HalpSanityCheckTable+0x9e
a90bb618 806eb14d a90bb63c 00000002 a90bb710 hal!CPQOSBGetIRQ+0x8
a90bb6a8 f7420ae0 00000000 00000000 00000002 hal!VLSISetTrigger+0x3f
a90bb6cc f7420b74 869917e0 00000002 a90bb710 pci!PciReadWriteConfigSpace+0x38
a90bb6ec f7420fcc 869c59b8 a90bb710 00000090 pci!PciWriteDeviceConfig+0x1e
a90bb814 f7423cbd 869c59b8 a90bb89c 00000090 pci!PciExternalWriteDeviceConfig+0x1ac
a90bb838 f742034d 869c59b8 00000000 a90bb89c pci!PciWriteDeviceSpace+0x5d
a90bb858 f70d4212 869c59b8 00000000 a90bb89c pci!PciWriteAgpConfig+0x1d
a90bb874 f70f3851 868a2358 00000004 00000000 VIDEOPRT!VideoPortSetBusData+0x3a
WARNING: Stack unwind information not available. Following frames may be wrong.
a90bb8a8 f7104c33 868a2358 000000ea 00000000 igxpmp32+0xc851
a90bb8f8 f70d435b 868a2358 000000ea 86798000 igxpmp32+0x1dc33
a90bb91c f70e1114 a90bb9b4 00000000 867b2f38 VIDEOPRT!pVpGeneralBugcheckHandler+0x61
a90bb9dc 804ef19f 86589790 86833710 00000000 VIDEOPRT!pVideoPortDispatch+0x4aa
a90bba1c bf93cc22 86589790 0023002c 00000000 nt!MiFlushSectionInternal+0x256
a90bba44 bf960b99 00000000 00000000 a90bba98 win32k!GetValuesFromInf+0x7c
a90bba64 bf8b90a2 e1921008 00000065 00000000 win32k!WatchdogDrvDitherColor+0x59
a90bba98 bf8054d3 e190ac78 00000000 00000000 win32k!RGNOBJ::bOutline+0x1d0
a90bbaac bf86fc5e e190ac78 00000000 00000000 win32k!SURFMEM::~SURFMEM+0x5f
a90bbc0c bf870474 e190ac68 e39efd08 a90bc6f4 win32k!vExpandAndCopyText+0x315
a90bc300 bf8ba517 e190ac78 a90bc43c e39efd08 win32k!EngTextOut+0x67e
a90bc34c bf8ba6aa bf870130 a90bc3d0 e190ac78 win32k!ENUMUNDERLAYS::ENUMUNDERLAYS+0x5d
a90bc3e0 bf811ab7 e190ac78 a90bc43c e39efd08 win32k!STROBJ_vOffset+0x76
a90bc668 bf812fb1 a90bc908 e3558a34 e3558a90 win32k!GreExtTextOutWLocked+0xdae
a90bc7d0 bf80c3b4 a90bc908 7ffdd1dc 00000060 win32k!GreBatchTextOut+0x2af
a90bc924 805415fd 0000022b 0013fb78 0013fc2c win32k!NtGdiFlushUserBatch+0x7e9
a90bc934 7c90e514 badb0d00 0013fb78 bbed6bc8 nt!RtlIpv4StringToAddressExW+0x7e
a90bc948 a90bc970 bf80ec69 bbed6930 00000084 0x7c90e514
a90bc94c bf80ec69 bbed6930 00000084 00000000 0xa90bc970
a90bc970 bf820d0a bbed6930 00000001 a90bcc38 win32k!NtUserDispatchMessage+0x5a
a90bc9a4 0013fb70 00000023 bbc13cd0 bf82321c win32k!xxxWindowHitTest2+0xe6
a90bc9bc 00000000 00000000 00000000 00000000 0x13fb70



STACK_COMMAND:  kb


FOLLOWUP_IP:
pci!PciReadWriteConfigSpace+38
f7420ae0 ??              ???


SYMBOL_STACK_INDEX:  5


SYMBOL_NAME:  pci!PciReadWriteConfigSpace+38


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: pci


IMAGE_NAME:  pci.sys


DEBUG_FLR_IMAGE_TIMESTAMP:  480252bb


FAILURE_BUCKET_ID:  0x8E_pci!PciReadWriteConfigSpace+38


BUCKET_ID:  0x8E_pci!PciReadWriteConfigSpace+38


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


 


 

Alıntı
Topic starter Gönderildi : 01/06/2009 11:35
Murat GUCLU
(@muratguclu)
Üye

Merhaba;

Hangi uygulamaya çalıştırıken bu hatayı alıyorsun? OUTLOOK.EXE ile ilgili bir sıkıntı gibi gözüküyor. Tam hatanın kaynağını bulmak için full memory dump alıp. Microsoft tan symbols ları indirmen gerekir.

CevapAlıntı
Gönderildi : 03/06/2009 01:46
Paylaş: