BSOD on new PC build, error code 50

coldspring · 01 Jun 2014

Dear all,

I am trying to solve the mystery of my PC crash problem and hoping to get some help from you experts here. Normally I could solve computer related problems myself. But this one is just beyond my ability.

Early this year I built a PC for photo editing. I have numerous accounts of BSOD with it. Yesterday I did one more time of Windows 7 fresh installation and still got the same problem. There wasn't a clear pattern when the crash would occur but I found I would get BDOD (mostly error code 50, occationally code 3b) most often under several conditions:

1. When I tried to install drivers for the Asus MB, chipset fix, and other Asus software.
2. When I install Windows update. I selected to install all updates and the computer would crash in the middle of installation. I had to run the Windows Update several times to finish all updates.
3. When I use Photoshop Lightroom. It could crash when I import photos on cards, or when I edit photos.
4. Sometimes Windows would crash when no particular tasks are running. For example, if I left the computer on for the night, very often in the morning I would find it had crashed .

My PC has:
i7-4770K
Asus Z87-A MB
G.SKILL Ripjaws X 16GB (2x8GB) F3-1600C9D-16GXM
Samsung 840 EVO 120GB SSD
running on Windows 7 Professional x64

I tried to analyze the minidump files myself, but the information I got was quite vague. I still had no idea whether the problem was caused by faulty parts on the MB or bad memories. Just to clarify, I have installed the latest drivers and even BIOS for the Asus MB. I also run many passes of stress test for the memories but couldn't detect any problem. I uploaded here the SF folder and a few earlier minidump files I saved. I would appreciate it greatly if someone can take a look at them and point me to the right direction.

Thanks a lot! Please let me know if I need to provide any other information.

Arc · 01 Jun 2014

Hi coldspring.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result.
__________________________

Code:

BugCheck 50, {ffff98a00e0c6fb8, 1, fffff80003009147, 7}

*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys

Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+537 )

Followup: MachineOwner
---------

coldspring · 01 Jun 2014

Hi Arc,

Thanks for reply! I have done Memtest86+ test several times, some 8 passes and some 16 passes. I didn't get any error. Is there anything else I should do?

Thank you.

Arc · 01 Jun 2014

Well, then 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

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Golden · 01 Jun 2014

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffb8a00e36ae50, 0, fffff8800533f1d8, 7}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal+6c )

Followup: MachineOwner
---------

I see lots of references to DirectX components in the .dmp files. Whilst we wait for Arc, perhaps you could run a Windows Update, and check the Optional updates to see what is offered for download there please.

*** EDit*** I see Arc just replied, please follow his suggestion first.

coldspring · 01 Jun 2014

Hi Arc,

Thanks! I will run the Driver Verifier and report back.

Hi Golden,

Thank you for your suggestions too. Here are files in the optional update list. I will try to update those.

coldspring · 01 Jun 2014

Hi Arc,

I enabled Driver verifier for all non-MS items as you told me and installed all optional Windows update following Golden's suggestion. The computer initially failed to restart after enabling Driver Verifier but a second restart went through. It just experienced the first crash, this time when I tried to wake it up from idle. The error this time however is c9, which I had never experienced before. Again, the restart from the crash failed the first time but succeeded the 2nd time. The SF report is attached.

It will be great if you or others can take a look at it. Much appreciated!

Coldspring

Golden · 01 Jun 2014

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {228, fffff8800657a9d4, fffff9801b2ccb40, 0}

*** WARNING: Unable to verify timestamp for iusb3hub.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3hub.sys
Probably caused by : USBSTOR.SYS ( USBSTOR!USBSTOR_FdoSetPowerD0Completion+0 )

Followup: MachineOwner
---------

Driver Reference Table

Update your Intel USB3.0 hub driver from this site:
https://downloadcenter.intel.com/default.aspx

coldspring · 01 Jun 2014

Here it happened again, still c9 error during idle. SF report is attached.

Thanks!

Coldspring

Golden · 01 Jun 2014

This is the date of that driver from analysis in post #8:

Code:

1: kd> lmvm iusb3hub
start             end                 module name
fffff880`0554e000 fffff880`055ad000   iusb3hub T (no symbols)           
    Loaded symbol image file: iusb3hub.sys
    Image path: \SystemRoot\system32\DRIVERS\iusb3hub.sys
    Image name: iusb3hub.sys
    Timestamp:        Fri Mar 29 23:06:15 2013 (51558ABF)
    CheckSum:         00064C0C
    ImageSize:        0005F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

And this is the date from the very latests dump:

Code:

2: kd> lmvm iusb3hub
start             end                 module name
fffff880`04d58000 fffff880`04db7000   iusb3hub T (no symbols)           
    Loaded symbol image file: iusb3hub.sys
    Image path: \SystemRoot\system32\DRIVERS\iusb3hub.sys
    Image name: iusb3hub.sys
    Timestamp:        Fri Mar 29 23:06:15 2013 (51558ABF)
    CheckSum:         00064C0C
    ImageSize:        0005F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

It appears you never updated the driver. Follow the link I posted earlier, locate your device and driver and post the details here.