how exactly do you pinpoint a problem?

[Saucz]

I know that i have a problem with my build but how can i figure what the problem is? I know i'm supposed to install the ram video, cpu and heatsink. But that's already 4 variables there. If there is a problem with the mobo, no matter what it is, does it not post?

 

[FghtinIrshNvrDi]

you describe what you have, what you've done, and the symptoms in the Hardware troubleshooting forum. I mean, here is good too, but searching the troubleshooting forum may lend more results.

Ryan

 

[æArchOAngelæ]

to pinpoint problems it takes time, but when you put so much money into the computer youll take the time to test everything, running programs prime helps. and checking your drivers and stuff like that also if its a hardware problem bios beeps help, my mobo has a little lcd display that tells me =)

 

[Nitestick]

look up diagnostic flowcharts. in diagnosing a pc you basically work by elimination. you do one thing to see what sort of outcome that gives and based on that information you can get closer to the answer

 

[FghtinIrshNvrDi]

I like to disassemble the entire computer down to the Power supply, motherboard, processor and ram. Start adding components one at a time, and when it no longer works, you know what piece is causing the problem. I actually had a 10/100 lan card preventing a computer from booting. Don't ask, I don't know.

Ryan

 

[Nitestick]

i've had the same problem with a lan card. basically anything can be suspect in a pc. of course some things are far more likely than others but don't rule anything out. you must eliminate possible causes one by one