none
What does KERNELBASE!RaiseException+0x39 mean? And how does it happen? RRS feed

  • Question

  • Hello.

    I've developed an application in C# that runs in Windows Server 2008 R2 (enterprise service pack 1).

    I use WinDiag to capture the dump file when the program crashes, and get following information by WinDbg.

    And I've captured several First-Chance-Exception dump files.

    First_Chance_Exception_0X406D1388:

    CONTEXT:  (.ecxr)
    rax=00000000c349e712 rbx=000000000000000e rcx=0000000026b4f300
    rdx=00000000000000b0 rsi=0000000000000048 rdi=000000007751f5ac
    rip=000007fefd16a06d rsp=0000000026b4f910 rbp=0000000026b4fa00
     r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
    r11=0000000026b4f950 r12=0000000020b01490 r13=0000000000000001
    r14=0000000020b015a8 r15=0000000020b01480
    iopl=0         nv up ei pl nz na po nc
    cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000204
    KERNELBASE!RaiseException+0x39:
    000007fe`fd16a06d 4881c4c8000000  add     rsp,0C8h
    Resetting default scope
    
    FAULTING_IP: 
    KERNELBASE!RaiseException+39
    000007fe`fd16a06d 4881c4c8000000  add     rsp,0C8h
    
    EXCEPTION_RECORD:  (.exr -1)
    ExceptionAddress: 000007fefd16a06d (KERNELBASE!RaiseException+0x0000000000000039)
       ExceptionCode: 406d1388 (Visual C++ exception)
      ExceptionFlags: 00000000
    NumberParameters: 3
       Parameter[0]: 0000000000001000
       Parameter[1]: 000007fed9b75338
       Parameter[2]: 00000000ffffffff
    
    DEFAULT_BUCKET_ID:  APPLICATION_FAULT

    My application is still able to run until access violation exception occurs.

    I have no idea what happen to it.

    Second_Chance_Exception_C0000005:

    CONTEXT:  (.ecxr)
    rax=0000000035ffffef rbx=0000000000000001 rcx=0000000031d0dc70
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=000007feea24e8f5 rsp=000000002b3bf568 rbp=00000000000000fa
     r8=00000000d7ffffbc  r9=000000002086e170 r10=00000000000003e8
    r11=0000000094000022 r12=0000000000000001 r13=0000000000000004
    r14=0000000000000000 r15=00000000300cc8a0
    iopl=0         nv up ei pl zr na po nc
    cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010244
    vray!PluginManagerUtilsBase::getFactory+0x3ff55:
    000007fe`ea24e8f5 4d8b14c1        mov     r10,qword ptr [r9+rax*8] ds:00000001`d086e0e8=????????????????
    Resetting default scope
    
    FAULTING_IP: 
    vray!PluginManagerUtilsBase::getFactory+3ff55
    000007fe`ea24e8f5 4d8b14c1        mov     r10,qword ptr [r9+rax*8]
    
    EXCEPTION_RECORD:  (.exr -1)
    ExceptionAddress: 000007feea24e8f5 (vray!PluginManagerUtilsBase::getFactory+0x000000000003ff55)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 00000001d086e0e8
    Attempt to read from address 00000001d086e0e8
    
    DEFAULT_BUCKET_ID:  INVALID_POINTER_READ

    How should I resolve this problem?

    Any help is appreciated!

    Tuesday, January 30, 2018 3:33 AM

Answers

  • FAIK exception 0X406D1388 is associated with a call to SetThreadName( DWORD dwThreadID, LPCSTR szThreadName), which should be begnin.
    Details:
    Naming threads in Win32 And .Net
    https://blogs.msdn.microsoft.com/stevejs/2005/12/20/naming-threads-in-win32-and-net/

    With kind regards
    • Marked as answer by Keaghen Wednesday, January 31, 2018 8:06 AM
    Tuesday, January 30, 2018 11:10 AM

All replies

  • I also did something like this to try to catch this exception in the program. But it doesn't help.
    <configuration> 
    
    <runtime> 
    
    <legacyUnhandledExceptionPolicy enabled="true" /> 
    
    </runtime> 
    
    </configuration> 
    AppDomain.CurrentDomain.UnhandledException += new UnhandledExceptionEventHandler(CurrentDomain_UnhandledException);


    Tuesday, January 30, 2018 3:54 AM
  • FAIK exception 0X406D1388 is associated with a call to SetThreadName( DWORD dwThreadID, LPCSTR szThreadName), which should be begnin.
    Details:
    Naming threads in Win32 And .Net
    https://blogs.msdn.microsoft.com/stevejs/2005/12/20/naming-threads-in-win32-and-net/

    With kind regards
    • Marked as answer by Keaghen Wednesday, January 31, 2018 8:06 AM
    Tuesday, January 30, 2018 11:10 AM
  • Really thanks for your help.

    Still I do not find what exactly the reason is, at least it gives me a better understanding of the problem.

    Wednesday, January 31, 2018 8:06 AM