Please help to solve this Faulting application name: Explorer.EXE, version: 6.3.9600.16441, time stamp: 0x5265dec8

Faulting application name: Explorer.EXE, version: 6.3.9600.16441, time stamp: 0x5265dec8
Faulting module name: verifier.dll, version: 6.3.9600.16384, time stamp: 0x5215f8f7
Exception code: 0x80000003
Fault offset: 0x000000000000abd4
Faulting process id: 0x13fc
Faulting application start time: 0x01cf2a60ac1727ab
Faulting application path: C:\WINDOWS\Explorer.EXE
Faulting module path: C:\WINDOWS\system32\verifier.dll
Report Id: d489ba61-9655-11e3-bf26-f82fa8e6dde2
Faulting package full name: 
Faulting package-relative application ID: 

Hi,
Try to run sfc /scannow command to repair the corrupted system file:
Use the System File Checker tool to repair missing or corrupted system files
http://support.microsoft.com/kb/929833
Also we could a easier way system restore to roll back to a time when everything works fine:
How to  refresh, reset, or restore your PC
http://windows.microsoft.com/en-IN/windows-8/restore-refresh-reset-pc
Karen Hu
TechNet Community Support

Similar Messages

  • Faulting application name: explorer.exe, version: 6.3.9600.17039, time stamp: 0x53156588

    Hi, I'm running Windows 8.1 Pro, and having problems where explorer will crash every couple of hours.  
    here's the event viewer log info:
    Faulting application name: explorer.exe, version: 6.3.9600.17039, time stamp: 0x53156588
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x0000000000000000
    Faulting process id: 0x2dfc
    Faulting application start time: 0x01cf7e970bd1516c
    Faulting application path: C:\windows\explorer.exe
    Faulting module path: unknown
    Report Id: a2e8b887-ea95-11e3-8265-0050b66098e2
    Faulting package full name: 
    Faulting package-relative application ID: 
    I opened up the dump file, and i'm having a hard time making out what the issue might be.  Any assistance would be appreciated.   Thank you!
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*C:\SYMBOLS*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\SYMBOLS*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 8 Version 9600 MP (4 procs) Free x64
    Product: WinNt, suite: SingleUserTS
    Built by: 6.3.9600.17031 (winblue_gdr.140221-1952)
    Machine Name:
    Debug session time: Mon Jun  2 12:15:42.000 2014 (UTC - 7:00)
    System Uptime: not available
    Process Uptime: 0 days 0:07:27.000
    Loading unloaded module list
    This dump file has an exception of interest stored in it.
    The stored exception information can be accessed via .ecxr.
    (2230.9d4): Access violation - code c0000005 (first/second chance not available)
    ntdll!NtWaitForMultipleObjects+0xa:
    00007ffc`20b2b13a c3              ret
    0:054> !analyze -v
    *                        Exception Analysis                                   *
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for sppc.dll - 
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for dlumd11.dll - 
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ClassicStartMenuDLL.dll - 
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ClassicExplorer64.dll - 
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for GROOVEEX.DLL - 
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for msvcr90.dll - 
    FAULTING_IP: 
    +50951de2c52b
    00000000`00000000 ??              ???
    EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
    ExceptionAddress: 0000000000000000
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000008
       Parameter[1]: 0000000000000000
    Attempt to execute non-executable address 0000000000000000
    CONTEXT:  0000000000000000 -- (.cxr 0x0;r)
    rax=00000000066e0000 rbx=0000000000000003 rcx=00000000066e0000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000003
    rip=00007ffc20b2b13a rsp=000000000980d428 rbp=000000000980dee0
     r8=0000000000001000  r9=0000000000000000 r10=0000000000000040
    r11=0000000000000286 r12=0000000000000010 r13=000000000980d840
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000246
    ntdll!NtWaitForMultipleObjects+0xa:
    00007ffc`20b2b13a c3              ret
    PROCESS_NAME:  explorer.exe
    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:  0000000000000008
    EXCEPTION_PARAMETER2:  0000000000000000
    WRITE_ADDRESS:  0000000000000000 
    FOLLOWUP_IP: 
    propsys!PSPropertyBag_WriteInt+3c
    00007ffc`19a2945c 488b4c2438      mov     rcx,qword ptr [rsp+38h]
    FAILED_INSTRUCTION_ADDRESS: 
    +3c
    00000000`00000000 ??              ???
    NTGLOBALFLAG:  0
    APPLICATION_VERIFIER_FLAGS:  0
    APP:  explorer.exe
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    FAULTING_THREAD:  00000000000009d4
    BUGCHECK_STR:  APPLICATION_FAULT_SOFTWARE_NX_FAULT_NULL
    PRIMARY_PROBLEM_CLASS:  SOFTWARE_NX_FAULT_NULL
    DEFAULT_BUCKET_ID:  SOFTWARE_NX_FAULT_NULL
    LAST_CONTROL_TRANSFER:  from 00007ffc19a2945c to 0000000000000000
    STACK_TEXT:  
    00000000`0980ed68 00007ffc`19a2945c : 00000000`1edc55b0 00000000`1edc55b0 00000000`00000000 00007ffc`1c581762 : 0x0
    00000000`0980ed70 00007ffc`08848361 : 00000000`183c3ad0 00000000`1edc55b0 00000000`1edc55b0 00000000`00000000 : propsys!PSPropertyBag_WriteInt+0x3c
    00000000`0980edc0 00007ffc`088482c4 : 00000000`00000000 00000000`00000425 00007ffc`16461240 00000000`00000425 : explorerframe!CShellBrowser::_OnFrameStateChanged+0x81
    00000000`0980ee10 00007ffc`087ef021 : 00000000`00000001 00000000`00000425 00000000`00000425 00000000`00000033 : explorerframe!CShellBrowser::WndProcBS+0x8aa
    00000000`0980f0b0 00007ffc`1ff62434 : 00000000`00000001 00000000`0980f360 00000000`00000000 00000002`00000030 : explorerframe!IEFrameWndProc+0x7d
    00000000`0980f100 00007ffc`1ff63fe2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : user32!UserCallWinProcCheckWow+0x140
    00000000`0980f1c0 00007ffc`1ff6409d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : user32!DispatchClientMessage+0xa2
    00000000`0980f220 00007ffc`20b2c99f : 00000000`18215570 00007ffc`087ffd50 00000000`18215570 00000000`0980f310 : user32!_fnDWORD+0x2d
    00000000`0980f280 00007ffc`1ff61fea : 00007ffc`1ff6341d 00000000`00000064 00000000`00000000 00000000`0980f3a0 : ntdll!KiUserCallbackDispatcherContinue
    00000000`0980f308 00007ffc`1ff6341d : 00000000`00000064 00000000`00000000 00000000`0980f3a0 00007ffc`087f0dab : user32!NtUserMessageCall+0xa
    00000000`0980f310 00007ffc`1ff65191 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00abecc0 : user32!SendMessageWorker+0x118
    00000000`0980f3a0 00007ffc`087f736c : 00000000`183111e0 00000000`17e90f80 00000000`00020732 00000000`00000000 : user32!SendMessageW+0x105
    00000000`0980f400 00007ffc`088479bb : 00000000`0000000c 00000000`183111e0 00000000`00000000 00000000`00000000 : explorerframe!CBrowserHost::ForwardMessageToBrowser+0x1c
    00000000`0980f430 00007ffc`088484e1 : 00000000`17e90ef8 00000000`00020732 00000000`00000000 00000000`17e90f80 : explorerframe!CExplorerFrame::OnBrowserCreated+0xcb
    00000000`0980f480 00007ffc`08847dcb : 00000000`203caba8 00000000`1edc55b0 00000000`17e90ee0 00000000`16237630 : explorerframe!CBrowserHost::OnBrowserCreated+0xb5
    00000000`0980f4c0 00007ffc`08843133 : 00000000`16237630 00000000`16237630 00000000`16237630 00000000`1edc55b0 : explorerframe!CShellBrowser::AfterWindowCreated+0xc7
    00000000`0980f500 00007ffc`08842f80 : 00000000`16237630 00000000`0980f730 00000000`00000003 00000000`18311140 : explorerframe!CBrowserHost::Initialize+0xef
    00000000`0980f530 00007ffc`087f9bc0 : 00000000`18311140 00000000`00200000 00000000`0980f730 00000000`00000003 : explorerframe!CExplorerFrame::Initialize+0x3c
    00000000`0980f560 00007ffc`087fb3b6 : 00000000`18311140 00000000`16237630 00000000`00200000 00007ffc`1e102d9d : explorerframe!BrowserThreadProc+0x50
    00000000`0980f5a0 00007ffc`087fb366 : 18bc0f9b`000047ae 00000000`15ff61e0 00000000`00000000 00007ffc`1ff62f2f : explorerframe!BrowserNewThreadProc+0x3a
    00000000`0980f5d0 00007ffc`087f8549 : 00000000`00002230 00000000`000009d4 00000000`0000000f 00000000`0000000b : explorerframe!CExplorerTask::InternalResumeRT+0x12
    00000000`0980f600 00007ffc`1ebde4fc : 00000000`00000000 00000000`00000000 ffffffff`fffffffe 00000000`00200000 : explorerframe!CRunnableTask::Run+0xc9
    00000000`0980f630 00007ffc`1ebde6df : 00000000`10605f50 00000000`10605f50 00000000`00000000 00000000`00000010 : shell32!CShellTaskThread::ThreadProc+0x284
    00000000`0980f780 00007ffc`1c588023 : 00000000`00000001 00000000`00000001 00000000`00000000 00000000`00000000 : shell32!CShellTaskThread::s_ThreadProc+0x2f
    00000000`0980f7b0 00007ffc`200e16ad : 00000000`0040e300 00000000`00000000 00000000`80004005 00000000`00000000 : SHCore!Microsoft::WRL::FtmBase::MarshalInterface+0x17b
    00000000`0980f8d0 00007ffc`20b04629 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0xd
    00000000`0980f900 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  propsys!PSPropertyBag_WriteInt+3c
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: propsys
    IMAGE_NAME:  propsys.dll
    DEBUG_FLR_IMAGE_TIMESTAMP:  53511853
    STACK_COMMAND:  ~54s; .ecxr ; kb
    FAILURE_BUCKET_ID:  SOFTWARE_NX_FAULT_NULL_c0000005_propsys.dll!PSPropertyBag_WriteInt
    BUCKET_ID:  APPLICATION_FAULT_SOFTWARE_NX_FAULT_NULL_NULL_IP_propsys!PSPropertyBag_WriteInt+3c
    ANALYSIS_SOURCE:  UM
    FAILURE_ID_HASH_STRING:  um:software_nx_fault_null_c0000005_propsys.dll!pspropertybag_writeint
    FAILURE_ID_HASH:  {a6c58e48-fd4e-59a9-7e83-f1b082937554}
    Followup: MachineOwner

    Hi，
    Please upload the dump file to a public folder such as OneDrive, then paste the download link here for further analyzing.
    Have you installed any third party tool which might be related with Explorer in your system? if you have, please uninstalled it as a test.
    Windows Explorer crashes are mostly caused by an incompatible Shell Extension.
    You can run tool ShellExView to find the culprit, in the pane sort the entries with manufacturers. Disable all non-Microsoft *.dll files, and check the result. If the issue does not occur, one of the files can be the culprit. We could narrow down it one by
    one.
    For download link and user guide, please see this link (ShellExView is included in it)
    http://technet.microsoft.com/en-us/magazine/2009.06.toolbox.aspx
    Yolanda Zhu
    TechNet Community Support

  • I use msn internet browser and it constantly crashes with the info from event viewer: Faulting application name: msn.exe, version: 10.50.19.1000, time stamp: 0x51ddb7de this can happen numerous times in a single day help please

    Log Name:      Application
    Source:        Application Error
    Date:          2/26/2014 2:16:26 PM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SuperFlyXPS
    Description:
    Faulting application name: msn.exe, version: 10.50.19.1000, time stamp: 0x51ddb7de
    Faulting module name: MSHTML.dll, version: 11.0.9600.16518, time stamp: 0x52f365cb
    Exception code: 0xc0000005
    Fault offset: 0x00175363
    Faulting process id: 0x1260
    Faulting application start time: 0x01cf32a011d4aeb4
    Faulting application path: C:\Program Files (x86)\MSN\MSNCoreFiles\msn.exe
    Faulting module path: C:\Windows\system32\MSHTML.dll
    Report Id: a1704306-9f33-11e3-acde-782bcbac25e5
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-02-26T22:16:26.000000000Z" />
        <EventRecordID>80997</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SuperFlyXPS</Computer>
        <Security />
      </System>
      <EventData>
        <Data>msn.exe</Data>
        <Data>10.50.19.1000</Data>
        <Data>51ddb7de</Data>
        <Data>MSHTML.dll</Data>
        <Data>11.0.9600.16518</Data>
        <Data>52f365cb</Data>
        <Data>c0000005</Data>
        <Data>00175363</Data>
        <Data>1260</Data>
        <Data>01cf32a011d4aeb4</Data>
        <Data>C:\Program Files (x86)\MSN\MSNCoreFiles\msn.exe</Data>
        <Data>C:\Windows\system32\MSHTML.dll</Data>
        <Data>a1704306-9f33-11e3-acde-782bcbac25e5</Data>
      </EventData>
    </Event>
    need help with . . .

    Hi,
    I found a useful link:
    MSN has encountered a problem needs to close or MSN is not responding Error
    https://answers.msn.com/solution.aspx?solutionid=11abae39-d906-4113-bb4e-ecfaa81798f0
    Please take a look of this part
    (Common Faulty Module on MSN
    Mshtml.dll)
    *Instead of MSN, here is a another software called Skype, just instroduce it to you, hope you can enjoy it.*
    Yolanda Zhu
    TechNet Community Support

  • Faulting application name: grpwise.exe, version: 14.0.0.2524

    I have one user on Windows 7 Pro x64 that will have his GroupWise crash out about once a day. He says sometimes he will be working in other programs and a popup will come up that GroupWise has stopped responding and to close program.
    The event log shows:
    Faulting application name: grpwise.exe, version: 14.0.0.25243, time stamp: 0x5334b3ec
    Faulting module name: gwenv1.dll, version: 14.0.0.25243, time stamp: 0x5334b1f9
    Exception code: 0xc0000005
    Fault offset: 0x00450dfb
    Faulting process id: 0x2308
    Faulting application start time: 0x01cfc22505c31a56
    Faulting application path: C:\Program Files (x86)\Novell\GroupWise\grpwise.exe
    Faulting module path: C:\Program Files (x86)\Novell\GroupWise\gwenv1.dll
    Report Id: f3b0976c-2e26-11e4-8725-f8b156b229f2
    Any ideas why?
    Ken

    Originally Posted by smflood
    On 28/08/2014 14:06, RLMILLIES wrote:
    > I have one user on Windows 7 Pro x64 that will have his GroupWise crash
    > out about once a day. He says sometimes he will be working in other
    > programs and a popup will come up that GroupWise has stopped responding
    > and to close program.
    >
    > The event log shows:
    >
    > Faulting application name: grpwise.exe, version: 14.0.0.25243, time
    > stamp: 0x5334b3ec
    > Faulting module name: gwenv1.dll, version: 14.0.0.25243, time stamp:
    > 0x5334b1f9
    > Exception code: 0xc0000005
    > Fault offset: 0x00450dfb
    > Faulting process id: 0x2308
    > Faulting application start time: 0x01cfc22505c31a56
    > Faulting application path: C:\Program Files
    > (x86)\Novell\GroupWise\grpwise.exe
    > Faulting module path: C:\Program Files
    > (x86)\Novell\GroupWise\gwenv1.dll
    > Report Id: f3b0976c-2e26-11e4-8725-f8b156b229f2
    >
    > Any ideas why?
    No but please can you try the SP1 client which was recently released.
    It's available for download @
    https://download.novell.com/Download...d=adKLQO6vZjA~
    HTH.
    Simon
    Novell Knowledge Partner
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below. Thanks.
    So far so good - The client has not crashed since the update.
    Sincerely,
    Ken

  • Faulting module name: AcroRd32.dll, version: 10.1.1.33, time stamp: 0x4e64f98b

    Hi,
    In a Win7 (32 bit) environment with IE8 and Acrobat Reader X (Version 10.1.1.33)  a number of our PC's and laptops get the following error messages on a fairly consistant basis:
    Faulting application name: iexplore.exe, version: 8.0.7601.17514, time stamp: 0x4ce79912
    Faulting module name: AcroRd32.dll, version: 10.1.1.33, time stamp: 0x4e64f98b
    Exception code: 0xc0000005
    Fault offset: 0x000931d8
    Faulting process id: 0x1790
    Faulting application start time: 0x01cedee9854abf7a
    Faulting application path: C:\Program Files\Internet Explorer\iexplore.exe
    Faulting module path: C:\Program Files\Adobe\Reader 10.0\Reader\AcroRd32.dll
    Report Id: 49797133-4aea-11e3-b595-f4b7e2e6eb69
    Does anyone have any idea of how to fix this issue or what may be the cause of it? Is is solely related to Acrobat or do you think IE8 may be the cause? We use IE8 due to restrictions on some web based applications we use and cannot upgrade to a newer version of this.
    Thanks

    I don't know what is causing this, but the first thing I would try is to update Adobe Reader to version 10.1.8 (or 11.0.5).

  • Faulting module name: ntdll.dll, version: 6.2.9200.17046, time stamp: 0x53b4864c

    We are having somewhat regular crashes (every couple of weeks) of RDS.  Our analysis shows heap corruption.  RAM tests okay.
    Log Name: Application
    Source: Application Error
    Date: 4/17/2015 2:37:50 PM
    Event ID: 1000
    Task Category: (100)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: APPSERVER.ourdomain.local
    Description:
    Faulting application name: svchost.exe_TermService, version: 6.2.9200.16420, time stamp: 0x505a9a4e
    Faulting module name: ntdll.dll, version: 6.2.9200.17046, time stamp: 0x53b4864c
    Exception code: 0xc0000005
    Fault offset: 0x0000000000006ff5
    Faulting process id: 0x250
    Faulting application start time: 0x01d07834faefc615
    Faulting application path: C:\Windows\System32\svchost.exe
    Faulting module path: C:\Windows\SYSTEM32
    tdll.dll
    Report Id: fea9607e-e549-11e4-940f-00155d0c0502
    Log Name: Application
    Source: Windows Error Reporting
    Date: 4/17/2015 2:38:07 PM
    Event ID: 1001
    Task Category: None
    Level: Information
    Keywords: Classic
    User: N/A
    Computer: APPSERVER.ourdomain.local
    Description:
    Fault bucket , type 0
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0
    Problem signature:
    P1: svchost.exe_TermService
    P2: 6.2.9200.16420
    P3: 505a9a4e
    P4: ntdll.dll
    P5: 6.2.9200.17046
    P6: 53b4864c
    P7: c0000005
    P8: 0000000000006ff5
    P9:
    P10:
    Analysis symbol:
    Rechecking for solution: 0
    Report Id: fea9607e-e549-11e4-940f-00155d0c0502
    Report Status: 0
    Hashed bucket:
    - These events indicated that program(svchost.exe_TermService) stopped unexpectedly. Which causes the issue with the remote session.
    - For further investigation checked the AppCrash dump file on the server and found below error:
    PROCESS_NAME: svchost.exe
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
    EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)
    ExceptionAddress: 000007fb7c3f6ff5 (ntdll!RtlpHeapFindListLookupEntry+0x0000000000000129)
    ExceptionCode: c0000005 (Access violation)
    PRIMARY_PROBLEM_CLASS: HEAP_CORRUPTION
    BUGCHECK_STR: APPLICATION_FAULT_HEAP_CORRUPTION_HEAP_CORRUPTION_INVALID_POINTER_READ_CONTEXT_MISMATCH.
    Any ideas?

    Hi Rick,
    Firstly, please try to fully patch the terminal server, and disable third party software if there’s any installed.
    If the issue persists, please check whether KB2984976 is installed, if yes, please remove it.
    Best Regards,
    Amy
    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]

  • Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e21213c

    Hi,
    Good day!
    I'm having this issue when I just installed an application. I have been searching this kernelbase.dll thing but none of them have fix or any workaround. Hopefully with the great technical guys here can help me with this issue.
    The server is windows 2008 R2
    From the event viewer I got this
    Faulting application name: Tlc.LogManager.Svc.exe, version: 7.0.1.5108, time stamp: 0x51d1ee27
    Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e21213c
    Exception code: 0xe0434352
    Fault offset: 0x000000000000cacd
    Faulting process id: 0x1130
    Faulting application start time: 0x01cf6dbd862da5b1
    Faulting application path: D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.LogManager.Svc.exe
    Faulting module path: C:\Windows\system32\KERNELBASE.dll
    Report Id: fefb5c84-d9b0-11e3-9578-5ef3fcdc0b9f
    Application: Tlc.LogManager.Svc.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.ArgumentNullException
    Stack:
       at Tlc.CapCollector.Common.CapPersistentStateManager..ctor(Tlc.Interfaces.BusinessObjects.IAssetBusinessObject, Tlc.PersistentState.IPersistentStateStore, Tlc.Interfaces.ApplicationLog.IApplicationLog, Int32, Tlc.CapCollector.AgentDiscovery.CapAgentAutoDiscovery)
       at Tlc.LogManager.Lib.ascMan.OnMessageBusStart(Tlc.Interfaces.MessageBus.IMessageBus, Tlc.Interfaces.ApplicationLog.IApplicationLog, Tlc.Interfaces.ApplicationLog.IApplicationLog, Tlc.Interfaces.ApplicationLog.IApplicationLog)
       at Tlc.MessageBus.ActiveMQMessageBus.Start()
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
       at System.Threading.ThreadHelper.ThreadStart()
    Fault bucket , type 0
    Event Name: CLR20r3
    Response: Not available
    Cab Id: 0
    Problem signature:
    P1: tlc.logmanager.svc.exe
    P2: 7.0.1.5108
    P3: 51d1ee27
    P4: Tlc.CapCollector
    P5: 7.0.1.5108
    P6: 51d1edf4
    P7: f2
    P8: 34
    P9: System.ArgumentNullException
    P10:
    Attached files:
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_tlc.logmanager.s_4d5cd055f698b9b7d9e989629dd2eb52d0be2b_1a6a145b
    Analysis symbol:
    Rechecking for solution: 0
    Report Id: fefb5c84-d9b0-11e3-9578-5ef3fcdc0b9f
    Version=1
    EventType=CLR20r3
    EventTime=130443543988233973
    ReportType=2
    Consent=1
    ReportIdentifier=8c35a7c6-d9a9-11e3-9578-5ef3fcdc0b9f
    IntegratorReportIdentifier=8c35a7c5-d9a9-11e3-9578-5ef3fcdc0b9f
    Response.type=4
    Sig[0].Name=Problem Signature 01
    Sig[0].Value=tlc.logmanager.svc.exe
    Sig[1].Name=Problem Signature 02
    Sig[1].Value=7.0.1.5108
    Sig[2].Name=Problem Signature 03
    Sig[2].Value=51d1ee27
    Sig[3].Name=Problem Signature 04
    Sig[3].Value=Tlc.CapCollector
    Sig[4].Name=Problem Signature 05
    Sig[4].Value=7.0.1.5108
    Sig[5].Name=Problem Signature 06
    Sig[5].Value=51d1edf4
    Sig[6].Name=Problem Signature 07
    Sig[6].Value=f2
    Sig[7].Name=Problem Signature 08
    Sig[7].Value=34
    Sig[8].Name=Problem Signature 09
    Sig[8].Value=System.ArgumentNullException
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.1.7601.2.1.0.272.7
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=18441
    DynamicSig[22].Name=Additional Information 1
    DynamicSig[22].Value=3ada
    DynamicSig[23].Name=Additional Information 2
    DynamicSig[23].Value=3adac3ca3b54f3f7659e16fb4fdadcbe
    DynamicSig[24].Name=Additional Information 3
    DynamicSig[24].Value=b033
    DynamicSig[25].Name=Additional Information 4
    DynamicSig[25].Value=b0336032f99007ec98baa22debc5fb25
    UI[2]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.LogManager.Svc.exe
    UI[3]=Tlc.LogManager.Svc has stopped working
    UI[4]=Windows can check online for a solution to the problem.
    UI[5]=Check online for a solution (recommended)
    UI[6]=Check for a solution later (recommended)
    UI[7]=Close
    UI[8]=Tlc.LogManager.Svc stopped working and was closed
    UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
    UI[10]=&Close
    LoadedModule[0]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.LogManager.Svc.exe
    LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
    LoadedModule[2]=C:\Windows\SYSTEM32\MSCOREE.DLL
    LoadedModule[3]=C:\Windows\system32\KERNEL32.dll
    LoadedModule[4]=C:\Windows\system32\KERNELBASE.dll
    LoadedModule[5]=C:\Windows\system32\ADVAPI32.dll
    LoadedModule[6]=C:\Windows\system32\msvcrt.dll
    LoadedModule[7]=C:\Windows\SYSTEM32\sechost.dll
    LoadedModule[8]=C:\Windows\system32\RPCRT4.dll
    LoadedModule[9]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
    LoadedModule[10]=C:\Windows\system32\SHLWAPI.dll
    LoadedModule[11]=C:\Windows\system32\GDI32.dll
    LoadedModule[12]=C:\Windows\system32\USER32.dll
    LoadedModule[13]=C:\Windows\system32\LPK.dll
    LoadedModule[14]=C:\Windows\system32\USP10.dll
    LoadedModule[15]=C:\Windows\system32\IMM32.DLL
    LoadedModule[16]=C:\Windows\system32\MSCTF.dll
    LoadedModule[17]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
    LoadedModule[18]=C:\Windows\system32\MSVCR100_CLR0400.dll
    LoadedModule[19]=C:\Windows\assembly\NativeImages_v4.0.30319_64\mscorlib\bc19222db4406c472d9aa1f8b6e0f470\mscorlib.ni.dll
    LoadedModule[20]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\nlssorting.dll
    LoadedModule[21]=C:\Windows\system32\ole32.dll
    LoadedModule[22]=C:\Windows\system32\CRYPTBASE.dll
    LoadedModule[23]=C:\Windows\system32\CRYPTSP.dll
    LoadedModule[24]=C:\Windows\system32\rsaenh.dll
    LoadedModule[25]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System\0f8f78b729ce16dd078f5d5f734a1110\System.ni.dll
    LoadedModule[26]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.ServiceProce#\7b167f31f23d4aed19dfa65ad3d29480\System.ServiceProcess.ni.dll
    LoadedModule[27]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll
    LoadedModule[28]=C:\Windows\system32\OLEAUT32.dll
    LoadedModule[29]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Xceed.Zip.v5.1.dll
    LoadedModule[30]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Xceed.GZip.v5.1.dll
    LoadedModule[31]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Xceed.Tar.v5.1.dll
    LoadedModule[32]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Xceed.Compression.Formats.v5.1.dll
    LoadedModule[33]=C:\Windows\system32\VERSION.dll
    LoadedModule[34]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Common.dll
    LoadedModule[35]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Xceed.FileSystem.v5.1.dll
    LoadedModule[36]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Xceed.Compression.v5.1.dll
    LoadedModule[37]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.LogManager.Lib.dll
    LoadedModule[38]=C:\Windows\assembly\GAC_MSIL\VistaDB.4\4.1.0.0__dfc935afe2125461\VistaDB.4.dll
    LoadedModule[39]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Interfaces.dll
    LoadedModule[40]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Enums.dll
    LoadedModule[41]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Core\7a93c267da35a5f16b6fa5a10482eb4e\System.Core.ni.dll
    LoadedModule[42]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Data\5a47dfd0b200a502a4d5d27ee99bcc3c\System.Data.ni.dll
    LoadedModule[43]=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll
    LoadedModule[44]=C:\Windows\system32\WS2_32.dll
    LoadedModule[45]=C:\Windows\system32\NSI.dll
    LoadedModule[46]=C:\Windows\system32\CRYPT32.dll
    LoadedModule[47]=C:\Windows\system32\MSASN1.dll
    LoadedModule[48]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xml\5d9f385419332f14eaf937556199856f\System.Xml.ni.dll
    LoadedModule[49]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Dal.LogManager.Client.dll
    LoadedModule[50]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Data.Service#\5ac492f703d6d741140f7cd45ef3c746\System.Data.Services.Client.ni.dll
    LoadedModule[51]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Dal.LogManager.Local.dll
    LoadedModule[52]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Data.Entity\c41b30de7215a62c8ca5bfe6e04ea763\System.Data.Entity.ni.dll
    LoadedModule[53]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.DataAccess.Config.dll
    LoadedModule[54]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.LogManager.Log.dll
    LoadedModule[55]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Utils.dll
    LoadedModule[56]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.LogMessageClassifier.dll
    LoadedModule[57]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Wintellect.PowerCollections.dll
    LoadedModule[58]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\nsoftware.IPWorks.dll
    LoadedModule[59]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Configuration\11581b5eba4b3ff58441c638ab66c742\System.Configuration.ni.dll
    LoadedModule[60]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Web\7e5af1fdbcffeab8daffc7633f9c337a\System.Web.ni.dll
    LoadedModule[61]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Drawing\1266d26c7b7843d308e2705cb8239d55\System.Drawing.ni.dll
    LoadedModule[62]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Windows.Forms\f0acb5c0e7dc2c42c6c61f3aa1278338\System.Windows.Forms.ni.dll
    LoadedModule[63]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.CommonAssemblyInfo.dll
    LoadedModule[64]=C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17514_none_2b24536c71ed437a\gdiplus.dll
    LoadedModule[65]=C:\Windows\system32\WindowsCodecs.dll
    LoadedModule[66]=C:\Windows\system32\shell32.dll
    LoadedModule[67]=C:\Windows\system32\profapi.dll
    LoadedModule[68]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\webengine4.dll
    LoadedModule[69]=C:\Windows\system32\USERENV.dll
    LoadedModule[70]=C:\Windows\system32\PSAPI.DLL
    LoadedModule[71]=C:\Windows\system32\urlmon.dll
    LoadedModule[72]=C:\Windows\system32\WININET.dll
    LoadedModule[73]=C:\Windows\system32\iertutil.dll
    LoadedModule[74]=C:\Windows\system32\SspiCli.dll
    LoadedModule[75]=C:\Windows\system32\shfolder.dll
    LoadedModule[76]=C:\Windows\system32\bcrypt.dll
    LoadedModule[77]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Configuratio#\c080a9ed31f78466f2400bba623af2f8\System.Configuration.Install.ni.dll
    LoadedModule[78]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Web.Services\6cd002594b56953e9c210581e7f3f3cd\System.Web.Services.ni.dll
    LoadedModule[79]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.PersistentState.dll
    LoadedModule[80]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Mitre.CommonEventExpression.dll
    LoadedModule[81]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.ClientServer.Communications.dll
    LoadedModule[82]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Numerics\215d813343ba0950ad6e148e2098018b\System.Numerics.ni.dll
    LoadedModule[83]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Management\da51604aa808b94c181181b37c727078\System.Management.ni.dll
    LoadedModule[84]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.VisualBas#\af08f116e2c31d2c65bd492804fb2fef\Microsoft.VisualBasic.ni.dll
    LoadedModule[85]=C:\Windows\system32\RpcRtRemote.dll
    LoadedModule[86]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\wminet_utils.dll
    LoadedModule[87]=C:\Windows\system32\CLBCatQ.DLL
    LoadedModule[88]=C:\Windows\system32\wbem\wmiutils.dll
    LoadedModule[89]=C:\Windows\system32\wbemcomn.dll
    LoadedModule[90]=C:\Windows\system32\wbem\wbemprox.dll
    LoadedModule[91]=C:\Windows\system32\wbem\wbemsvc.dll
    LoadedModule[92]=C:\Windows\system32\wbem\fastprox.dll
    LoadedModule[93]=C:\Windows\system32\NTDSAPI.dll
    LoadedModule[94]=C:\Windows\system32\mswsock.dll
    LoadedModule[95]=C:\Windows\System32\wshtcpip.dll
    LoadedModule[96]=C:\Windows\System32\wship6.dll
    LoadedModule[97]=C:\Windows\system32\DNSAPI.dll
    LoadedModule[98]=C:\Windows\system32\IPHLPAPI.DLL
    LoadedModule[99]=C:\Windows\system32\WINNSI.DLL
    LoadedModule[100]=C:\Windows\system32\rasadhlp.dll
    LoadedModule[101]=C:\Windows\System32\fwpuclnt.dll
    LoadedModule[102]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Devart.Data.MySql.dll
    LoadedModule[103]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Transactions\122cea70c5d0d591f9af1f4316848fd1\System.Transactions.ni.dll
    LoadedModule[104]=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Transactions\v4.0_4.0.0.0__b77a5c561934e089\System.Transactions.dll
    LoadedModule[105]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Devart.Data.dll
    LoadedModule[106]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\nsoftware.IPWorksSSL.dll
    LoadedModule[107]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Data.OracleC#\850abdea1c65b88ba24a77f0191caea8\System.Data.OracleClient.ni.dll
    LoadedModule[108]=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Data.OracleClient\v4.0_4.0.0.0__b77a5c561934e089\System.Data.OracleClient.dll
    LoadedModule[109]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xml.Linq\9d14b7bc969452800c0456286309d41d\System.Xml.Linq.ni.dll
    LoadedModule[110]=C:\Windows\assembly\GAC_MSIL\VistaDB.Entities.4\4.1.0.0__dfc935afe2125461\VistaDB.Entities.4.dll
    LoadedModule[111]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.EnterpriseSe#\48264d6ad04173a3a82cc06b70c5cd28\System.EnterpriseServices.ni.dll
    LoadedModule[112]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.EnterpriseSe#\48264d6ad04173a3a82cc06b70c5cd28\System.EnterpriseServices.Wrapper.dll
    LoadedModule[113]=C:\Windows\Microsoft.Net\assembly\GAC_64\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.Wrapper.dll
    LoadedModule[114]=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Data.Entity\v4.0_4.0.0.0__b77a5c561934e089\System.Data.Entity.dll
    LoadedModule[115]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Runtime.Seri#\08fba6b56d838ad48b4451c82e5728d4\System.Runtime.Serialization.ni.dll
    LoadedModule[116]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.RuleEngine.dll
    LoadedModule[117]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.EventForwarder.dll
    LoadedModule[118]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Lucene.Net.dll
    LoadedModule[119]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.ServiceModel\d072039db89cac96d9e0b1ae9b3a94f4\System.ServiceModel.ni.dll
    LoadedModule[120]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.ServiceModel#\43f892698b9de4d752c13cc2d91ff16d\System.ServiceModel.Web.ni.dll
    LoadedModule[121]=C:\Windows\assembly\NativeImages_v4.0.30319_64\SMDiagnostics\ac74a156499a8303d5788ab299881d5d\SMDiagnostics.ni.dll
    LoadedModule[122]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Runtime.Dura#\2f02efd9ddb7417ffd5c06cfe6e865ca\System.Runtime.DurableInstancing.ni.dll
    LoadedModule[123]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.IdentityModel\33ac21194152cf9a89b82d9cd38b398d\System.IdentityModel.ni.dll
    LoadedModule[124]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xaml\535e182d16212c61bc8b22e0309d3362\System.Xaml.ni.dll
    LoadedModule[125]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Data.Services\84226b67f4623bd3b0dde9aa00c5c88d\System.Data.Services.ni.dll
    LoadedModule[126]=C:\Windows\system32\pcwum.DLL
    LoadedModule[127]=C:\Windows\system32\httpapi.dll
    LoadedModule[128]=C:\Windows\system32\cryptnet.dll
    LoadedModule[129]=C:\Windows\system32\WLDAP32.dll
    LoadedModule[130]=C:\Windows\system32\SensApi.dll
    LoadedModule[131]=C:\Windows\system32\dsrole.dll
    LoadedModule[132]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.MessageBus.dll
    LoadedModule[133]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Apache.NMS.dll
    LoadedModule[134]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Google.ProtocolBuffers.dll
    LoadedModule[135]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\nsoftware.IPWorksSSH.dll
    LoadedModule[136]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Reports.dll
    LoadedModule[137]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\SecureBlackbox.dll
    LoadedModule[138]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.GenericDbLogCollector.dll
    LoadedModule[139]=C:\Windows\system32\ntmarta.dll
    LoadedModule[140]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\perfcounter.dll
    LoadedModule[141]=C:\Windows\system32\pdh.dll
    LoadedModule[142]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\nsoftware.System.dll
    LoadedModule[143]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\diasymreader.dll
    LoadedModule[144]=C:\Windows\system32\aspnet_counters.dll
    LoadedModule[145]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_perf.dll
    LoadedModule[146]=C:\Windows\system32\Secur32.dll
    LoadedModule[147]=C:\Windows\system32\CFGMGR32.dll
    LoadedModule[148]=C:\Windows\system32\security.dll
    LoadedModule[149]=C:\Windows\system32\credssp.dll
    LoadedModule[150]=C:\Windows\system32\schannel.DLL
    LoadedModule[151]=C:\Windows\system32\ncrypt.dll
    LoadedModule[152]=C:\Windows\system32\bcryptprimitives.dll
    LoadedModule[153]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\nsoftware.IPWorksSSNMP.dll
    LoadedModule[154]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Apache.NMS.ActiveMQ.dll
    LoadedModule[155]=C:\Windows\system32\NLAapi.dll
    LoadedModule[156]=C:\Windows\system32\napinsp.dll
    LoadedModule[157]=C:\Windows\System32\winrnr.dll
    LoadedModule[158]=C:\Windows\system32\rasman.dll
    LoadedModule[159]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.CapCollector.dll
    LoadedModule[160]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.CapIDL.dll
    LoadedModule[161]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Dto.dll
    FriendlyEventName=Stopped working
    ConsentKey=CLR20r3
    AppName=Tlc.LogManager.Svc
    AppPath=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.LogManager.Svc.exe

    Hi Ross Rene,
    Sorry for the delay.
    Please make sure the App is compatible with the .Net framework installed, please check the .net version.
    Best Regards,
    Anna

  • IIS charsh with error: Faulting application name: w3wp.exe

    Hi Team,Question
    I am new to Window Azure. Recently I encounter a issue on my production server, where my application hosted on Azure server was automatically getting down in every 2 Hrs,when i have checked the error logs I got the error:
    Faulting application name: w3wp.exe,version: 8.5.9600.16384,time stamp: 0X5215df96
    Please help me out to solve the problem.
    Thanks,
    Ashwin
    Thanks Ashwin

    Hi,
     Thanks for Posting.
     Please refer to the following thread which talks about the same error, and suggests analyzing the crash dump  
    https://social.msdn.microsoft.com/Forums/en-US/5df570d8-1f19-47b3-9d76-e737e858aa6d/iis-crash-with-faulting-application-w3wpexe-faulting-module-mscorwksdll-version-205072742?forum=clr
      If this does not help, i would suggest to get a Support Ticket created so that an engineer from the TechSupport team can personally look into this issue. you can create a support ticket from within the management portal or using the following link.
      http://azure.microsoft.com/en-us/support/options/
      Regards,
      Nithin.Rathnakar.
      **There is Duplicate thread for this issue, which i will be closing marking the link for this thread.
      

  • Application Error: Event ID 1000; Faulting application name: PrintIsolationHost.exe

    Hello, dear colleagues!
    I have problem with printing on RDS (Windows Server 2012 R2). We are executing printer drivers in isolated processes. But sometimes PrintIsolationHost.exe faults 200 times a hour and causes Print Spooler to fail.
    Examples of errors:
    Faulting application name: PrintIsolationHost.exe, version: 6.3.9600.16384, time stamp: 0x5215f03c
    Faulting module name: ntdll.dll, version: 6.3.9600.17114, time stamp: 0x53649e73
    Exception code: 0xc0000374
    Fault offset: 0x00000000000f87a8
    Faulting process id: 0x1347c
    Faulting application start time: 0x01d0187efb514f3b
    Faulting application path: C:\Windows\system32\PrintIsolationHost.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: 423cfe70-8472-11e4-95a3-005056a224fb
    Faulting package full name:
    Faulting package-relative application ID:
    Faulting application name: splwow64.exe, version: 6.3.9600.16384, time stamp: 0x5215f01d
    Faulting module name: ntdll.dll, version: 6.3.9600.17114, time stamp: 0x53649e73
    Exception code: 0xc0000374
    Fault offset: 0x00000000000f87a8
    Faulting process id: 0xae7c
    Faulting application start time: 0x01d01846b8f40037
    Faulting application path: C:\Windows\splwow64.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: 2d5ef196-8472-11e4-95a3-005056a224fb
    Faulting package full name:
    Faulting package-relative application ID:
    Faulting application name: spoolsv.exe, version: 6.3.9600.16384, time stamp: 0x5215d570
    Faulting module name: ntdll.dll, version: 6.3.9600.17114, time stamp: 0x53649e73
    Exception code: 0xc0000005
    Fault offset: 0x0000000000030489
    Faulting process id: 0x143b0
    Faulting application start time: 0x01d0187a74d7b105
    Faulting application path: C:\Windows\System32\spoolsv.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: ddb33928-8472-11e4-95a3-005056a224fb
    Faulting package full name:
    Faulting package-relative application ID:
    Faulting application name: spoolsv.exe, version: 6.3.9600.16384, time stamp: 0x5215d570
    Faulting module name: KERNELBASE.dll, version: 6.3.9600.17055, time stamp: 0x532954fb
    Exception code: 0xc0000002
    Fault offset: 0x0000000000005bf8
    Faulting process id: 0x142b8
    Faulting application start time: 0x01d0187fab656d9c
    Faulting application path: C:\Windows\System32\spoolsv.exe
    Faulting module path: C:\Windows\system32\KERNELBASE.dll
    Report Id: f10aa42a-8472-11e4-95a3-005056a224fb
    Faulting package full name:
    Faulting package-relative application ID:
    How can I explore it? 
    Thanks.

    Hi,
    Thank you for posting in Windows Server Forum.
    Generally the error which you are facing occurs due to many different scenario. But the main reason to cause this will result from a corrupt or damaged version of the ntdll.dll file itself, corrupt hardware drivers, corrupt printer drivers, or issues between
    Windows and other programs.
    - Please run sfc /scannow from your command prompt.
    - Delete the printer driver and re-install again with specific printing models.
    Apart you can check below link for print spooler crash troubleshooting guides.
    Print Spooler Crash Troubleshooting Steps
    http://blogs.technet.com/b/perfguru/archive/2008/08/06/print-spooler-crash-troubleshooting-steps.aspx
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • SkyDrive.exe error: event id 1000, Faulting application name: skydrive.exe

    Symptoms since upgrading to Windows 8.1:
    SkyDrive won't sync new files, e.g. files I've created in Excel for instance do not show in SkyDrive or, predictably, in other devices
    There is no SkyDrive icon in the task bar
    I keep getting the following in Event Viewer:
    Faulting application name: skydrive.exe, version: 6.3.9600.16412, time stamp: 0x5243d370
    Faulting module name: msvcrt.dll, version: 7.0.9600.16384, time stamp: 0x5215f944
    Exception code: 0xc0000005
    Fault offset: 0x0000000000007a6e
    Faulting process id: 0x16f0
    Faulting application start time: 0x01ced636efff9d54
    Faulting application path: C:\Windows\System32\skydrive.exe
    Faulting module path: C:\WINDOWS\system32\msvcrt.dll
    Any help would be appreciated.

    Thanks Andre,
    Looked at 'Conversion Tables.xls'. It did contain some hidden macros that I didn't know about. I just now deleted them.
    Am I to understand that either deleteing the macros or excluding 'Conversion Tables.xls' from SkyDrive will stop the Event ID 1000 application errors in Event Viewer? I got another series of four today:
    Faulting application name: skydrive.exe, version: 6.3.9600.16412, time stamp: 0x5243d370
    Faulting module name: msvcrt.dll, version: 7.0.9600.16384, time stamp: 0x5215f944
    Exception code: 0xc0000005
    Fault offset: 0x0000000000007a6e
    Faulting process id: 0x1d84
    Faulting application start time: 0x01cedbc6da13a0bb
    Faulting application path: C:\Windows\System32\skydrive.exe
    Faulting module path: C:\WINDOWS\system32\msvcrt.dll
    Report Id: 18500c7d-47c1-11e3-bf15-d4716ab3aad1
    Faulting package full name:
    Faulting package-relative application ID:
    Again, thanks.

  • I continually get this: Application Error 1000_(100)_"Faulting application name: MyAppName.exe Faulting module name: MSVBVM60.DLL

    I have a VB6 application which connects to a SQL Server.  I am running my exe on a Windows Server Terminal Server.  I frequently have my EXE crash and close at random.  My EXE doesn't log any error because the crash occurred outside of my
    application. 
    Here is the Windows event error:
    07/17/14 4:59:49 PM    Application Error    1000    (100)    "Faulting application name: MyApp.exe, version: 8.0.0.0, time stamp: 0x53adc042
    Faulting module name: MSVBVM60.DLL, version: 6.0.98.15, time stamp: 0x4a5bda6c
    Exception code: 0xc0000006
    Fault offset: 0x00054948
    Faulting process id: 0x24d4
    Faulting application start time: 0x01cfa1fe336df3db
    Faulting application path: N:\MyApp\MyApp.exe
    Faulting module path: C:\Windows\system32\MSVBVM60.DLL
    Report Id: 498ee913-0df5-11e4-a940-000c29a03ae8"
    I have tried to search the internet but I have yet to find a solution.  Any help or explanation would be greatly appreciated.

    Hello,
    Thank you for your post.
    I’m afraid that it is not the correct forum for this issue, since this forum is to
    discusses the usage of Visual Studio IDE such as
    WPF & SL designer, Visual Studio Guidance Automation Toolkit,
    Developer Documentation and Help System and
    Visual Studio Editor.
    Since you are working with VB6 application, I suggest that you can consult on these popular third-party forums which support Visual Basic 6for better solutions:
    VB Forums
    VB City
    Best regards,
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Event 1000 and event 1026 Faulting application name: DistributedCacheService.exe

    I have 2 WFE, 1 App,  all 3 Distributed Cache in Services On Server of CA are started,  but only 2 AppFabricCachingService are started on 3 server Services. When I go to notable server which AppFabricCachingService not started, found
    the application event log 1000 and 1026.
    Event 1000:
    Faulting application name: DistributedCacheService.exe, version: 1.0.4632.0, time stamp: 0x4eafeccf
    Faulting module name: KERNELBASE.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c78c
    Exception code: 0xe0434352
    Fault offset: 0x000000000000a49d
    Faulting process id: 0x3ff0
    Faulting application start time: 0x01cf5e97bc497df8
    Faulting application path: C:\Program Files\AppFabric 1.1 for Windows Server\DistributedCacheService.exe
    Faulting module path: C:\Windows\system32\KERNELBASE.dll
    Report Id: 1bb07d62-ca8c-11e3-a299-005056b837e0
    Event 1026:
    Application: DistributedCacheService.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: Microsoft.ApplicationServer.Caching.DataCacheException
    Stack:
       at Microsoft.ApplicationServer.Caching.VelocityWindowsService.StartServiceCallback(System.Object)
       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
       at System.Threading.ThreadPoolWorkQueue.Dispatch()
    I tried many times and many method, sometimes it is WFE1, sometimes it is WFE2, now it is APP server. 
    Don't know why.
    Thanks in advance.
    Awen

    Stop it on all servers then start on App servers, if it is stable then you can add another server and more.
    But it is not recommended to run the DC on all servers in farm, but in your case you have 3 servers.here MSFT position.
    "On a farm with four or more servers, you must not start the Distributed Cache service on all servers on the farm. If you configure all
    servers as cache hosts, you may experience reliability and performance problems in the farm."
    Are all of your server in the farm have the same memory, if not then that's your problem.
    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

  • Faulting application name: IEXPLORE.EXE

    When my user trying to play any Video or access some staff on social media..IE 10 x is crashing...
    Firefox working just fine
    It IS HP Bussness Class PC, new WIn 8 Pro X 64 install
    Any ideas?
    Log Name:      Application
    Source:        Application Error
    Date:          9/5/2013 10:42:47 AM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      DSwin8.xxxxxxxxxxxxxx.com
    Description:
    Faulting application name: IEXPLORE.EXE, version: 10.0.9200.16660, time stamp: 0x51f1c5f3
    Faulting module name: mwtsp.dll, version: 1108.0.0.0, time stamp: 0x50670c44
    Exception code: 0xc0000005
    Fault offset: 0x000465f2
    Faulting process id: 0x157c
    Faulting application start time: 0x01ceaa46247c5f75
    Faulting application path: C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE
    Faulting module path: C:\Windows\system32\mwtsp.dll
    Report Id: 6e2b6b44-1639-11e3-be7c-8851fb5c73d3
    Faulting package full name:
    Faulting package-relative application ID:
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-09-05T14:42:47.000000000Z" />
        <EventRecordID>7425</EventRecordID>
        <Channel>Application</Channel>
        <Computer>DSwin8.torontoairways.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>IEXPLORE.EXE</Data>
        <Data>10.0.9200.16660</Data>
        <Data>51f1c5f3</Data>
        <Data>mwtsp.dll</Data>
        <Data>1108.0.0.0</Data>
        <Data>50670c44</Data>
        <Data>c0000005</Data>
        <Data>000465f2</Data>
        <Data>157c</Data>
        <Data>01ceaa46247c5f75</Data>
        <Data>C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE</Data>
        <Data>C:\Windows\system32\mwtsp.dll</Data>
        <Data>6e2b6b44-1639-11e3-be7c-8851fb5c73d3</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Hi Isaac Goldfarb,
    Based on BurrWalnut and Andre.Ziegler’s suggestion, please try to run SFC scan to solve this issue:
    System File Checker (SFC) scan can troubleshoot missing or corrupted system files on your computer.
    Open an elevated command prompt. To do this, type
    cmd in the Start, right-click Command Prompt, and then click
    Run as administrator in the bpottom. If you are prompted for an administrator password or for a confirmation, type the password, or click Yes.
    At the command prompt, type the command sfc /scannow and then press
    ENTER.
    The
    sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions.
    For more information, please review this article Sfc to get more help:
    http://technet.microsoft.com/en-us/library/ff950779.aspx
    Regards,
    Lany Zhang

  • Event 1000, Application Error (Faulting application name: w3wp.exe - Faulting module name: KERNELBASE.dll)

    Hello Guys,
    While running a web application am getting an error like: Remote server not responding. Below are the details of event viewers which been captured at the same time when this error happened:
    Event 1000, Application Error
    Faulting application name: w3wp.exe, version: 7.5.7600.16385, time stamp: 0x4a5bd0eb
    Faulting module name: KERNELBASE.dll, version: 6.1.7600.16850, time stamp: 0x4e211da1
    Exception code: 0xe053534f
    Fault offset: 0x000000000000a88d
    Faulting process id: 0x%9
    Faulting application start time: 0x%10
    Faulting application path: %11
    Faulting module path: %12
    Report Id: %13
    Event 1001, Windows Error Reporting
    Fault bucket , type 0
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0
    Problem signature:
    P1: w3wp.exe
    P2: 7.5.7600.16385
    P3: 4a5bd0eb
    P4: KERNELBASE.dll
    P5: 6.1.7600.16850
    P6: 4e211da1
    P7: e053534f
    P8: 000000000000a88d
    P9: 
    P10: 
    Attached files:
    C:\Windows\Temp\WERC9CD.tmp.WERInternalMetadata.xml
    C:\Windows\Temp\WERC9CE.tmp.hdmp
    C:\Windows\Temp\WEREE30.tmp.mdmp
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_w3wp.exe_30877924d6b2c607fe88a8718915f25fb79093_cab_e905f2b0
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: d46a6849-8f6a-11e1-98af-00215e6e4855
    Report Status: 4
    This is an priority issue which we are facing in IIS. IIS is configured for Framework 2.0 and underlying OS is - Windows
    Server 2008 R2 Standard.This issue is replicable and occurring frequently Please suggest how to resolve it. Any input related to above issue is appreciable.

    Please refer similar discussions and see if they help
    Faulting application name: w3wp.exe 
    http://telligent.com/support/communityserver/community_server_2008/f/288/t/1067447.aspx 
    Event ID: 1000, Faulting application w3wp.exe, faulting module unknown, 
    http://social.msdn.microsoft.com/forums/en-US/clr/thread/9be88a2f-c8cc-4a73-9371-45ab73982123
    For IIS related queries, please post them in IIS forum - http://forums.iis.net/
    A UNIVERSE without WINDOWS is CHAOS !
    This posting is provided "AS IS" with no warranties or guarantees and confers no rights.
    About Me !!!

  • Fault application name flash.exe dvaui.dll

    hi. i have been having recurring crashes, Windows Applications Event View log indicating that Flash exe failed, see below:
    Faulting application name: Flash.exe, version: 11.5.1.349, time stamp: 0x4e5bcaea
    Faulting module name: dvaui.dll, version: 5.0.0.19847, time stamp: 0x4d79ee6c
    Exception code: 0xc0000005
    Fault offset: 0x0015e8f8
    Faulting process id: 0x1c4c
    Faulting application start time: 0x01cc90a28b6b6f98
    Faulting application path: C:\Program Files (x86)\Adobe\Adobe Flash CS5.5\Flash.exe
    Faulting module path: C:\Program Files (x86)\Adobe\Adobe Flash CS5.5\dvaui.dll
    Report Id: b892f5b4-fca8-11e0-9705-0009dd50a16a
    This has been happening on my new machine when i work in Flash Pro CS5.5 - a part of CS5.5 Classic Collection, when i make animations using drawing and various other tools, specifically, when i do things quickly.
    i mean that literally; when i select a keyframe, deselect deselect it, reselect, right-click, delete, do these quicly, sometimes it will happen when i go to save my work after having made many changes to it, then Flash will crash i.e. the cursor spins, the the interface is dimmed, and then all my internet browswers dim including windows browswers, the task bar disappears, Start menu disappears - i cant shutdown, so i hit the restart btn on my tower, but Windows doesnt load, rather i get a black screen asking me to insert a media disc, if i dont and restart by hitting the button on the tower, i get the black screen asking for a media disc, which i do, i insert the Windows installation cd in my optical drive, go to the Repair tools, and use the Shutdown btn there. This is the only way to get my machine out of the loop, to recover, and Windows starts normally.
    Because the crash was happening when i work fast, i was wondering if it's to do with a memory issue, and BTW, saving an .fla takes about 10-20 seconds, is NOT immediate, and disables the software as it is saving. The file in question is 1,092 KB.
    My machine consists of an i7 2600k cpu, unraided 4 hard disks including a Vertex SSD 120G for the OS and programs, and 3 additional WD at 7200rpm 1 and 2 terrabyte sized, a DVI PCI-e Video Card GTX 580 3G "Phantom". And 16G ram - Gskill DDR3 1600MHz
    And, i am NOT having this issue with any other software; i have CS5.5 Classic Collection installed on my machine and am using Windows 7 Ultimate 64bit.
    I would appreciate your help.
    thanks

    Have you tried recreating your preference files in Flash CS5.5? Please be sure to backup any previous preference files before doing this so that you can save them if needed
    http://kb2.adobe.com/cps/520/cpsid_52048.html

