Marvell network interface won't connect to network.

Running ultimate x64. The motherboard I am using has two built-in NICs. The Marvell interface won't connect to the network. Sometimes it will get labeled 'unknown network' and get a 169.***.***.*** address. Sometimes it will actually get assigned an IP in the network but it can't reach the router or the internet. There have been times when the 'network and sharing center' briefly showed 'internet' access when the cable is first plugged in but then it goes back to just connected to network. However, it still can't reach the router or the internet. Looking at Wireshark there seems to be communication with the interface. A couple of differences I noticed between the working interface and this one is that is working are these Wireshark lines (working NIC is 192.168.200.128, NOT working NIC is 192.168.200.130, router is 192.168.200.1)

Working NIC

Code:

301    33.042435000    192.168.200.128    192.168.200.255    BROWSER    243    Host Announcement TOWER, Workstation, Server, NT Workstation, Potential Browser
302    33.096788000    192.168.200.1    192.168.200.255    BROWSER    252    Local Master Announcement RT-N66R, Workstation, Server, Print Queue Server, Xenix Server, NT Workstation, NT Server, Master Browser, Domain Master Browser, DFS server
303    33.099335000    192.168.200.1    192.168.200.255    BROWSER    250    Domain/Workgroup Announcement HOMEOFFICE, NT Workstation, Domain Enum

NON-Working NIC

Code:

286    21.008517000    192.168.200.130    192.168.200.255    BROWSER    230    Browser Election Request
663    60.000148000    192.168.200.130    192.168.200.255    BROWSER    243    Local Master Announcement TOWER, Workstation, Server, NT Workstation, Potential Browser, Master Browser
889    92.542556000    192.168.200.130    192.168.200.255    BROWSER    248    Domain/Workgroup Announcement HOMEOFFICE, NT Workstation, Domain Enum

It looks like when the Marvell is connected the computer is trying to be the 'master' in the network instead of the router.

Are there some areas in the registry that could be corrupted? Is it possible to try the 32-bit version of the Marvell driver? If so, how? If this is hardware damage would I be getting the kind of communication I'm getting? Please help?

Well I found out I am a victim of using 4 gigs of ram screwing up the network card. Has anyone ever found a workaround for this issue?