Wipeout causes hard crash

[hencoop]

I am having an issue with wipeouts again (here is the Prior thread).  I've updated my video card driver, the solution from the prior thread, but to no avail. 

My drawing has two xreferences, both are overlays.

I have run RECOVER on the primary file and both xreferences.  The results of each was "No errors found".

I have exectuted (REPEAT 6  (VLA-PURGEALL *active-document*)) on each drawing (setting and afterwards releasing *active-document* in each)

Actions that cause a hard crash:

• Grip editing the wipeout (two other wipeouts do not cause a crash)
• Starting the STRETCH command and specifying a crossing rectangle that crosses the wipeout.
• Selecting the wipeout by any means (except by AutoLISP).
• Deleting the wipeout and creating a new wipeout and then trying to select the new wipeout:
  • Select the existing wipeout without crashing by using (SSGET "X" '((0 . "WIPEOUT"))) and then unselecting the other wipeouts that don't have this problem.
  • recreate a wipeout using a NEW polyline as the boundary, deleting the polyline.

I was able to get an editable wipeout created... for a short time.  I 1st created a square wipeout by specifying each corner (no polyline).  Editing it caused no problem.  Next, I created a random polygonal wipeout by specifying each corner.  Editing it caused no problem.  Then, I created a rectangular polyline by specifying corners.  I chamfered this polyline, offset it to make the chamfered corner intersect the rectangle corner and then offset it again by 0.025" inside.  This polyline is where I need it to mask.  I created another wipeout from this polyline, deleting the polyline.  I was able to grip edit this new wipeout... 3 or 4 times before a hard crash.

[michal.holda.]

Hi @hencoop, 

Have you tried to repair the drawing using the methods from the article - https://knowledge.autodesk.com/support/civil-3d/troubleshooting/caas/sfdcarticles/sfdcarticles/How-t...

Have you tried to reset your C3D profile? See: https://knowledge.autodesk.com/support/civil-3d/troubleshooting/caas/sfdcarticles/sfdcarticles/Resol.... 

[hencoop]

@michal.holda. I have already done some of the suggested steps as previously described.  I did a WBLOCK as suggested in the linked information.  The file resulting from that has the same problem.  This problem does not happen in any other drawing I have.  It reminds me of a similar problem I had decades ago where AutoCAD would experience a hard crash when I viewed a certain area at a closer zoom factor than the drawing was happy with.  I was never able to solve that problem either.  Today, my WBLOCK output drawing crashed when I zoomed in to the area where the offending wipeout HAD been (it was no longer in the source drawing).

Since this problem has limited itself to just one specific drawing, I am not willing to reset my AutoCAD to defaults.  Besides, my AutoCAD installation is less than a month old.  I reset (essentially reinstalled) my Win10 OS and reinstalled and updated my AutoCAD 2022, AutoCAD Map 2022 and AutoCAD Civil 3D 2022 less than a month ago.  This was motivated by my OS misbehaving (likely because of the "adjustments" I made to avoid using MS Edge and One Drive).

[hencoop]

@michal.holda. 

I used the ORBIT command to change the viewing angle away from PLAN and then zoomed in and out repeatedly without crashing.  When I selected ALL I crashed.

I removed all of the wipeouts that were not in blocks and saved the drawing.  I still crashed when zooming in on the area where they were.  There is a dynamic block of a door in plan there.  It has wipeouts in it.   I deleted it and then zoomed in and out on the are very much without a crash.  At this point, no other wipeouts are in the drawing, but there is an xref that has more of the same dynamic door block with wipeouts.

I reinserted the dynamic door block, zoomed in and out and quickly crashed.  Notably, the reinserted dynamic block was "inverted", i.e., the draworder of all its elements was reversed.  the wipeouts were all on top of the other elements.

This dynamic door block is causing the problem.  I edited it to have only HATCHes instead of WIPEOUTs and correct the draworder, but it still causes crashes.  I inserted the reworked version of it in a new blank drawing, selected it and zoomed in and out and quickly crashed.

I've attached the problem block.  I atttached the version of the block written out of the other drawing which does not have the draworder or crashing problem (and it does have wipeouts).  I lost the edits I made replacing the wipeouts with hatches.  It makes no difference, both versions caused a crash in my one drawing (but not the other!).  This block version should have the correct draworder.  I've attached the drawing that crashes (expansion plan) when this door block is in it (and its xreference that does not crash even though it has several of these door blocks in it).

[hencoop]

@michal.holda. The problem is NOT limited to WIPEOUTs.  I replaced ALL wipeouts with images (I.e., a 1x1 pixel bitmap image scaled, clipped and faded) and the crashing problem persists.  Here is the revised drawing with IMAGEs instead of WIPEOUTs.  To force the crash, I must select a block containing the image and then zoom far enough in so that some of its clipping boundary is off the screen.

[hencoop]

@michal.holda.  This morning I created a wipeout in a blank new drawing.  Then, I zoomed in and out a lot... no problem.  Then, I selected the wipeout and zoomed in until a boundary point was outside my display... HARD CRASH.

If you can create a wipeout in a new drawing (in AutoCAD Civil 3D 2022.0.1 Update), select it, and scroll zoom in until part of it is outside your display without causing a hard crash, I'll be persuaded to reset my AutoCAD to defaults.

[hencoop · Accepted solution]

@michal.holda. I installed AutoCAD Civil 3D 2023 (without any updates) and tried to recreate this problem and could not. 🙂

[hencoop]

The new AutoCAD Civil 3D 2023 installation just crashed (about noon today) exactly like the old AutoCAD Civil 3D 2022 installation had been!  This is the Event report:

Faulting application name: acad.exe, version: 30.2.53.0, time stamp: 0x61f8c0b0
Faulting module name: rblast16.hdi, version: 16.2.53.0, time stamp: 0x61f8acf8
Exception code: 0xc0000409
Fault offset: 0x0000000000005341
Faulting process id: 0x34e4
Faulting application start time: 0x01d8de556af92542
Faulting application path: C:\Program Files\Autodesk\AutoCAD 2023\acad.exe
Faulting module path: c:\program files\autodesk\autocad 2023\drv\rblast16.hdi
Report Id: 4e34e1a2-40c7-4fc7-a2c5-12106fc6f3ae
Faulting package full name: 
Faulting package-relative application ID: 

I looked back through the Event Viewer for my first crash of the day using AutoCAD Civil 3D 2022 which I found at 10:10 AM this morning.  This is that Event report:

Faulting application name: acad.exe, version: 30.1.173.0, time stamp: 0x63229462
Faulting module name: rblast16.hdi, version: 16.1.173.0, time stamp: 0x632278f8
Exception code: 0xc0000409
Fault offset: 0x0000000000005404
Faulting process id: 0x38dc
Faulting application start time: 0x01d8dd657cd1e88f
Faulting application path: C:\Program Files\Autodesk\AutoCAD 2022\acad.exe
Faulting module path: c:\program files\autodesk\autocad 2022\drv\rblast16.hdi
Report Id: aef43f4d-ca59-4e7f-ad27-fd9744747371
Faulting package full name: 
Faulting package-relative application ID: 

I should have checked the Event Viewer the first time this happened (but it typically just says the faulting app is acad.exe)  The faulting module is rblast16.hdi in both cases.  This recommended fix is to update the video card drivers.  I had done that in C3D 2022.  I rolled it back to a previous driver to see if the latest driver was causing the problem... it wasn't.  Another suggested fix is to set the system variable GFXDX12 to 0.  This rolls the DirectX implementation back to DX11.  Some video cards are not compatible with DirectX 12.  Mine is an Nvidia Quadro RTX 4000 with 8GBytes of GDDR6 256 bit Samsung RAM.  Specifications state: GPU supports DX 12.0 API, Hardware Feature Level 12_1.

I've made sure that when I start AutoCAD Civil 3D 2022 there are no customizations loaded at all... no custom menu, no custom lisp, no custom arx... nothing.  I could still make it crash by selecting something with a wipeout in it and zooming in on it.  Then, I changed GFXDX12 from 1 to 0, closed and reopened AutoCAD C3D 2022.  I could not make it crash!.  I changed GFXDX12 back to 1, closed and reopened AutoCAD C3D 2022 and tried again to confirm... BUT I COULD NO LONGER MAKE IT CRASH!?  It appears to have something to do with DirectX12, but only until AutoCAD is directed to use DirectX11?  After which DirectX12 is fine?

This is so very baffling.  I'll run it some on Friday to see if the no-crash condition holds. (I've got to do a site visit tomorrow).

[hencoop · Accepted solution]

I've reenabled all of the customizations I use and still cannot cause the problem.

RECAP:  The crashing appears to be caused by the video card driver and more specifically AutoCAD's implementation of DirectX 12 in conjunction with it, but only until the AutoCAD system variable GFXDX12 is cycled from 1 to 0 and back to 1 again.  Having finally done that cycle, I can no longer reproduce the crash on demand.  I could reproduce it up and until I cycled GFXDX12 back to 1 in my clean installation with absolutely NO customizations.  I added all of my customizations back in and I cannot reproduce the crash on demand as I had been able to.

P.S. Prior to this problem arising, I had experienced a number of times that AutoCAD had turned graphics hardware acceleration off automatically.