BOOT ISSUE--HELP

[Vilezz]

Issue

My dad's PC will randomly get a boot error(image uploaded) I've reinstalled windows 10 and it did run for a couple of hours on a different PC; however, we got the boot error again after 2 days in the original rig, and it now refuses to boot past the bios at all. I don't really know what to do after this point. 

System Build

• -WD Blue 1tb HDD
• -Corsair CX500 80 plus bronze
• -AMD FX-6300
• Gigabyte GA-78LMT AM3+
• 8 gb ddr3
• TP-Link PCI wireless adapter
• OS- Win 10

[bgibbz]

Do you have another hdd you can use? It may be a drive failure. Also, check ram. You can do this by shifting one stick at a time through each dimm slot and seeing if any configurations do not work. 

[Vilezz]

On 10/18/2016 at 8:29 PM, bgibbz said:

Do you have another hdd you can use? It may be a drive failure. Also, check ram. You can do this by shifting one stick at a time through each dimm slot and seeing if any configurations do not work. 

Thanks for the quick reply, and I'll try another hdd and check the ram when I go over his house this weekend.

 If I still get the same boot error what else should I try? Just trying to save time for when I head over.

[bgibbz]

4 minutes ago, Vilezz said:

Thanks for the quick reply, and I'll try another hdd and check the ram when I go over his house this weekend.

 If I still get the same boot error what else should I try? Just trying to save time for when I head over.

If it isn't hdd or RAM, it could either be Motherboard, GPU, CPU, or PSU.

 

1. PSU - unlikely, as generally a computer wouldn't power on or would frequently power off if the PSU was the issue, and i have never seen a dead PSU result in a failure to boot. 
2. GPU - I assume you are using integrated graphics from your CPU, as you did not mention any discrete graphics when you listed the specs.
3. Motherboard. This is where things get a bit more tricky to check. You can start by resetting the CMOS. See your motherboard manual to find out how to do this.  You can also visibly inspect the board, sometimes you may notice a popped capacitor or a scorch mark in the board. 
4. CPU - I would say CPU is unlikely as your system is able to POST, but it can be possible. If you run all of the above tests and cant determine if any of those is the problem, the CPU is possible. CPUs tend to last longer than motherboards though, so i would replace the Motherboard before i replace the CPU.

As a quick note - before you do any part testing or hardware diagnostics, try booting into a windows installation media disk (or usb drive). The problem could simply be a corrupt part of you operating system. If you can successfully boot into a windows install disk, try running diskpart through the cmd prompt and listing disks, if your drive is not listed than your issue is likely a dead drive. You can also run a troubleshooter through the installation media if the drive is detected, as that may detect and fix any faults in the OS files. 

[Vilezz]

7 minutes ago, bgibbz said:

If it isn't hdd or RAM, it could either be Motherboard, GPU, CPU, or PSU.

 

1. PSU - unlikely, as generally a computer wouldn't power on or would frequently power off if the PSU was the issue, and i have never seen a dead PSU result in a failure to boot. 
2. GPU - I assume you are using integrated graphics from your CPU, as you did not mention any discrete graphics when you listed the specs.
3. Motherboard. This is where things get a bit more tricky to check. You can start by resetting the CMOS. See your motherboard manual to find out how to do this.  You can also visibly inspect the board, sometimes you may notice a popped capacitor or a scorch mark in the board. 
4. CPU - I would say CPU is unlikely as your system is able to POST, but it can be possible. If you run all of the above tests and cant determine if any of those is the problem, the CPU is possible. CPUs tend to last longer than motherboards though, so i would replace the Motherboard before i replace the CPU.

As a quick note - before you do any part testing or hardware diagnostics, try booting into a windows installation media disk (or usb drive). The problem could simply be a corrupt part of you operating system. If you can successfully boot into a windows install disk, try running diskpart through the cmd prompt and listing disks, if your drive is not listed than your issue is likely a dead drive. You can also run a troubleshooter through the installation media if the drive is detected, as that may detect and fix any faults in the OS files. 

Okey dokey. Also, forgot to mention I did try the windows recovery drive, but it didn't stop the issue.