Lightroom: 4.4RC very unstable, blue screen quite often "windows must shut down"

  • 1
  • Problem
  • Updated 6 years ago
  • (Edited)
I get the windows blue screen quite often
"windows must shut down"
it happens in develop module while doing basic things : zoom and labeling

it did happen with early version, but stopped with LR4.3,
I am going back to LR 4.3

Asus P5B, Intel quad Q9650, windows7, 6Giga RAM DDR2
Photo of Hervé Le Lous

Hervé Le Lous

  • 4 Posts
  • 2 Reply Likes
  • frustrated

Posted 6 years ago

  • 1
Photo of jdv

jdv, Champion

  • 728 Posts
  • 56 Reply Likes
If you are getting blue screens then look to your hardware. Lightroom uses some resources and each release uses them differently. But an app cannot crash your entire OS. You have some bad memory or a bad driver.
Photo of John Spacey

John Spacey

  • 101 Posts
  • 20 Reply Likes
"But an app cannot crash your entire OS"

Oh dear..... Yes it can. An 'app' CAN cause a blue screen.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 818 Reply Likes
No, an app cannot. An application can ask a driver, OS or hardware to do something that then triggers the bluescreen - but only if there is a fault in the driver, OS or hardware.
The application itself cannot cause a bluescreen.
The point of the bluescreen is that it is a low level hardware or kernel fault, not a simple application error.
Photo of Son Nguyen

Son Nguyen

  • 61 Posts
  • 12 Reply Likes
Yes it can, but if you are the only one experiencing this problem out of thousands of people then it's pretty high chances that there is something wrong with your hardware. I have the same hardware with OP, I got blue screen when opening Firefox and Diablo III. Turn out the power supply was faulty.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 818 Reply Likes
Again, no - applications cannot directly cause bluescreens. The bluescreen is different from an application crash because it indicates a very low level fault in the OS, kernel level drivers, or hardware.
Photo of Hervé Le Lous

Hervé Le Lous

  • 4 Posts
  • 2 Reply Likes
Thank you for your comments
I summarize:
LR4.4RC CANNOT be the cause of blue screens

BUT , it is the only program that causes blue screens on MY computer
So all other programs work fine with my harware
and my hardware is faulty when working with LR 4.4rc

I have read that in a famous Kafka's novel and wont argue anymore
have a nice day
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 818 Reply Likes
Your hardware or drivers are faulty - it is just lightroom that uses the faulty code (so far, you'd probably hit it elsewhere if you tried more applications).
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 384 Reply Likes
Just to be clear: BSOD means bad hardware *OR* driver bug. It's entirely possible that Lr exercises hardware or driver in a fashion other apps don't (e.g. ever notice how much ram Lr uses compared to other apps?).

Have you checked ram and updated drivers, esp. display driver?

Also, I assume you've run Windows Update - i.e. problem could also be OS, and if not hardware / drivers, then re-install Windows.
Photo of LRuserXY

LRuserXY

  • 426 Posts
  • 41 Reply Likes
Just trying to clarify what the others already tried to explain:

LR may have triggered the blue screen, but it is not its fault!

By definition (!), any application may tell the operating system to do anything via the OS API, regardless of whether it is illegal or not or whether it may kill the hardware or not. It is the responsbility of the operating system and its underlying drivers to check for the legitimacy of the API call and if it does not check out, report an error to the application, for example, when the application wants to delete a file without permission to do so - or when trying to draw outside the screen etc. etc.

If the operating system crashes (e.g. windows with its blue screen), this indicates a fault in the hardware, a fault in some driver, or in the worst case a fault (a bug) in the operating system itself. The application is not at fault - again: by definition.

We all know that LR can be very resource hungry (CPU, RAM) and also does a lot of graphics activity (redrawing in scrolling the thumbnails all the time, updating the display when zooming or panning, etc. Because of that resouce hunger, LR may be unintentionally triggering some special imperfection present in your system that other application don't trigger.

The important part is to understand the "by definition" thing (and yes, I repeat myself over and over here): Any application may do anything it wants - a modern operating system has to remain "calm" and stable - and stop the application in a case of emergency, but never crash itself. If it does, it is the fault of the OS itself, and/or its underlying drivers and hardware.

A blue screen in windows is never a case for Adobes support. It is a case for Microsofts support, for the support of your PC vendor or the support of the vendors of other hardware (e.g. graphics card).
Photo of Hervé Le Lous

Hervé Le Lous

  • 4 Posts
  • 2 Reply Likes
Thank you , I think I have a better understanding now
Can you tell me how to check my RAM?
I will check my drivers (screen driver)
I keep win7 updated regularly
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 818 Reply Likes
RAM isn't easy - software based testers only catch the most obvious problems (which usually would have preventing booting anyway), and hardware testers are expensive and hard to come by. The most reliable way for an end user to test RAM is by replacing it with other sticks of RAM and seeing if the problem disappears.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 384 Reply Likes
1st try enabling ram check in boot rom (press Del upon power-up). I have had better luck with it than Chris has I think (it's caught every ram problem I've ever had, m'self personally, which, granted, is not that many... - most (but not all) of which did not prevent booting). Booting only requires a relatively small amount of good ram at the lower addresses, Lr is using way more ram than it takes to boot, or run other apps...

If such tests turn up the problem, then you're done, if not, then it's time to consider ram card swapping...

Note: bad ram sockets can also be a problem, and card swapping won't reveal such a problem, whereas ram checkers (sometimes, if not often) will.
Photo of LRuserXY

LRuserXY

  • 426 Posts
  • 41 Reply Likes
memtest86+ does a good job at RAM testing. It found some defects in my old Dell's RAM that the diagnostic test did not find. It it better than most other RAM tests because it swaps itself to another location and also tests the RAM that it is running itself from - so every part of the RAM that can be used by OS and applications is actually tested.

Of course, like Chris Cox said, it cannot find every possible error, but it seems to come very close.

P.S. It is also important to check the hardware in general, preferably using the PC vendors diagnostic disc (or builtin in Bios). While not as likely as RAM defects, other components of the PC can show defects, too.

P.P.S. Windows 7 has also an integrated memory diagnostics tool. However, I don't know how thorough it is compared to memtest86+. The advantage is that you don't have to create a boot disk or flash drive. It just runs before windows boots.