I already re-installed Autocad and .Net stuff..
Window Error below
Faulting application name: acad.exe, version: 28.0.161.0, time stamp: 0x5a9e3d4e
Faulting module name: clr.dll, version: 4.7.2661.0, time stamp: 0x5ac79663
Exception code: 0xc0000005
Fault offset: 0x000000000019a379
Faulting process id: 0x2500
Faulting application start time: 0x01d3f797ed90fcc7
Faulting application path: C:\Program Files\Autodesk\AutoCAD 2018\acad.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 749c4ac1-638b-11e8-9872-0090f5cc983a
Solved! Go to Solution.
Solved by john.vellek. Go to Solution.
Hi @Anonymous,
I am sorry you are having this crashing. Can you please prepare a NFO file for me? This will help me understand the configuration of your computer. Please also tell me any CER crash report numbers that you have submitted (if any).
This appears to be a .NET issue but I would love to see the above information before making suggestions.
Please select the Accept as Solution button if my post solves your issue or answers your question.
Hi @Anonymous,
While await some more information from you, please verify that your AutoCAD 2018 is fully up-to-date using your account page or your Autodesk Desktop App.
i suggest that you also take a look at your graphics drivers to make sure they are current as well.
Please select the Accept as Solution button if my post solves your issue or answers your question.
did a uninstall of .net 4.7.1 and install of 4.6.2
repaired autocad install
reset autocad to defaults...
no crash as of yet
(NPO file attachment on this page does not seen to work.)
Hi @Anonymous,
i guess I would have tried going to .NET 4.7.2 but I am glad that this working for you at present. You can zip up the NFO if you want me to look at it or you can email it to me at john.vellek@autodesk.com (please include a link to this thread in the email).
Hi @Anonymous,
It looks like your graphics driver is fairly old. I suggest trying this newer one.
(There is a print job stuck in the queue)
It also appears that you have quite a few things running at startup. If the problem returns you can try running a MSCONFIG (diagnostic startup) to see if turning any of them off helps.
IN your Windows Error Reporting I see that you have several instances of Razer Syanpse Service.exe that fails and also WSCOMMCNTR4.exe.
Lastly, I see that clr.dll has been crashing which indicates a .Net error is likely at the root. This last occurrence was at 5/292018 just before noon. If you changed your .Net after that lets see if that error returns.
another crash ...looks like the same thing
looks like Windows update installed .Net 4.7.1 again...
Faulting application name: acad.exe, version: 28.0.161.0, time stamp: 0x5a9e3d4e
Faulting module name: clr.dll, version: 4.7.2650.0, time stamp: 0x5ab1c520
Exception code: 0xc0000005
Fault offset: 0x000000000017f4a9
Faulting process id: 0xc30
Faulting application start time: 0x01d3fea0e0f75053
Faulting application path: C:\Program Files\Autodesk\AutoCAD 2018\acad.exe
Application: acad.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FEF347F4A9 (000007FEF3300000) with exit code 80131506.
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: ac3d293a-6aa3-11e8-9781-0090f5cc983a
still randomly crashing
Faulting application name: acad.exe, version: 28.0.161.0, time stamp: 0x5a9e3d4e
Faulting module name: clr.dll, version: 4.7.3062.0, time stamp: 0x5ab9567c
Exception code: 0xc0000005
Fault offset: 0x00000000000a8e2f
Faulting process id: 0x2008
Faulting application start time: 0x01d40cae283f25eb
Faulting application path: C:\Program Files\Autodesk\AutoCAD 2018\acad.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 6ec6ca8b-78a2-11e8-95df-0090f5cc983a
HI @Anonymous,
I am sorry you are still seeing this issue. I found this page that might give you some more detail.
I suggest that rather than continue to fight this, I would rebuild the computer from scratch. It sounds like you likely have some bad registry entries.
Please select the Accept as Solution button if my post solves your issue or answers your question.
Can't find what you're looking for? Ask the community or share your knowledge.