Re: How to troubleshoot bugchecks on my own?

This is STATUS_ILLEGAL_INSTRUCTION. Don't know what's wrong, though.

"Armin Zingler" <az.nospam@xxxxxxxxxx> wrote in message
news:ePK8HCSUIHA.5980@xxxxxxxxxxxxxxxxxxxxxxx
Hi group,

I am looking for a starting point how to debug bugchecks on my own. I'm an
experienced developer, mainly several sorts of "Basic", but I don't have a
problem getting deeper into C and Assembler code (that I once did ~20
years
ago). I'd have to (and I am ready to) learn a lot. What I currently do
is load the full memory dump in Windbg and do the usual !anyalyze -v.
Before, I did set the symbol server path. What now? I know how to look up
the bugcheck codes, but what I am looking for is how to find out the
*reason* and the faulty part. I don't expect anyone to analyze it for me,
I'd do the work on my own. But, where to start? Do you have a link about
the "howto"?
Thanks! (Though, I appended the output below)

Armin



KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
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: 8057f39a, The address that the exception occurred at
Arg3: ba217c14, 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: nt!IopXxxControlFile+37e
8057f39a 85db test ebx,ebx

TRAP_FRAME: ba217c14 -- (.trap 0xffffffffba217c14)
ErrCode = 00000000
eax=88aaf7b8 ebx=88aaf7b8 ecx=804f0f18 edx=88aaf7b8 esi=888ba458
edi=89165d08
eip=8057f39a esp=ba217c88 ebp=ba217d00 iopl=0 nv up ei pl zr na pe
nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010246
nt!IopXxxControlFile+0x37e:
8057f39a 85db test ebx,ebx
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: explorer.exe

LAST_CONTROL_TRANSFER: from 804fe7e3 to 804f9f13

FAILED_INSTRUCTION_ADDRESS: nt!IopXxxControlFile+37e
8057f39a 85db test ebx,ebx

