I reported this issue on github a while back, but it turns out it is a reasonably serious DLL conflict. More details here:
Collaboration for Revit: 2015.6/2016.1 breaks other add-ins | Revit Products | Autodesk Knowledge Network

Users reported that installing the Collaboration for Revit® 2015.6 or 2016.1 add-in is causing other add-ins to stop working.
There seems to be a DLL conflict with the latest Collaboration for Revit add-in.
Status: This incident is currently being investigated for a possible cause and resolution
Incident ID: 72448
Workaround: Continue using the 2015.5 or 2016.0 version of the Collaboration for Revit Add-in.
Note: If you need to remove the newer add-in (Autodesk A360 Collaboration for Revit…), you will also want to remove the new version of the “Personal Accelerator for Revit” and “Dynamo 0.8.1”

Did you know that you can access Navisworks Options directly from the Start Menu? Just click on Start and type “Options Editor”. Then, if you hover over the entries in that list you can pick the Options Editor for the right version of Navisworks by reading the tooltip.

Why would we want to do this? Well, if you have a Graphics Driver problem, it might cause Navisworks to continually crash when you start the program. If you head into the Options Editor, you can go to Interface – Display – Drivers and disable various options until Navisworks decides to load up again.

For example, try unticking everything except OpenGL – you might find that Navisworks can now load (this tip may particularly help if you are trying to run Navisworks in a virtual machine).

Another stable choice may be to select only the software-mode drivers:

Here is the persistent crash – it was happening when any RVT file was closed:
View Revit 2015 Update 5 crashes when closing any file 

Here’s what fixed the problem:
Renaming “C:ProgramDataAutodeskApplicationPlugins” folder (this disables certain integrations)

