none
Access violation - code c0000005 RRS feed

  • Question

  • Access violation - code c0000005 (first/second chance not available)
    eax=00000000 ebx=00000001 ecx=00000000 edx=00000000 esi=451d3800 edi=06472670
    eip=1d233bd7 esp=348ae574 ebp=348ae5a0 iopl=0         nv up ei pl zr na pe nc
    cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    1d233bd7 3909            cmp     dword ptr [ecx],ecx  ds:002b:00000000=????????

    0:048> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Exception Analysis                                   *
    *                                                                             *
    *******************************************************************************

    *** WARNING: Unable to verify checksum for System.Web.ni.dll
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for kernel32.dll -
    ***** OS (WOW64 kernel32) symbols are WRONG. Please fix symbols to do analysis.

    *** WARNING: Unable to verify checksum for mscorlib.ni.dll
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ole32.dll -
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for TpiClient.dll -
    *** WARNING: Unable to verify checksum for CjnStrObject.dll
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for CjnStrObject.dll -
    *** WARNING: Unable to verify checksum for System.ni.dll
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for FTSClient.dll -
    *** WARNING: Unable to verify checksum for System.Web.RegularExpressions.ni.dll
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for TPIExtClient.dll -
    *** WARNING: Unable to verify checksum for System.Xml.ni.dll
    *** WARNING: Unable to verify checksum for System.Data.ni.dll
    *** WARNING: Unable to verify checksum for TpiNewSearchCtrl.DLL
    GetPageUrlData failed, server returned HTTP status 404
    URL requested: http://watson.microsoft.com/StageOne/w3wp_exe/7_5_7601_17514/4ce7a5f8/unknown/0_0_0_0/bbbbbbb4/c0000005/1d233bd7.htm?Retriage=1

    FAULTING_IP:
    +191296
    1d233bd7 3909            cmp     dword ptr [ecx],ecx

    EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
    ExceptionAddress: 1d233bd7
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 00000000
       Parameter[1]: 00000000
    Attempt to read from address 00000000

    PROCESS_NAME:  w3wp.exe

    MODULE_NAME: System_Web_ni

    FAULTING_MODULE: 76920000 kernel32

    DEBUG_FLR_IMAGE_TIMESTAMP:  4ef6cb6f

    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    EXCEPTION_PARAMETER1:  00000000

    EXCEPTION_PARAMETER2:  00000000

    READ_ADDRESS:  00000000

    FOLLOWUP_IP:
    System_Web_ni+191296
    71ab1296 c745e400000000  mov     dword ptr [ebp-1Ch],0

    FAILED_INSTRUCTION_ADDRESS:
    +51702faf0484dbe8
    1d233bd7 3909            cmp     dword ptr [ecx],ecx

    MOD_LIST: <ANALYSIS/>

    NTGLOBALFLAG:  0

    APPLICATION_VERIFIER_FLAGS:  0

    IP_ON_HEAP:  1d233663
    The fault address in not in any loaded module, please check your build's rebase
    log at <releasedir>\bin\build_logs\timebuild\ntrebase.log for module which may
    contain the address if it were loaded.

    MANAGED_STACK:
    (TransitionMU)
    348AE574 1D233BD7 TpiNewSearchCtrl!TPI.Web.UI.WebControls.SearchCondition.PutKeyWordToSession(System.String)+0x77
    348AE5A8 1D233663 TpiNewSearchCtrl!TPI.Web.UI.WebControls.SearchCondition.BuildSearchWordCondition(System.String ByRef, System.String ByRef, System.String, System.String)+0xd3
    348AE5EC 1D2320AC TpiNewSearchCtrl!TPI.Web.UI.WebControls.SearchCondition.GetSearchConditionByXmlNode(System.Xml.XmlNodeList)+0xd2c
    348AE73C 1D231200 TpiNewSearchCtrl!TPI.Web.UI.WebControls.SearchCondition.GetAttatchCondition()+0x58
    348AE74C 1D23117F TpiNewSearchCtrl!TPI.Web.UI.WebControls.SearchCondition.ConstructCondition()+0x2f
    348AE758 1D231057 TpiNewSearchCtrl!TPI.Web.UI.WebControls.SearchCondition.GetSearchCondition(TPI.CommonFunc.ISearchCondition ByRef, System.String ByRef, Boolean ByRef)+0x37
    348AE774 1D230DFA TpiNewSearchCtrl!TPI.Web.UI.WebControls.TPINewSearchCtrl.GetSqlForNoSearch(System.String, System.String ByRef, Boolean)+0x10a
    348AE794 0160DBB2 KNS!KNS.Logic.SearchHelper.ExecuteSearch(TPI.Web.UI.WebControls.TPINewSearchCtrl)+0x2fa
    348AE7D4 0160D120 KNS!KNS.request.SearchHandler.ExecuteSearch()+0x28
    348AE7E4 0160D0D6 KNS!KNS.request.SearchHandler.ProcessRequest(System.Web.HttpContext)+0x8e
    348AE7F8 71AB1296 System_Web_ni!System.Web.HttpApplication+CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()+0xb6
    348AE82C 71A83AAC System_Web_ni!System.Web.HttpApplication.ExecuteStep(IExecutionStep, Boolean ByRef)+0x4c
    348AE86C 7207CB6A System_Web_ni!System.Web.HttpApplication+PipelineStepManager.ResumeSteps(System.Exception)+0x48a
    (TransitionUM)
    (TransitionMU)
    348AE914 7205D2D1 System_Web_ni!System.Web.HttpRuntime.ProcessRequestNotificationPrivate(System.Web.Hosting.IIS7WorkerRequest, System.Web.HttpContext)+0x1fd
    348AE984 721322C6 System_Web_ni!System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr, IntPtr, IntPtr, Int32)+0x212
    (TransitionUM)
    (TransitionMU)
    348AEEE4 72132373 System_Web_ni!System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr, IntPtr, IntPtr, Int32)+0x2bf
    348AEF6C 7213208F System_Web_ni!System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr, IntPtr, IntPtr, Int32)+0x27
    (TransitionUM)

    MANAGED_STACK_COMMAND:  _EFN_StackTrace

    LAST_CONTROL_TRANSFER:  from 1d233663 to 1d233bd7

    ADDITIONAL_DEBUG_TEXT:  
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. ; Followup set based on attribute [Is_ChosenCrashFollowupThread] from Frame:[0] on thread:[PSEUDO_THREAD]

    FAULTING_THREAD:  ffffffff

    BUGCHECK_STR:  APPLICATION_FAULT_NULL_INSTRUCTION_PTR_NULL_POINTER_READ_WRONG_SYMBOLS

    PRIMARY_PROBLEM_CLASS:  NULL_INSTRUCTION_PTR

    DEFAULT_BUCKET_ID:  NULL_INSTRUCTION_PTR

    FRAME_ONE_INVALID: 1

    STACK_TEXT:  
    348ae574 1d233bd7 tpinewsearchctrl!TPI.Web.UI.WebControls.SearchCondition.PutKeyWordToSession+0x77
    348ae5a8 1d233663 tpinewsearchctrl!TPI.Web.UI.WebControls.SearchCondition.BuildSearchWordCondition+0xd3
    348ae5ec 1d2320ac tpinewsearchctrl!TPI.Web.UI.WebControls.SearchCondition.GetSearchConditionByXmlNode+0xd2c
    348ae73c 1d231200 tpinewsearchctrl!TPI.Web.UI.WebControls.SearchCondition.GetAttatchCondition+0x58
    348ae74c 1d23117f tpinewsearchctrl!TPI.Web.UI.WebControls.SearchCondition.ConstructCondition+0x2f
    348ae758 1d231057 tpinewsearchctrl!TPI.Web.UI.WebControls.SearchCondition.GetSearchCondition+0x37
    348ae774 1d230dfa tpinewsearchctrl!TPI.Web.UI.WebControls.TPINewSearchCtrl.GetSqlForNoSearch+0x10a
    348ae794 0160dbb2 kns!KNS.Logic.SearchHelper.ExecuteSearch+0x2fa
    348ae7d4 0160d120 kns!KNS.request.SearchHandler.ExecuteSearch+0x28
    348ae7e4 0160d0d6 kns!KNS.request.SearchHandler.ProcessRequest+0x8e
    348ae7f8 71ab1296 system_web_ni!System.Web.HttpApplication_CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute+0xb6
    348ae82c 71a83aac system_web_ni!System.Web.HttpApplication.ExecuteStep+0x4c
    348ae86c 7207cb6a system_web_ni!System.Web.HttpApplication_PipelineStepManager.ResumeSteps+0x48a
    348ae914 7205d2d1 system_web_ni!System.Web.HttpRuntime.ProcessRequestNotificationPrivate+0x1fd
    348ae984 721322c6 system_web_ni!System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper+0x212
    348aeee4 72132373 system_web_ni!System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper+0x2bf
    348aef6c 7213208f system_web_ni!System.Web.Hosting.PipelineRuntime.ProcessRequestNotification+0x27


    SYMBOL_STACK_INDEX:  a

    SYMBOL_NAME:  system_web_ni!System.Web.HttpApplication_CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute+191296

    FOLLOWUP_NAME:  MachineOwner

    IMAGE_NAME:  System.Web.ni.dll

    STACK_COMMAND:  _EFN_StackTrace ; ** Pseudo Context ** ; kb

    BUCKET_ID:  WRONG_SYMBOLS

    FAILURE_BUCKET_ID:  NULL_INSTRUCTION_PTR_c0000005_System.Web.ni.dll!System.Web.HttpApplication_CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute

    WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/w3wp_exe/7_5_7601_17514/4ce7a5f8/unknown/0_0_0_0/bbbbbbb4/c0000005/1d233bd7.htm?Retriage=1

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

    Friday, September 27, 2013 7:48 AM