STACK_TEXT: ba2177dc 804fe7e3 0000008e c000001d 8057f39a
nt!KeBugCheckEx+0x1b
ba217ba4 80541415 ba217bc0 00000000 ba217c14 nt!KiDispatchException+0x3b1
ba217c0c 805413ae ba217d00 8057f39a badb0d00
nt!CommonDispatchException+0x4d
ba217c24 80544d2b 8887e210 ba217c44 ba217c78 nt!Kei386EoiHelper+0x172
ba217ce0 80534b99 ba217c88 ba21770c ffffffff nt!KiSwapContext+0x2f
ba217d34 805409ac 000005e0 000003e9 00000000 nt!ExReleaseResourceLite+0x8d
ba217d34 7c91eb94 000005e0 000003e9 00000000 nt!KiFastCallEntry+0xfc
01d2e964 7c91da69 7c831333 000005e0 000003e9 ntdll!KiFastSystemCallRet
01d2e968 7c831333 000005e0 000003e9 00000000 ntdll!ZwFsControlFile+0xc
01d2e9c8 77e60b48 000005e0 0014b8d8 00000a20
kernel32!TransactNamedPipe+0x4e
01d2e9f8 77e601ba 000010b0 00000a20 0014b8d8 RPCRT4!NMP_SyncSendRecv+0x54
01d2ea18 77e607b1 0014b8d8 00000a20 01d2eb30
RPCRT4!OSF_CCONNECTION::TransSendReceive+0x9e
01d2ea94 77e60731 10000000 0012e008 00000001
RPCRT4!OSF_CCONNECTION::SendFragment+0x226
01d2eaec 77e60593 00000000 000009f0 01d2eb30
RPCRT4!OSF_CCALL::SendNextFragment+0x1d2
01d2eb34 77e604e0 01d2ebb8 01d2eb74 00000001
RPCRT4!OSF_CCALL::FastSendReceive+0x144
01d2eb50 77e60a2f 01d2ebb8 01d2eb74 01d2ebb8
RPCRT4!OSF_CCALL::SendReceiveHelper+0x58
01d2eb7c 77e5aaf6 0014b8f0 01d2eb9c 77e5ab27
RPCRT4!OSF_CCALL::SendReceive+0x41
01d2eb88 77e5ab27 01d2ebb8 76e52c18 01d2ef94 RPCRT4!I_RpcSendReceive+0x24
01d2eb9c 77ed4675 01d2ebe4 0014c2e0 7c809920 RPCRT4!NdrSendReceive+0x2b
01d2ef78 76e56f36 76e52c18 76e52b8c 01d2ef94 RPCRT4!NdrClientCall2+0x222
01d2ef8c 76e56400 0012c888 01af37b0 000009e4
rasman!RasRpcSubmitRequest+0x1b
01d2efc8 76e55d97 00000000 01af37b0 000009e4
rasman!RemoteSubmitRequest+0x30
01d2efe0 76e570cb 00000000 01af37b0 000009e4 rasman!PutRequestInQueue+0x2b
01d2f024 76e54a18 00000000 00000039 00020000 rasman!SubmitRequest+0xd1
01d2f044 76ebba51 00000000 00020000 00000000
rasman!RasEnumConnectionPorts+0x2e
01d2f408 76ea715d 01d2f42c 01d2fbb8 01d2fb44
RASAPI32!SubEntryFromConnection+0x9e
01d2f8f8 763e2005 00020000 01d2f910 01d2fc08
RASAPI32!RasGetConnectStatusW+0xda
01d2fb48 76402861 00020000 01d2fbb8 01d2fc08
NETSHELL!HrRasGetNetconStatusFromRasConnectStatus+0x44
01d2fbc8 76400d32 01d2fbe4 01d2fc08 00180900
NETSHELL!CRasStatEngine::HrUpdateData+0x4e
01d2fbec 763fd7a4 01b2b5c0 01d2fc08 01d2fc8c
NETSHELL!CNetStatisticsEngine::UpdateStatistics+0x2d
01d2fc10 763fe7eb 029bf996 763fe7b5 01b29748
NETSHELL!CNetStatisticsCentral::RefreshStatistics+0x4e
01d2fc24 7e368734 00000000 00000113 000075f0
NETSHELL!CNetStatisticsCentral::TimerCallback+0x36
01d2fc50 7e369857 763fe7b5 00000000 00000113
USER32!InternalCallWinProc+0x28
01d2fcb8 7e369791 00000000 763fe7b5 00000000 USER32!UserCallWinProc+0xf3
01d2fd10 7e368a10 01d2fd68 00000000 01d2fd8c
USER32!DispatchMessageWorker+0x10e
01d2fd20 765c155a 01d2fd68 00000000 765c0000 USER32!DispatchMessageW+0xf
01d2fd8c 765c3746 765c0000 00000000 000a0110 stobject!SysTrayMain+0x177
01d2ffb4 7c80b683 00000000 00000000 00000000
stobject!CSysTray::SysTrayThreadProc+0x4f
01d2ffec 00000000 765c36f7 00000000 00000000 kernel32!BaseThreadStart+0x37


STACK_COMMAND: kb

FOLLOWUP_IP: nt!IopXxxControlFile+37e
8057f39a 85db test ebx,ebx

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 45e5484a

SYMBOL_NAME: nt!IopXxxControlFile+37e

FAILURE_BUCKET_ID: 0x8E_BAD_IP_nt!IopXxxControlFile+37e

BUCKET_ID: 0x8E_BAD_IP_nt!IopXxxControlFile+37e

Followup: MachineOwner



.

Relevant Pages

  • How to troubleshoot bugchecks on my own?
    ... This is a very common bugcheck. ... Some common problems are exception code 0x80000003. ... This will let us see why this breakpoint is ...
    (microsoft.public.win32.programmer.kernel)
  • Terminal Server 2008 BSOD
    ... I pasted bugcheck Analysis below. ... Some common problems are exception code 0x80000003. ... This will let us see why this breakpoint is ... Frame IP not in any known module. ...
    (microsoft.public.windows.server.general)
  • Re: WinXP stopping: error 0x8E
    ... Here is what an 0x8E bugcheck says. ... If it is your video card you can try some older drivers to see ... Some common problems are exception code 0x80000003. ...
    (microsoft.public.windowsxp.hardware)
Loading