Device conflict between Intel SMBus controller 27DA and (Standard system
devices)
DeviceDesc System board ACPI\PNP0C01\3
Conflict I/O = Minimum Address: 0x000010c0 Maximum Address: 0x000010df
This was almost impossible to find because there are not any System
indications of the conflict. Running MSINFO32 Shows the conflict but does not
list it as a problem in the Conflict part of the report. No Dr Watson, no
event logs, and no BSOD. However for a year I have lost 3 dvd drives and
6month old 9 Vt Battery. The OEM decieded against my wishes to change out the
hard drive and the motherboard. I was never able to load the WinDbg Symbols
from the ser only load them as custom. from DDK CD. I had several very
strange problems with software that was more kernal base such as Acronis
Diskkeeper, Acronis 9.1 Backup Software, System Mechanic Pro. and serveral
Windows programs I downloaded to test the system until I just gave up and
started reading every text log, Inf file, and finnally every part of the
Device Driver Manager. That was when I discovered the conflict. Unlike most
systems, this on has 4 System Board devices ACPIPNP0C01/1 ACPIPNP0C01/2 THEN
3 AND 4. It was the ACPIPNP0C01/3 which recorded the conflict with the Intel
ICH7 SMBus Controller and viesa versa. After several months of reaserch I
found a Document at http://www.acpi.info/. This clearly outlines the need
for Microsoft, Intel, Phoniex, and the OEMs to put a better architecture. My
Laptop was exchanged last week it now has a T7200 2GB RAM and 120GB HD with
Vista Ultimate. However the conflict is still there. Because this articale
include 5 OEMs I went to several cumputer stores that I work with and the
managers let me go through each of the laptop device manager and do a print
screen and download my findings to a USB. The other OEMS had memory
conflicts in the PCI bus but not anything like issues on my system. However
from what I can see this is related to the BIOS coding and the Intel Moble
Chipset. I have a very good program that I ran which gives an Advanced Reg
Comparison for both devices and it is very clear that half of one device is
missing and half of the other device is missing. My problem is that the OEM
will not take me seriously to let me talk to a software engineer or even pass
the information on. Microsoft and Intel want nothing to do with it and every
time I try so send someone who would know what I should do or at least get
the into to the right person I can not do that because the Advanced Reg
Comparison only runs an extration for .reg and .reg hive, not a text file.
So I had to use Print Screen to get a copy of it. I have yet to find anyone
in the OEM or Microsoft that will allow the bitmap to be transfered by email.
I understand why but I don't know what to do next. I don't want to make
this public I don't think that would be fair pactice. But I have found so
many systems that are like this I know it must be effecting the customer
relations and the techs who have to handle calls that don't know what to do
because no one knows about this issue. What do you suggest I do? Please
email mail with some kind of answer even if you don't have a good one. At
least I will know you took the time to read this. My whole purpose is to
make these systems work this is not personal. I own my software and hardware
repair business so I have many more computers than most people. Oh one more
item I found. This is not happening on any laptop to uses AMD. Nor have I
found any Desktops running the Core 2 Duo aor Core Duo with any of these
issues.
--
Student of the eternal learning process of Windows.