BSOD during startup, 0x00000050

[arj123]

Hi there, Ive had my PC for a few years now and for the last year during the startup I get a BSOD, and the error is 0x00000050, and I took a screenshot of the screen too. Any help? Not sure if its a faulty RAM, as I can't remember changing it lol. Any help would be appreciated. Thanks.

PS. its an HP if that helps!

 

[Arc]

Can you boot to windows, even in safe mode? If so, Post it following the Blue Screen of Death (BSOD) Posting Instructions.

If not, Follow it:
Troubleshooting Windows 7 Failure to Start

 

[arj123]

Sorry it's a bit late but I've figured out that it has something to do with a USB as the PC works fine when there isn't anything plugged into the USB ports at the front of the PC...and when u plug a USB in the front, the PC ends up showing the same blue screen of death...and ideas on how to fix the front USB ports?

 

[Arc]

It is difficult to frame any idea without seeing the necessary data.

 

[arj123]

Ok i will try to get the data

 

[arj123]

Hi there I've been a bit busy for the past few days however I noticed that for the first step there's 3 options - complete, kernel and small memory dump...which one should I use?

 

[Arc]

Option 2, point 2. Small memory dump (minidump).

 

[arj123]

Hi there, I managed to do the BSOD Mini Dump and I've attached the .zip file, what are my next steps. Thanks, appreciate it.

 

[Arc]

First of all, do it: How to Revert the Win7 1394ohci.sys to the Legacy Driver

Next, do some hardware tests like ....

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.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results. Will be needed to take further actions depending on the the results.
__________________________________________________________________________________________

BugCheck 50, {830b7d38, 1, 820f2ef6, 0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+9baf1 )

Followup: MachineOwner
--------------------------------------------------------------------------------------
BugCheck BE, {807c6938, 676121, 9ca63bf4, b}

Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+dc )

Followup: MachineOwner
--------------------------------------------------------------------------------------
BugCheck A, {39dd2fa, 2, 1, 8206ff6b}

Probably caused by : hardware ( nt! ?? ::LBKOJDO::`string'+b )

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

 

[arj123]

Ok I will do that...what did the BSOD posting I attached return?

 

[Arc]

The suggestions are based on that.

 

[arj123]

Okay thanks I'll try what you suggested but I'm realizing now that the blue screen will come up randomly...will something happen of the blue screen turns up while doing one of the tests?

 

[Arc]

Okay thanks I'll try what you suggested but I'm realizing now that the blue screen will come up randomly...will something happen of the blue screen turns up while doing one of the tests?

Nothing bad will happen, but those may be important to analyze.

 

[arj123]

Hi there, I've gotten some good/bad news!

I did the first thing that you suggested and I did the memory test using the Bootable USB file...so I let it run, and after about 2 hours, it had 2 passes, and then all of a sudden the whole bottom of the screen started filling with errors, and it kept going...the error count was increasing very rapidly and it ended up reaching about 160 000 errors at which point I turned off my PC as I didn't know how long that would last...I took 2 pictures about 5 seconds apart and you can see just how many errors showed up however it seems to indicate the same amount of space each time (2xxx mb)...do you know what the problem is from this test? I've attached the 2 pictures.

Thanks for all your help so far!

 

[Arc]

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

 

[arj123]

So if I have 4 RAM sticks and 4 slots essentially I would have to run memtest a maximum of 16 times? And when u say get a result, do u mean that I just keep letting memtest run until it returns results?

 

[Arc]

If you want to avoid all those workload, replace your RAMs with new ones. If those also give the same issue, think about the motherboard.

This test is time consuming, but worthy at the end.

 

[arj123]

Ok, so am I right to say this:
If I take all the RAMs out and put one of them in the first slot, and run memtest and it comes out fine and then it comes out fine for the rest of the slots, then that means that the slots are fine, and the problem is one of the other RAMs right?

 

[Arc]

Ok, so am I right to say this:
If I take all the RAMs out and put one of them in the first slot, and run memtest and it comes out fine and then it comes out fine for the rest of the slots, then that means that the slots are fine, and the problem is one of the other RAMs right?

Right.

 

[arj123]

And also if I did find out that it wasn't the slots, could I just put one of the other RAMs into the PC and run memtest and if there's an error it means it's the RAM stick? And do this for the remaining RAMs if it comes out ok?