"STOP 0x0000001E" or "STOP 0x0000008E"
Posted 2009/05/21 09:28[원인]
운영체제가 지원하지 않는 고성능 CPU (대용량 L3 캐쉬를 포함한) 상에서 실행되어 발생한 문제점 같습니다.
[해결방법]
L3 캐시를 부팅 BIOS에서 Disable하거나 Windows 2003의 경우 SP1이상으로 업그레이드 하시기 바랍니다.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;924439
[참고]
DbgBreakPoint
Breakpoint는 Asynchronous Procedure Call (APC)가 발생하기 전에 Processor가 계속해서 code를 실행하는 경우에 발생하게 됩니다.
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 80000003, The exception code that was not handled
Arg2: 8045b2ec, The address that the exception occurred at
Arg3: 00000000, Parameter 0 of the exception
Arg4: bca17948, Parameter 1 of the exception
Debugging Details:
------------------
The call to LoadLibrary(kdextx86) failed, Win32 error 0n2
"지정된 파일을 찾을 수 없습니다."
Please check your debugger configuration and/or network access.
The call to LoadLibrary(kdextx86) failed, Win32 error 0n2
"지정된 파일을 찾을 수 없습니다."
Please check your debugger configuration and/or network access.
The call to LoadLibrary(kdextx86) failed, Win32 error 0n2
"지정된 파일을 찾을 수 없습니다."
Please check your debugger configuration and/or network access.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - .
FAULTING_IP:
nt!DbgBreakPoint+0
8045b2ec cc int 3
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: bca17948
DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
BUGCHECK_STR: 0x1E
PROCESS_NAME: LSASS.EXE
EXCEPTION_RECORD: ba948924 -- (.exr 0xffffffffba948924)
ExceptionAddress: 8045b2ec (nt!DbgBreakPoint)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 00000000
Parameter[1]: bca17948
Parameter[2]: 00000000
TRAP_FRAME: ba948978 -- (.trap 0xffffffffba948978)
ErrCode = 00000000
eax=00000001 ebx=8a52ca68 ecx=bca17948 edx=00000000 esi=00000000 edi=00000000
eip=8045b2ed esp=ba9489ec ebp=ba948a18 iopl=0 nv up ei pl nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000213
nt!DbgBreakPoint+0x1:
8045b2ed c3 ret
Resetting default scope
LAST_CONTROL_TRANSFER: from 8046be55 to 80430a18
STACK_TEXT:
ba948908 8046be55 ba948924 00000000 ba948978 nt!KiDispatchException+0x30e
ba948970 8046c44c 00000000 8ac631a8 8a52ca68 nt!CommonDispatchException+0x4d
ba948970 8045b2ed 00000000 8ac631a8 8a52ca68 nt!KiTrap03+0x98
ba9489e8 bca178b2 892381e0 892381c8 00000000 nt!DbgBreakPoint+0x1
ba948a44 bca14474 88db3028 00000005 bca0f796 afd!AfdAddressListQuery+0xa2
ba948a78 ba948a50 8048953c ba948ad0 80465a40 afd!AfdGetGroup+0x16c
WARNING: Frame IP not in any known module. Following frames may be wrong.
ba948a84 80465a3f 804008c0 ffffffff ba948ae0 0xba948a50
ba948b90 8045a69a 8047c4c0 8a2d2a40 8aa65a80 nt!_except_handler2+0xb7
ba948c14 804b6990 fe9590e4 00000000 fe959008 nt!PsReturnPoolQuota+0xe2
ba948c78 804543c6 8aa66668 804543e0 ba948d64 nt!IopSynchronousServiceTail+0x60
ba948d34 8046b339 0000135c 000013a4 00000000 nt!ObReferenceObjectByHandle+0x1c2
ba948d34 77f88403 0000135c 000013a4 00000000 nt!KiSystemService+0xc9
00f9f680 74f44141 0000135c 000013a4 00000000 ntdll!ZwDeviceIoControlFile+0xb
00f9f6fc 74f44dfa 0000135c 0d7483f0 00000010 msafd!WSPBind+0x162
00f9f7b8 74f44c6a 0000135c 0fdd3118 00000010 msafd!SockDoConnect+0x243
00f9f7e8 74fac21d 0000135c 0fdd3118 00000010 msafd!WSPConnect+0xb8
00f9f834 779689c3 0000135c 0fdd3118 00000010 WS2_32!connect+0x64
00f9f854 779654d8 0fdd3108 0302cad3 00000001 DNSAPI!Dns_OpenTcpConnectionAndSend+0x4f
00f9f92c 7796570a 00f9f9c4 00002000 0dc92e90 DNSAPI!Dns_NegotiateTkeyWithServer+0x247
00f9f9c8 77965959 0fdcf0a8 0fddd008 00000000 DNSAPI!Dns_DoSecureUpdate+0xcb
00f9fa6c 7796b145 0fdcf0a8 0fddd008 00000000 DNSAPI!Dns_DoSecureUpdate+0x31a
00f9fac0 7796149d 0dc8d278 00002000 0dc93450 DNSAPI!Dns_UpdateLib+0x109
00f9faec 7795e4d5 0dc8d278 00002000 0dcbb2b8 DNSAPI!DnsUpdate+0x4c
00f9fb10 7795e433 00000000 0dc8d278 00002000 DNSAPI!DoQuickUpdateEx+0x1e
00f9fe5c 7795fb87 0dc8d278 00002000 00000000 DNSAPI!DoQuickUpdate+0x1ad
00f9fe88 7795fc02 00f9fed8 00000000 00002000 DNSAPI!modifyRecordsInSetPrivate+0xc3
00f9feac 7651f6ea 00f9fed8 00000000 00002000 DNSAPI!DnsModifyRecordsInSet_UTF8+0x1c
00f9ff24 7651f968 000f6620 00000001 000f6620 netlogon!NlDnsUpdate+0x11d
00f9ff3c 765203d9 00f9ff94 000f6620 00f9ff88 netlogon!NlDnsRegisterOne+0x62
00f9ff60 765204f4 00f9ff94 000f6620 00f9ff88 netlogon!NlDnsScavengeOne+0x58
00f9ff9c 7655bb91 00000000 00000000 00000038 netlogon!NlDnsScavengeWorker+0x111
00f9ffb4 77e5b3bc 00000000 00000000 00000038 netlogon!NlWorkerThread+0x94
00f9ffec 00000000 7655bafb 00000000 00000000 KERNEL32!BaseThreadStart+0x52
STACK_COMMAND: kb
FOLLOWUP_IP:
afd!AfdAddressListQuery+a2
bca178b2 e9e4b8ffff jmp afd!AfdJoinLeaf+0x47 (bca1319b)
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: afd!AfdAddressListQuery+a2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: afd
IMAGE_NAME: afd.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 425aeca9
FAILURE_BUCKET_ID: 0x1E_afd!AfdAddressListQuery+a2
BUCKET_ID: 0x1E_afd!AfdAddressListQuery+a2
Followup: MachineOwner
---------
1: kd> .exr 0xffffffffba948924
ExceptionAddress: 8045b2ec (nt!DbgBreakPoint)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 00000000
Parameter[1]: bca17948
Parameter[2]: 00000000
1: kd> .trap 0xffffffffba948978
ErrCode = 00000000
eax=00000001 ebx=8a52ca68 ecx=bca17948 edx=00000000 esi=00000000 edi=00000000
eip=8045b2ed esp=ba9489ec ebp=ba948a18 iopl=0 nv up ei pl nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000213
nt!DbgBreakPoint+0x1:
8045b2ed c3 ret
1: kd> lmvm afd
start end module name
bca00000 bca1f140 afd (pdb symbols) DownstreamStore\afd.pdb\4247F9041\afd.pdb
Loaded symbol image file: DownstreamStore\afd.dbg\425AECA91f140\afd.dbg
Image path: \SystemRoot\System32\drivers\afd.sys
Image name: afd.sys
Timestamp: Tue Apr 12 06:31:21 2005 (425AECA9)
CheckSum: 000275B2
ImageSize: 0001F140
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
1: kd> dd bca00000
bca00000 00905a4d 00000003 00000004 0000ffff
bca00010 000000b8 00000000 00000040 00000000
bca00020 00000000 00000000 00000000 00000000
bca00030 00000000 00000000 00000000 000000c0
bca00040 0eba1f0e cd09b400 4c01b821 685421cd
bca00050 70207369 72676f72 63206d61 6f6e6e61
bca00060 65622074 6e757220 206e6920 20534f44
bca00070 65646f6d 0a0d0d2e 00000024 00000000
'프로그래밍 > Debugging' 카테고리의 다른 글
| 프로세스 디버깅 하기 (0) | 2009/07/24 |
|---|---|
| Crash Dump 발생시 기본 체크 사항들 (0) | 2009/07/24 |
| "STOP 0x0000001E" or "STOP 0x0000008E" (0) | 2009/05/21 |
| Bugcheck 9F (0) | 2009/04/20 |
| 원격지에서 직접 커널 혹은 유저 모드 디버깅 하기 (0) | 2009/04/20 |
| [Windbg] 실시간 커널 디버깅 하기 (0) | 2009/04/20 |
- Filed under : 프로그래밍/Debugging
- Tag : 0x0000001E, 0x0000008E, Bugcheck, Debug, error code
- Comment Trackback
