Hardware Resource Conflict (Code 12). It means Windows is trying to assign memory or interrupt requests (IRQ) to your network card, but those specific “addresses” are already being used by another piece of hardware or reserved by the BIOS.

Given that the VIA Rhine III is a legacy network adapter (popular in the late 90s/early 2000s), this is most common on older systems or when using older hardware on newer motherboards.

Here is the step-by-step troubleshooting guide to fix this, ordered from the easiest solution to the most involved.

1. Uninstall and Re-detect the Device (Most Common Fix)

Force Windows to forget the current resource allocation and try again from scratch.

1. Right-click the Start button and select Device Manager.
2. Expand Network adapters.
3. Right-click the VIA Rhine III Compatible Fast Ethernet Adapter.
4. Select Uninstall device. (If asked, check “Delete the driver software for this device” if available).
5. Restart your computer.
6. Upon reboot, Windows will detect the hardware as “new” and attempt to assign free resources automatically.

2. Adjust BIOS Settings (Crucial for Older Hardware)

Since this is an older PCI card, the BIOS often holds onto resources that Windows needs.

1. Restart your computer and enter the BIOS/UEFI Setup (usually by pressing Del, F2, or F10 during boot).
2. Look for a menu named PnP/PCI Configuration or Advanced.
3. Find the setting “PnP OS Installed”.
   • If you are running Windows XP or newer, set this to Yes (or Enabled).
   • If you are running Windows 98/ME, set this to No.
4. Look for a setting called “Reset Configuration Data” or “Clear ESCD”. Set this to Enabled. (This forces the BIOS to forget old hardware assignments).
5. Look for ACPI Settings. Try toggling ACPI support (Enable/Disable) to see if it frees up IRQs.
6. Save and Exit the BIOS.

3. Move the Network Card to a Different Slot

On older motherboards, PCI slots often share IRQ lines. If the slot you are using shares an IRQ with a device that cannot be moved (like USB or Video), you will get a Code 12 error.

1. Power down the PC and unplug it.
2. Open the case.
3. Remove the VIA Network Card.
4. Insert it into a different PCI slot.
5. Boot up and check Device Manager.

4. Disable Unused Legacy Ports

If your system is low on resources (common in older BIOS versions), you can free up IRQs by disabling hardware you aren’t using.

1. Enter the BIOS Setup.
2. Go to Integrated Peripherals or I/O Device Configuration.
3. Disable any of the following if you do not use them:
   • COM Ports (Serial Ports)
   • LPT Port (Parallel/Printer Port)
   • Game Port
   • Floppy Disk Controller
4. Save and Exit.

5. Update or Change Drivers

The generic Windows driver might be reporting resources incorrectly.

1. Go to Device Manager > Right-click the VIA Adapter > Update Driver.
2. Select Browse my computer for drivers.
3. Select Let me pick from a list of available drivers.
4. If you see multiple versions of the VIA Rhine driver, try selecting a different one (e.g., if you are on a 64-bit system, ensure you aren’t forcing a 32-bit legacy driver, or vice versa).
5. Note: Since this card is vintage, official drivers are hard to find. If you are on Windows 10/11, you may need to use the “VIA Vinyl” driver package or run the driver in Compatibility Mode for Windows XP.

6. The “Nuclear Option”: Clear CMOS

If the BIOS resource table is corrupted, clearing the CMOS will reset all hardware settings to factory default.

1. Power down and unplug the PC.
2. Locate the CMOS battery (a silver coin cell) on the motherboard.
3. Remove the battery for 5 minutes, then put it back in.
4. Alternatively, use the CLR_CMOS jumper on the motherboard if available.
5. Boot up (you will need to re-enter BIOS to set your time/date) and let Windows re-detect all hardware.

A Note on Compatibility

If you are trying to use this VIA Rhine III card on a modern computer (Windows 10 or 11):

• Voltage Mismatch: Older PCI cards use 5V signaling. Newer motherboards often only support 3.3V. If the card is physically compatible but electrically mismatched, it can cause resource errors.
• Driver Support: Microsoft dropped support for this chipset years ago. If the steps above do not work, the hardware may simply be too old for your current operating system. You may need to purchase a modern Gigabit Ethernet PCIe adapter (they are very cheap) to replace it.