BSOD on new PC build, error code 50

coldspring · 01 Jun 2014

Hi Golden,

Thanks for the suggestion! It appears that we were posting at the same time. I just updated the USB3.0 driver. The computer crashed again when I tried to restart after the installation. This time I got an error 50. I don't know if the iusb3hub.sys issue caused that, as I suppose the the new driver will take effect after the restart? Or maybe I am really dealing with more than one problem here?

Anyway, I attached the new SF report here (060114-23368-01.dmp). Thanks a lot for spending your time helping me.

Coldspring

Golden · 01 Jun 2014

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff280116e3338, 1, fffff80002edecc4, 7}


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

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

Mmm......it suggests RAM again, but you already tested using MemTest86+ right?

Can you try Driver Verifier again please? What anti-virus software is installed?

coldspring · 01 Jun 2014

Yes, I MemTest86+ was the first test I run after seeing error 50. I think I run it 3 times, each over 8 passes. Should I try one more time? I don't have anti-virus installed yet. In the past I use Microsoft Security Essentials.

Just now my Lightroom crashed again, very similar to what happened in my last Windows installations. It showed that ntdll.dll was faulty. Could it be related?

I will run Driver Verifier again.

Thanks.

Coldspring

Golden · 01 Jun 2014

Mmmm.....one last time of MemTest86+ will be conclusive, although I suspect it won't find errors.

Upload that latests .dmp associated with ndll.dll and lets have a look.

Do you have any devices plugged into the USB3.0 ports?

coldspring · 01 Jun 2014

Hi Golden,

I can try MemTest86+ one more time. It would take me a couple of days to post back.

Windows didn't crash when Lightroom crashed last time. It was only an APPCRASH. Is there any .dmp file for it? I did have a card reader plugged in one of the USB3.0 port when the computer crashed last three times. But the computer crashed before I plugged it in.

I am running Driver Verifier again. Will report back.

Coldspring

Golden · 01 Jun 2014

OK. No, there is no specific .dmp for Lightroom. Lets see what Driver Verifier spits out.

coldspring · 02 Jun 2014

Hi Golden,

It crashed this morning, when I tried to wake it up from sleep. Here is the report. Thanks for looking at it.

Coldspring

Golden · 02 Jun 2014

Aha! Something completely different! I'm going to ask Arc to look at this : he is the master at these.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

*** WARNING: Unable to verify timestamp for iaStorA.sys

Arc · 02 Jun 2014

Hi coldspring.

Make it sure that the SSD is running with the latest firmware.
How to Upgrade Samsung SSD Firmware | StorageReview.com - Storage Reviews

Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

Right click on "my computer" icon and click "manage" on the context menu.
It will open the "computer management" window.
Select "Device Manager" in the left pane, It will list all the existing devices up.
Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
Select one Intel device item under it, right click, uninstall.
Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

Make it sure that the USB3 driver is the Version 2.5.0.19.

Let us know the results.

coldspring · 02 Jun 2014

Hi Arc,

I did what you suggested: upgraded Samsung SSD Firmware with Samsung Magician; uninstalled intel rapid storage; uninstalled intel IDE ATA/ATAPI controller; downgraded USB3 driver to 2.5.0.19.

The computer seemed to entered into a loop. Restart -> request to run Samsung Magician -> reload hard drives -> request to restart computer. The first two rounds of restart didn't go through the first try. After three rounds, I removed Samsung from Windows startup folder. It seemed to break the loop. It hasn't crashed for about 1 hr.

Should I run driver verifier now?

Thank you for your help.

Coldspring