If any one ever saw this stack trace, or have any idea or a lead for me,
or just willing to help me, please …
Thanks
FAULTING_IP:
nt!KiUnlinkThread+c
804e163c 8916 mov [esi],edx
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address
at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 73707249, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804e163c, address which referenced memory
Debugging Details:
WRITE_ADDRESS: 73707249
CURRENT_IRQL: 1c
FAULTING_IP:
nt!KiUnlinkThread+c
804e163c 8916 mov [esi],edx
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from 805360bf to 804e2a52
STACK_TEXT:
b79d6788 805360bf 00000003 b79d6ae4 00000000
nt!RtlpBreakWithStatusInstruction
b79d67d4 80536b96 00000003 73707249 804e163c
nt!KiBugCheckDebugBreak+0x19
b79d6bb4 804e0aac 0000000a 73707249 0000001c nt!KeBugCheck2+0x574
b79d6bb4 804e163c 0000000a 73707249 0000001c nt!KiTrap0E+0x238
b79d6c48 804e1690 8a008340 8a008348 00000000 nt!KiUnlinkThread+0xc
b79d6c5c 804e178c 00000001 b79d6c78 00000001 nt!KiUnwaitThread+0x12
b79d6c88 804ea21c e30ddeb0 89d681e8 89d68020 nt!KiWaitTest+0xab
b79d6ca0 80578972 8a008340 00000001 00000001 nt!KeReleaseSemaphore+0x52
b79d6d50 804dd99f 00000164 00b6f7b8 00b6f7b8
nt!NtRequestWaitReplyPort+0x5ff
b79d6d50 7c90eb94 00000164 00b6f7b8 00b6f7b8 nt!KiFastCallEntry+0xfc
00b6f79c 7c90e3ed 77e9dbdf 00000164 00b6f7b8 ntdll!KiFastSystemCallRet
00b6f7a0 77e9dbdf 00000164 00b6f7b8 00b6f7b8
ntdll!ZwRequestWaitReplyPort+0xc
00b6f8ec 77e9da7c 000d5d00 00008000 00000001
RPCRT4!LRPC_CASSOCIATION::ActuallyDoBinding+0x21e
00b6f964 77e7be9e 000d5d00 00b6f9ec 000d0dc4
RPCRT4!LRPC_CASSOCIATION::AllocateCCall+0x18c
00b6f9cc 77e7bdb0 00b6f9ec 76a9ec58 000d0dc4
RPCRT4!LRPC_BINDING_HANDLE::AllocateCCall+0x202
00b6f9f8 77e78dc9 000d0dc4 000d0df0 000d0df0
RPCRT4!LRPC_BINDING_HANDLE::NegotiateTransferSyntax+0xd3
00b6fa10 77e78e00 000d0dc4 00000000 00b6fa30
RPCRT4!I_RpcGetBufferWithObject+0x5b
00b6fa20 77e7942d 000d0dc4 000d0db0 00b6fdf0 RPCRT4!I_RpcGetBuffer+0xf
00b6fa30 77ef4595 000d0df0 000000e8 000d5d00 RPCRT4!NdrGetBuffer+0x28
00b6fdf0 76a9ebac 76a9ec08 76a9ebba 00b6fe0c
RPCRT4!NdrAsyncClientCall+0x1b6
00b6fe04 76a9eb74 000bcb28 000d5d00 000bcbc4 rpcss!RawRundownOid+0x18
00b6ff00 76a9e72f 000c9e10 00000012 00b6ff54
rpcss!CProcess::RundownOids+0x1a3
00b6ff38 76a9e7c8 00000012 00b6ff54 7c9106eb
rpcss!CServerOxid::RundownOids+0x37
00b6ffb4 7c80b50b 00000000 7c9106eb 000c7140
rpcss!ObjectExporterTaskThread+0x11d
00b6ffec 00000000 76a9e280 00000000 00000000
kernel32!BaseThreadStart+0x37
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nt!KiUnlinkThread+c
804e163c 8916 mov [esi],edx
FAULTING_SOURCE_CODE:
SYMBOL_STACK_INDEX: 4
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KiUnlinkThread+c
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77
FAILURE_BUCKET_ID: 0xA_W_VRF_nt!KiUnlinkThread+c
BUCKET_ID: 0xA_W_VRF_nt!KiUnlinkThread+c
Followup: MachineOwner
Get the latest news on SurfControl and our products,
subscribe to our monthly e-newsletter, SurfAdvisory at:
http://www.surfcontrol.com/resources/surfadvisory/surfadvisory_signup.aspx
*********************************************************************
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying, distribution or any action taken
or omitted to be taken in reliance on it, is prohibited and may be
unlawful. If you believe that you have received this email in error,
please contact the sender.
*********************************************************************