Maybe you are looking for

  • Upgraded to 1.1, problem navigating in grid

    Hi Is it possible to change the result grid behaviour to be like in 1.0? I find it quite problematic to not beeing able to use the cursor keys to navigate in the grid. Every cell always gets in edit mode directly even though it's a read only grid, an

  • White Gridlines in MS Excel

    Hello One of our PowerrBook G4 Computer has a small problem. In Excel all the gridlines are white. When I go to the settings, the color of the grid is set to automatic (Automactic is black). When I switch to the black, the grid is availible. I need t

  • Photoshop CS3 gives me an error "not compatible with his version.."  when trying to reopen files

    Photoshop CS3 gives me an error- "Could not complete your request because this file is not compatible with his version of photo shop" when I try and reopen psd's or layered tiffs, it usually happens to files over 1gb in size, I can open them up in il

  • Lost Version of iMovie after HDD Replacement

    Hi The hard drive on my 27" iMac failed and was replaced for free by my local Apple store under the replacement program. All of my data was backed up, but I lost some of my applications. When my iMac was returned, it had an out of date version of OSX

  • McAfee Siteadvison 3.1 warns that FF 3.6.8 has problems when downloading directly from Mozilla

    FF 3.6.7 popped up a download msg telling me that 3.6.8 was avaliable to correct problems. The update seemed to go as expected, but when I opened the new version and went directly to Mozilla to download a copy of the program from there, McAfee's Site