Answers

  • I don't think you have just one problem.  The problem where it fails after days is probably due to the server going off line for backups.   I don't think you are actually connecting when it crashes after a few seconds.  There may be an existing connection that is prohibiting a new connection or the server may not be responding.  There are two eay things you can try to find the short problems

    1) Before making a new connection check the status of existng connection using the following cmd.exe command

    Netstat -a               -  this will list the port numbers and server that you are connected to

    2) Trace the connection using a sniffer like wireshark or fiddler.


    jdweng

    Monday, September 30, 2013 11:57 AM

All replies

  • The stack trace seems to have the most information.  Perhaps the keyword is null?  It seems like a possibility based on this code.  Could also be something wrong with the cookies. Hard to tell from just the dump though.  The debugger will make this more clear.

    Run your application in the debugger and when you get your exception at SearchCondition.PutKeyWordToSession start doing some more detective work to figure out exactly what happened.  

    Friday, September 27, 2013 12:17 PM
  • I have got more dumps in the last two days. But it seems different position cause this exception happened.

    Here are some stacks .

    1a86f1dc 7404a733 30526c20 30243bdc 014e77c8 mscorwks!CorExitProcess+0x6ae5
    1a86f1f8 74049ec2 30526c20 2fa7cc98 1a86f5f4 mscorwks!CorExitProcess+0xa31d
    1a86f224 73fbe126 3465e764 30526c20 00000001 mscorwks!CorExitProcess+0x9aac
    1a86f23c 73fbe0f8 74046068 3465e764 1a86f954 mscorwks!GetMetaDataInternalInterface+0xcdbb
    1a86f258 73fbd09d 1a86f920 3465e764 00000001 mscorwks!GetMetaDataInternalInterface+0xcd8d
    1a86f36c 73fbcdb6 1a86f5f4 1a86f398 00000000 mscorwks!GetMetaDataInternalInterface+0xbd32
    1a86f3c8 73f7aacf 1d13b02c 1a86f920 00000000 mscorwks!GetMetaDataInternalInterface+0xba4b
    1a86f3dc 73f792cd 1a86f468 73fbccae 1a86f920 mscorwks!CreateAssemblyNameObject+0x12a40
    1a86f5c0 73f7973f 2a3b7a70 1a86f920 73f7973f mscorwks!CreateAssemblyNameObject+0x1123e
    1a86f8fc 73fbcbac 73fbccae 1a86f920 00000500 mscorwks!CreateAssemblyNameObject+0x116b0
    1a86f92c 74045cad 2a3b7a70 00000001 00000002 mscorwks!GetMetaDataInternalInterface+0xb841
    1a86f978 74045374 00000001 00000000 014e8468 mscorwks!CorExitProcess+0x5897
    1a86f9a4 7404571e 00000000 ffffffff 014e8468 mscorwks!CorExitProcess+0x4f5e
    1a86f9c4 7404529f 00000000 00000000 014e8468 mscorwks!CorExitProcess+0x5308
    1a86f9e8 74011172 1a86fa00 1a86fa2c 1a86fa50 mscorwks!CorExitProcess+0x4e89
    1a86fafc 769333aa 014e8468 1a86fb48 77399ef2 mscorwks!IEE+0x3e9e
    1a86fb08 77399ef2 014e8468 56f6af62 00000000 kernel32!BaseThreadInitThunk+0x12
    1a86fb48 77399ec5 74011124 014e8468 ffffffff ntdll!__RtlUserThreadStart+0x70
    1a86fb60 00000000 74011124 014e8468 00000000 ntdll!_RtlUserThreadStart+0x1b

    0:041> !clrstack
    OS Thread Id: 0xbf8 (41)
    ESP       EIP     
    1d57e920 1cb59ac1 KNet.NNS.Monitor.Log.tryGet(System.Collections.Specialized.NameValueCollection, System.String)
    1d57e950 1cb5976b KNet.NNS.Monitor.Log..ctor(System.Web.HttpContext)
    1d57e9c0 1cb5962c KNet.NNS.Monitor.LoggingService.WriteLog()
    1d57e9e8 1cb5907c KNet.NNS.Monitor.LoggingService.Process()
    1d57e9fc 1cb58f77 KNet.NNS.Monitor.FilterModule.context_EndRequest(System.Object, System.EventArgs)
    1d57ea28 7082ffc5 System.Web.HttpApplication+SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
    1d57ea40 70823aac System.Web.HttpApplication.ExecuteStep(IExecutionStep, Boolean ByRef)
    1d57ea80 70e1cb6a System.Web.HttpApplication+PipelineStepManager.ResumeSteps(System.Exception)
    1d57ea84 70e137dc [InlinedCallFrame: 1d57ea84]
    1d57eb28 70dfd2d1 System.Web.HttpRuntime.ProcessRequestNotificationPrivate(System.Web.Hosting.IIS7WorkerRequest, System.Web.HttpContext)
    1d57eb98 70ed22c6 System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr, IntPtr, IntPtr, Int32)
    1d57eb9c 70ed208f [InlinedCallFrame: 1d57eb9c]
    1d57f0e4 00d2237c [NDirectMethodFrameStandalone: 1d57f0e4] System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr, System.Web.RequestNotificationStatus ByRef)
    1d57f0f4 70ed2373 System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr, IntPtr, IntPtr, Int32)
    1d57f17c 70ed208f System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr, IntPtr, IntPtr, Int32)
    1d57f27c 00d2237c [ContextTransitionFrame: 1d57f27c]

    0:033> !clrstack
    OS Thread Id: 0xe70 (33)
    ESP       EIP     
    1c79e864 01892e0c TPI.CommonFunc.DBClass.BuildConnect()
    1c79e8a8 018925d4 KNS.Global.Session_Start(System.Object, System.EventArgs)
    1c79e8e8 70541735 System.Web.SessionState.SessionStateModule.RaiseOnStart(System.EventArgs)
    1c79e8f8 6fcdba2e System.Web.SessionState.SessionStateModule.CompleteAcquireState()
    1c79e924 6fcdb699 System.Web.SessionState.SessionStateModule.BeginAcquireState(System.Object, System.EventArgs, System.AsyncCallback, System.Object)
    1c79e97c 6fd00ce3 System.Web.HttpApplication+AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
    1c79e990 6fcd3afc System.Web.HttpApplication.ExecuteStep(IExecutionStep, Boolean ByRef)
    1c79e9d0 702ccb6a System.Web.HttpApplication+PipelineStepManager.ResumeSteps(System.Exception)
    1c79e9d4 702c37dc [InlinedCallFrame: 1c79e9d4]
    1c79ea78 702ad2d1 System.Web.HttpRuntime.ProcessRequestNotificationPrivate(System.Web.Hosting.IIS7WorkerRequest, System.Web.HttpContext)
    1c79eae8 703822c6 System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr, IntPtr, IntPtr, Int32)
    1c79eaec 7038208f [InlinedCallFrame: 1c79eaec]
    1c79f034 00c723fb [NDirectMethodFrameStandalone: 1c79f034] System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr, System.Web.RequestNotificationStatus ByRef)
    1c79f044 70382373 System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr, IntPtr, IntPtr, Int32)
    1c79f0cc 7038208f System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr, IntPtr, IntPtr, Int32)
    1c79f1cc 00c723fb [ContextTransitionFrame: 1c79f1cc]

    Both in managed thread and native mscorwks threads may cause exception.

    Is this means the hardware (memory , disk I/O) error cause this happened?

    Sunday, September 29, 2013 4:31 AM
  • It looks like you are having issues with an http application.  I would start by using a sniffer like wireshark or fiddler to trace the IP messages to see if a bad message (http request or response) is the root cause of the problem.

    Is the problem occuring randomly or after the session has been running for a long period of time?  sometimes server shut down for maintenace or shutdown when a session is inactive and can cause exception like this.  to prevent a idle seesion from shutdown the interface having the client impliment the "keep alive" mode will help.


    jdweng

    Sunday, September 29, 2013 7:07 AM
  • not after session running long time, yesterday is crash 3 times, the process up-time are 7, 11 and 5 seconds, and days before it running a long time.
    Monday, September 30, 2013 3:29 AM
  • I don't think you have just one problem.  The problem where it fails after days is probably due to the server going off line for backups.   I don't think you are actually connecting when it crashes after a few seconds.  There may be an existing connection that is prohibiting a new connection or the server may not be responding.  There are two eay things you can try to find the short problems

    1) Before making a new connection check the status of existng connection using the following cmd.exe command

    Netstat -a               -  this will list the port numbers and server that you are connected to

    2) Trace the connection using a sniffer like wireshark or fiddler.


    jdweng

    Monday, September 30, 2013 11:57 AM