If camera raw also crashes I would suspect a problem with either read permissions on the images or some sort of file corruption so I would check that first. If that is OK you might try sharing one of the offending images here through a dropbox (or similar) link so others can test whether this is a general problem with certain kinds of dng files.
I have just gotten home so I fired the PC up and the same issue is occurring. I selected an image on my W raid drive, copied it over to my main drive and tried opening the dng with PS. The copy seemed to go fine BUT ps crashed. I sent off a crash report. I then tried importing the copied file at its new location. The import seemed to go ago and then the following error message appeared which I have posted in the attachment. I also grabbed the properties of the file at the same time. As I say, moving the file seemed to cause no issues...
I have uploaded a representative image if people wish to see. The image should have an embedded custom camera profile created by the passport software. It is dual illuminant in case that is a factor. I am wondering if this is a factor since the profiles have been moved and changed in this release. I embed my custom profile in the dng. Can people see the profile?
If it is a file permissions issue, could it somehow be related to the following issue I posted about in LuLa a few months ago here LuLa Thread I had on file permissions and issues resolving them.
I am not able to make any changes on the image in LR CC. If I zoom in on PV4 edited images before the upgrade, I now get a File Access was Denied error message...
I’m having no problems using the sliders with your image or zooming 1:1
Could it be a permissions issue?
Dose the folder & partition have read & write access?
Several months ago I posted in here re file permission issues I was having. I also posted the following on Luminous Landscape forums here http://forum.luminous-landscape.com/index.php?topic=120830.0
At the bottom of page 2 is the result. It took around 3 months to resolve. I wonder if this update returned the file permissions issue?
The linked dng file works perfectly fine in Classic, Lightroom CC, and camera raw in Photoshop. It's clearly not the file or Lightroom but something hardware related on your computer or a system misconfiguration which could be permissions related. Very hard to tell from a distance.
The following did the trick for me. LR, Bridge, ACR and PS are now working as they should.
This comes from the following Adobe Help File. Troubleshoot unexpected behaviour in user accounts
5. Reset the access settings on the account-specific application data folders.
Complete this task only if the account that you are troubleshooting is an administrator account and is not on a network domain.
Account-specific errors can occur if the account doesn't have full read/write access to the folders with the Adobe application preferences files and account-specific data files. You can use the icacls command to reset the access settings. Do the following:
Close all applications.
Choose Start > All Programs > Accessories. Right-click Command Prompt and choose Run As Administrator. A command-line window opens.
In the command-line window, type each of the following commands exactly as they appear below. Press Enter after each command.
Important: Type a space before and after each of the switches -- /T, /C, and /grant -- in every command.
icacls "%userprofile%\AppData\Local" /T /C /grant "%username%":F
icacls "%userprofile%\AppData\Roaming" /T /C /grant "%username%":F
icacls "%userprofile%\AppData\Local" /T /C /grant system:F
icacls "%userprofile%\AppData\Roaming" /T /C /grant system:F
Close the command-line window.
Open the Adobe application and try to reproduce the issue.
What I find interesting is that this issue occurred when I upgraded from 7.1 to 7.2. Now from 7.2 to 7.3 the same issue occurred. I wonder if this is something specific to my machine or something with a wider impact?