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

[odessit40]

Hello

I started having BSODs randomly - seems like it happens due to intense graphic load - such as using Photoshop or Lightroom. Unfortunately, I cannot pinpoint the issue as the BSOD's give random codes.

I ran memtests without any errors, I swamped a brand new Videocard from 1gb to 2gb, but still the problem persists.

Any help would be very much appreciated.

 

[Thedoctor44]

BugCheck [COLOR="red"]124[/COLOR], {[COLOR="Blue"]0[/COLOR], [COLOR="Green"]fffffa800e5187f8[/COLOR], 0, 0}

Probably caused by : [COLOR="Red"]hardware[/COLOR]

0x124 bugchecks indicate a fatal hardware error has occurred, the 1st parameter is a machine check exception which means the CPU has found a fault with a hardware piece and has initiated a bugcheck.

The 3rd parameter is the address where the WHEA error record is stored, lets have a look.

3: kd> [COLOR="Green"]!errrec fffffa800e5187f8[/COLOR]
===============================================================================
Common Platform Error Record @ fffffa800e5187f8
-------------------------------------------------------------------------------
Record Id     : 01cf794a62ac3724
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : [COLOR="Blue"]Machine Check Exception[/COLOR]
Timestamp     : 5/27/2014 1:24:27
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800e518878
Section       @ fffffa800e518950
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Data Write
Flags         : 0x00
Level         : 1
CPU Version   : 0x0000000000100f43
Processor ID  : 0x0000000000000002

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa800e5188c0
Section       @ fffffa800e518a10
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000002
CPU Id        : 43 0f 10 00 00 08 04 02 - 09 20 80 00 ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa800e518a10

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800e518908
Section       @ fffffa800e518a90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : [COLOR="Orange"]DCACHEL1_DWR_ERR[/COLOR] (Proc 2 Bank 0)
  Status      : 0xf612c00000000145
  Address     : 0x0000000004453490
  Misc.       : 0x0000000000000000

That's a level 1 Cache data read error, looks like the CPU is at fault.

Stress test your CPU with Prime95

I recommend running Prime95 for around 2 hours

   Warning

As with most stress tests your component's temperature will rapidly increase.
It is advised that you download a temperature monitoring program like HWmonitor
Keep an eye on your temperatures and stop the tests if it starts to overheat

Free your startup, remove all unnecessary programs from launching when you first login.

http://www.sevenforums.com/tutorials/1401-startup-programs-change.html

Daemon Tools/Alcohol is known cause of BSODs.

Registry and SPTD problems | DAEMON Pro Help
How to remove sptd.sys from system

1. Uninstall Daemon Tools.
2. Download the SPTD standalone installer and follow these steps:
3. Double click the executable to open it
4. Click the button shown below

If the button it is grayed out, as shown in the image, there is no more SPTD installation on your system, and you can just close the window.

Post back the results.

 

[odessit40]

I ran Memtest for the whole day - initially it picked up 2 errors (attached). I then tried to isolate the problem to each memory stick and/or DIMM slot...so i ran the specific test which identified the error 4 times (for each RAM stick and for each DIMM Slot)....results came clean
I uninstalled Daemon Tools, so will see
I ran FurMark - it leveled out the GPU's temp at 76C and CPU stopped around 55-58C
PS. I do not thing it's the hard drive as I swamped 2 hard drives (System was cloned) and the problem persisted.

Any other ideas? I will keep you posted as to the Stability after Daemon removal.

 

[odessit40]

Crashed again as soon as I started to work in Lightroom
COuld it be the Motherboard?
Here's the latest MemDump

Any help would be GREATLY appreciated. ( I really dont have time now to build the new rig..even just reinstalling everything)

 

[Thedoctor44]

Try your HDD anyway, I'm starting to have my doubts.
You are still getting 0x124 bugchecks.

Did you run Prime95 as suggested?

 

[odessit40]

Running Prime95 for 2 hours now - no problems
50C on CPU, MB at 40C

I tried something last night - i pulled out all RAM module from all 4 slots...put in a module into the 1st slot, and Lightroom crashed it out....
then i put in the module into slots 2 and 3....stable...added a module into slot 4....so currently running 12GB of RAM from DIMM slots 2-4...so far, stable
Did not experience crashes in Lightroom...yet.
So i have 2 ideas - 1) Dimm Slot has gone bad... 2) Crucial RAM is not so reliable.

 

[odessit40]

Crashed out again
Going to try to swap SSD's now...

I am completely clueless at this point...

 

[Thedoctor44]

I can't vouch for crucial seen as though I've never been with their products, it could indeed be a faulty DIMM slot.

Upload the new dump files.

 

[odessit40]

Latest dump file

PS. I meant Corsair RAM (not Crucial)

 

[Thedoctor44]

No new dump files.
The latest one is a 0x124 from the 26th which I think I analysed before.

Check in C:/Windows/minidump for new .dmp files.

 

[odessit40]

I accidentally switched from small memory dump to Kernel....
i am sure it will crash in no time and i will provide the file
COmputer was idle and BSOD'ed with 0x000001E code

 

[Thedoctor44]

If you switched to Kernel Memory Dumps then check here:
C:/Windows/memory.dmp

A Kernel Memory Dump will give us more insight.

You will have to upload the file to a sharing site like OneDrive.

 

[odessit40]

For some reason, i can't locate the DMP files....Win7 is not generating and I checked all the options

 

[Thedoctor44]

A driver may well be behind all of this.
Lets give Driver Verifier a try see if it can pick anything up.

Enable driver verifier but only enable the options: Standard settings and IRP logging step 3.
Don't enable Force Pending I/O Requests

Enable Driver Verifier to monitor the drivers.
Driver Verifier -Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

We use Driver Verifier as it puts a stress on the drivers, and so it makes the unstable drivers crash. This should flag the driver responsible in the dump file.
It

Driver Verifier will make the system laggy, this is normal so don't worry.

Before enabling DV, make sure that you have earlier System restore points made in your computer.

If there are no points, make a System Restore Point Manually

Post back the results.

 

[odessit40]

Thanks, trying it now

 

[odessit40]

After the crash, memdump should be created?>

 

[odessit40]

crashes out, but nothing is created.
Tried running Lightroom from Safe mode....BSOD - hardware.
Clueless

 

[Thedoctor44]

Ah yes I forgot.
You had errors before in memtest.
Try testing each stick at a time.

 

[odessit40]

I am re-installing win7 and will try with a clean system. Will report back

i am leaning towards driver conflict

 

[Golden]

Did you replace the faulty RAM?

If I recall correctly, you:

1. Got 2 errors when all the DiMM's were inserted; and
2. Got 0 errors when you tested them individually

When you performed the individual tests, did you run for a minimum of 8 passes on each?

If you haven't solved this particular issues, then I would concluded either the RAM and/or motherboard is faulty. You will continue to experience 0x124 BSOD's until you get to the bottom of that.