I'm on the release version LR 4.1
It's typically very stable, but when I enable the Secondary Display, it starts crashing every 10 - 15 mintues.
Win7x64
12GB RAM
ATI Catalyst 12.4 (was the same under 12.1)
Internal 256GB SSD w/ OS and catalogs
External 5.5TB eSata w/ RAW files
Canon 5d2 & 5d3 files
2x Dell U3011 displays
I've googled and searched the forums. Lots comes up about older versions, but I'm not finding anything about the current release version. Windows offers to check for a solution online and close the application.
Is anyone else experiencing this?
Edit: Crash Info
Problem signature:
Problem Event Name: APPCRASH
Application Name: lightroom.exe
Application Version: 4.1.0.11
Application Timestamp: 4fb2266f
Fault Module Name: StackHash_0048
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 000000000e03b641
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0048
Additional Information 2: 00488ae103b27b53b750fd0a6befe5ac
Additional Information 3: 3ff7
Additional Information 4: 3ff7fba6a8eae8d3bb747e40a2be9b11
Message was edited by: Digihotaru
Yes, Victoria. This is happening on Catalyst 12.1 and 12.4. (I skipped 12.2. and 12.3 as I was having no problems on 12.1 until I added the second display and this started happening. I am not having trouble in any other applications.)
I rarely ever work in less than full screen mode. Is this something I should test? Any particular sizes I should try?
Hi Victoria. I'm using a utility called "Sizer" to lock the primary and secondary windows to 1920x1200. I'll let you know what happens.
It seems more likely this is an LR issue, or at least something specific to how LR interacts with the video driver, no? If it were strictly an internal driver-fault, I would expect to see a bluescreen with a mention of an ATI dll.
Will report back when I have more.
Yeah that's what I've done. Sizer let's me assign a WxH number of pixels to an app, so for example I can tell it to "size" LR to 1920x1200 even while the display is running at 2560x1600. So far no crash, but I'd like to go a few days before I feel comfortable reporting back for sure. The issue has been squirrely and inconsistent.
Bummer, it just crashed again. This is with both windows (not screens, just the LR windows) locked to 1920x1200.
I also reinstalled LR4.1 today just for grins.
Problem signature:
Problem Event Name: APPCRASH
Application Name: lightroom.exe
Application Version: 4.1.0.11
Application Timestamp: 4fb2266f
Fault Module Name: StackHash_0048
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c000001d
Exception Offset: 000000002f6499a2
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0048
Additional Information 2: 00488ae103b27b53b750fd0a6befe5ac
Additional Information 3: 3ff7
Additional Information 4: 3ff7fba6a8eae8d3bb747e40a2be9b11
I've just seen a Photoshop page saying that there's a beta Catalyst version available. http://helpx.adobe.com/photoshop/kb/photoshop-crashes-or-features-phot oshop.html It's a really long shot, but I can't help but think graphics are involved.
Over the last few days I've been processing 2000+ photos from a recent trip. Initially, LR 4.1 would crash periodically - after a couple hours. As I got to the end yesterday evening, LR would crash after just a few photos and it even crashed right as I selected my first photo to work on after restarting.
I haven't processed this many photos at once in a while so I wasn't noticing issues. This is also the first big project on LR 4.x
I haven't tested going with a single display enough to know if dual display is the cause but it didn't crash until I went back to dual display. I'm running Catalyst 12.4. I actually haven't had much success with 12.3 or 12.4 honestly. I think my system was more stable pre-12.x.
I'm going to try the suggestion of reverting drivers to see if that helps.
Right now, I'm just trying it with Catalyst Control Center uninstalled and running just the video drivers. Ever since upgrading to 12.x, I've been having weird Crossfire crashes that may or may not be related to the LR crashes with dual display.
I'm going to spend some time tonight with dual-display, no CCC. I'm almost finished with the processing. If all goes well with this, I can try reinstalling CCC (can't decide between 11.8 - the last ver. that worked or 12.6) and running single display as I won't really need dual display to do my selects.
Ha! I probably should've tested single display before uninstalling 12.3. I'm not going to guarantee anything. If this setup works, I'm going to stick with it until I'm done and leave the troubleshooting until later.
I'm getting "Not Responding" - LR freezes, no BSOD. Vista (64-bit) and everything else continues to run normally. I kill LR from the Task Manager. I also tried with Crossfire off. Didn't help. It just got very bad, very quickly.
Crazy. I just had the same crash, except this time I'm on my laptop. Completely different machine, but still the common thread is two screens.
I have the laptop's display + an external Dell 2407 WFP, with both screens in use for LR.
Still an ATI video card, but a 7690M (vs a 5870 in my desktop.)
| Driver Packaging Version | 8.882.2.3-110930a-126246C-HP | |
| Provider | ATI Technologies Inc. | |
| 2D Driver Version | 8.01.01.1178 | |
| 2D Driver File Path | /REGISTRY/MACHINE/SYSTEM/ControlSet001/Control/CLASS/{4D36E968-E325-11 CE-BFC1-08002BE10318}/0000 | |
| Direct3D Version | 7.14.10.0855 | |
| OpenGL Version | 6.14.10.11013 | |
| Catalyst Control Center Version | 2011.0930.2209.37895 |
Updating the driver in this machine isn't easy, because it supports switchable graphics. (But yes, I'm on the ATI card at the moment.)
It sound more and more like a bug. Can I get you to post it over at the Official Feature Request/Bug Report Forum so it can be tracked properly. You could include a link to this thread too.
Hi Victoria. I see a thread over there that's about 10 months old and seems to describe my issue. It was originally created to discuss LR 3.4, though as comments progress eventually we wind our way up to 4.1RC. Would you recommend starting a new thread, or bumping the old one?
Anyone else experiencing this issue might pop over and click the +1 button to help us get some attention.
[Edit:The OP over there is on an ATI card, but a commenter jumps in a month ago with the same issue on nVidia. I wonder if we're barking up the wrong tree with graphics drivers?]
Message was edited by: Digihotaru
Aha! We might be on to something a little revealing. Dan Tull responded to the thread in the bugs forum, and while he never fully got to the bottom of the issue, he was working on the theory that it was related to custom monitor profiles. This would be true for 100% of my machines. Could others here who have had the same issue also comment on whether they're using custom profiles?
We could be a lot of help by getting some minidumps to Dan to look at.
Here's the thread in the bug report forum:
And here are the instructions for configuring your Windows computer to collect mini-dumps:
http://msdn.microsoft.com/en-us/library/bb787181(v=vs.85).aspx
These are not the same as the dumps that your computer creates during a BSOD, so it's important to actually read through that MSDN article, make the configuration changes, and start getting LR to crash again.
Dan has a gmail address that he provides in the bug thread so we can send the minidumps to him, so I'm going to assume that it's ok to share that here, too. dantull@ you-know-the-rest.
Just to add my two cents. I have custom profiles for my monitors but they're handled by ColorEyes Display Pro. Not sure if your profiles are 3rd party or through the card.
Since uninstalling Catalyst Control Center, I've had no LR crashes. So from Thurs. to Sat. - dual monitor the whole time. As far as I can tell it hasn't affected performance.
That might be worth sharing with Dan over in the other thread, chaos888.
FWIW, I don't think Dan was concerned with what device created the profiles, just that they were custom profiles. I've been on the road and haven't been able to work on this as much as I'd like, but I'll get back to it next week.
North America
Europe, Middle East and Africa
Asia Pacific