BSOD while booting up, bug check code 0x00000050

Hi Gx557 :).

Do you have more dump files?
Please manually check the minidump folder.

Code:

C:\Windows\minidump

If dump files are present in that folder copy them to the Desktop, zip and upload in your next post.

As for the troubleshooting procedure;

Clean your start up procedure:

• Troubleshoot Application Conflicts by Performing a Clean Startup

   Warning

The Following Method Should NOT Be Performed On An SSD!

Please test both HDD's:

1. Perform a Disk Check | Disk Check- Scroll down to OPTION TWO of the tutorial and use the /R switch in the CHKDSK command | chkdsk C: /R.
2. Then Post the Disk Check results following | This Tutorial.
3. Once back in Windows, download Crystal Disk Info and post a screenshot (multiple shots if you have more than one drive).
4. Download SeaTools for DOS if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
5. If SeaTools for DOS is unable to recognize your HDD:
6. Visit HDDdiag and follow the instructions | Or follow the instructions below.

If SeaTools For DOS does not recognize the drive;
Boot into the BIOS using the *Fx key.
Look for an entry called SATA Mode (or something similar), it should be set to IDE / AHCI.
It's probably set to AHCI which is why SeaTools doesn't recognize them in the DOS environment.
Set it to IDE then save and exit usually by pressing the F10 key.
Now boot into SeaTools and it should detect the drives.
Start the Long Test and let it run.
Upon completion don't try to boot into Windows as it will only result in a BSOD, go back into the BIOS
and change the SATA setting back to what it was in the first place.

• *Popular BIOS access keys.

Please enable Driver Verifier:

Arc said:

Your crash dumps are not showing any finite probable cause.

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.

Keep us posted.

OK thanks, please disable DV now.

• Driver Verifier - Enable and Disable

It appears that you have a failing HDD, which one is it?
The OS HDD or a secondary HDD?

I am some what skeptical when it come to software "fixing" the HDD, what it's doing is marking those
sectors as unusable (you will see a storage capacity shrinkage). That will help in the I/O operations
but it doesn't guaranty the rest of the HDD won't deteriorate over time.
Once it starts to develop bad sectors, if you can RMA it I would.

Sorry for the late reply, but yes if you have an image of the system you can use Acronis
to apply it to the new HDD.

Good luck :) .