Recently updated to sp1 and it fixed a different fatal error I was receiving however, now I have another issue where AutoCad closes when I am switching or closing out drawings. I get this in my event viewer ever time it happens. Any idea what could be causing this? The pc is a new hp with a xeon e3-1270 16gb ram with a Quadro k4000
Log Name: Application
Source: Application Error
Date: 7/15/2014 3:08:05 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: XXXXXXXXXXXXX
Description:
Faulting application name: WSCommCntr4.exe, version: 4.0.3.0, time stamp: 0x52df746e
Faulting module name: WSCommCntr4.exe, version: 4.0.3.0, time stamp: 0x52df746e
Exception code: 0xc0000005
Fault offset: 0x0000000000015a1e
Faulting process id: 0x12cc
Faulting application start time: 0x01cfa02b51eea97d
Faulting application path: C:\Program Files\Common Files\Autodesk Shared\WSCommCntr4\Lib\WSCommCntr4.exe
Faulting module path: C:\Program Files\Common Files\Autodesk Shared\WSCommCntr4\Lib\WSCommCntr4.exe
Report Id: bad83072-0c5b-11e4-a616-a0481ca055a6
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-07-15T20:08:05.000000000Z" />
<EventRecordID>15600</EventRecordID>
<Channel>Application</Channel>
<Computer>2UA4180PTL.3s.local</Computer>
<Security />
</System>
<EventData>
<Data>WSCommCntr4.exe</Data>
<Data>4.0.3.0</Data>
<Data>52df746e</Data>
<Data>WSCommCntr4.exe</Data>
<Data>4.0.3.0</Data>
<Data>52df746e</Data>
<Data>c0000005</Data>
<Data>0000000000015a1e</Data>
<Data>12cc</Data>
<Data>01cfa02b51eea97d</Data>
<Data>C:\Program Files\Common Files\Autodesk Shared\WSCommCntr4\Lib\WSCommCntr4.exe</Data>
<Data>C:\Program Files\Common Files\Autodesk Shared\WSCommCntr4\Lib\WSCommCntr4.exe</Data>
<Data>bad83072-0c5b-11e4-a616-a0481ca055a6</Data>
</EventData>
</Event>
Thank you I greatly appreciate the reply. I will try that and update at a later time if any more issue come up.
@Anonymous wrote:Thank you I greatly appreciate the reply. I will try that and update at a later time if any more issue come up.
Just curious if this helped you. It looks like one of our users is getting the same errors.
Thanks!