Solved

MAC transmit FIFO under-run

Posted on 2007-03-24
6
2,370 Views
Last Modified: 2013-12-01
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.

0
Comment
Question by:maninblac1
6 Comments
 
LVL 10

Expert Comment

by:bbrunning
ID: 18787451
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
 
LVL 24

Expert Comment

by:Kenneniah
ID: 18802504
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
 
LVL 6

Expert Comment

by:kane77573
ID: 18817444
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
 
LVL 9

Author Comment

by:maninblac1
ID: 18948005
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
 
LVL 1

Accepted Solution

by:
Computer101 earned 0 total points
ID: 18970653
PAQed with points refunded (250)

Computer101
EE Admin
0

Featured Post

How to improve team productivity

Quip adds documents, spreadsheets, and tasklists to your Slack experience
- Elevate ideas to Quip docs
- Share Quip docs in Slack
- Get notified of changes to your docs
- Available on iOS/Android/Desktop/Web
- Online/Offline

Join & Write a Comment

In this article we have discussed the manual scenarios to recover data from Windows 10 through some backup and recovery tools which are offered by it.
NTFS file system has been developed by Microsoft that is widely used by Windows NT operating system and its advanced versions. It is the mostly used over FAT file system as it provides superior features like reliability, security, storage, efficienc…
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

706 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now