Blue screen with Adobe Lightroom Classic

[KvackEvolution]

So i am using Lightroom on my new built editing PC. The problem is that after using it for like some couple of minutes it crashes the whole Windows. It happens specially sometimes(not always) when opening or moving photos but can happen even if i have minimised Lightroom to surf in Chrome instead.

I first i thought it was the graphics card so i turned off graphics acceleration in Lightroom. But still the same.
I use standard Windows Update driver for my 1050 because i thought it would not matter if i got the real Nvidia driver with Experience and the card is Low profile, since i do not play games on it.
Then i ran a memtest, but came out without any problems or errors. Turned on XMP in BIOS. So i founded out that Lightroom may not be so happy with CPUs over 4 cores, i have a 8 core CPU.

So i found that you can set a target line to allocate only 4 cores to Lightroom. But still it made no difference.

So here iam, without any more clues. Somebody that know what else i can test?

It is three different types of BSODs happening randomly each time when Lightroom is running.

KMODE_EXCEPTION_NOT_HANDLED

MEMORY_MANAGEMENT

FAULTY_HARDWARE_CORRUPTED_PAGE

Specs:
Os: Windows 10 Pro
Ram: 16 GB (2x 8gb) Corsair Vengeance LPX 3000 MHz
CPU: AMD Ryzen 1800x 3.7 GHz with 8 Cores
GPU: ASUS Geforce 1050 Expedition 2 GB
HDD: M.2 Samsung 960 EVO 250 gb, WD Black 2TB. And a Xyzel NAS server i store pictures on too in Lightroom.
MOBO: ASUS Prime B350M
PSU: Fractal Design 650 W
Case: Fractal Design Define R6

Regards

 

[Colif]

ntfs = New Tech File System

see if this helps
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC

also run chkdsk C: /f in command prompt (admin) - it will pop up 2 paragraphs, just type Y enter to let it run at start up

I would run HDTune on the nvme and other storage and confirm the drives are in good shape, as Memory management can also be storage drives.
Faulty Hardware Corrupted Page also points at the drives but can also be corrupted system files

Memory management is either drivers, ram or hdd.

Can you follow option one on the following link - here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

 

[KvackEvolution]

Fixed it.

Problem was that SSD was working too much because Lightroom stored all the photos on the SSD but i moved them to another drive. Then i downloaded Geforce drivers for the Graphics and the system became more stable.

Checked the system files with scannow as you said but it was all clear. Then just to be sure i downloaded CrystalDisk programs and did a read/write test and the results were fine too.

So my conclusion is that the SSD was 90% full in storage and was working over its limit and caused the crashes.

 

[KvackEvolution]

Well the problem isnt over yet.... Well sort off. Those messages are gone but there is one more called SYSTEM_SERVICE_EXCEPTION. Still happens after sometime regulary.

But this one i got a dump file from:

Link to DMP file: http://www.filedropper.com/061718-11218-01

What should i do ? Google a little about and found a program called Driver Analyser. Should i test it ?

Regards

 

[gardenman]

Hi, the link you provided to the dump file doesn't work. Try re-posting it and make sure the link works.

 

[gardenman]

Ignore my previous reply. The link is valid and working. Due to the excessive advertising websites use these days, it's sometimes difficult to tell what is an advertisement and what is the actual content on the page. And I'm getting old. That's my excuse.

I ran the dump file through the debugger and got the following information: https://pste.eu/p/jnCi.html

File: 061718-11218-01.dmp (Jun 17 2018 - 10:16:14)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: ntkrnlmp.exe (Process: Registry)
Uptime: 0 Day(s), 1 Hour(s), 14 Min(s), and 59 Sec(s)

Motherboard: https://www.asus.com/us/Motherboards/PRIME-B350M-A/
You have BIOS version 3401 (12/04/2017). The latest BIOS available for your system is version 4014 (2018/06/01). Note: Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

I can't help you with this. Wait for additional replies. Good luck.

 

[KvackEvolution]

Hi, the link you provided to the dump file doesn't work. Try re-posting it and make sure the link works.

