There are several reasons that NVivo may be coding slowing and/or crashing:

1. Make sure you have a default printer defined on your Windows device.
   1. NVivo relies on this to display the codes in the right hand window. 
      1. If the option for Windows to manage your printers and scanners is selected under Printers and Scanners, disable it and select either a physical or print to pdf app. 
      2. Avoid using network printers as your default if you sometimes work outside of the network as that will also cause the issue.
2. Sample Project: After confirming a printer has been defined, please check and see if you experience the same slowness with the Sample Project to determine whether or not the issue is project specific. If the Sample Project is working as expected, this indicates a project specific issue.
3. Workflows
   We recommend that you work on your projects locally (i.e. the desktop or other accessible location)
   1. Upload them to the mapped drives when you are done working on it for the day.  
      1. NVivo creates a Temp folder when you open the files directly on a network. Network latency can cause slowness.
      2. Uploading copies to cloud drive provides redundancy of the project files in case corruption occurs or a project file is accidentally deleted.
4. Cloud Storage Synch
   Cloud Storage Services like ICloud and OneDrive take memory resources from your computer when they synch with your local computer/desktop. They can also cause your local file changes to be overwritten.  We recommend disabling synch while working on your NVivo files.
5. Number of Codes
   NVivo navigates the coding structure in the database to find the code you have selected. If you have thousands of them, the coding process in particular may be very slow.
   1. This is not relevant if multiple projects have the same issue.
6. Large Source Files
   1. If you have source files of several hundred pages, please be aware that NVivo must navigate the pages as you work.
      1. We recommend that you split them into smaller source files or even smaller projects (where possible).
   2. If you are importing with large audio/video files, we recommend you store them outside of the project.
      
      1. Select the NVivo audio or video file (that contains the media file) in the List View.
      2. On the Home tab, in the Item menu, select Audio or Video Properties.
      3. Open the Audio or Video tab.
      4. Under Media, select Not Embedded - file location, then Browse to specify the location for the stored media file.
7.  Project File Size
   Once a project file becomes over 2GB in size, you will likely experience performance issues.

1. 1. Remove any unnecessary content from the project or split the project into multiples (if possible).
2. Code Hierarchy/Opening Codes
   1. We recommend a node hierarchy of no greater than 5 levels deep.
3. Customization Folder Corruption
   1. Deleting the customizations in the path below can also fix slowness when opening codes.  
      C:\Users\[username]\AppData\Roaming\QSR_International
      C:\Users\[username]\AppData\Local\QSR_International  (If it exists)
      1. As of NVivo 14.23.3, "QSR_International" is now "Lumivero, LLC".
      2. Within these folders, delete all folders where the name starts with NVivo.exe_Url (e.g rename to old NVivo.exe_Url).

If none of these configurations apply to the project, you can also compact your project regularly when they see a decrease in performance which removes database fragmentation.
See this Compact Project Help Page for details: