something is Horribly Wrong with christmas build, PLEASE HELP !!

Page 3 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

GuitarDaddy

Lifer
Nov 9, 2004
11,465
1
0
Try putting the Asus disk in and booting up while holding down F2.

And plug in some speakers if you haven't already
 

VINMAN

Senior member
Oct 13, 1999
433
0
0
done speakers, but its not even getting to the Keyboard, no lights flash on it or anything
 

digitalbooyah

Member
Aug 29, 2004
25
0
0
Have you plugged in the PC speaker? At least if you got a certain amount of beeps that could help...

but you're right, you NEED spare parts at this point to narrow it down.
 

VINMAN

Senior member
Oct 13, 1999
433
0
0
no pc speaker, case doesnt have one, dont know if there is one on the MB? will check the manual again
 

Pez D Spencer

Banned
Nov 22, 2005
401
0
0
Im guessing ESD damage. Id say that the board got fried during the installation of the floppy drive when everything quit working. Were you taking proper ESD precautions? An ESD shock that you can actually feel is around 30,000 volts. It only takes 3000 to fry something so even if you dont feel it its still very possible to fry something.
 

Doctorweir

Golden Member
Sep 20, 2000
1,689
0
0
Just to make a final one on the EZ_Plug and end the discussion:
EZ_PLUG is an Asus-concept to supply additional power to the PCIe ports.
This is intended to enhance stability of SLI-Setups.
If you only have one card, it is not neccessary to plug it (but des not hurt either ;)).
Any standard Molex connector from the PSU will do.

PC speaker should not be necessary, speech reporter tells you through the front speakers what's up.
I would start removing everything...CPU, RAM, Vid...everything! and fire up the board. See (or better hear) if speech reporter works. Also try Guitar Daddy's suggestion with the emergency boot. The Asus Mobo CD will boot even with corrupted BIOS and restore it..

Good luck.
 

crazylegs

Senior member
Sep 30, 2005
779
0
71
think they just about covered everything....

sounds like a nightmare to me your in big time need of some crappy old spares to help you fault test!

good luck buddy... she'll be a beauty once shes up n running :)
 

InfiniteLurker

Senior member
Mar 3, 2004
235
1
81
Originally posted by: rnp614
btw once its fixed you'll definitely be happy you didnt get a dell. I'm sure glad that I didnt and I went through hell to get my system to boot properly...so much so that even though the bios is now updated i'm scared to get a dual core for it might not work!

:disgust:

Picking the parts one by one and building your own computer that works is a great experience - IF you are prepared for these type of issues. If you don't mind or possibly enjoy tweaking, and troubleshooting and re-tweaking, building is the way to go. If you want a working 'out-of-the-box' stable solution and aren't looking for a bleeding edge configuration or an Alienware pricetag, Dell is a great and can-be-cheap solution. My Dell that I had before I built my Celeron 300 overclocked to 450 (those were the days) machine way back is still pluggin' away. Of course, I'm not going to be playing Half-Life 2 on it though... :)

Just some thoughts from the non-hate-everything-Dell camp.


 

Lasthitlarry

Senior member
Feb 24, 2005
775
0
0
I heard that motherboard has issues, your part selection has to be just right, and the motherboard actually increases the vcore by like .625 or something, which COULD potentially fry the cpu.

From what it sounds like you have a power issue, somehow your video card isn't working.

Since you cannot use other parts to test, I would say bring it to a local computer shop.

Can you think of anything you did while installing the floppy drive?

PS: Those wires are a big mess, hard to tell anything from those pics.
 

imported_electron

Senior member
Nov 6, 2005
427
0
0
First off I admit to not reading the whole thread, I'm pressed for time, but I had that "You're system is not ACPI compliant" problem once and after replacing jus tthe motherboard the problem was fixed. Hope that helps.