NEED HELP!!!!!

[red209]

ok here it goes, Last night i dropped my comp and the heatsink fell off and one of the clips that holds it on broke, so i went to fry's and got a new volcano 9 hs and snapped it on...when i boot up my comp the cd roms and hard drives start up but i HEAR NO BEEPS and it only shows "no signal" on my monitor i have a iwill kk266 mobo with a amd 1.6 processor i have stripped my mobo bare and booted it but i get the same problem and it doesnt even show my bios. i have cleared the cmos and it didnt help. was wondering if u guys think my mobo or chip may be fried ..... any ideas would be greaty appreciated . bad thing is i just bought a new radeon 9700 pro and i think ill have to take it back to pay for a new mobo or chip

 

[Zepper]

Boilerplate-01:
. Most frequent causes of failure to boot:
1- RAM, CPU or AGP video card not seated properly, or a bent pin.
2- Drive data cable on upside down or only on half the pins or shifted . a pin or two (usu Floppy or Zip drives).
3- CMOS needs to be cleared (AC power must usually be disconnected or . attempt to clear CMOS may fail) Unless your mobo does not use a power-off CMOS clear - check your mobo manual for specific info.
.bh.
4- On many new mobos there is a CPU protection feature (esp. on Athlon/Socket A mobos) that will not allow the system to start if there is no fan (or a fan without a working speed sensor wire) connected to the fan power connector on the mobo (specifically marked "CPU Fan"). If you tried to start your machine without a fan properly connected, you have to attach a proper and working fan and clear the CMOS before it will boot.

.bh.

 

[amdskip]

What he said but I'm betting the video card and the ram need to be reset on the mobo.

 

[tjaisv]

Definitely sounds like something is either installed improperly or worse yet physically damaged. Either way you'll need to isolate the problem. Get access to another computer's components to try and eliminate the non-functional component in your system. I'd start out by first replacing the mobo with a different one (use the same CPU and all the same cables). If that didn't resolve the problem you'd know that the mobo wasn't the issue. So from there you could move on to another component or group of components (you get the idea) until you finally arrived at the cause.

 

[red209]

dont know if u guys even read my post but i have stripped it bare and it wont start....so as far as isolating the problem its either my mobo or chip

 

[red209]

is there anything else that could keep it from making no beep when it boots???????

 

[tjaisv]

Ok follow these steps:

1)strip your mobo absolutely bare again (disconnect all cables, remove all cards, remove all RAM and remove cpu) and examine both your mobo and cpu closely to see if there any visible signs of damage (the cpu shouldn't be chipped in any way)
2)next, make sure that the mobo is properly grounded to the case. A stand off (plastic peg that isolates the mobo from the case) could have broken off causing the case to make direct contact with the mobo, subsequently preventing your comp from posting
3)next, reinstall your cpu (don't install the cpu heatsink or fan) and connect just the power supply cable to the mobo; don't install anything else (not even your vid card or RAM).
4)now start the computer. If you hear ANY beeps, that's a good sign as it means your cpu and mobo are probably ok; and you can go ahead and install your other components one by one until you encounter your beepless-boot problem, in which case you'll have then found your malfunctioning component. But if you don't hear ANY beeps, that almost definitely means either your cpu or mobo is dead; you wont know for sure which one it is unless you use another functioning cpu or mobo to isolate.

I'm guessing you might of shorted something out in your mobo when u dropped it, or your cpu was damaged somehow when the heatsink fell off. Another possibility would be damaged RAM, but if it was just that then you should at least be getting some kind of error beeps on post. Check out this thread another guy had almost the same problem you're having.