I/O Port or Memory Address Conflicts in Windows NT

 Last reviewed: August 22, 1995
Article ID: Q135346
The information in this article applies to:
  • Microsoft Windows NT Server versions 3.5 and 3.51
  • Microsoft Windows NT Workstation versions 3.5 and 3.51

SYMPTOMS

When you remove a driver for a PCI device, keep the device enabled in the computer BIOS, and add another PCI device, Windows NT may assign the same I/O port or memory address used by the previous device driver to the new PCI device driver.

CAUSE

When a new PCI device driver requests an I/O port or memory address, Windows NT does not check for unused addresses. The I/O port or memory address usage in Windows NT is registered through the device drivers.

WORKAROUND

To work around this problem, do one of the following before adding the new PCI device:

  • Disable the device using the same I/O port or memory address in the computer BIOS.
  • Physically remove the device from the computer.
  • Add the device driver back (this registers the I/O port or memory address in Windows NT).

STATUS

Microsoft has confirmed this to be a problem in Windows NT versions 3.5 and 3.51. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbenv kbbug3.50 kbbug3.51
KBSubcategory: ntconfig
Additional reference words: prodnt 3.50 3.51 logon lock hang

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: August 22, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.