Boot Failure Troubleshooting Flowchart

[punisher186]

I searched for a similar thread and found nothing, so I figured I would create this thread as the chart has helped many in the past.

Direct link: http://goo.gl/K5DSt

[Hood]

Very nice, very handy when you're freakin' out 'cause your rig won't boot. Even if you know all this stuff, it always helps to organize your thoughts and proceed logically. Thank you, I will save a copy of this in my "Tools" folder.... no wait, if I can't boot, I can't see the flow chart, I'll have to print a hard copy too in case it's my main rig that won't boot.

[punisher186]

Here is a white version for if you want to print: https://needaguide.files.wordpress.c...3718407951.png let me know how the quality turns out if you decide to make one.

[eidairaman1]

pure and simple, when starting from scratch ensure everything is working properly before installing in the case.

Ya that's a Fault Tree there.

Most Powerup issues are a short/grounding issue with the motherboard, case, pci/pci e expansion (Connects motherboard edge to case via PCI bracket)

Even the IO panel template/shield could cause short/grounding issues)

Powersupply cant provide enough power or just went pop

Rarity would be the powerswitch.

Its funny i never seen such a fault tree before till now. I was already executing most of those troubleshooting procedures for machines i built and new customers

[Hood]

Originally Posted by punisher186

Here is a white version for if you want to print: https://needaguide.files.wordpress.c...3718407951.png let me know how the quality turns out if you decide to make one.

Thank you very much for this, I love stuff like this - knowledge is power, and every day I'm reminded of how little I know and how much more I want to know (at least about computers). I know enough to be thoroughly dangerous, but compared to those who conceive and design and build all these parts, I am retarded. I should have been an electronics engineer, instead I'm a mechanic. I never like math anyway.

[eidairaman1]

Originally Posted by Hood

Thank you very much for this, I love stuff like this - knowledge is power, and every day I'm reminded of how little I know and how much more I want to know (at least about computers). I know enough to be thoroughly dangerous, but compared to those who conceive and design and build all these parts, I am retarded. I should have been an electronics engineer, instead I'm a mechanic. I never like math anyway.

Pickup an ASVAB book, give you general knowledge of electronics.

Engineers are great but they dont know every nuance of how the stuff works or fails for that matter- mechanics, technicians do.

[Jetster]

http://www.fonerbooks.com/pcrepair.htm

[Wrathier]

Thank you guys, nice chart. I have not had one of those since my edu.

Nice to have an updated one again.

[profkefah]

man u r really genius
thank u man

[jaydeee]

this is something!
Thanks for your knowledge.

[eidairaman1]

its funny certain board makers put this chart in the back, not exactly the same but close. Thats another reason i tell people to Read the F***in Manual

[americanlifestyle7]

Just because the operating system won't boot doesn't mean that your hard drive is failing. Hard drive failures are actually pretty rare, unless something jars the laptop while it's working. Most people don't know where to start when faced with a laptop that doesn't start up like usual, which is why I wrote The Laptop Repair Workbook. Starting with an introduction to laptop technology and cost considerations in repairing laptops, it moves onto twelve diagnostic flowcharts with explanatory text, of which the drive problems flowchart below is just one.

[tacosRcool]

Awesome chart!

[Chevalr1c]

Thanks for this, I have put a link to this thread in my signature.

[samuelwilliam]

that's are really a nice work and booting failure are stopped for finding a genuine reasons by understanding the flowchart.