Results 1 to 5 of 5

Thread: Pci Simple Communication Controller Driver

  1. #1
    Join Date
    Mar 2010
    Posts
    54

    Pci Simple Communication Controller Driver

    Hello everyone,

    After installation of the software,I went back via my driver install CD to get the stuff functioning. Everything is going fine except something assumed as PCI Simple Communications Controller.

    It doesn't appear to be affecting anything adversely but I am unable to get any associated information regarding this online. The entire threads, I did so many search have pointed back to Microsoft's Update pages, that I do not yet want to tempt just yet. I have my board is a DQ965GF. Do you have all any suggestions?

  2. #2
    Join Date
    Apr 2008
    Posts
    2,139

    Pci Simple Communication Controller Driver

    Hello all,

    I got the solution of this problem. If you would move to device manager, click on the PCI simple communications controller and then jump for property and get the details. You will get a code such as
    PCI/VEN_8086&DEV_27D8&SUBSYS...

    The VEN code indicates that the vendor and the DEV code means device: in my scenario, the vendor is 8086 and the device is 27D8. Once you get two codes,visit on www.pcidatabase.com. Enter the two codes and you should get the name of your hardware. That is the place where you can find the appropriate driver downloads for your hardware.

  3. #3
    Join Date
    Jan 2008
    Posts
    3,755

    Pci Simple Communication Controller Driver

    Although, different for Toshiba, but worth a shot. The device property :

    PCI\VEN_8086 DEV_3B64...

    Recently,I downgraded a Windows 7 Dell Inspiron 1564 to Win XP Pro for a client and suffering with the same problem. 'PCI Simple Communications Controller' flagged in Dev Mgr turned out to be 'Intel Management Engine Interface' (Intel MEI). After a long searching on the internet, I found a little solution on the web, found a post suggesting Dell package R243176 would have the driver what I needed. Try out this, it was like charm for me...

  4. #4
    Join Date
    May 2008
    Posts
    3,316

    Pci Simple Communication Controller Driver

    OK, that board is another section of Intel's desktop line. Unfortunately I didn't get any Windows Server 2003 compatible drivers for this on Intel's web site, that is likely to be the causes you are getting that error.

    That's how Device Manager presents an unrecognized serial device, which could be any number of things. I don't think, There is any simple method to tell except by using Device Manager with careful manner to see if any of the needed MB devices are missing.

  5. #5
    Join Date
    Apr 2008
    Posts
    4,642

    Pci Simple Communication Controller Driver

    I had a similar scenario that is being discussed when installation of WHS on a system I built to house it.

    In my case, The Gigabit Ethernet Controller required a driver that Windows Server 2003 did not allow at the time of setup. After I executed the driver and software tools CD from my mb, it installed the required driver(s) and WHS properly connected to the router and therefor the Internet, automatically connected to automatic updates and downloaded and installed them.

Similar Threads

  1. Replies: 2
    Last Post: 04-11-2011, 10:23 PM
  2. Replies: 5
    Last Post: 18-03-2011, 10:12 AM
  3. How to get the missing driver for PCI communication controller in Intel DP35DP
    By Perro Justy in forum Motherboard Processor & RAM
    Replies: 4
    Last Post: 15-12-2010, 08:22 AM
  4. windows Xp PCI Communication Controller for fujitsu Siemens driver
    By hospitable85 in forum Windows Software
    Replies: 3
    Last Post: 10-10-2010, 10:43 AM
  5. Driver question -PCI Simple Communications Controller
    By Bailee in forum Windows Software
    Replies: 4
    Last Post: 21-08-2010, 06:30 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,714,027,246.93137 seconds with 16 queries