That file dosn't matter anymore. As i was replying for the first time i got a new bsod message saying FAULTY_HARDWARE_CORRUPTED_PAGE

Both messages refereeing to the same driver file

I try Google Drive this time with a new dump file:
https://drive.google.com/open?id=1exIzEkUnSVQbo7oocMk2Yrptl7mJMbz2

 

[gardenman]

All of the dumps matter, even the previous one as they can be different types of errors caused by different things.

I ran the dump file through the debugger and got the following information: https://pste.eu/p/j8EW.html

File: 061718-9593-01.dmp (Jun 17 2018 - 12:58:53)
BugCheck: [FAULTY_HARDWARE_CORRUPTED_PAGE (12B)]
Probably caused by: ntkrnlmp.exe (Process: MemCompression)
Uptime: 0 Day(s), 2 Hour(s), 40 Min(s), and 31 Sec(s)

I can't help you with this. Wait for additional replies. Good luck.

 

[Colif]

Try running Memtest86 on your ram sticks, one stick at a time, up to 8 passes. It will create a bootable USB so you don't run it in windows. The only error count you want is 0 - anything higher is too many and you need to remove/replace memory.

It is likely I overlooked one area of PC that also plays big part in data corruption errors. See if Memory checks out

Updating to latest BIOS can also help as many bios updates add memory compatibility enhancements which could fix the errors.

 

[KvackEvolution]

Already did a memtest on them as you said. Results where 0.

 

[Colif]

The FAULTY_HARDWARE_CORRUPTED_PAGE bug check has a value of 0x0000012B. This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.

While is says its hardware, its often caused by software. Its misleading there.

SSD checks out.
Memory checks out...

Viable Solutions for faulty hardware corrupted page blue screen error
In fact, even Microsoft cannot confirm a 100% working method to fix the discussing issue. Though it's not a good thing to happen, the FAULTY_HARDWARE-CORRUPTED_PAGE error really will not cause damage to any computer, because usually the computer will do a restart and for most cases, the computer just went back to normal.

Only for people who experienced a frequent blue screen disaster, there are some suggested fixing methods that deserve a try.

1. Download the latest update of Windows 10, 8, 7 operating system.

2. Update all drivers, especially the display driver. For Dell, Lenovo, HP, Asus computer users, you'd better visit the official website and get the drivers.

3. Find a disk cleanup program, and simply use the program to clean your hard drive. Check the tutorial disk clean up Windows 10 which helps clean up junk files, delete temporary files and system files.

4. Check and repair hard disk partition errors in Windows.

5. Run Windows system file checker. In the command prompt, type "sfc /scannow" and hit ENTER.

6. Factory reset your Windows, or clean install Windows 10. This will definitely result in complete data loss, so remember to create a backup with EaseUS Todo Backup software.

https://www.easeus.com/todo-backup-resource/faulty-hardware-corrupted-page.html


ntkrnlmp.exe is part of the windows kernel. We think it stands for New Technology Kernel Multi Processor. what each part of kernel does is a bit of a mystery to me.

 

[KvackEvolution]

Since i have tried that now and it didn't do any difference at all. Should i try and reinstall Windows?

 

[Colif]

Did you ever run chkdsk?

also run chkdsk C: /f in command prompt (admin) - it will pop up 2 paragraphs, just type Y enter to let it run at start up

I mentioned it before.

I don't know what cause is, I am hesitant to get you to fresh install - I would read the instructions on here and ask them, they have more people who can get to bottom of this and perhaps avoid a fresh install - https://www.tenforums.com/bsod-crashes-debugging/ (can link to this thread if they start repeating instructions). I am curious what cause is, so if you get an answer, come and tell us

 

[KvackEvolution]

So i posted in the Windows10 subreddit and guided me through the drivers i needed to update which was Network, Chipset etc. that apparently where dated back as far as 2013. I also updated BIOS.

The PC runs more smoother now. I call the case closed for now

Link to the post: https://reddit.app.link/XgDIanZCyO

Thanks for everyone's responses and help