Welcome Dialog

Welcome to the Community!

We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.


Lightroom 8.4 gpu issues

3 Votes
Community Beginner ,
Aug 29, 2019 Aug 29, 2019

Copy link to clipboard

Copied

Bug Won't fix
TOPICS
Desktop

Views

13

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
21 Comments
Adobe Employee ,
Aug 29, 2019 Aug 29, 2019

Copy link to clipboard

Copied

Does it make a difference if you try doing a clean driver install of the latest game driver? Follow Solution 4 of this troubleshooting guide https://helpx.adobe.com/lightroom-classic/kb/troubleshoot-gpu.html to do a clean driver install.

When I tried to work on very large images, the problems were worse. For example, I have a pano that is something like 26,000 x 6,000 pixels and it was impossible to do any DM changes.
Can you help elaborate on this on the issues that you ran into when you did it?

Translate

Translate

Report

Report
Community Beginner ,
Aug 29, 2019 Aug 29, 2019

Copy link to clipboard

Copied

I think I did a clean install when I switched to the Creator drive around August 1st but I may reinstall just to make sure.

Just to be clear, are you recommending switching from the Nvidia Creator driver to the Game driver? From Nvidia's web site, I thought the Creator driver was recommended for Adobe products as well as other 'creator' products.

With respect to the pano issues, i have a panorama that is 22675 pixels by 8903 pixels. With the GPU enabled, I was pretty much unable to do any edits to that image. Moving sliders seemed to make no difference in the displayed image or make crazy changes. Here is a screen capture showing the problem. The first image is when I first go into the develop module. The second picture is what is displayed after barely moving the temperature slider.

The worst part is it isn't consistent. If I touch the temp slider and move it a little in the opposite direction, either nothing changes, it goes back to a normal display or it changes in some other unpredictable way.

Also, though it seems to happen much faster with the large pixel dimension pano, I see similar issues with other, smaller images over time.

It almost seems like moving a slider is acting like a different slider is being moved...




Translate

Translate

Report

Report
Adobe Employee ,
Aug 29, 2019 Aug 29, 2019

Copy link to clipboard

Copied

Hi Walt, we currently do not support SLI mode, so the first step I would suggest is to turn that off.  But it sounds like you already tried that, and it seemed to make things worse. 

This is not what I expect, and the NVIDIA 1080 Ti card is one that we've tested in-house and should support.  We have been using the game-ready drivers (at the time of development, the creator ready drivers were actually a little older).  

Would you mind running dxdiag (the diagnostic tool built into Windows) and sending us the log file for that?

Thanks,
Eric

Translate

Translate

Report

Report
Community Beginner ,
Aug 29, 2019 Aug 29, 2019

Copy link to clipboard

Copied

Here's the  info from dxdiag.

As I said, I thought I'd done a clean install when I first installed the Creator driver right after it came out but I'll be able to a reinstall in a little while just to test that out.

I'm relatively technical and willing to try things or check things out at a deeper level if it will help.

Do you recommend using the 'default' settings for lightroom.exe in the Nvidia control panel 3d settings?

Thanks,
Walt


------------------
System Information
------------------
      Time of this report: 8/29/2019, 18:16:49
             Machine name: THEMIS
               Machine Id: {56946B3C-5044-4C74-9A88-A2B46777C693}
         Operating System: Windows 10 Pro 64-bit (10.0, Build 18362) (18362.19h1_release.190318-1202)
                 Language: English (Regional Setting: English)
      System Manufacturer: Alienware
             System Model: Alienware Area-51 R3
                     BIOS: 1.0.4 (type: UEFI)
                Processor: AMD Ryzen Threadripper 1950X 16-Core Processor  (32 CPUs), ~3.4GHz
                   Memory: 65536MB RAM
      Available OS Memory: 65418MB RAM
                Page File: 59671MB used, 15473MB available
              Windows Dir: C:\WINDOWS
          DirectX Version: DirectX 12
      DX Setup Parameters: Not found
         User DPI Setting: 120 DPI (125 percent)
       System DPI Setting: 144 DPI (150 percent)
          DWM DPI Scaling: Enabled
                 Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
 DirectX Database Version: Unknown
           DxDiag Version: 10.00.18362.0267 64bit Unicode

