BSOD on new PC build, error code 50

[Golden]

See if it stays stable for a while first.

 

[Arc]

Hi Arc,
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.

Well done! It should not be there in startup.

Should I run driver verifier now?

Do as golden suggested. See how it works after applying the changes.

See if it stays stable for a while first.

 

[coldspring]

Hi Arc and Golden,

Here is an update. I am happy to report that the computer has been stable after I did what you told me to, no single crash. But I noticed something. First, in Device Manager, there are several new entries under IDE ATA/ATAPI controllers, labeled as ATA Channel 0-5. They weren't there before. To clarify, I have three more HDDs installed. Second, it became very slow to open some file types (such as JPEG) on my network drive. It can take tens of minutes to open a image file of 200K but a movie file of 1 GB opens instantly. It also takes a looooong time to copy any file from the NAS to my local HDD. What is going on here? Is there any fix for it?

The computer also seems a little bit slow. But it's just my impression and I don't have accurate measurement.

So I guess the problem was really caused by the SSD and software conflict, right? This computer was built based on the suggestion of a well known hardware website. I assume a lot of people have done the same thing. I imagine they would have run into the same trouble. Do you think there is any hardware problem?

Thanks!

Chun

 

[coldspring]

Hi Arc and Golden,

The funny thing is it crashed again just a few minutes after I posted the update. This time the error code was a. While I was writing this report, Firefox crashed, and it won't even restart. I eventually had to open it in Safe Mode. In my previous Windows installations, Firefox also crashed very often. So I guess it was still a similar problem.

Again, I attached the SF report here. I hope you could find some information.

Thanks,

Coldspring

 

[Golden]

Looks like an Intel video driver problem.

fffff800`00b9c8e8  fffff880`04dba668Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR="Red"]igdkmd64.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
 igdkmd64+0xf7668

Driver Reference Table

Please follow link and check for an updated driver.

 

[Arc]

Intel® HD Graphics 4600: Intel® Iris™ and HD graphics Driver for Windows* 7

 

[coldspring]

I updated the Intel graphics drivers. But the computer still crashes. It happened when I tried to wake it up from sleep. Again, the SF report is attached.

Thanks!

 

[Arc]

Disable Driver Verifier. http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Does the BSODs continue? Let us know.

 

[coldspring]

Hi Arc,

Yes, BSOD still continues. You can find the minidump files in my previous post. Do you think the crashes were caused by Driver Verifier? The last time I check it, Driver Verifier wasn't enabled for most of the drivers.

Coldspring

 

[Arc]

I checked the last file before posting, obviously.

It said that the BSOD was caused by USBSTOR.sys, and pointing to be the Intel XHCI driver is failing. Golden pointed to the same a few days ago, and you replied in post #11 that you updated it. So, at this point, it may be assigned as a driver verifier caused BSOD. But it will be accepted as a fact only after seeing any further crash dumps with DV disabled.

If you get any further BSOD after disabling DV, let us see.

 

[coldspring]

Just a quick update. I have disabled driver verifier. It has been two days and the computer is still running fine. I will use it a little longer and report back. But so far it has been looking good. Thanks for all the help.

Coldspring

 

[Arc]

OK mate. Take the time necessary for observing the situation.

 

[coldspring]

Hi Arc and Golden,

Sorry for not updating for so long. I have been busy with work and didn't get much time on my computer. I have turned on the computer occasionally. From what I can tell, it is much more stable after I did what you suggested. Today I had some time to process some photos, and the computer crashed again, when I was doing some computing and memory heavy editing. Like before, the report is attached. It will be great if you could take a look.

Thanks a lot!

Chun

 

[coldspring]

One more crash, also during photo editing. Can it be a hardware problem?

 

[Arc]

It is still blaming the memory.

BugCheck 50, {fffffb40020bbfc0, 0, fffff80002eb3ea5, 7}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+49d )

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

If you are sure that RAM is not failing, you may enable driver verifier for one more time.

mobo?
​