• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

A8N SLI Premium

R

RoosterKooster

Member
I took Thursday off. Yesterday I arrived at work, fired up Thunderbird and noticed my inbox was stuck at late Wednesday afternoon. No new emails would download. I use IMAP and suspected something strange with the configuration. After several attempts of blowing away my profile, uninstalling, deleting all traces of TBird in the registry I was stumped. Several were stumped.

I don't do viruses! 🙂 In addition to Thunderbird, ad-aware se was unable to successfully install its definition update file. It couldn't read the downloaded file. I downloaded the trial of Avast Server virus scanner. It failed to run successfully. I installed Symantec Corporate client. It could not update the definitions. Downloaded them fine - just couldn't read them.

I was worried. WTF is going on. My IT guy got stinger onto a floppy and we ran that. Drive "C" appeared ok or at least not hindered by the small number of viruses Stinger scans for.

Suddenly, a Ford moment. Out of the IT guy came - "try the other interface". Ok, disabled the NVidia port (lower one) and cleared the TCP-IP configuration. Then, enabled and configured the marvel interface. Viola. Ad-aware updates fine. Was able to copy avast anti-virus from another computer and run it.

This system is less than 2 weeks old. I am running v6.66 of the NVisia drivers and bios 1006.

Monday I'll see if the drivers became hosed or if the port is flakey.

Anyoen experience any similar network interface issues with the A8N?

Thanks,
 
i've had problems with the network interface on the a8n, but i had problems with the marvell port acting all flaky until i started using the generic driver on marvells website. I never install the nvidia firewall because i've had problems with that in the past, so if u have that enabled and installed that would be the first thing i would check.
 
Originally posted by: dball3
I've had problems with the network interface on the a8n, but I had problems with the marvell port acting all flaky until i started using the generic driver on marvells website. I never install the nvidia firewall because i've had problems with that in the past, so if u have that enabled and installed that would be the first thing i would check.
Click to expand...

Initially the marvel yukon interface was working just fine. After some undetermined period, my system had just frozen and left quite similar in appearance to what bad hardware drivers (video cards especially) will often exhibit. The screen was frozen. keyboard and mouse inputs were ineffective. Keyboard state keys were toggling the leds.

This happened twice. This morning I googled and found a reference to bad marvel yukon driver. I downloaded the newest driver and updated the drivers on the affected system. We'll see what happens.

Hardforum thread about Marvel yukon driver problem

Marvel Yukon Driver Info

Newest Marvel Yukon Driver D/L

FWIW, my NVidia interface seems to be totally hosed. I tried new drivers and old drivers. I still have corrupt files downloaded using that interface and UltraVNC can't stay connected. I have uninstalled that interface and disabled in the bios.

Has anyone seen similar behavior with their A8N SLI Premium/Deluxe ?
 
Almost sounds like a Resource conflict.

Have you checked this:

Open Device Manager, select "View" on the Menu bar, and "Resources by Connection".

Check your IRQ's, specifically check the one your NIC is using, and see if any PCI devices are using the same one. If so, you may need to move the PCI card to another slot.

I had this problem with my Sound Card (PCI) and Video (PCIEX) sharing the same IRQ. Caused Stuttering/Freezing and other odd behavior. Moved to another PCI slot and different IRQ - problems solved 🙂

 
It's not a resource conflict. I do not have an PCI cards in use. Everything is onboard except the PCI-Express card.

Apparently, the newest Marvel Yukon driver fixed the lockup problem.
 
ActiveArmor and Network Access manager are not running/installed.

I use a static IP. I am properly configured for pri and sec dns servers.

I renstalled the 6.66 drivers and 1007 bios a while ago.

The friggin Wan Miniport (IP) #2 bang in device manager is a drag. I am not certain what caused that to appear but it won't go away and attempts to update the driver fail because it can't successfully load an associated (unspecified) driver.

Windows sucks! Asus sucks!
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top