------------
DxDiag Notes
------------
      Display Tab 1: No problems found.
        Sound Tab 1: No problems found.
        Sound Tab 2: No problems found.
        Sound Tab 3: No problems found.
          Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D:    0/4 (retail)
DirectDraw:  0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay:  0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow:  0/6 (retail)

---------------
Display Devices
---------------
           Card name: NVIDIA GeForce GTX 1080 Ti
        Manufacturer: NVIDIA
           Chip type: GeForce GTX 1080 Ti
            DAC type: Integrated RAMDAC
         Device Type: Full Device (POST)
          Device Key: Enum\PCI\VEN_10DE&DEV_1B06&SUBSYS_36001028&REV_A1
       Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] 
 Device Problem Code: No Problem
 Driver Problem Code: Unknown
      Display Memory: 43739 MB
    Dedicated Memory: 11031 MB
       Shared Memory: 32708 MB
        Current Mode: 3840 x 2160 (32 bit) (60Hz)
         HDR Support: Not Supported
    Display Topology: Internal
 Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
     Color Primaries: Red(0.639648,0.330078), Green(0.209961,0.709961), Blue(0.150391,0.059570), White Point(0.313477,0.329102)
   Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000
        Monitor Name: Generic PnP Monitor
       Monitor Model: DELL UP3216Q
          Monitor Id: DEL40C1
         Native Mode: 3840 x 2160(p) (59.997Hz)
         Output Type: Displayport External
