Did I break it?

[Guest]

I have an AthlonXP 1600+ (unlocked) running at 11.5 X 133 for 1533Mhz...

Only problem is that after unlocking it and testing different speeds to see what it would run at, my NIC (built-in to Dragon+ mobo) no longer works properly.

When connected to the 10/100 router, I have no link light and a "network cable disconnected" message in windows. When plugged into my 10mbps hub, it works fine and connects to the network.

During the speed adjustments, I set the fsb as high as 140mhz, only a 7mhz jump, could this have partly fried the NIC?

There are no conflicts in device manager, the correct driver is installed, I've flashed the bios. I stuck another nic in it which works fine and have tested all the ports on the router.

It appears the problem is definitely the onboard nic...the flashing lights on the router and absence of a link light occur whether the system is on or off...

Any ideas?

 

[Guest]

Nah dont think so. Bought a 1700+XP from o/c uk and some crucial cas2.5 p2100 ram and my systems currently at 1600mhz.
I cranked the fsb to 166MHZ and it really didnt like it, no suprise really and it wouldnt even load to the bios with some nice colours on the screen too.
So I reset the cmos and started again and here I am.
So I dont think thats your problem.
Is your system cool enought? Have you recently downloaded a new driver ?
I had a similar problem once when I installed an aupdated driver for my 3com card so I reverted back to the original driver and it works no problem know!
Just gonna get some copper heat sinks for my ram and put a blow hole in and I reckon I can get the FSB to 155 and it`ll still be stable.Well ive got an article with the fastest benchmarks for 3dmark for the kg7 and this guys running his machine at 175FSB.Step by step instructions too so anyone could do it!
Spacerider


Ah,thank God for the CMOS RESET!

 

[labdog]

rollback your system to its "standard" previous conditions.
if the nic works, it's not crashed.

i don't know if you do this but you have to raise the vCore of your cpu when you oc it. else this can invole strange randomly crashes anywere on your system.

finaly, built-on onbard components arent often of very good quality & could not support oc.


if you know you don't know, the way could be more easy.

 

[Guest]

Thanks for the replies...I tried everything I could think of...new drivers, flashed the bios, reset the cmos and nothing worked...

And although I had the system overclocked, I had set the fsb back to 133 after I unlocked the chip, so it didn't make sense why the nic wasn't working at 133 when it had worked at 140...

Well, I just unplugged everything to see if maybe a wire was bent or missing in the rj45 plug...and then tried it one last time and it works!!!

(I had called SOYO and been told to exchange it with the distributor for a new board, but since that requires taking it all apart again and then driving an hour into virginia, I wanted to see if I could fix it)

So anyway, now my question is WTF? Why does it work now? And should I still get a new board?

The only thing that could have "fixed" it was unplugging the psu and that doesn't seem real scientific to me...

Thanks again

 

[phsstpok]

Take a close look at where the motherboard standoffs are located. Make sure all of them mate up with mounting holes on the motherboard. A stray standoff can cause intermittent shorts.

<b>We are all beta testers!</b>

 

[Guest]

It's the overclocking...don't know why the NIC is getting funny now at 133 fsb when it ran fine at 140...only difference now is the unlocked multiplier on the cpu...

I was able to reproduce the problem and solution, so I'm almost positive that's the problem. Thanks

 

[labdog]

you have to pay attention to RJ45 connectors.
they have weak contacts & can give you easily short-cuts.
i already was obligated to cut the RJ45 connector & replace it properly with another one for some lan cables to fix the pb.

so i think your pb is your RJ45 cable (especialy if it's an 8 wires cable).
you have just to buy another good quality one.


if you know you don't know, the way could be more easy.

 

[labdog]

this is because i talk about short-cuts on RJ45 connectors & cables


if you know you don't know, the way could be more easy.

 

[Ncogneto]

When connected to the 10/100 router, I have no link light and a "network cable disconnected" message in windows. When plugged into my 10mbps hub, it works fine and connects to the network.

lapdog is right. It is not your motherboard, the problem either lies with in the router or the cable. The fact that it worked on your 10 mb/s hub should have been a tell tale sign. Replace the cable, if this doesn't work look closely for bent pins on the hub.

It's not what they tell you, its what they don't tell you!