Skip to main content
tbbiggs
Inspiring
January 4, 2024
Answered

Instant BSOD upon launch - CRAW corruption

  • January 4, 2024
  • 2 replies
  • 2869 views

I was editing within LR Classic and was synching settings between a batch of 23 photographs. Specifically, I was syncing the AI masking tool for backgrounds. The process crashed (BSOD) about halfway through. Kernel exception. After forced restart, any attempt to open LR resulted in a subsequent BSOD as soon as an image (the last one I was on before the crash) displayed.

 

I was able to successfully open another catalog without a crash. I was able to open the same catalog I was working in AFTER I moved the original .NEF files to an alternate disk location. Subsequently, I also discovered that if I attempt to open any of the .NEF files I was working on in Photoshop 2024, I also get a BSOD.

 

Earlier today, I worked through a batch of .NEF images from the same shoot day and exported those out without a problem, however, I am now unable to launch those .NEFs without another BSOD.

 

I'm wondering if CRAW is corrupted somehow? Or, possibly, something to do with the specific codec that is required to work with Z9 image files? I am going to test that and attempt to open RAW files from a different camera, but I have not done so yet.

 

I have done the following:

Updated graphics card

Completed all system updates

Restarted

 

Help very much appreciated.

This topic has been closed for replies.
Correct answer tbbiggs

Assuming that you do indeed have the latest manufacturer's graphics driver, and that copying the raw files to another installation of LR on another computer doesn't trigger the problem, that's strongly pointing at a hardware issue. The next steps would be as others have suggested:

 

- Work through the steps for diagnosing BSODs.

 

- Run thorough hardware diagnostics, especially on memory.

 

- Eliminate the disk as a possible issue by using another disk.

 

- See if the cooling system has problems, e.g. clogged fans. LR uses the CPU and GPU much more heavily than the typical app, and starting up LR can quickly trigger overheating, in which case the computer can sometimes halt.  Besides trying to analyze the system events, you can get one of several reputable utilities for monitoring temperature. (Intel recently withdrew theirs, which was very easy to use.)


I believe I have isolated the problem.

 

Before I give more details, I'd like to comment on this thread, and why it's a great example of how online help gets so derailed so easily. There's a ton of opporunity to learn here I believe.

 

I gave an initial description of the problem that was reasonably specific, adequately detailed, and specifically isolated the things I'd tried so far. Instead of operating from the assumption that I'd actually done so, respondents did exactly the opposite, making me feel like I was being treated like a fool. While I am no genuis software developer, I'm an advanced computer user, an extremely experienced Lightroom user (I would hazard a guess that no one here has been using it much longer than I have, if at all unless they work at Adobe) and I have more than a baseline understanding of 'the usual suspects.' Instead of asking me about any of that, most respondents assumed I was a newbie. Then, doubling down, almost no one actually bothered to even read my replies to them. For example, you said, "Eliminate the disk as a possible issue by using another disk," even though I'd just said, "(and, unmentioned, stored on different SSDs."

 

Now, granted, your last reply did have several new suggestions, so I do appreciate the continued effort, I'm simply saying all this because I truly believe that more productive conversations will be had when the presumption is not 'OP is dumb.'

 

Anyway, the solution (I believe):

 

I was going to open an .NEF directly from the memory card and see what happened. I accidentally double clicked on one, and instead of opening Photoshop like it usually would, it opened Windows Photos. There, it said, 'Windows Raw Image Extension update available.' I clicked to update, updated, and then tried to open one of the problem files with Photoshop. This time, it did not BSOD, but it DID error. That error was: "Could not open (xxxxxxx) because the file-format module cannot parse the file."

 

I restarted the computer, and upon restart, I could open that file (and all other Z9 files) normally in both LR and PS. I have since tested dozens, done an export, and everything works correctly.

 

So, I don't know exactly what happened or why it happened when it did, but the issue seems to be resolved. I will update if it returns.

2 replies

tbbiggs
tbbiggsAuthor
Inspiring
January 5, 2024

Kernel Exception Not Handled

johnrellis
Legend
January 5, 2024

When the operating system crashes, it is always by definition either a hardware problem or a bug in the operating system itself or a driver. A primary responsibility of the operating system is to stop applications from interfering with other applications and, in particular, from crashing the whole machine.  When an application can cause the operating system or driver to crash, the OS developers consider that a high-priority bug to be fixed immediately, because such bugs are one of the primary methods bad people use to break into systems.

 

The quickest way to determine whether the a particular raw file is corrupted is to upload it to Dropbox, Google Drive, or similar and post the sharing link here. If the file works correctly in other LR installations, that strongly indicates it isn't corrupted.

 

Regarding graphics drivers, there are MANY posts here from people insisting they've updated to "the latest". Unfortunately, Windows Update and some computer manufacturers' crapware utilities can report that a driver is up-to-date when in fact it's woefully out of date. The only way to verify you have the latest driver is by going directly to the manufacturer's web site:

https://helpx.adobe.com/lightroom-classic/kb/troubleshoot-gpu.html#solution-4 

 

I don't see where you indicated the method you used to "update" the graphics driver. But you can put the issue to rest by doing the LR menu command Help > System Info and copy/pasting the entire contents here.

dj_paige
Legend
January 4, 2024

BSOD is almost always a bad driver somewhere or a hardware malfunction somewhere. Make sure your GPU has the most recent studio driver, and if that doesn't fix the problem then you need to run diagnostics on all of your hardware. The Windows forums have lots of discussion about how to diagnose the cause of BSOD, and I'm sure Google can find some advice as well.

tbbiggs
tbbiggsAuthor
Inspiring
January 4, 2024

As I isolated in my initial comment, I have ensured that the GPU is up to date, as are all other drivers.

 

I have also now verified that only Z9 RAW files cause the BSOD malfunction, other NEF files open and function normally. This issue is almost certainly not hardware related.

dj_paige
Legend
January 4, 2024
quote

I have also now verified that only Z9 RAW files cause the BSOD malfunction, other NEF files open and function normally. This issue is almost certainly not hardware related.


By @tbbiggs

 

Disagree. BSOD is almost always hardware or driver. Maybe the Z9 photos put more stress on the hardware because they are larger than other Nikon raw files. Also, did you update teh driver with the latest STUDIO driver?