Upon further investigation, I had to move the AutodeskSiteDesignerForRevit2015.bundle out of the ApplicationPlugins folder (in other words, delete it) to correct the issue. Then, I installed R2 (Autodesk_Revit_2015_R2.sfx.exe , Autodesk Site Designer (AutodeskSiteDesignerForRevit.msi), and UR5 for R2 (Autodesk_Revit_2015_R2_UR5.sfx.exe).

Here’s what didn’t work:

  • renaming uistate.dat
  • renaming revit.ini
  • renaming  “C:ProgramDataAutodeskRevitAddins2015.ren”
  • reinstalling Revit 2015 using steps below
  • applying RVT2015UR4.msp
  • uninstalling Dynamo
  • running Revit as Administrator
  • uninstalling Sundial and other Citrix Revit versions
  • renaming Revit program folder and Addins folder and reinstalling
  • making a new user profile

Reinstall steps:

  1. Uninstall Revit 2015 from Programs and Features in Windows
  2. Start Setup from your Suite media (in my case, Building Design Suite Ultimate 2015)
  3. You will need to input your serial number
  4. Ensure only Revit 2015 is ticked (gray tick), and do not install Service Packs
  5. Also untick BIM360 addin under Revit 2015 (if it finds a newer one the setup may fail)
  6. Untick BIM360 addin under Navisworks 2015 (if it finds a newer one the setup may fail)
  7. After Revit 2015 is installed, start it up to ensure activation is ok
  8. Install R2 (Autodesk_Revit_2015_R2.sfx.exe)
  9. Install UR5 for R2 (Autodesk_Revit_2015_R2_UR5.sfx.exe)
  10. Start Revit and test closing a file

How did this bug happen? I’m not entirely sure, but I think the number of  updates and the confusion around which UR5 update is for which Revit version may have resulted in Revit 2015 getting sad. But, its happy again now… and its a good lesson to remember the ApplicationPlugins folder when diagnosing Revit problems.

Something from the journal:
ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=000007FEFCDE940D 

In our case, we had to add local PC “Users” permissions for Full Control to this file:

I recommend that you review each PackageContents.xml in the ProgramData location to check for appropriate permissions.

Key lines from journal:
‘ 0:< Autodesk Revit 2014 
‘ 0:< 64-bit load point = C:Program FilesAutodeskRevit 2014 
‘ 0:< this journal = C:UsersljohnsonAppDataLocalAutodeskRevitAutodesk Revit 2014Journalsjournal.0008.txt 
‘ 0:< ::0:: Delta VM: Avail -54 -> 8387401 MB, Used +8 -> 186 MB, Peak +39 -> 218 MB; RAM: Avail -15 -> 12989 MB, Used +13 -> 241 MB, Peak +14 -> 242 MB 
‘ 0:< Exception occurred 
‘C 24-Sep-2013 09:05:39.639;   0:< ExceptionCode=0xe0434352 ExceptionFlags=0x00000001 ExceptionAddress=000007FEFD17940D 
‘ 0:<   System (MB) [Available /  Total ]  [Revit Memory Usage (MB)   ] 
‘ 0:< RAM Statistics:    12989 /    16291       241=InUse      242=Peak  
‘ 0:< VM  Statistics:  8387402 /  8388607       186=InUse      218=Peak  
‘ 0:< Unconverted MessageBox “An unrecoverable error has occurred.  The program will now be terminated.  All of your data has been recently saved, so there is no need to create recovery files.” 

Basic fix method found at:
Other possible solutions:
  • Delete Autodesk, Inc. folder
  • Delete cascade
  • Make a new user profile and see if that works
As per:

I recently tried to open an RVT project in Revit, and Revit 2013 with web Update 2 would just hard crash (no error report or anything).

What to do?

I copied the RVT to C:TEMP – still no go.

So perhaps a linked import with saved Absolute Path is causing the issue?

I disabled my LAN adapter, then opened the file from C:TEMP again (with Audit checked) – and it opened!

Next step – resave the file to its network location.

Then, one by one, reload links.  Reloaded all RVT links ok.  Save.  Now for the DWG links.  They all loaded ok too!

Save, close the file and re-open.  No problems now.

It would seem that the Audit was able to correct something, but Revit wanted itself to be isolated from the network.

In conclusion, disabling your network adapter may allow you to open a file that is causing a hard crash in Revit.

EDIT – interestingly, opening the RVT in an NDA related product showed a ‘dimensions no longer parallel’ error message.

This poem has done the email forward rounds for years, and has been incorrectly attributed to various authors.  It is in the style of Dr Seuss, but was authored by Gene Ziegler.  Here is the full version, from this link:

Bits Bytes Chips Clocks
Bits in bytes on chips in box.
Bytes with bits and chips with clocks.
Chips in box on ether-docks.

Chips with bits come. Chips with bytes come.
Chips with bits and bytes and clocks come.

Look, sir. Look, sir. read the book, sir.
Let’s do tricks with bits and bytes, sir.
Let’s do tricks with chips and clocks, sir.

First, I’ll make a quick trick bit stack.
Then I’ll make a quick trick byte stack.
You can make a quick trick chip stack.
You can make a quick trick clock stack.

And here’s a new trick on the scene.
Bits in bytes for your machine.
Bytes in words to fill your screen.

Now we come to ticks and tocks, sir.
Try to say this by the clock, sir.

Clocks on chips tick.
Clocks on chips tock.
Eight byte bits tick.
Eight bit bytes tock.
Clocks on chips with eight bit bytes tick.
Chips with clocks and eight byte bits tock.

Here’s an easy game to play.
Here’s an easy thing to say….

If a packet hits a pocket on a socket on a port,
and the bus is interrupted as a very last resort,
and the address of the memory
makes your floppy disk abort
then the socket packet pocket
has an error to report!

If your cursor finds a menu item
followed by a dash,
and the double-clicking icon
puts your window in the trash,
and your data is corrupted cause
the index doesn’t hash,
then your situation’s hopeless,
and your system’s gunna crash.

You can’t say this? What a shame, sir!
We’ll find you another game, sir.

If the label on the cable
on the table at your house
says the network is connected
to the button on your mouse,
but your packets want to tunnel
on another protocol,
that’s repeatedly rejected
by the printer down the hall,
and your screen is all distorted
by the side-effects of gauss,
so your icons in the window
are as wavy as a souse,
then you may as well reboot
and go out with a bang,
cause as sure as I’m a poet,
the sucker’s gunna hang!

When the copy of your floppy’s
getting sloppy on the disk,
and the microcode instructions
cause unnecessary risc,
then you have to flash your memory
and you’ll want to RAM your ROM.
quickly turn off your computer
and be sure to tell your mom!


More info at:
Plagiarized Poem – Why Computers Sometimes Crash! by Dr. Seuss

To kill the Communication Center … in Regedit replace all the (1) with (0) see image.
(you will need to login to Revit Forum)

Then rename WSCommCntr2.exe to AAWSCommCntr2.exe
( C:Program FilesCommon FilesAutodesk SharedWSCommCntrlibAAWSCommCntr2.exe)

via this post
New AUBench (archive) – Page 22

Obviously, you may need to change the Registry location depending on what version of Revit you are using…

If you don’t want to manually edit the Registry, you can use the CAD Manager Control utility as per this post:
Revit 2011 closes right after the splash screen – Autodesk Discussion Groups

If you are having Communication Center issues, it may be due to a corrupted XML file.  Refer to this Revit support page:
Revit 2010 products hang at or before splash screen

This AutoCAD support page is along similar lines:
How to disable the Communication Center in Autocad? 

I recently stumbled across the fix for an issue that has annoyed me for ages.

The problem we had was that Revit would always crash when tearing off any ribbon panel. This issue affected two of our high end Vista 64 bit Workstations. I had tried many things to fix the issue, all to no avail. So, are you ready for the solution?

Both of these workstations were running a pre-release version of Service Pack 2 for Vista. The Windows desktop had the following text imprinted on it – Build 6002 – Evaluation Version. I determined that this note referred to a Release Candidate of Service Pack 2, and not to the actual licensing of Vista itself. The fix is as follows:

  1. Uninstall Service Pack 2. (Go to Control Panel – Programs and Features. Then click ‘View Installed Updates’. The update is labeled as Service Pack for Microsoft Windows (KB948465). Once this was uninstalled, I could now tear off the ribbon panels successfully, with no crashes.
  2. To put Service Pack 2 on, you can use a couple of methods. After removing SP2, I allowed Windows Update to install updates. However, this did not reinstate SP2 onto my system.
  3. I then downloaded the Service Pack 2 package for 64 bit, and installed it. Finally, I was back at SP2, and my ribbon panels would still tear off without any crashing!

Please note that this process will probably take a couple of hours. However, I am very happy that I can now tear off the Workplane ribbon panel – it is very handy to have that panel always visible.I guess I better contact Autodesk now and notify them of the fix…this Service Request has been open since 23 June 2009!