Network Controller driver

[mattmag]

On my new Gigabyte GA-965P-S3 motherboard, the integrated network controller chip seems to be destroying Windows. I don't use the chip, and I don't want a "no cable connected" icon in my system tray. But when i disable the chip in device manager, the computer refuses to boot Windows correctly and begins destroying itself to a point where the only thing i can think to do is restore a backup of my hard drive created with Gigabyte Express Recovery 2. What can I do to get this thing to go away without destroying my computer?

[timberwolf]

"I don't want a "no cable connected" icon in my system tray".  Let's say you want to leave it alone, but take it out of your task tray.  Open up Network out of your Control Panel.  Select that adapter (The on-board is a Marvell 8056 Gigabit LAN Controller) Select it, and go to properties.  Uncheck the "display when not connected" check box.

Another way would be to uninstall it in Windows, then disable it in BIOS.  There's a way in BIOS to disable the integrated network controller.   To get into it, press Delete as soon as the computer boots.  Go into the Integrated Perphials part of BIOS, and disable the Onboard H/W LAN.  I'm going by page 36 in the manual.  

The 11 Mb English edition can be had here:
http://www.gigabyte.com.tw/Support/Motherboard/Manual_Model.aspx?ClassValue=Motherboard&ProductID=2321&ProductName=GA-965P-S3

For network connectivity, you can use an add-in PCI card instead.  I would recommend a 3Com brand NIC.
 
Also, I note that there's been three revisions to that board's BIOS since 7/20/2006.  Two of which deal with memory fixes.  You may want to see what version you are running.  

[mattmag]

Thanks for your reply.

When I disable it in BIOS, I get the same problem. Also, I have the F4 bios, the newest revision available at Gigabyte's website. I'm using a Belkin wireless card for network connectivity, but I would like to have my ethernet controller working but disabled.

[ale52]

You might go to Gigabytes website and see if this is a "known problem" & see if there is a fix.

You'd think with the latest BIOS you'd be OK...but you never know  :-?

Alan <><  

[GX1_Man]

Some motherboards will not work correctly unless the onboard NIC is disabled if you arfe using a wireless PCI card.  

[mattmag]

well, technically the problem isnt actually harming my computer's performance, but it just worries me that its acting so strangely. i can connect to the internet with my wireless card (im using this computer right now), but i just dont like the fact that something on my brand new fairly expensive computer isnt working. I'd like to have my network controller enabled in bios but disabled in windows so that i can enable it occasionally when i need a wired connection.

[2k_dummy]

A NIC cannot fully initialize unless it is connected. Connect it to the router and reboot. Then go into device manager and select it properties and "disable in this profile". Reboot again and you should be able to disconnect it with no problem. You can plug it in and go to device manager and enable any time you choose.

[timberwolf]

well, technically the problem isnt actually harming my computer's performance, but it just worries me that its acting so strangely. i can connect to the internet with my wireless card (im using this computer right now), but i just dont like the fact that something on my brand new fairly expensive computer isnt working. I'd like to have my network controller enabled in bios but disabled in windows so that i can enable it occasionally when i need a wired connection.

This is doable.  Windows XP?  Enable the onboard NIC in BIOS.  After the computer boots, you should be able to select the adapter, right click and pick "disable".  I'm still puzzled by your original post that card was destroying windows.  How so ?

[mattmag]

yeah, this is exactly what i tried because i had this configuration on my previous computer. however, doing so causes windows to freeze up and upon rebooting i get various error messages such as:

"Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM"
"NTLDR is missing"
and if these messages do not appear and windows actually does start, i get messages about various dlls and then it freezes.

it seems like a very odd reason for all this to happen, but i have tried it numerous times and by just leaving it alone it has been fine for over a week, so im entirely sure that its the cause. i would like to fix it, though.