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

[essenbe]

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.

Golden is 100% correct. If you have ram problems, a clean install will not help. The ram issue has to be dealt with before anything else. You are getting 0X124 errors which indicate a hardware problem. You received errors while testing ram. The next step is obvious. You have a ram problem. You need to label the sticks and run each stick in each slot for a minimum of 8 passes or until you receive an error. If you receive an error , stop the test and move the stick to the next slot and run the test again, and note which stick received errors and in which slots. That is the only way to determine if the problem is the ram or the motherboard Dimm Slots. Corsair is a reputable and well respected company and has a lifetime warranty on their ram, if you are concerned about that. But, you can have either a bad Motherboard or bad ram. You have to determine which one before proceeding. Again, a clean install will not help and it is not a driver problem. As long as your ram is throwing errors, you will BSOD. You have to fix that before proceeding any further. Period, end of story.

 

[odessit40]

So here's the latest update:
1. Brand new board - checked compatibility with CPU and RAM...both are good
2. Clean Install...
3. Ran Memtest Pro for 8 passes - 0 errors

the system still gives me BSOD - says unrecoverable hardware problem

Will post memdump here shortly.

I am clueless at this point...only 2 ideas are left
1. Either the hard drive carrying the photos has gone bad
2. Lightroom version is corrupt and is causing issues
and possibly not enough voltage to RAM? - i have Vengeance 4gb x 4 - with specs 9-9-9-24 with 1.5v

 

[essenbe]

Oddessit40, I have never heard of memtest Pro. If you will check post #2 it gives a link to the tutorial about memtest, which links to memtest86+. We ask for specific tests for a reason. Please run memtest86+ for 8 complete passes. Even if you get the same results, you will know your ram was tested properly. Memtest86+ is the industry standard and is used by every hardware enthusiast I know, for one simple reason. It is the best test available and better than all the rest.

 

[odessit40]

Will run memtest that you recommended. Meanwhile, here's the memdump

 

[Golden]

Host Name:                 ODESSIT40_1-PC
OS Name:                   Microsoft Windows 7 Ultimate 
OS Version:                6.1.7601 Service Pack 1 Build 7601
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          ODESSIT40_1
Registered Organization:   
Product ID:                00426-OEM-8992662-00173
Original Install Date:     6/9/2014, 9:27:51 AM
System Boot Time:          6/9/2014, 8:17:15 PM

I'm not sure why we missed this before, but at this stage I would recommend you stop investing money in hardware, and spend it on a genuine version of Windows. An ASUS OEM on a retail motherboard constitutes a counterfeit installation. Perhaps this installation is a contributor to the problems.

 

[odessit40]

ok, thanks, will give this a shot.

 

[odessit40]

Aside from the possible un-genuine version of windows, any other ideas? I am worried that I will spend 200 dollars on a brand new Win7 and then this problem with persist

 

[essenbe]

Unfortunately, without a valid Windows activation we are precluded from helping with illegal software by forum policy. If you will get a valid activated copy of windows and post the MGADiag results here, we will be happy to help you.
http://www.sevenforums.com/windows-...ne-activation-issue-posting-instructions.html

 

[odessit40]

Great, thanks guys....give me a few days to sort it out

 

[essenbe]

No problem, take your time, we'll be here, and be more than willing to help with a genuine Windows installation.

 

[odessit40]

I just downloaded a copy from digital river (supposedly it's an official microsoft distribution site)...it gives 30 days trial

Do you know if it is legit?

 

[essenbe]

Digital River ISOs are almost always legit, but what you are paying for is the activation number. That's the part that counts.

 

[odessit40]

I just burned the ISO from digital river to my dvd - tried to boot into the disk...was told that drivers were not found. (boot was from an external dvd-rom)

any suggestions?

 

[odessit40]

Just BSOD after genuine copy of Win7 was installed...
could it be a hard drive on which the photos are stored?

 

[odessit40]

I am attaching the latest crash files - i HAVE NO IDEA WHAT TO DO ANYMORE

 

[odessit40]

One more zip of memdump

 

[essenbe]

Oddesit, I am assuming you can still boot into Windows. As soon as you do, click start, ype device manager and post a screenshot of device manager ( http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html ).

Next do this:
Open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.


And last, click start, open control panel, category view and you should see uninstall a program, click that. Expand the window as much as possible and post a screenshot of the whole window. If it takes 2 screenshots, that's OK. It will will us what software you have installed and so we will know if you have a program installed that is causing conflicts.

 

[essenbe]

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. Follow this tutorial for instructions.
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

 

[odessit40]

No integrity violations have been found.
will run the driver verifier..

 

[essenbe]

I would recommend removal of McAfee as it is a big cause of BSODs and install Microsoft security essentials (Microsoft Security Essentials - Microsoft Windows) . To remove McAfee go to http://www.sevenforums.com/tutorials/78961-av-uninstallers.html and find McAfee products and click on tool.