none
.NET Service is crash --The memory could not be %s RRS feed

  • 问题

  • DumpFile contains important information, so is hard to transfer to internet.

    I hope the commity can tell me method to analyze  the problem

    I use Windbg Command "!analyze -v", the result is below.  

    FAULTING_IP: 

    clr!CopyPDBs+1fc09
    000007fe`f9a8e29d 4c8901          mov     qword ptr [rcx],r8

    EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
    ExceptionAddress: 000007fef9a8e29d (clr!CopyPDBs+0x000000000001fc09)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000001
    NumberParameters: 2
       Parameter[0]: 0000000000000001
       Parameter[1]: 000000001fef0000
    Attempt to write to address 000000001fef0000

    PROCESS_NAME:  xxx.xxx.Async.CacheUpdateService.Car3.exe

    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.

    MODULE_NAME: clr

    FAULTING_MODULE: 0000000076e40000 ntdll

    DEBUG_FLR_IMAGE_TIMESTAMP:  4ba21eeb

    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:  0000000000000001

    EXCEPTION_PARAMETER2:  000000001fef0000

    WRITE_ADDRESS:  000000001fef0000 

    FOLLOWUP_IP: 
    clr!CopyPDBs+1fc09
    000007fe`f9a8e29d 4c8901          mov     qword ptr [rcx],r8

    FAULTING_THREAD:  0000000000096b90

    BUGCHECK_STR:  APPLICATION_FAULT_INVALID_POINTER_WRITE_WRONG_SYMBOLS

    PRIMARY_PROBLEM_CLASS:  INVALID_POINTER_WRITE

    DEFAULT_BUCKET_ID:  INVALID_POINTER_WRITE

    LAST_CONTROL_TRANSFER:  from 000007fef9a8e283 to 000007fef9a8e29d

    STACK_TEXT:  
    00000000`1feed8e8 000007fe`f9a8e283 : 00000000`0000003f 00000000`00000000 00000000`001216d8 00000000`001216d0 : clr!CopyPDBs+0x1fc09
    00000000`1feed8f0 0057005c`003a0043 : 006f0064`006e0069 0073005c`00730077 00650074`00730079 005c0032`0033006d : clr!CopyPDBs+0x1fbef
    00000000`1feedd40 006f0064`006e0069 : 0073005c`00730077 00650074`00730079 005c0032`0033006d 00330065`006c006f : 0x57005c`003a0043
    00000000`1feedd48 0073005c`00730077 : 00650074`00730079 005c0032`0033006d 00330065`006c006f 006c0064`002e0032 : 0x6f0064`006e0069
    00000000`1feedd50 00650074`00730079 : 005c0032`0033006d 00330065`006c006f 006c0064`002e0032 00000000`0000006c : 0x73005c`00730077
    00000000`1feedd58 005c0032`0033006d : 00330065`006c006f 006c0064`002e0032 00000000`0000006c 00000000`00000000 : 0x650074`00730079
    00000000`1feedd60 00330065`006c006f : 006c0064`002e0032 00000000`0000006c 00000000`00000000 8c00002f`71c04733 : 0x5c0032`0033006d
    00000000`1feedd68 006c0064`002e0032 : 00000000`0000006c 00000000`00000000 8c00002f`71c04733 0057005c`003a0043 : 0x330065`006c006f
    00000000`1feedd70 00000000`0000006c : 00000000`00000000 8c00002f`71c04733 0057005c`003a0043 006f0064`006e0069 : 0x6c0064`002e0032
    00000000`1feedd78 00000000`00000000 : 8c00002f`71c04733 0057005c`003a0043 006f0064`006e0069 0073005c`00730077 : 0x6c


    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  clr!CopyPDBs+1fc09

    FOLLOWUP_NAME:  MachineOwner

    IMAGE_NAME:  clr.dll

    STACK_COMMAND:  ~50s; .ecxr ; kb

    BUCKET_ID:  WRONG_SYMBOLS

    FAILURE_BUCKET_ID:  INVALID_POINTER_WRITE_c0000005_clr.dll!CopyPDBs

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

    ---------------------------------------------------------------------------------------------------------------------

    0:050> !clrstack
    OS Thread Id: 0x96b90 (50)
    Failed to start stack walk: 80070057

    ---------------------------------------------------------------------------------------------------------------------

    0:050> !dumpstack
    OS Thread Id: 0x96b90 (50)
    Current frame: clr!CopyPDBs+0x1fc09
    Child-SP         RetAddr          Caller, Callee
    000000001feed8e0 000007fef9a8e283 clr!CopyPDBs+0x1fbef, calling clr!CopyPDBs+0x1fbf8

    • 已编辑 liaoqs 2017年5月11日 2:59
    2017年5月11日 2:41

全部回复

  • 你好,

    请问这个.Net Service,是你自定义的Service 吗? 可以通过Debug 来重现你的问题吗?

    Best regards,

    Cole Wu


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    2017年5月11日 8:43
    版主
  • 是我自己的,  是偶发, 但是当一台机器同时部署多个这样的服务,频率会高些。

    开发语言用的是C# ,   framework是 4.0

    服务是无法单独运行的, 里面涉及到消息、缓存的IO



    • 已编辑 liaoqs 2017年5月11日 10:49
    2017年5月11日 10:43
  • 是我自己的,  是偶发, 但是当一台机器同时部署多个这样的服务,频率会高些。

    开发语言用的是C# ,   framework是 4.0

    服务是无法单独运行的, 里面涉及到消息、缓存的IO

    2017年5月12日 1:08
  • 你好,

    我建议在你的服务中加一下日志(比如使用log4Net). 看看是哪行代码出错了, 还有相关的入参, 详细的错误信息,这样可以更好的定位错误。

    Best regards,

    Cole Wu


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    2017年5月12日 1:35
    版主
  • !analyze -v  显示是第50个线程引起,但是第50个线程托管代码的栈都没有。  如果是托管代码出错,导致Crash这就简单了。

    0:050> !clrstack
    OS Thread Id: 0x96b90 (50)
    Failed to start stack walk: 80070057

    ---------------------------------------------------------------------------------------------------------------------

    0:050> !dumpstack
    OS Thread Id: 0x96b90 (50)
    Current frame: clr!CopyPDBs+0x1fc09
    Child-SP         RetAddr          Caller, Callee
    000000001feed8e0 000007fef9a8e283 clr!CopyPDBs+0x1fbef, calling clr!CopyPDBs+0x1fbf8

    2017年5月12日 10:57
  • 你好,

    你有没有试过 Carl Fan 提供的解决方案?

    https://social.technet.microsoft.com/Forums/windows/en-US/ba3daf69-6323-4604-bf27-909aa222d27b/my-net-service-is-crash-the-memory-could-not-be-s?forum=w7itproperf

    Best regards,

    Cole Wu


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    2017年5月18日 6:39
    版主