Lightroom crashes when rendering Develop preview under Vista 64-bit

I'm running Windows Vista Ultimate 64-bit and Lightroom 1.1 crashes every time I click the "Develop" pane. My images are DNG files without the original RAW embedded.
Lightroom ONLY crashes when I load an image in Develop. If I open Develop without any image selected, it's fine (no image is displayed). I can zoom in to 100% in Library and it works fine. Exporting images to JPG works fine. Editing photos in the Library pane is fine. The crash data is:
Problem signature:
Problem Event Name: APPCRASH
Application Name: lightroom.exe
Application Version: 1.1.0.0
Application Timestamp: 4677e8e1
Fault Module Name: MFC80U.DLL
Fault Module Version: 8.0.50727.163
Fault Module Timestamp: 4484afec
Exception Code: c0000005
Exception Offset: 0002511c
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033
I've uninstalled LR 1.1 and reinstalled and it does the same thing. When I uninstall LR 1.1 and the install LR 1.0 (the previous version) Develop does open, but it doesn't render the images correctly - it looks like it misinterprets the white balance by about 1,500k degrees (very ugly), but Library shows the correct image/white-balance.
I've updated my nVidia 7900 graphics drivers to the latest version, appropriate to my OS and architecture. I've disabled XMP creation and Adobe Photo Downloader, as well as all other running applications (Antivirus, spyware, itunes, etc).
This USED to work fine in Vista and I did not make any significant changes, but I expect it's an issue with WindowsUpdate causing an incompatibility. I can't roll-back to my Vista state when it worked a month ago (that's another Vista frustration).
Anyway advice or comments would be GREATLY appreciated since this is an integral part of my professional workflow. I own a legitimate, licensed copy of both Lightroom and Vista, yet neither company is willing to talk to me unless I pay them money, which I think is complete extortion, but I digress.
Thanks in advance for your help.

Has anyone got a resolution on this? I have the same issue. Lightroom crashes when I click develop and the develop module begins to render the image. Clicking develop with no image selected allows the develop module to load however selecting develop on the menu bar and choosing either previous photo or next photo causes lightroom to crash while rendering an image.
I have a 64 bit capable HP XW8400 workstation with 2 dual core Xeon processors, 4 GB RAM, and a nVidia FX 4400 graphics card. This video card was put in as a test. the original video card was an nVidia quadra NVS something. When I ran the NVS card I used the drivers certified for Adobe CS2. I am running 32 bit Windows XP SP2 with all current updates. I do not have any MS office components installed on this system.
I read of some troubles around the Realtek HD audio driver and some Adobe applications (not Lightroom). Since I have this sound device I disabled it and removed the drivers...still crashes.
I also disabled the Intel VT in the system bios (I believe this is required to run 64 bit XP or Vista)... no change. Also disabled the NX feature...no change.
I also loaded VMware workstation 6.0 and installed Lightroom in a 32bit Windows XP SP2 VM. In the VM Lightroom works perfectly on the same machine...just not as snappy...
This stinks...Lightroom works perfectly on my poky laptop.

Similar Messages

  • AE crashes when I RAM preview, gives this message

    Has anyone ever seen this type of error message? If so, how do I fix it?
    I'm running CS5 on a mac. Thanks.
    Update: I made another file with a solid moving from one corner to the next and it RAM previewed without error. Figured I'd throw that out there.

    Oh wow, ok here we go.
    Running Version 10.0.2.4 on a dual booted Mac (using the Mac side)
    OS - OS X v 10.6.8
    2 x 2.26 GHz Quad Core Intel Xeon - 16 GB RAM 1066 MHz DDR3
    The file wouldn't even open when I switched to the PC side which has vista I think, but I'm not positive.
    Had Photoshop CS5 open, have 3rd party plugins and codecs installed but aside from Particular 2 I'm not using any in the area I'm trying to preview.
    Not using multi processing or render multiple frames. Using a 2048 X 1152 size (this was comped then scaled down to 1920 x 1080) quicktime at 23.976 for just under 36 seconds with an Animation codec.
    Was ram previewing the area I wanted, earlier in the day. It all of a sudden just started crashing when I tried previewing at all in this file. Went back to the last version I saved last night and it ram previewed fine.
    I checked for updates in Help - Updates and it said it was completely updated.
    Sorry about not including this earlier.
    Thanks!

  • Crashes when rendering /Realtek drivr problem

    hi,
    love 6.5 then 7 but Pro is driving me potty... My system keeps crashing when rendering and also - or maybe becaused of?! - I keep getting 'can't playback audio / audio inputs are deactivated / adobe default sound drivers are in half duplex mode'. Are these problems linked? I've built up a large project - if I reinstall Pro will I lose it? I know I can't open it in 7.0 - pity! All help appreciated thankyou.
    Ps ram is not a problem. I'm on vista.

    Try this:
    Support:kb402308 Realtek HD Audio
    Cheers
    Eddie
    PremiereProPedia   (
    RSS feed)
    - Over 300 frequently answered questions
    - Over 250 free tutorials
    - Maintained by editors like
    you
    Forum FAQ

  • My new iMac with FCPX crashes when rendering complex templates and crashes when exporting with Motion 5

    My new iMac with FCPX crashes when rendering complex templates and crashes when exporting with Motion 5
    Using Motion 5.0.6 and Final Cut Pro X 10.0.7 on New iMac (December 2012)  Mountain Lion,
    Intel Core i7 quad-core a 3,4GHz, Turbo Boost fino a 3,9GHz
    32GB di SDRAM DDR3 a 1600MHz - 4 x 8GB
    Fusion Drive da 3TB
    NVIDIA GeForce GTX 680MX 2GB GDDR5
    During the rendering of complex FCPX mac crashes and I have to force a restart.
    I also happens when I try to export movies with Motion 5.
    Does anyone have the same problem with my new iMac?

    Problems such as yours are sometimes caused by files that should belong to you but are locked or have wrong permissions. This procedure will check for such files. It makes no changes and therefore will not, in itself, solve your problem.
    First, empty the Trash.
    Launch the Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    Triple-click anywhere in the line below to select it, then drag or copy it — do not type — into the Terminal window:
    find . $TMPDIR.. \( -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 -o -acl \) 2> /dev/null | wc -l
    Press return. The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear.
    The output of this command, on a line directly below what you entered, will be a number such as "35." Please post it in a reply.

  • Lightroom crashes when saving Metadata to files

    After updating the IPTC Caption to describe photographs, Lightroom crashes when I try to save the metadata to the files. Using Lightroom V4 x64 on a PC running Windows 7.
    Andy ideas?

    This is what I see in the event:
    Faulting application name: lightroom.exe, version: 3.4.1.10, time stamp: 0x4dd53458
    Faulting module name: MSVCR100.dll, version: 10.0.30319.1, time stamp: 0x4ba220dc
    Exception code: 0xc0000005
    Fault offset: 0x000000000003c250
    Faulting process id: 0x1bac
    Faulting application start time: 0x01cc551d95539f01
    Faulting application path: C:\Program Files\Adobe\Adobe Photoshop Lightroom 3.4\lightroom.exe
    Faulting module path: C:\Windows\system32\MSVCR100.dll
    Report Id: 2407c769-c116-11e0-83cc-001e4fb6c7c5

  • AE CS4 crashes when rendering

    Since the last update to version 9.0.3.8 dva 2.0.0.161039  crashes when rendering.

    I have AE 9.0.3, using a windows Intel Core i7-2600 Processor (8M Cache, 3.40 GHz) 4GB RAM.
    It a very simple project, with version 9.0.2 to and are already' succeeded in renderind and after the upgrade to 9.0.3 fails more to do, after a good start and fast after a while begins to slow down until total blockade.
    Sorry but I do not speak English and it's difficult to explain. Do you understand Italian?

  • Why does pre pro cc crash when rendering?

    Why does my pre pro cc crash when rendering?  It has done this repeatedly

    There can be a LOT of reasons.  You'll need to start investigating and eliminating variables.
    Start by turning GPU acceleration off if it's turned on, and go from there.

  • After effects crashes when rendering error: (-209)(512)

    after effects crashes when rendering , can anyone help me??
    after effects error: ..\..\OpenCv\src\video\optflowbm.cpp:103: error: (-209)
    (512)
    ( 25 :: 241 )

    We need to know a lot more if we're going to help you. Please provide answers to the questions listed here: "FAQ: What information should I provide when asking a question on this forum?"

  • After Effects crashes when rendering to H264

    Hi,
    On one of my computers, After Effects Crashes when rendering to H264. It always chrashes when doing the last frame of a clip. I think its when muxxing the m4a and the m4v together...
    Does anyone have a solution? maybe there is some odd codec trash going on?
    Thanks in advance!

    10.Rick Gerard,
    Nov 22, 2012 6:07 AM   in reply to espedg
    Report
    In every version of AE that has been capable of exporting h.264 the quality has been significantly lower than exporting with an app that gives you the option of multi-pass rendering. This has always been true for MPEG codecs that use inter frame (temporal) compression. You just can't get the same quality without multi pass compression. This goes back to the first use of MPEG streams.
    AE CS6 may have H.264 encoding broken internally, but any pro has never used AE to render highly compressed delivery codecs because AE was never designed to be the right tool for the job.

  • Speed Grade Crashes when rendering

    SpeedGrade crashes on me when I try to render graded footage to an h.264 file.  I have tried both mts footage from the canon xh-a1 that has been converted to quicktime as well as footage straight out of the 5D Mark 2.  I can grade the footage, but every time I try to render the footage I get, 100% render completion and then SpeedGrade crashes.  Also no file is ever created from the output. Very Frustrating.  Any thoughts on what could be the problem.
    Thanks

    I have been using the English version and It crashes all the same.
    Date: Tue, 29 May 2012 09:33:59 -0600
    From: [email protected]
    To: [email protected]
    Subject: Speed Grade Crashes when rendering
        Re: Speed Grade Crashes when rendering
        created by Dennis Weinmann in SpeedGrade - View the full discussion
    Thank you for sending the crash report. This is a known issue and only affects Italian builds. We have isolated this and working on a fix. Please stay tuned and use an English version of SpeedGrade in the meantime. Thanks
         Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4447743#4447743
         To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4447743#4447743. In the Actions box on the right, click the Stop Email Notifications link.
         Start a new discussion in SpeedGrade by email or at Adobe Forums
      For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

  • PremeierePro CC crash when rendering - not enough memory

    I´m on working with a 90 minute project and when trying to render PP CC crash.
    PremeierePro CC crash when rendering. It says not enough memory. I´m on a MacBookPro Retina:
    Processor  2.8 GHz Intel Core i7
    Memory  16 GB 1600 MHz DDR3
    Graphics  Intel HD Graphics 4000 1024 MB
    Software  OS X 10.9.1 (13B42)

    Kevin said "Update the drivers for both your video cards" so it seems he knows more than I do about Mac's
    Read below about some problems/fixes for dual cards
    -http://helpx.adobe.com/premiere-pro/kb/error---preludevideo-play-modules.html
    -http://forums.adobe.com/thread/1001579
    -Use BIOS http://forums.adobe.com/thread/1019004?tstart=0
    -link to why http://forums.adobe.com/message/4685328
    -http://www.anandtech.com/show/4839/mobile-gpu-faceoff-amd-dynamic-switchable-graphics-vs-n vidia-optimus-technology/2

  • Does Adobe Premiere 7 work ok and is it supported under Vista 64 bits operating system

    Does Adobe Premiere 7 work ok and is it supported under Vista 64 bits operating system?

    No, it's not supported under any 64-bit operating system.
    But it seems to work in compatibility mode, which turns on automatically in Vista. It may occasionally suffer a hiccup, but it seems to work for many people.
    Just make sure all of your firmware, RealTek drivers and Quicktime are up to date.

  • PreP crashes when rendering preview on timeline

    Hi,
    I'm using CS3. PrePro crashes when I try to render a preview on the timeline. It was working fine, then a few days ago it started doing what I described. I was almost done with the project when this started happening. I'm still able to make an AVI of the sequences,...but of course that is not a solution. Any suggestions on how to fix?
    Thanks for your help,
    Mary

    First, work through the steps here http://ppro.wikia.com/wiki/Troubleshooting
    If your problem isn't fixed, report back with the DETAILS asked for in the 15 questions at the end of that link... for question #1 you may use the FREE http://www.headbands.com/gspot/

  • Lightroom crashes when I try to access one particular folder

    Recently I've been renaming and reorganizing my image folders directly from Lightroom, instead of doing this in Mac finder or Bridge. Recently I renamed one particular folder that immediately caused lightroom to crash, and then keep crashing immediately after relaunching because it keep trying to load this folder in the library mode. Finally I decided to try and quickly select a different folder before it could crash, and this indeed worked. But it still crashes every time I try to view the contents of this folder. I tried deleting this folder from the catalog and then re-importing it, but after importing 10 or so images out of 500, it crashes agian. Could there be some corrupt file in this folder or what?

    I managed to get my Lightroom to a point were it crashes when I browse through certain folder.
    While testing possible solution for slow thumbnails problem I did the following:
    I shutdown Lightroom, renamed my preview folder, restarted Lightroom, rendered standard previews to folder X, browsed through those images few times, shutdown Lightroom again, removed new preview folder and renamed the old one back.
    Now, every time I browse through the folder X my Lightroom crashes at certain point. After brief testing there is no problems when I browse through other folders. Rendering standard previews to folder X did not help. I discarded all 1:1 preview from that folder I'm now rendering them again. Maybe that helps...
    Edit: Discarding and rendering 1:1 previews for all images in problematic folder removed my crashing problems.

  • LR3 Fix for Crash when using Develop Module

    Adobe tech provided the following fix for my system which crashed when switching to the Develop module.
    This is the  response I received from Adobe Tech.  
    Recreating the preferences file corrected the problem.
    Their help was right-on and appreciated.
    Ed
    * to Customer**
    06/11/201018:11:12
    Hi Ed,
    Thank you for getting back to us. I appreciate your promptness in
    responding to our email.
    The information provided was really helpful in understanding the issue.
    In order to resolve this issue I would request you to perform the below
    mentioned steps in order to resolve this issue:
    * Remove Lightroom beta from your system as you have the the full
    purchase version Adobe Lightroom 3.0 (Because there may be conflicts
    between the Beta Version and original product)
    * Try to create new Catalog with some new images and check if you are
    facing the same issue with Develop module.
    * Check if other functions are working fine like Slideshow, Print, Web.
    If the problem still exist after removing the Lightroom beta version
    from your PC, then perform the below mentioned troubleshooting steps:
    * Re-create the Photoshop Lightroom preferences file.
    Re-create the Photoshop Lightroom 3.0 and 1.x preferences files to
    eliminate problems that a damaged preferences file might cause. If you
    do not delete your 1.x preferences as well as your 3.0 preferences,
    other issues may occur.
    To re-create the Photoshop Lightroom preferences file:
    1. Quit Photoshop Lightroom.
    1. Rename the Lightroom 3 Preferences.agprefs file (for example, to
    Lightroom 3 Preferencesagprefs.old) and the Lightroom Prefere
    nces.agprefs file (for example, to Lightroom Preferences.old) in the
    Documents and Settings/[Username ]/Application
    Data/Adobe/Lightroom/Preferences folder.
    1. Start Photoshop Lightroom. Photoshop Lightroom creates a new
    preferences file.
    If the problem continues, the preferences file isn't the cause. To
    restore custom settings, delete the new preferences file and restore the
    original name of the previous preferences file.
    * Also Send us the Image size and format on which your are working in
    Lightroom hence resulting in this issue.
    This should resolve your issue. If it does, please let us know, however
    in case it does not; please revert with any new information that you
    might want to add which will help us in resolving your issue.
    You can also try referring to our knowledge base and User to User forums
    by clicking on the following links:
    Knowledgebase: http://www.adobe.com/cfusion/search/index.cfm
    U2U Forums: www.forums.adobe.com

    Creating a new catalogue and importing the images does not resolve the problem.
    The problem is only occuring on a few images from a particular collection.
    Creating a virtual copy also will not edit in photoshop.
    Creating a virtual copy and reseting the develop settings will allow the ctrl-e command to work.
    However, manually re-applying the develop settings once again stops the ctrl-e command working.

Maybe you are looking for

  • BT Yahoo E-mail - how to protect my primary addres...

    I've just joined, and it looks like a good time to join as I've only found 11 postings to check on 'BT Yahoo E-mail'. I've also tried the BT website but I get confused with the many different names, and confused between Yahoo and BT Yahoo. If you are

  • Assign master data fields of assets and equipment

    i want to include vehicle licence number in field assignments between FI-Asset accounting and Plant Management. How do i implement the enhancement to that effect. path spro .... AssetAccounting->Master Data -> Automatic Creation of Equipment Master R

  • Envy 7640

    Hi I try to install full drivers for my HP ENVY 7640 but it fails. After a while the installprocess stopps and I get this message: ......failed to start. Verify that you have sufficient privileges to start system services. I´m admin of my PC so I don

  • Function module (Incound idoc)

    Hi please advise when creating an Inbound FM from scratch the are some exporting parameter such as *"             VALUE(WORKFLOW_RESULT) LIKE  BDWFAP_PAR-RESULT *"             VALUE(APPLICATION_VARIABLE) LIKE  BDWFAP_PAR-APPL_VAR *"             VALUE

  • Bulleted List

    I have an unordered list in a web page which does not show bullets. I also have a horizontal menu  which has its own class. It includes a CSS rule to set List-Style: None which has probably got a lot to do with this problem.... Realising the potentia