Solved BSOD - primarily when using Lightoom (sometimes just randomly)

[essenbe]

If you want to try that first, go ahead. But, I would also suggest, if you haven't to run your Hard Drive Manufacturer's diagnostic program on all hard drives, both the short drive self test and the long test. If you have a friend who is good with electronics and has a multi meter, see if you can persuade him to come over and test your PSU. If it is possible, see if he can test the 12V rail at full load as well as at idle.

If you will tell me the had drive manufacturer, I'll give you the link to their diagnostic test.

 

[odessit40]

I'll see who I can find

Quite a peculiar problem, right?

 

[essenbe]

When you did Driver Verifier, you should have selected only non Microsoft drivers, and crashing upon the OS loading should be a sign it is a third party driver.

 

[essenbe]

Pretty much, it is. It is turning out to be one of those tough ones. If you have replaced the Motherboard, if I am right, then test the hard drives, and can get a good test (and person doing the test) on the PSU, it seems there is nothing left but software.

 

[odessit40]

I am really leaning to software - PSU is relatively new - less than a year old

 

[essenbe]

Well, software is a different animal than hardware. A piece of software can be fine, but conflict with another driver from another piece of software. By themselves, they are fine, but together they will crash the computer. And it is very difficult to tell which 2 pieces are doing it. Then there are other pieces of software which are known to cause BSODs, McAfee being one of them and is almost impossible to completely get rid of.

 

[odessit40]

I give up

Another BSOD - same circumstances.
I ran "WhoCrashed" to analyaze minidump

On Sun 6/22/2014 7:49:10 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0x1E3)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800E61E028, 0xB630A000, 0xA9000175)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

[essenbe]

Please post the dump file located at C:/windows/minidump. It will probably It is probably the last one, but the numbers ate the date and time they are usually 0622140156 which would be 06-22-2014 at 1:56 plus the seconds. But, you will have to provide admin permissions, but copy them and paste them to a folder on the desktop. Then highlight that folder, right click it, select send to > compressed zip folder and upload it using the paperclip icon in the reply window.

 

[essenbe]

Odessit, just be a little more patient and relax. I have called in the Calvary to help. It hurts my Ego to do that but, I think it's needed. I almost believe it is the Lightroom program itself causing the problem, but we'll see what all the smart guys say. If they figure something else out, then I will admit they are smarter than me. Begrudgingly, of course. :roflmao:

 

[odessit40]

Thanks so much, b/c i am really out of ideas. Maybe it's the host hard drive. I also read somewhere that sometimes when you have multiple hardrives, it caused issues for the OS as it gets confused which hard drive to access.

Anyway, here't the memdump archive

 

[odessit40]

Ps. I've removed and reinstalled Lightroom, upgraded to 5.5 (brand new latest version) and still.

 

[Boozad]

Can you confirm you now have a legitimate copy of Windows. And are you overclocking any of your components?

I have to disappear shortly but I'll be around to try and help essenbe where possible.

 

[odessit40]

Boozad, please the attached screen shot

 

[odessit40]

No, no overclockinjg, running everything as normal.

 

[Boozad]

OK, I'll re-read through the thread and see what's been changed etc and see if something shakes loose. Have you tried using Lightroom using the onboard graphics? It may be an idea to rule out the GPU completely by uninstalling it, physically removing it and hooking up to the onboard graphics.

 

[essenbe]

Not true about multiple drives. They are not a problem. Look at my computer. It has no problems at all.

View attachment 322774

 

[odessit40]

I don't have an internal GPU, but i switched cards - I went from 1gb EVGA card with 192 CUda cores to 2gb ASUS HD850

 

[essenbe]

Odessit, Boozad lives across the big pond in the UK. it's around Midnight for him, not to mention he really needs his beauty sleep.

 

[odessit40]

thanks for all the help. Looking forward to r4esolving this issue

 

[essenbe]

Can you find another hard drive, or transfer all the stuff off of one onto another drive, so we can have 1 drive to wipe clean? We will do an experiment and see if we can tell what's happening. If done that way, it wouldn't bother your Windows installation you are using now. If you are up for it, let me know first. I want to micro manage this. It should confirm it is a hardware or a software problem.