MAC transmit FIFO under-run

I've got a Vista Business x64 desktop with a Mavell Yukon ethernet adapter.  I have the latest WHQL drivers from Marvell however my NIC suffers from reoccuring MAC transmit FIFO under-run errors and crashes.  The only way to fix the problem is to reboot or do a repair of the connection, and problem seems to occur more frequently when i'm using remoting into my desktop, it almost never happens when i'm on it, but only after i disconnect.  Is there a driver setting i can change that will eliminate this error?

It generates a system event id of 93 from source yukon64 which i identify as the driver for the NIC.

LVL 9
maninblac1Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

bbrunningCommented:
I've got an onboard marvell yukon 10/100/1000 on my mobo that constantly shuts off too unless I disable/re-enable or just reboot.

I solved the problem by buying another PCI network adapter and use that instead. I think the marvells aren't programmed well for vista yet...most likely a driver problem.
0
KenneniahCommented:
Hmm haven't had any issues with mine (Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller).
I'm just using the built-in Vista drivers, haven't installed anything from Marvell.
0
kane77573Commented:
I would just put a pci NIC in there.
In my personal exp and corp envionment, Marvells are the worst NICs this IT dept has ever seen.
Always have problems with them.
I would personally disable it in the bios and pop a simple PCI nic in
0
maninblac1Author Commented:
It appears that i've identified the source of the problems.  It's a combination of bad drivers(i've updated), and a bad network connection.  Contacted the information fabric here, they report carrier sense errors in the local subnet switch, i had my machine hooked up through a shady passthrough switch (never had any problems with it till now), but it seems like bypassing the switch has resolved the issue.

I'd forgotten that that switch was back there, never thought to check.
0
Computer101Commented:
PAQed with points refunded (250)

Computer101
EE Admin
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
System Utilities

From novice to tech pro — start learning today.