Monitor Capabilities: HDR Not Supported
Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP
      Advanced Color: Not Supported
         Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\nvddsi.inf_amd64_962fbdf66aea94b9\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvddsi.inf_amd64_962fbdf66aea94b9\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvddsi.inf_amd64_962fbdf66aea94b9\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvddsi.inf_amd64_962fbdf66aea94b9\nvldumdx.dll
 Driver File Version: 26.21.0014.3170 (English)
      Driver Version: 26.21.14.3170
         DDI Version: 12
      Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
        Driver Model: WDDM 2.6
 Graphics Preemption: Pixel
  Compute Preemption: Dispatch
            Miracast: Not Supported by Graphics driver
      Detachable GPU: No
 Hybrid Graphics GPU: Not Supported
      Power P-states: Not Supported
      Virtualization: Paravirtualization 
          Block List: No Blocks
  Catalog Attributes: Universal:False Declarative:False 
   Driver Attributes: Final Retail
    Driver Date/Size: 07/23/2019 18:00:00, 959336 bytes
         WHQL Logo'd: n/a
     WHQL Date Stamp: n/a
   Device Identifier: {D7B71E3E-5846-11CF-FA7F-0E161BC2D735}
           Vendor ID: 0x10DE
           Device ID: 0x1B06
           SubSys ID: 0x36001028
         Revision ID: 0x00A1
  Driver Strong Name: oem0.inf:0f066de3bc14d6b4:Section052:26.21.14.3170:pci\ven_10de&dev_1b06&subsys_36001028
      Rank Of Driver: 00D10001
         Video Accel: 
         DXVA2 Modes: DXVA2_ModeMPEG2_VLD  DXVA2_ModeVC1_D2010  DXVA2_ModeVC1_VLD  DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT  DXVA2_ModeH264_VLD_Stereo_NoFGT  DXVA2_ModeH264_VLD_NoFGT  DXVA2_ModeHEVC_VLD_Main  DXVA2_ModeHEVC_VLD_Main10  DXVA2_ModeMPEG4pt2_VLD_Simple  DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC  DXVA2_ModeVP9_VLD_Profile0  DXVA2_ModeVP9_VLD_10bit_Profile2  
   Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {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 
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: 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)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {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 
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) 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=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: 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)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {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 
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,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=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,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=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,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=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,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=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,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=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
        D3D9 Overlay: Supported
             DXVA-HD: Supported
        DDraw Status: Enabled
          D3D Status: Enabled
          AGP Status: Enabled
       MPO MaxPlanes: 1
            MPO Caps: Not Supported
         MPO Stretch: Not Supported
     MPO Media Hints: Not Supported
         MPO Formats: Not Supported
    PanelFitter Caps: Not Supported
 PanelFitter Stretch: Not Supported

-------------
Sound Devices
-------------
            Description: Speakers / Headphones (Realtek Audio)
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0899&SUBSYS_10280805&REV_1000
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: RTKVHD64.sys
         Driver Version: 6.00.0001.8393 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: n/a
          Date and Size: 03/06/2018 00:00:00, 6111680 bytes
            Other Files: 
        Driver Provider: Realtek Semiconductor Corp.
         HW Accel Level: Basic
              Cap Flags: 0x0
    Min/Max Sample Rate: 0, 0
Static/Strm HW Mix Bufs: 0, 0
 Static/Strm HW 3D Bufs: 0, 0
              HW Memory: 0
       Voice Management: No
 EAX(tm) 2.0 Listen/Src: No, No
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

            Description: Realtek Digital Output (Realtek Audio)
 Default Sound Playback: No
 Default Voice Playback: No
            Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0899&SUBSYS_10280805&REV_1000
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: RTKVHD64.sys
         Driver Version: 6.00.0001.8393 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: n/a
          Date and Size: 03/06/2018 00:00:00, 6111680 bytes
            Other Files: 
        Driver Provider: Realtek Semiconductor Corp.
         HW Accel Level: Basic
              Cap Flags: 0x0
    Min/Max Sample Rate: 0, 0
Static/Strm HW Mix Bufs: 0, 0
 Static/Strm HW 3D Bufs: 0, 0
              HW Memory: 0
       Voice Management: No
 EAX(tm) 2.0 Listen/Src: No, No
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

            Description: DELL UP3216Q (NVIDIA High Definition Audio)
 Default Sound Playback: No
 Default Voice Playback: No
            Hardware ID: HDAUDIO\FUNC_01&VEN_10DE&DEV_0082&SUBSYS_10283600&REV_1001
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: nvhda64v.sys
         Driver Version: 1.03.0038.0016 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: n/a
          Date and Size: 03/18/2019 00:00:00, 228608 bytes
            Other Files: 
        Driver Provider: NVIDIA Corporation
         HW Accel Level: Basic
              Cap Flags: 0x0
    Min/Max Sample Rate: 0, 0
Static/Strm HW Mix Bufs: 0, 0
 Static/Strm HW 3D Bufs: 0, 0
              HW Memory: 0
       Voice Management: No
 EAX(tm) 2.0 Listen/Src: No, No
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

---------------------
Sound Capture Devices
---------------------
---------------------
Video Capture Devices
Number of Devices: 0
---------------------
-------------------
DirectInput Devices
-------------------
      Device Name: Mouse
         Attached: 1
    Controller ID: n/a
Vendor/Product ID: n/a
        FF Driver: n/a

      Device Name: Keyboard
         Attached: 1
    Controller ID: n/a
Vendor/Product ID: n/a
        FF Driver: n/a

      Device Name: Cordless Device
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
        FF Driver: n/a

      Device Name: Cordless Device
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
        FF Driver: n/a

      Device Name: USB Receiver
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
        FF Driver: n/a

      Device Name: Cordless Keyboard
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
        FF Driver: n/a

      Device Name: Cordless Keyboard
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
        FF Driver: n/a

      Device Name: USB Receiver
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
        FF Driver: n/a

      Device Name: UP3216Q_0B27_141021v1
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x04D8, 0x0B27
        FF Driver: n/a

      Device Name: Cordless Receiver
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
        FF Driver: n/a

      Device Name: Cordless Receiver
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
        FF Driver: n/a

      Device Name: USB Receiver
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
        FF Driver: n/a

Poll w/ Interrupt: No

-----------
USB Devices
-----------
+ USB Root Hub (USB 3.0)
| Vendor/Product ID: 0x1022, 0x43BA
| Matching Device ID: USB\ROOT_HUB30
| Service: USBHUB3
| Driver: USBHUB3.SYS, 3/18/2019 22:43:43, 618296 bytes

+-+ USB Composite Device
| | Vendor/Product ID: 0x046D, 0xC52B
| | Location: Port_#0009.Hub_#0001
| | Matching Device ID: USB\COMPOSITE
| | Service: usbccgp
| | Driver: usbccgp.sys, 3/18/2019 22:43:43, 183608 bytes
| | 
| +-+ Logitech USB Input Device
| | | Vendor/Product ID: 0x046D, 0xC52B
| | | Location: 0001.0000.0000.009.000.000.000.000.000
| | | Matching Device ID: usb\vid_046d&pid_c52b&mi_00
| | | Service: HidUsb
| | | Driver: hidusb.sys, 7/25/2019 15:34:07, 45568 bytes
| | | Driver: hidclass.sys, 7/25/2019 15:34:07, 211968 bytes
| | | Driver: hidparse.sys, 7/25/2019 15:34:07, 46080 bytes
| | | Driver: LogiLDA.DLL, 10/13/2016 21:55:24, 3942864 bytes
| | | Driver: LdaCx2.dll, 10/13/2016 21:55:18, 2468304 bytes
| | | Driver: msvcp110.dll, 10/13/2016 21:55:26, 670800 bytes
| | | Driver: msvcr110.dll, 10/13/2016 21:55:28, 838224 bytes
| | | Driver: vccorlib110.dll, 10/13/2016 21:55:30, 363616 bytes
| | | 
| | +-+ HID Keyboard Device
| | | | Vendor/Product ID: 0x046D, 0xC52B
| | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD
| | | | Service: kbdhid
| | | | Driver: kbdhid.sys, 3/18/2019 22:43:43, 46592 bytes
| | | | Driver: kbdclass.sys, 3/18/2019 22:43:43, 70968 bytes
| | | 
| +-+ USB Input Device
| | | Vendor/Product ID: 0x046D, 0xC52B
| | | Location: 0001.0000.0000.009.000.000.000.000.000
| | | Matching Device ID: USB\Class_03&SubClass_01
| | | Service: HidUsb
| | | Driver: hidusb.sys, 7/25/2019 15:34:07, 45568 bytes
| | | Driver: hidclass.sys, 7/25/2019 15:34:07, 211968 bytes
| | | Driver: hidparse.sys, 7/25/2019 15:34:07, 46080 bytes
| | | 
| | +-+ HID-compliant mouse
| | | | Vendor/Product ID: 0x046D, 0xC52B
| | | | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE
| | | | Service: mouhid
| | | | Driver: mouhid.sys, 3/18/2019 22:43:43, 35840 bytes
| | | | Driver: mouclass.sys, 3/18/2019 22:43:43, 66872 bytes
| | | 
| +-+ Logitech Unifying USB receiver
| | | Vendor/Product ID: 0x046D, 0xC52B
| | | Location: 0001.0000.0000.009.000.000.000.000.000
| | | Matching Device ID: usb\vid_046d&pid_c52b&mi_02
| | | Service: LEqdUsb
| | | Driver: LEqdUsb.sys, 4/13/2018 22:15:16, 94840 bytes
| | | Driver: LkmdfCoInst.dll, 4/13/2018 22:15:24, 1854072 bytes
| | | 
| | +-+ Logitech HID-compliant Unifying device
| | | | Vendor/Product ID: 0x046D, 0xC52B
| | | | Location: DJ Bus 0
| | | | Matching Device ID: {a3535e08-eb26-49a9-8ae0-786ed1242812}\logi_hid_device
| | | | Service: LHidEqd
| | | | Driver: LHidEqd.sys, 4/13/2018 22:15:18, 23160 bytes
| | | | Driver: LkmdfCoInst.dll, 4/13/2018 22:15:24, 1854072 bytes
| | | | 
| | | +-+ Logitech HID-compliant Unifying keyboard
| | | | | Vendor/Product ID: 0x046D, 0xC52B
| | | | | Matching Device ID: hid\vid_046d&class_0000001a&col01
| | | | | Lower Filters: LHidFilt
| | | | | Service: kbdhid
| | | | | Driver: LHidFilt.Sys, 4/13/2018 22:15:20, 86648 bytes
| | | | | Driver: kbdhid.sys, 3/18/2019 22:43:43, 46592 bytes
| | | | | Driver: kbdclass.sys, 3/18/2019 22:43:43, 70968 bytes
| | | | | Driver: LkmdfCoInst.dll, 4/13/2018 22:15:24, 1854072 bytes
| | | | 
| | +-+ Logitech HID-compliant Unifying device
| | | | Vendor/Product ID: 0x046D, 0xC52B
| | | | Location: DJ Bus 0
| | | | Matching Device ID: {a3535e08-eb26-49a9-8ae0-786ed1242812}\logi_hid_device
| | | | Service: LHidEqd
| | | | Driver: LHidEqd.sys, 4/13/2018 22:15:18, 23160 bytes
| | | | Driver: LkmdfCoInst.dll, 4/13/2018 22:15:24, 1854072 bytes
| | | | 
| | | +-+ Logitech HID-compliant Unifying keyboard
| | | | | Vendor/Product ID: 0x046D, 0xC52B
| | | | | Matching Device ID: hid\vid_046d&class_0000001e&col01
| | | | | Lower Filters: LHidFilt
| | | | | Service: kbdhid
| | | | | Driver: LHidFilt.Sys, 4/13/2018 22:15:20, 86648 bytes
| | | | | Driver: kbdhid.sys, 3/18/2019 22:43:43, 46592 bytes
| | | | | Driver: kbdclass.sys, 3/18/2019 22:43:43, 70968 bytes
| | | | | Driver: LkmdfCoInst.dll, 4/13/2018 22:15:24, 1854072 bytes
| | | | | 
| | | +-+ Logitech HID-compliant Unifying Mouse
| | | | | Vendor/Product ID: 0x046D, 0xC52B
| | | | | Matching Device ID: hid\vid_046d&class_0000001e&col02
| | | | | Upper Filters: LMouFilt
| | | | | Lower Filters: LHidFilt
| | | | | Service: mouhid
| | | | | Driver: LHidFilt.Sys, 4/13/2018 22:15:20, 86648 bytes
| | | | | Driver: LMouFilt.Sys, 4/13/2018 22:15:24, 69240 bytes
| | | | | Driver: mouhid.sys, 3/18/2019 22:43:43, 35840 bytes
| | | | | Driver: mouclass.sys, 3/18/2019 22:43:43, 66872 bytes
| | | | | Driver: LkmdfCoInst.dll, 4/13/2018 22:15:24, 1854072 bytes
| | | | | Driver: LMouFiltCoInst.dll, 4/13/2018 22:15:28, 63096 bytes

----------------
Gameport Devices
----------------

------------
PS/2 Devices
------------
+ HID Keyboard Device
| Vendor/Product ID: 0x046D, 0xC232
| Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD
| Service: kbdhid
| Driver: kbdhid.sys, 3/18/2019 22:43:43, 46592 bytes
| Driver: kbdclass.sys, 3/18/2019 22:43:43, 70968 bytes

+ HID-compliant mouse
| Vendor/Product ID: 0x046D, 0xC231
| Matching Device ID: HID_DEVICE_SYSTEM_MOUSE
| Service: mouhid
| Driver: mouhid.sys, 3/18/2019 22:43:43, 35840 bytes
| Driver: mouclass.sys, 3/18/2019 22:43:43, 66872 bytes

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 436.4 GB
Total Space: 974.8 GB
File System: NTFS
      Model: PM961 NVMe SAMSUNG 1024GB

      Drive: E:
 Free Space: 1850.5 GB
Total Space: 1907.6 GB
File System: NTFS
      Model: ST2000DM001-1ER164

      Drive: G:
 Free Space: 6472.8 GB
Total Space: 9537.4 GB
File System: NTFS
      Model: ST10000DM0004-1ZC101

      Drive: 😧
      Model: HL-DT-ST DVD+-RW GS40N
     Driver: C:\WINDOWS\SYSTEM32\DRIVERS\CDROM.SYS, 10.00.18362.0001 (English), 3/18/2019 22:43:39, 173056 bytes

--------------
System Devices
--------------
     Name: Killer E2500 Gigabit Ethernet Controller
Device ID: PCI\VEN_1969&DEV_E0B1&SUBSYS_08051028&REV_10\FF2AEC2D309C23FF00
   Driver: C:\WINDOWS\system32\DRIVERS\e2xw10x64.sys, 9.00.0000.0049 (English), 11/26/2018 09:53:10, 164816 bytes

     Name: PCI standard host CPU bridge
Device ID: PCI\VEN_1022&DEV_1461&SUBSYS_00000000&REV_00\3&11583659&0&C9
   Driver: n/a

     Name: PCI standard host CPU bridge
Device ID: PCI\VEN_1022&DEV_1461&SUBSYS_00000000&REV_00\3&11583659&0&C1
   Driver: n/a

     Name: Standard NVM Express Controller
Device ID: PCI\VEN_144D&DEV_A808&SUBSYS_A801144D&REV_00\6&17F903&0&0040000B
   Driver: C:\WINDOWS\system32\DRIVERS\stornvme.sys, 10.00.18362.0001 (English), 3/18/2019 22:43:41, 142648 bytes

     Name: AMD USB 3.10 eXtensible Host Controller - 1.10 (Microsoft)
Device ID: PCI\VEN_1022&DEV_43BA&SUBSYS_08051028&REV_02\4&2EEC526C&0&0009
   Driver: C:\WINDOWS\system32\DRIVERS\USBXHCI.SYS, 10.00.18362.0207 (English), 7/25/2019 15:34:07, 531976 bytes
   Driver: C:\WINDOWS\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.18362.0207 (English), 7/25/2019 15:34:07, 131960 bytes

     Name: PCI standard host CPU bridge
Device ID: PCI\VEN_1022&DEV_1464&SUBSYS_00000000&REV_00\3&11583659&0&CC
   Driver: n/a

     Name: PCI standard host CPU bridge
Device ID: PCI\VEN_1022&DEV_1464&SUBSYS_00000000&REV_00\3&11583659&0&C4
   Driver: n/a

     Name: NVIDIA GeForce GTX 1080 Ti
Device ID: PCI\VEN_10DE&DEV_1B06&SUBSYS_36001028&REV_A1\4&1C3D25BB&0&0019
   Driver: C:\WINDOWS\system32\DRIVERS\NVIDIA Corporation\Drs\dbInstaller.exe, 26.21.0014.3170 (English), 7/25/2019 08:29:02, 733064 bytes
   Driver: C:\WINDOWS\system32\DRIVERS\NVIDIA Corporation\Drs\nvdrsdb.bin, 7/24/2019 16:46:08, 1589488 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvddsi.inf_amd64_962fbdf66aea94b9\NvContainerSetup.exe, 1.00.0010.0000 (English), 7/25/2019 08:29:56, 4551320 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvddsi.inf_amd64_962fbdf66aea94b9\NvCplSetupInt.exe, 1.00.0010.0000 (English), 7/25/2019 08:29:58, 102590664 bytes
   Driver: C:\Program Files (x86)\NVIDIA Corporation\coprocmanager\detoured.dll, 2.01.0000.0224 (English), 7/25/2019 08:30:22, 29576 bytes
   Driver: C:\Program Files (x86)\NVIDIA Corporation\coprocmanager\nvd3d9wrap.dll, 26.21.0014.3170 (English), 7/25/2019 08:30:14, 236992 bytes
   Driver: C:\Program Files (x86)\NVIDIA Corporation\coprocmanager\nvdxgiwrap.dll, 26.21.0014.3170 (English), 7/25/2019 08:30:32, 162696 bytes

Translate

Translate

Report

Report
Community Beginner ,
Aug 29, 2019 Aug 29, 2019

Copy link to clipboard

Copied

Also, not sure if it makes a difference but my display is a Dell UP3216Q which is a 4k monitor

Translate

Translate

Report

Report
Community Beginner ,
Aug 29, 2019 Aug 29, 2019

Copy link to clipboard

Copied

Ok, did the clean reinstall and at first I thought it was working but after going into and out of the DM a few times and a round trip through Photoshop on one of the images, problems returned. Here are two screen captures of a different image which is 11648px X 8736px. I took it into DM and made some small changes and the displayed image got patchy. When I go back to LM, it displays correctly but if I go right back into DM it is still patchy.

When I first went into DM, 9.4GB out of 11GB of VRAM was being used. After going into and out of DM and the round trip through PS, VRAM usage is up to 10.4GB. I could be wrong but it seems like the problems start showing up when the usage is over 10GB.



Translate

Translate

Report

Report
Adobe Employee ,
Aug 29, 2019 Aug 29, 2019

Copy link to clipboard

Copied

Walt, thanks for the info.  Out of curiosity, do the problems occur if you stay only within Lr (without going into Ps)?  Or, do they still occur when going into & out of the Lr Develop module.

The driver package that you have should work correctly -- that's the same one I have in my dev machine, which is also running a GTX 1080.

Translate

Translate

Report

Report
Adobe Employee ,
Aug 29, 2019 Aug 29, 2019

Copy link to clipboard

Copied

The 4K display should be no problem.  We've been testing internally on displays up to 8K.  On my 1080 system I also use a Dell 4K display (a slightly older model than yours).

Translate

Translate

Report

Report
Community Beginner ,
Aug 29, 2019 Aug 29, 2019

Copy link to clipboard

Copied

Ok, I think I have a little more info. After doing the clean re-install and sending you the images above, I noticed SLI was re-enabled so I disabled it again and rebooted.  Things seemed to be a lot better and VRAM usage was down a bit to ~9.5GB. I did a couple of round trips through PS without a problem but then I did an "Open as Smart Object in PS". After that, problems started showing up again and VRAM usage was up to ~10.7GB.

So it may be an issue between using the Camera Raw code via the DM in LR and then opening the same image as a smart object in PS. I do this quite often.

I'll reboot again and see if the problem appears if I don't open as a SO in PS.

Translate

Translate

Report

Report
Community Beginner ,
Aug 29, 2019 Aug 29, 2019

Copy link to clipboard

Copied

I know it's hard to prove when something isn't going to happen but it seems like I can do a lot if I stay in LR and the only anomaly I see is if dehaze is non-zero, some of the other sliders such as WB temp or tint are very laggy (wasn't this an old problem that got fixed?). I also seem to be able to go in and out of PS as long as I used a rasterized object, not a smart object. After making the round trip as a SO, i can work a little bit but other problems always start to show up, especially zooming in and out. It will eventually stop working and all I get is a gray screen when I try to zoom in. I'll keep experimenting tomorrow and see if I notice any other patterns.

Translate

Translate

Report

Report
Adobe Employee ,
Aug 29, 2019 Aug 29, 2019

Copy link to clipboard

Copied

Ok, thanks Walt for the additional info.  We'll look into it further on our end (using the key step of further editing as a smart object in Ps to repro).

Translate

Translate

Report

Report
LEGEND ,
Aug 29, 2019 Aug 29, 2019

Copy link to clipboard

Copied

Some questions


1. For clarity, you mentioned the Nvidia Creator driver, now at https://www.nvidia.com/Download/index... I see the option for Studio Driver (SD) or Game Ready Driver (GRD) not Creator. Studio driver is described as being for creatives. Perhaps another link. Studio shows up as v431.70, Game Ready as v436.15.. Note that the Studio driver is almost a month older.
Apparently a name change by Nvidia, Creator changed to Studio?



2. Have you tried the Game Ready driver?

Translate

Translate

Report

Report
Community Beginner ,
Aug 30, 2019 Aug 30, 2019

Copy link to clipboard

Copied

Sorry, yes, the driver I have installed is the Nvidia Studio Driver version 431.70. On their web site they call it the Studio Driver for Creative Applications and I picked up the creator part. I thought Nvidia promoted the Game Ready driver as being more leading edge but the Studio Driver was more stable and tested with the major creative apps. That's why I installed the Studio Driver. If you think the Game Ready driver is better and well-tested, I can easily switch to that one.

Is that what you are recommending?

Translate

Translate

Report

Report
LEGEND ,
Aug 30, 2019 Aug 30, 2019

Copy link to clipboard

Copied

Just noticing the difference in release dates. However, when you look at the release notes for the latest Game Ready One, nothing is mentioned on fixing LRC issues.

Translate

Translate

Report

Report
LEGEND ,
Aug 30, 2019 Aug 30, 2019

Copy link to clipboard

Copied

Negative answer to the following is very unlikely

The two GPU's, they are the same make/model, correct?

And negative answer extremely unlikely, and you will need to inspect in Devices. The two GPU's, use the same driver. correct?

Translate

Translate

Report

Report
LEGEND ,
Aug 30, 2019 Aug 30, 2019

Copy link to clipboard

Copied

The screenshots, were they in Develop mode or Library mode?

And if Library mode, have you considered possible corrupt previews?

Not exactly the issue, but how: https://helpx.adobe.com/lightroom-classic/kb/lightroom-gives-error-preview-cache.html

Translate

Translate

Report

Report
Community Beginner ,
Aug 30, 2019 Aug 30, 2019

Copy link to clipboard

Copied

Given what I've found so far, I think I'll stay with the current Studio Driver to reduce the variables. It seems like there is something between LR & PS when I use smart objects. That seems to be the constant  at least so far. I have a lot of work to do in LR today so I'm going to see if it's stable if I don't take an image into PS as a smart object.

Translate

Translate

Report

Report
Community Beginner ,
Aug 30, 2019 Aug 30, 2019

Copy link to clipboard

Copied

Yes, they are two identical 1080 Ti GPUs that came with the machine from Alienware and they are both using the same driver.

Translate

Translate

Report

Report
Community Beginner ,
Aug 30, 2019 Aug 30, 2019

Copy link to clipboard

Copied

The pano images were both from the DM and the artifact appeared after barely bumping the WB temp slider. The second set were also from the DM after zooming in to 1:2, 1:1 and Fit.

Before doing a clean re-install, I was also getting some weird preview corruption which I fixed a couple of times by rebuilding the preview. However, I was also seeing anomalies where I would start an edit by hitting the "R" key from the Loupe view but the image in the crop preview was the previous image I had been working on. Nothing I tried would fix it until I exited and restarted LR.

Translate

Translate

Report

Report
New Here ,
May 19, 2020 May 19, 2020

Copy link to clipboard

Copied

Hi, please confirm if the issue still exists with 9.2.1 release. Thanks!

Translate

Translate

Report

Report
Adobe Employee ,
Aug 18, 2020 Aug 18, 2020

Copy link to clipboard

Copied

LATEST

Updates to Camera Raw, Lightroom Classic, and the Lightroom Ecosystem were released yesterday evening and contain a fix for this issue.  Please install the appropriate update and see if it solves this problem. 

Thank you for your patience.
Rikk Flohr - Customer Advocacy: Adobe Photography Products

Translate

Translate

Report

Report