Lightroom CC: Not responding - Windows blue cicle of death

  • 2
  • Problem
  • Updated 3 years ago
  • (Edited)
I continually encounter the situation of LR hanging ( not responding) when in Library module. I'm unable to do any other work when this is going on as LR is hogging control. Getting the Task manager to display can be difficult as I usually have to end the LR task via Task manager. When I do that nothing appears to have been lost. I also had this problem with LR5 versions.
The Camera raw cache is set to 12GB and I am NOT writing metadata changes to xmp files ( only with the ctrl/S cmd). I have 20GB of memory on a Dell XPS desktop with quad intel i7 processors running windows 8.1. The library is on the 'C' drive and all folders are on an external drive. I'm using two displays, one in grid mode the other in loupe mode.
LRCAT is 1.39GB
101520 all photographs
'C' drive 1.17 TB free of 1.80TB
External drive (E) 655GB free of 2.72GB
Keywords file when last saved 96/21/15) 325KB

This has happened under numerous situations when in the Library module. It usually occurs when I'm keywording multiple selected photos and adding titles and caption and then move on to select a another photo for keywording. I do a lot of nature photos and have a large bird/animal hierarchy for proper classification. I also have a large geographic keyword hierarchy to be able to pinpoint geographic locations of the photos. I use the "filter keywords" a lot and have the "keyword tags" area set to "will export". I've noticed that sometimes when I start to enter a keyword in the "filter keywords" prompt it displays one character and then it can be 5-10 seconds for the rest of my typed keyword to appear. It is common for LR to take 5-10 seconds or more when I finish keywording a selection of photos and then select a new photo to keyword before the "keywords tag" data will be filled in. But this "LR not responding" has happened under numerous situations. I've left in running overnight a couple of times and it did not clear itself. Other times it found its way out of the situation after several hours. The problem is very time consuming and I'm constantly waiting on LR before I can do my next action.
Photo of Ken Zaremba

Ken Zaremba

  • 7 Posts
  • 0 Reply Likes

Posted 3 years ago

  • 2
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 812 Reply Likes
Do you, by chance, have an ATI/AMD video card and updated to their 15.7 driver release?
Photo of Kevin

Kevin

  • 1 Post
  • 0 Reply Likes
I'm seeing this exact behavior and I did just update the driver. But not to 15.7.

DxDiag details below. Is there a workaround? Lightroom is basically useless for me right now.

Thanks!

---------------
Display Devices
---------------
Card name: AMD Radeon HD 7500 Series
Manufacturer: Advanced Micro Devices, Inc.
Chip type: AMD Radeon Graphics Processor (0x675D)
DAC type: Internal DAC(400MHz)
Device Type: Full Device
Device Key: Enum\PCI\VEN_1002&DEV_675D&SUBSYS_2B221028&REV_00
Display Memory: 4848 MB
Dedicated Memory: 1008 MB
Shared Memory: 3840 MB
Current Mode: 2560 x 1600 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: DVI
Monitor Id: KJT9220
Native Mode: 2560 x 1600(p) (59.860Hz)
Output Type: DVI
Driver Name: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
Driver File Version: 8.17.0010.1395 (English)
Driver Version: 15.200.1046.0
DDI Version: 11
Feature Levels: 11.0,10.1,10.0,9.3,9.2,9.1
Driver Model: WDDM 1.3
Graphics Preemption: DMA
Compute Preemption: DMA
Miracast: Not Supported
Hybrid Graphics GPU: Not Supported
Power P-states: Not Supported
Driver Attributes: Final Retail
Driver Date/Size: 6/22/2015 19:08:44, 1440592 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71EE2-241D-11CF-EB76-280BBEC2C535}
Vendor ID: 0x1002
Device ID: 0x675D
SubSys ID: 0x2B221028
Revision ID: 0x0000
Driver Strong Name: oem44.inf:cb0ae4141dbf8a7c:ati2mtag_NI:15.200.1046.0:pci\ven_1002&dev_675d
Rank Of Driver: 00DA2001
Video Accel: ModeMPEG2_A ModeMPEG2_C
DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeVC1_VLD
Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
D3D9 Overlay: Not Supported
DXVA-HD: Not Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4117 Posts
  • 1471 Reply Likes
Kevin, I believe that's the problem one - Driver Version: 15.200.1046.0 is the driver that's comes with Catalyst 15.7 from memory.
Photo of Ken Zaremba

Ken Zaremba

  • 7 Posts
  • 0 Reply Likes
Chris/Victoria: I'm not using an AMD Graphics card. I have a Nvidia GeForce 635 and all drivers are the latest and up to date. Suggestions?
Photo of Ken Zaremba

Ken Zaremba

  • 7 Posts
  • 0 Reply Likes
I went to the LR CC Help tab and selected system info: It is as follows. I've also opened this problem on LR Forums under "LR Installation & Performance" where there are some additional comments on behavior. I have several 6 minute .mp4 clips showing LR's attempt to sort itself out.

Lightroom version: CC 2015.1 [ 1025654 ]
License: Creative Cloud
Operating system: Windows 8.1 Home Premium Edition
Version: 6.3 [9600]
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 3.3 GHz
Built-in memory: 24525.7 MB
Real memory available to Lightroom: 24525.7 MB
Real memory used by Lightroom: 649.1 MB (2.6%)
Virtual memory used by Lightroom: 618.4 MB
Memory cache size: 315.9 MB
Maximum thread count used by Camera Raw: 4
Camera Raw SIMD optimization: SSE2,AVX,AVX2
System DPI setting: 120 DPI
Desktop composition enabled: Yes
Displays: 1) 2560x1440, 2) 1920x1200
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info:
GeForce GT 635/PCIe/SSE2

Check OpenGL support: Passed
Vendor: NVIDIA Corporation
Version: 3.3.0 NVIDIA 347.52
Renderer: GeForce GT 635/PCIe/SSE2
LanguageVersion: 3.30 NVIDIA via Cg compiler

Application folder: C:\Program Files\Adobe\Adobe Lightroom
Library Path: C:\Users\Ken\Pictures\Lightroom_CC\Lightroom Catalog.lrcat
Settings Folder: C:\Users\Ken\AppData\Roaming\Adobe\Lightroom

Installed Plugins:
1) Behance
2) Canon Tether Plugin
3) ColorChecker Passport
4) Export to Photomatix Pro
5) Facebook
6) jf Collection Publisher
7) jf Data Plot
8) jf Facebook
9) jf Flickr
10) jf Folder Status
11) jf Geocoding Support
12) jf Metadata Viewer
13) jf Metadata Wrangler
14) jf PicasaWeb
15) jf SmugMug
16) LR2/Mogrify
17) Show Focus Points

Config.lua flags: None

Adapter #1: Vendor : 10de
Photo of Ken Zaremba

Ken Zaremba

  • 7 Posts
  • 0 Reply Likes
Further LR behavior observed. With Ctrl/s command I wrote two directories containing several thousand photos out to an external drive to update the .xmp files.
The chattering of the drive while this write was occurring was audible. I then selected another folder and entered the state name alaska into the filter keywords box. After the beginning 'a' of alaska was displayed to the screen, all disk activity stopped and it took about 10 seconds before the remaining characters were displayed and disk action resumed. Something is amiss in the keyword "filter keyword" action. What could be causing this behavior?