Home > Enterprise Desktop Tips > Windows desktop management tips > The last resort for troubleshooting hardware resource conflicts
Enterprise Desktop Tips:
EMAIL THIS
 TIPS & NEWSLETTERS TOPICS 

WINDOWS DESKTOP MANAGEMENT TIPS

The last resort for troubleshooting hardware resource conflicts


Brien M. Posey, Contributor
11.26.2007
Rating: -3.60- (out of 5)


Expert advice on Windows-based systems and hardware
Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


Although plug-and-play technology has become fairly reliable as it has matured, in some cases, it still doesn't work perfectly. For example, to this day there are still system boards that contain ISA expansion slots, which allow modern PCs to use legacy devices. Sometimes ISA-based devices can interfere with PCI devices.

Likewise, some x86 system boards use IRQ sharing across two or more PCI slots. Most of the time this arrangement works well, but sometimes conflicts do occur.

If you don't happen to have an ACPI-based system, or a system that allows you to toggle between ACPI and non-ACPI modes, then you may be able to resolve hardware conflicts by manually reallocating hardware resources.

Before you begin – be forewarned

The technique I am about to show you is very similar to a resource allocation technique that used to be common for systems running Windows 95, Windows 98 and Windows ME. While you can generally use this technique without consequence in a Windows 9x or a Windows ME environment, Windows XP is a much more sophisticated operating system. Depending on the change you make, it is possible that you will receive a Blue Screen of Death, citing a STOP: 0x00000079 error.

When this error occurs, it is because the HAL (hardware abstraction layer) no longer matches the machine's hardware configuration. If this happens, you will have to perform a clean Windows installation (an upgrade won't work).

My point is that the following technique should allow you to resolve any hardware resource conflicts, but you must be prepared to install Windows from scratch if necessary.

Resolving hardware conflicts

Generally speaking, you must ensure that each hardware device has both a unique IRQ and memory range. If a hardware device uses a DMA, then that should be unique as well. When resource conflicts occur, typically either one or both of the conflict


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


RELATED CONTENT
Windows desktop management tips
Windows 7 improvements driving enterprise adoption
Mobile Device Manager joins Windows domains to mobile devices
Troubleshooting Microsoft WSUS connectivity issues
Should administrators use hard disk compression?
How to move hard drives and transplant system drives between servers
Combining folder redirection with roaming profiles
IPv6 protocol, Windows Vista features simplify peer ad-hoc networking
Reduce unapproved device driver installs via Group Policy in XP, Vista
Using Reliability and Performance Monitor to gauge system stability
When not to convert basic disks to dynamic disks

Windows XP management
New Enterprise Desktop e-zine
Reduce unapproved device driver installs via Group Policy in XP, Vista
Windows operating system management for the IT pro
Managing single sign-on security burdens in Windows
Why Windows Vista is superior to XP
Creating the Secure Managed Desktop
Managing Windows folders with Redirected Folders
Managing folders inside the Windows documents folder
Identity and Access Management Security School
Regaining lost functionality in the Windows XP Recovery Console

Microsoft Windows hardware, including laptop and notebook reviews
Intel's Moblin raises stakes on netbook OS race
Should administrators use hard disk compression?
How to move hard drives and transplant system drives between servers
Step-by-step guide: Laptop hacking
Step 1: How it can happen
Step 2: How to crack a laptop
Step 4: Laptop security summation
Step 3: How to secure a laptop
Establishing multiple hardware profiles in Windows XP
The Dell Latitude XT: A solid tablet, but at what cost?

RELATED GLOSSARY TERMS
Terms from Whatis.com − the technology online dictionary
XP key changer  (SearchEnterpriseDesktop.com)

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary


ing devices won't work. That being the case, your goal is to eliminate the conflict so that both devices can work. Incidentally, if you don't need both devices, then you can save yourself a whole lot of effort by simply disabling or removing the device that you don't need. To disable a device, simply right click on it in the Device Manager, and select the Disable command from the resulting shortcut menu. When you do, the device will be flagged with a red X, as shown in Figure A.

Figure A
[IMAGE]

If you do need to manually reallocate the resources that a device is using, then right click on the device and select the Properties command from the resulting shortcut menu. When you do, Windows will display the device's properties sheet. Now, select the properties sheet's Resources tab.

As you can see in Figure B, the Resources tab lists the memory range and the IRQ that the device is using. If the device were using a DMA, that would be listed as well.

Figure B
[IMAGE]

At this point, you must deselect the Use Automatic Settings check box. If this check box is not available, then your system probably uses the ACPI HAL, which ignores IRQ assignments that are stored in the firmware.

Now, select the resource that you want to reassign and click the Change Setting button. You will now have the opportunity to assign a different set of resources to the device. Notice the Device Conflict List at the bottom of Figure B. Windows compares the currently selected resources with those used by other devices and lists any conflicts. If any conflicts are listed, then you must choose different resources.

Once you have resolved the conflict, click OK and hope for the best. If you receive a STOP: 0x00000079 error, then it's time to reinstall Windows. Remember, this must be a clean install, not an upgrade.

[TABLE]

Rate this Tip
To rate tips, you must be a member of SearchEnterpriseDesktop.com.
Register now to start rating these tips. Log in if you are already a member.


Submit a Tip




DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.



Enterprise Desktop Security - Virus Protection, Malware Protection, Intrusion Detection
HomeTopicsITKnowledge ExchangeTipsMultimediaWhite PapersBlogs
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Site Map




All Rights Reserved, Copyright 2008 - 2009, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts