The PROBLEMS...
Ok, it's been up and running for a week now. I have been enjoying a 100mbps connection (over my 50mbps wireless I used previously). And have been gaming the hell out of Half-Life 2 Ep 1. I am getting really great framerates with this one. 150's and higher at max resolution and 8xAA). I plan on breaking the rig with Crysis next week.
I did have problem when putting this monster together. They were minor issues in my mind, but in fairness , I am posting them so maybe someone else will learn from my mistakes.
1. The first problem I had was during posting. I did NOT post succesfully the first time. (many people do not) My error was of the " I have been at this for HOURS and I am too tired to think straight even with this sugar and caffine coursing through my veins" variety of error. I was getting a 7F error (FDD Error). I checked all the cables, spend alot of time switching out cables. Cried a little (just kidding). Finally I woke the hell up and actually looked closer at my bios.
Well since I do not HAVE a 3.5 inch floppy drive , and the bios said I did, the 'puter was looking for it and telling me, "Hey Goober, wheres the drive?" After about 45 minutes of wasted time I changed the bios so no 3.5 was to be "looked for". Learn Grasshoppers from the stupidity of men.
2. After that debacle, I had another drive issue. My WD 750 Caviar was making a "clicking sound" every time it was accessed. (I know, oh crap). Well, I thought I was smart by putting th OS on 1 drive and everything else on the other. So when the drive did actually fail (and it did a day later) not big deal right? WRONG. I put some NVIDIA program needed at boot on the second drive I never figured it out but it had something to do with Nvidia networking. I tried everything I could find on the web about it. I even got thisd error after completely removing the defective drive.
NVIDIA BOOT AGENT 231.0528
PXE-E61: MEDIA TEST FAILURE, CHECK CABLE
PXE-M0F: EXITING NVIDIA BOOT AGENT
Anyway because this was on the failing drive I could not start windows (not even in safe mode It would not go past boot. SOOOOOO I had to re-install windows from the get go. GEEz. ( also had to call Microsoft to get a new keycode cuz I have installed the one I had over 5 times). WD is sending a new HD to me now. Its a cross shipment so I am not too entirely pissed although there goes another half a day. I is important to remember that with all these components its likely you will get 1 bad one. Thankfully the bad one I had was not critical to finishing the build. My 250GB is a Seagate Barracuda if anyone is taking notes.
(no its not loaded)
3. Zalman installed the wrong way. Remove, clean arctic silver off with prebought cleaner and surface pre treat (YAH!), reseat cooler ,NP 15 minutes. Blame it on the caffine and nerves....(BTW, this is the WRONG WAY...)
This is the right way...
4. WHY THE HELL DOES MY ETHERNET CONNECTION NOT WORK. OK this pissed me off. I could not get my TE adapter to connect. I had the system running fine on a wireless connection so how come when I attach the cable I get nothing? ARRRRGGG. Well a quick call the EVGA and we tested the ports by routing a ethernet wire from one port to the other , green light , hardware is good. Checked the ethenet adapter with a ping CMD, its working, so whats the hassle?
( a quick side note, EVGA should be considered in every build for no other reason than they are excellent in customer support, I have called the numerous times and I always speak with a competent , clear speaking (English is first language) , helpful person. And hold times are reasonable. add that they now have 24/7 support and its a no brainer. For fun call ASUS and ask thier customer support a simple question , you will get a stupid answer. Ask me about the time I asked if the new MOBO could support tri-SLI, its a funny story)
Anyway after hours of playing with my network settings, I fixed it. This again was something I should have done right off. I HAD reinstalled the latest drivers off EVGA website , but I failed to do something every NOOB forgets. I REINSTALLED THE DRIVERS OVER THE EXISITING ONES!. DOOH!. Well after realizing what a stupid mistake I was making, I UNINSTALLED THE DEVICE, THEN REINSTALLED THE LATEST DRIVERS AND VIOLA! WORKING ETHERNET..........OH WELL.
4. The final problem occured during the latest updates I am making. These are purely cosmetic changes (going U/V , cable wraps, decals you know the artistic fun stuff all first time builders go overboard with) suggestions welcome!
Anyway I used a different molex cable to attach my case fans power with. It was shorter and neater. BUt then on power up the fans would barley spin. Sometimes I even had to push them!. Well turns out the cable was not the 4 pin variety but only a 3 pin. So there was not enough power for the fans. I figured this one out in about 3 minutes, but it still counts a a mistake.
Thought this was Funny. Its the mess I have to clean up. I got all this out before my network problems, I INTENDED to wire up the room nice and neat, so much for that. Look intimidating, but its not. Cable ties are your best friend.
The next post will come in about a week. This will show the final build ( I hope) After I have had a chance to make it PURDY (pretty). I have about 50 bucks in "fancy schmancy do-dads" coming today or tommorrow. So hang tight , you get first looksees in a few more days.
Coming next.....
THE FINAL PRODUCT
Log in to comment