none
Trouble with Texas Instruments IEEE 1394 bus host controller

    Question

  • I have a SX38P2 Pro Shuttle PC with Windows 7 RTM installed, and I'm experiencing an odd problem with the onboard IEEE 1394 controller. I don't have any firewire devices attached to the PC (it has one mini-connector on front and a regular size on in the back), but the entry for the host controller itself looks REALLY strange in Device Manager. There are 4 entries for "IEEE 1394 Controller" showing up under an "Other devices" node, and 28(!) "Texas Instruments 1394 OHCI Compliant Host Controller" entries showing up under a "IEEE 1394 Bus host controllers" node. If I view by connection, all 32 entries show under Intel(R) 82801 PCI Bridge - 244E.

    The four "Other devices" entries all have a status of "No drivers are installed for this device" and give the location as PCI bus 4, device 28, 29, 30 and 31. Under resources it says "This device isn't using any resources because it has a problem"

    The 28 other entries show with one of 3 errors:
    Device 0 through 9 show code 12 (This device cannot find enough free resources that it can use)
    Device 10 shows code 10 (This device cannot start)
    Device 11-27 show code 31 (This device is not working properly because Windows cannot load the drivers required for this device)

    All of these 28 show the driver as "Texas Instruments 1394 OHCI Compliant Host Controller". Driver provider = Microsoft, Driver date = 6/21/2006, Driver version = 6.1.7600.16385, Digital Signer = Microsoft Windows. Driver details contain one file, 1394ohci.sys.

    This is driving me crazy since everything else on my Win7 installation is working so well. Any clues as what could be wrong and how to fix it would be greatly appreciated, and I will happily supply any additional troubleshooting information.

    Sunday, September 6, 2009 11:55 PM

Answers

  • Hi hecatol,

     

    You can try to run Windows Update to scan for updates. Make sure that the “Recommended updates” box in Windows Update->Change settings is chosen. Then click Check for updates, if the drivers for IEEE 1394 controllers are listed, please install them.

     

    If there is no proper driver, please have a look at the link below:

     

    Texas Instruments OHCI Compliant IEEE 1394 Host Controller driver

    Since the driver is for Windows XP, I suggest you install it in Windows XP compatible mode.

     

    Good luck.


    Cecilia Zhou
    Tuesday, September 8, 2009 8:20 AM
  • hecatol,
    The device is specifically listed in the Shuttle specs. Viewing the device at TI here would lead me to believe that the drivers may be altered from standards for the specific application of the integration of the device.

    In other words, try installing the Shuttle chipset Vista drivers, here,  which may include what is needed to resolve the issue. Then apply the Intel update.

    ASUS P4PE-P4 Extreme 3.4gHz-2gb G.Skill PC3200-XPSP3:55gb-Win7RC:17gb-DATA:500gb-ASUS N6800GT
    Tuesday, September 8, 2009 10:51 AM

All replies

  • Please look at the details tab in device manager, and post the hardware ID's and the compat ID's for a few of these devices please.
    Want to know if your hardware will work on Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Microsoft Logo'd Hardware List**
    Monday, September 7, 2009 12:30 AM
  • All 32 entries show the same HW and Compat ID groupings, regardless of the state/error code in device manager:

    HW IDs:
    PCI\VEN_104C&DEV_8023&SUBSYS_51061297&REV_00
    PCI\VEN_104C&DEV_8023&SUBSYS_51061297
    PCI\VEN_104C&DEV_8023&CC_0C0010
    PCI\VEN_104C&DEV_8023&CC_0C00

    Compat IDs:
    PCI\VEN_104C&DEV_8023&REV_00
    PCI\VEN_104C&DEV_8023
    PCI\VEN_104C&CC_0C0010
    PCI\VEN_104C&CC_0C00
    PCI\VEN_104C
    PCI\CC_0C0010
    PCI\CC_0C00
    Monday, September 7, 2009 4:43 AM
  • Wow, this is very weird!

    Please try uninstalling each of these nodes.  When you get the last one uninstalled, reboot your PC.  (Normally you don't have to reboot to reinstall drivers, but you're also getting a resource allocation issue.  When the PC restarts and all of these devices get reinstalled, hopefully that will resolve this).

    Have you installed any other drivers on this machine besides the ones that came with Windows 7?

    What other software have you installed?


    Want to know if your hardware will work on Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Microsoft Logo'd Hardware List**
    Monday, September 7, 2009 4:49 AM
  • I uninstalled all 32 instances and rebooted, then let the PC sit for a bit to see if the new hardware wiz would kick off. It hasn't so far, and in Device Manager I now show only one instance, listed under IEEE 1394 Bus host controllers. It is identified as "Texas Instruments 1394 OHCI Compliant Host Controller" with a yellow bang. Device status shows a code 10, this device cannot start, and the location is PCI bus 4, device 10, function 0. That location, device 10, was the only one that showed with a Code 10 even when I had all the 32 instances listed. HW/Compat IDs are the same as before:

    PCI\VEN_104C&DEV_8023&SUBSYS_51061297&REV_00
    PCI\VEN_104C&DEV_8023&SUBSYS_51061297
    PCI\VEN_104C&DEV_8023&CC_0C0010
    PCI\VEN_104C&DEV_8023&CC_0C00

    PCI\VEN_104C&DEV_8023&REV_00
    PCI\VEN_104C&DEV_8023
    PCI\VEN_104C&CC_0C0010
    PCI\VEN_104C&CC_0C00
    PCI\VEN_104C
    PCI\CC_0C0010
    PCI\CC_0C00

    It is a pretty clean machine - I did a fresh Win7 RTM install, adding Office 2007 Enterprise, Live Mesh, the Windows Live suite, Skype and the Zune desktop client. That's it. Last night, in an attempt to troubleshoot this, I did run the latest Intel's Chipset Device Software (infinst911autol.exe) but it didn't appear to make any difference.

    The only other potential oddity - and I think this is just my poor understanding of the intricacies of HID - is that I have two entries under keyboards - both named "HID Keyboard Device",  three entries under mice - all named "HID-compliant mouse", and A LOT of entries under the Human Interface Devices grouping (9 x HID-compliant consumer control device, 2 x HID-compliant device, 4 x USB input device). In terms of actual physical hardware, I have one keyboard, one mouse, a LifeCam, a smart card reader, speakers and a printer.

    Thanks for looking at this!
    Monday, September 7, 2009 5:12 AM
  • Please go to c:\Windows\inf\setupapi.dev.log.  Go to the bottom of the log, and scroll up.  Please copy all of the sections with a timestamp from today and paste them here.

    The HID thing having multiple devices is pretty normal.  The "normal" keys appear as one device, and the "special" keys (like power, calculator or keys that launch apps) appear as one or more nodes.  If you view "by connection" in device manager, you can see which devices are associated with each of those HID instances.

    Want to know if your hardware will work on Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Microsoft Logo'd Hardware List**
    Monday, September 7, 2009 5:23 AM
  • The entries with a timestamp from today actually amount to 1.5 MB of text, several thousand lines! Is there a sensible subset I could extract?
    Monday, September 7, 2009 5:36 AM
  • This is the last boot session, from after I uninstalled the devices manually an hour ago:

    [Boot Session: 2009/09/06 21:55:33.375]

    >>>  [Device Install (Hardware initiated) - pci\ven_104c&dev_8023&subsys_51061297&rev_00\4&3b662b29&0&50f0]
    >>>  Section start 2009/09/06 21:56:03.389
         ump: Creating Install Process: DrvInst.exe 21:56:03.389
         ndv: Retrieving device info...
         ndv: Setting device parameters...
         ndv: Searching just Driver Store...
         dvi: {Build Driver List} 21:56:03.592
         dvi:      Searching for hardware ID(s):
         dvi:           pci\ven_104c&dev_8023&subsys_51061297&rev_00
         dvi:           pci\ven_104c&dev_8023&subsys_51061297
         dvi:           pci\ven_104c&dev_8023&cc_0c0010
         dvi:           pci\ven_104c&dev_8023&cc_0c00
         dvi:      Searching for compatible ID(s):
         dvi:           pci\ven_104c&dev_8023&rev_00
         dvi:           pci\ven_104c&dev_8023
         dvi:           pci\ven_104c&cc_0c0010
         dvi:           pci\ven_104c&cc_0c00
         dvi:           pci\ven_104c
         dvi:           pci\cc_0c0010
         dvi:           pci\cc_0c00
         cpy:      Policy is set to make all digital signatures equal.
         dvi:      Enumerating INFs from path list 'C:\Windows\INF'
         inf:      Opened PNF: 'C:\Windows\System32\DriverStore\FileRepository\1394.inf_x86_neutral_3fdff0af299d9ddf\1394.inf' ([strings.0409])
         dvi:      Created Driver Node:
         dvi:           HardwareID   - PCI\CC_0C0010
         dvi:           InfName      - C:\Windows\System32\DriverStore\FileRepository\1394.inf_x86_neutral_3fdff0af299d9ddf\1394.inf
         dvi:           DevDesc      - 1394 OHCI Compliant Host Controller
         dvi:           DrvDesc      - 1394 OHCI Compliant Host Controller
         dvi:           Provider     - Microsoft
         dvi:           Mfg          - 1394 OHCI Compliant Host Controller
         dvi:           ModelsSec    - Generic.NTx86
         dvi:           InstallSec   - Generic.Install
         dvi:           ActualSec    - Generic.Install.NT
         dvi:           Rank         - 0x00ff2005
         dvi:           Signer       - Microsoft Windows
         dvi:           Signer Score - INBOX
         dvi:           DrvDate      - 06/21/2006
         dvi:           Version      - 6.1.7600.16385
         dvi:      Created Driver Node:
         dvi:           HardwareID   - PCI\CC_0C0010
         dvi:           InfName      - C:\Windows\System32\DriverStore\FileRepository\1394.inf_x86_neutral_3fdff0af299d9ddf\1394.inf
         dvi:           DevDesc      - 1394 OHCI Compliant Host Controller (Legacy)
         dvi:           DrvDesc      - 1394 OHCI Compliant Host Controller (Legacy)
         dvi:           Provider     - Microsoft
         dvi:           Mfg          - 1394 OHCI Compliant Host Controller (Legacy)
         dvi:           ModelsSec    - Legacy.NTx86
         dvi:           InstallSec   - Legacy.Install
         dvi:           ActualSec    - Legacy.Install.NT
         dvi:           Rank         - 0x00ff2005
         dvi:           Signer       - Microsoft Windows
         dvi:           Signer Score - INBOX
         dvi:           DrvDate      - 06/21/2006
         dvi:           Version      - 6.1.7600.16385
         dvi:      Created Driver Node:
         dvi:           HardwareID   - PCI\VEN_104C&CC_0C0010
         dvi:           InfName      - C:\Windows\System32\DriverStore\FileRepository\1394.inf_x86_neutral_3fdff0af299d9ddf\1394.inf
         dvi:           DevDesc      - Texas Instruments 1394 OHCI Compliant Host Controller
         dvi:           DrvDesc      - Texas Instruments 1394 OHCI Compliant Host Controller
         dvi:           Provider     - Microsoft
         dvi:           Mfg          - Texas Instruments
         dvi:           ModelsSec    - TI.NTx86
         dvi:           InstallSec   - Generic.Install
         dvi:           ActualSec    - Generic.Install.NT
         dvi:           Rank         - 0x00ff2002
         dvi:           Signer       - Microsoft Windows
         dvi:           Signer Score - INBOX
         dvi:           DrvDate      - 06/21/2006
         dvi:           Version      - 6.1.7600.16385
         inf:      Searched 1 potential matches in published INF directory
         inf:      Searched 35 INFs in directory: 'C:\Windows\INF'
         dvi: {Build Driver List - exit(0x00000000)} 21:56:14.106
         ndv: Selecting best match from just Driver Store...
         dvi: {DIF_SELECTBESTCOMPATDRV} 21:56:14.106
         dvi:      No class installer for 'IEEE 1394 Controller'
         dvi:      No CoInstallers found
         dvi:      Default installer: Enter 21:56:14.122
         dvi:           {Select Best Driver}
         dvi:                Selected driver installs from section [Generic.Install] in 'c:\windows\system32\driverstore\filerepository\1394.inf_x86_neutral_3fdff0af299d9ddf\1394.inf'.
         dvi:                Class GUID of device remains: {6bdd1fc1-810f-11d0-bec7-08002be2092f}.
         dvi:                Set selected driver complete.
         dvi:                Selected:
         dvi:                     Description - [Texas Instruments 1394 OHCI Compliant Host Controller]
         dvi:                     InfFile     - [c:\windows\system32\driverstore\filerepository\1394.inf_x86_neutral_3fdff0af299d9ddf\1394.inf]
         dvi:                     Section     - [Generic.Install]
         dvi:                     Signer      - [Microsoft Windows]
         dvi:                     Rank        - [0x00ff2002]
         dvi:           {Select Best Driver - exit(0x00000000)}
         dvi:      Default installer: Exit
         dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 21:56:14.122
         inf: Opened PNF: 'C:\Windows\INF\1394.inf' ([strings.0409])
         ndv: Searching Windows Update for drivers... 21:56:14.372
         inf: Opened PNF: 'C:\Windows\INF\1394.inf' ([strings.0409])
         ndv: Acquired WU search serialization mutex. 21:56:14.372
         ndv: About to release WU search serialization mutex. 21:56:26.701
         ndv: No driver found on Windows Update. 21:56:26.701
         ndv: Searching Driver Store and Device Path...
         dvi: {Build Driver List} 21:56:26.701
         dvi:      Searching for hardware ID(s):
         dvi:           pci\ven_104c&dev_8023&subsys_51061297&rev_00
         dvi:           pci\ven_104c&dev_8023&subsys_51061297
         dvi:           pci\ven_104c&dev_8023&cc_0c0010
         dvi:           pci\ven_104c&dev_8023&cc_0c00
         dvi:      Searching for compatible ID(s):
         dvi:           pci\ven_104c&dev_8023&rev_00
         dvi:           pci\ven_104c&dev_8023
         dvi:           pci\ven_104c&cc_0c0010
         dvi:           pci\ven_104c&cc_0c00
         dvi:           pci\ven_104c
         dvi:           pci\cc_0c0010
         dvi:           pci\cc_0c00
         cpy:      Policy is set to make all digital signatures equal.
         dvi:      Enumerating INFs from path list 'C:\Windows\inf'
         inf:      Opened PNF: 'C:\Windows\System32\DriverStore\FileRepository\1394.inf_x86_neutral_3fdff0af299d9ddf\1394.inf' ([strings.0409])
         dvi:      Created Driver Node:
         dvi:           HardwareID   - PCI\CC_0C0010
         dvi:           InfName      - C:\Windows\System32\DriverStore\FileRepository\1394.inf_x86_neutral_3fdff0af299d9ddf\1394.inf
         dvi:           DevDesc      - 1394 OHCI Compliant Host Controller
         dvi:           DrvDesc      - 1394 OHCI Compliant Host Controller
         dvi:           Provider     - Microsoft
         dvi:           Mfg          - 1394 OHCI Compliant Host Controller
         dvi:           ModelsSec    - Generic.NTx86
         dvi:           InstallSec   - Generic.Install
         dvi:           ActualSec    - Generic.Install.NT
         dvi:           Rank         - 0x00ff2005
         dvi:           Signer       - Microsoft Windows
         dvi:           Signer Score - INBOX
         dvi:           DrvDate      - 06/21/2006
         dvi:           Version      - 6.1.7600.16385
         dvi:      Created Driver Node:
         dvi:           HardwareID   - PCI\CC_0C0010
         dvi:           InfName      - C:\Windows\System32\DriverStore\FileRepository\1394.inf_x86_neutral_3fdff0af299d9ddf\1394.inf
         dvi:           DevDesc      - 1394 OHCI Compliant Host Controller (Legacy)
         dvi:           DrvDesc      - 1394 OHCI Compliant Host Controller (Legacy)
         dvi:           Provider     - Microsoft
         dvi:           Mfg          - 1394 OHCI Compliant Host Controller (Legacy)
         dvi:           ModelsSec    - Legacy.NTx86
         dvi:           InstallSec   - Legacy.Install
         dvi:           ActualSec    - Legacy.Install.NT
         dvi:           Rank         - 0x00ff2005
         dvi:           Signer       - Microsoft Windows
         dvi:           Signer Score - INBOX
         dvi:           DrvDate      - 06/21/2006
         dvi:           Version      - 6.1.7600.16385
         dvi:      Created Driver Node:
         dvi:           HardwareID   - PCI\VEN_104C&CC_0C0010
         dvi:           InfName      - C:\Windows\System32\DriverStore\FileRepository\1394.inf_x86_neutral_3fdff0af299d9ddf\1394.inf
         dvi:           DevDesc      - Texas Instruments 1394 OHCI Compliant Host Controller
         dvi:           DrvDesc      - Texas Instruments 1394 OHCI Compliant Host Controller
         dvi:           Provider     - Microsoft
         dvi:           Mfg          - Texas Instruments
         dvi:           ModelsSec    - TI.NTx86
         dvi:           InstallSec   - Generic.Install
         dvi:           ActualSec    - Generic.Install.NT
         dvi:           Rank         - 0x00ff2002
         dvi:           Signer       - Microsoft Windows
         dvi:           Signer Score - INBOX
         dvi:           DrvDate      - 06/21/2006
         dvi:           Version      - 6.1.7600.16385
         inf:      Searched 1 potential matches in published INF directory
         inf:      Searched 35 INFs in directory: 'C:\Windows\inf'
         dvi: {Build Driver List - exit(0x00000000)} 21:56:26.873
         ndv: Selecting best match from Driver Store (including Device Path)...
         dvi: {DIF_SELECTBESTCOMPATDRV} 21:56:26.888
         dvi:      No class installer for 'Texas Instruments 1394 OHCI Compliant Host Controller'
         dvi:      Default installer: Enter 21:56:26.888
         dvi:           {Select Best Driver}
         dvi:                Selected driver installs from section [Generic.Install] in 'c:\windows\system32\driverstore\filerepository\1394.inf_x86_neutral_3fdff0af299d9ddf\1394.inf'.
         dvi:                Class GUID of device remains: {6bdd1fc1-810f-11d0-bec7-08002be2092f}.
         dvi:                Set selected driver complete.
         dvi:                Selected:
         dvi:                     Description - [Texas Instruments 1394 OHCI Compliant Host Controller]
         dvi:                     InfFile     - [c:\windows\system32\driverstore\filerepository\1394.inf_x86_neutral_3fdff0af299d9ddf\1394.inf]
         dvi:                     Section     - [Generic.Install]
         dvi:                     Signer      - [Microsoft Windows]
         dvi:                     Rank        - [0x00ff2002]
         dvi:           {Select Best Driver - exit(0x00000000)}
         dvi:      Default installer: Exit
         dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 21:56:26.888
         inf: {SetupCopyOEMInf: C:\Windows\INF\1394.inf} 21:56:26.888
         inf:      Driver Store location: C:\Windows\System32\DriverStore\FileRepository\1394.inf_x86_neutral_3fdff0af299d9ddf\1394.inf
         inf:      Published Inf Path: C:\Windows\INF\1394.inf
         inf: {SetupCopyOEMInf exit (0x00000050)} 21:56:26.888
         dvi: Searching for hardware ID(s):
         dvi:      pci\ven_104c&dev_8023&subsys_51061297&rev_00
         dvi:      pci\ven_104c&dev_8023&subsys_51061297
         dvi:      pci\ven_104c&dev_8023&cc_0c0010
         dvi:      pci\ven_104c&dev_8023&cc_0c00
         dvi: Searching for compatible ID(s):
         dvi:      pci\ven_104c&dev_8023&rev_00
         dvi:      pci\ven_104c&dev_8023
         dvi:      pci\ven_104c&cc_0c0010
         dvi:      pci\ven_104c&cc_0c00
         dvi:      pci\ven_104c
         dvi:      pci\cc_0c0010
         dvi:      pci\cc_0c00
         inf: Opened PNF: 'C:\Windows\System32\DriverStore\FileRepository\1394.inf_x86_neutral_3fdff0af299d9ddf\1394.inf' ([strings.0409])
         dvi: Selected driver installs from section [Generic.Install] in 'c:\windows\system32\driverstore\filerepository\1394.inf_x86_neutral_3fdff0af299d9ddf\1394.inf'.
         dvi: Class GUID of device remains: {6bdd1fc1-810f-11d0-bec7-08002be2092f}.
         dvi: Set selected driver complete.
         ndv: Driver selected, now performing install...
         ndv: {Core Device Install} 21:56:26.888
         inf:      Opened PNF: 'C:\Windows\INF\1394.inf' ([strings.0409])
         inf:      Opened PNF: 'C:\Windows\INF\1394.inf' ([strings.0409])
         dvi:      {DIF_ALLOW_INSTALL} 21:56:26.904
         dvi:           No class installer for 'Texas Instruments 1394 OHCI Compliant Host Controller'
         dvi:           Default installer: Enter 21:56:26.904
         dvi:           Default installer: Exit
         dvi:      {DIF_ALLOW_INSTALL - exit(0xe000020e)} 21:56:26.904
         ndv:      Installing files...
         dvi:      {DIF_INSTALLDEVICEFILES} 21:56:26.904
         dvi:           No class installer for 'Texas Instruments 1394 OHCI Compliant Host Controller'
         dvi:           Default installer: Enter 21:56:26.904
         dvi:                {Install FILES}
         inf:                     Opened PNF: 'c:\windows\system32\driverstore\filerepository\1394.inf_x86_neutral_3fdff0af299d9ddf\1394.inf' ([strings.0409])
         inf:                     {Install Inf Section [Generic.Install.NT]}
         inf:                          CopyFiles=Generic.CopyFiles  (1394.inf line 61)
         flq:                          CopyFiles from an inbox inf.
         cpy:                          Open PnpLockdownPolicy: Err=2. This is OK. Use LockDownPolicyDefault
         flq:                          QueueSingleCopy...
         flq:                          Inf     : 'c:\windows\system32\driverstore\filerepository\1394.inf_x86_neutral_3fdff0af299d9ddf\1394.inf'
         flq:                          SourceInf: 'c:\windows\system32\driverstore\filerepository\1394.inf_x86_neutral_3fdff0af299d9ddf\1394.inf'
         flq:                          SourceSection: [sourcedisksfiles]
         flq:                          Source root path based on SourceInf
         flq:                          SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\1394.inf_x86_neutral_3fdff0af299d9ddf'
         flq:                          {FILE_QUEUE_COPY}
         flq:                               CopyStyle      - 0x09000000
         flq:                               {FILE_QUEUE_COPY}
         flq:                                    CopyStyle      - 0x09000000
         flq:                                    SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\1394.inf_x86_neutral_3fdff0af299d9ddf'
         flq:                                    SourceFilename - '1394ohci.sys'
         flq:                                    TargetDirectory- 'C:\Windows\system32\DRIVERS'
         flq:                                    TargetFilename - '1394ohci.sys'
         flq:                                    SourceDesc     - 'windows cd'
         flq:                               {FILE_QUEUE_COPY exit(0x00000000)}
         flq:                          {FILE_QUEUE_COPY exit(0x00000000)}
         inf:                     {Install Inf Section [Generic.Install.NT] exit (0x00000000)}
         dvi:                     Processing co-installer registration section [Generic.Install.NT.CoInstallers].
         inf:                     {Install Inf Section [Generic.Install.NT.CoInstallers]}
         inf:                     {Install Inf Section [Generic.Install.NT.CoInstallers] exit (0x00000000)}
         dvi:                     Co-installers registered.
         dvi:                     {Install INTERFACES}
         dvi:                          Installing section [Generic.Install.NT.Interfaces]
         dvi:                     {Install INTERFACES exit 00000000}
         dvi:                {Install FILES exit (0x00000000)}
         dvi:           Default installer: Exit
         dvi:      {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 21:56:26.920
         ndv:      Pruning file queue...
         dvi:      {_SCAN_FILE_QUEUE}
         flq:           ScanQ flags=620
         flq:                SPQ_SCAN_PRUNE_COPY_QUEUE
         flq:                SPQ_SCAN_FILE_COMPARISON
         flq:                SPQ_SCAN_ACTIVATE_DRP
         flq:           ScanQ number of copy nodes=1
         flq:           File 'C:\Windows\system32\DRIVERS\1394ohci.sys' pruned from copy.
         sig:           Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-Common-Drivers-Package~31bf3856ad364e35~x86~~6.1.7600.16385.cat'.
         cpy:           DrpSetRegFileProt 'C:\Windows\system32\DRIVERS\1394ohci.sys' Status=0 Class=Inbox Windows protected
         flq:           ScanQ action=200 DoPruning=32
         flq:           ScanQ end Validity flags=620 CopyNodes=0
         dvi:      {_SCAN_FILE_QUEUE exit(0, 0x00000000)}
         ndv:      Committing file queue...
         flq:      {_commit_file_queue}
         flq:           CommitQ DelNodes=0 RenNodes=0 CopyNodes=0
         flq:           CommitQ early exit: No nodes are queued
         flq:      {_commit_file_queue exit OK}
         ndv:      Registering CoInstallers...
         dvi:      {DIF_REGISTER_COINSTALLERS} 21:56:27.278
         dvi:           No class installer for 'Texas Instruments 1394 OHCI Compliant Host Controller'
         dvi:           Default installer: Enter 21:56:27.278
         inf:                Opened PNF: 'c:\windows\system32\driverstore\filerepository\1394.inf_x86_neutral_3fdff0af299d9ddf\1394.inf' ([strings.0409])
         inf:                {Install Inf Section [Generic.Install.NT.CoInstallers]}
         inf:                {Install Inf Section [Generic.Install.NT.CoInstallers] exit (0x00000000)}
         dvi:                Co-installers registered.
         dvi:           Default installer: Exit
         dvi:      {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 21:56:27.278
         ndv:      Installing interfaces...
         dvi:      {DIF_INSTALLINTERFACES} 21:56:27.278
         dvi:           No class installer for 'Texas Instruments 1394 OHCI Compliant Host Controller'
         dvi:           No CoInstallers found
         dvi:           Default installer: Enter 21:56:27.278
         dvi:                {Install INTERFACES}
         inf:                     Opened PNF: 'c:\windows\system32\driverstore\filerepository\1394.inf_x86_neutral_3fdff0af299d9ddf\1394.inf' ([strings.0409])
         dvi:                     Installing section [Generic.Install.NT.Interfaces]
         dvi:                {Install INTERFACES exit 00000000}
         dvi:           Default installer: Exit
         dvi:      {DIF_INSTALLINTERFACES - exit(0x00000000)} 21:56:27.278
         ndv:      Installing device...
         dvi:      {DIF_INSTALLDEVICE} 21:56:27.278
         dvi:           No class installer for 'Texas Instruments 1394 OHCI Compliant Host Controller'
         dvi:           Default installer: Enter 21:56:27.278
         dvi:                {Install DEVICE}
         inf:                     Opened PNF: 'c:\windows\system32\driverstore\filerepository\1394.inf_x86_neutral_3fdff0af299d9ddf\1394.inf' ([strings.0409])
         dvi:                     Processing Registry/Property directives...
         inf:                     {Install Inf Section [Generic.Install.NT]}
         inf:                     {Install Inf Section [Generic.Install.NT] exit (0x00000000)}
         inf:                     {Install Inf Section [Generic.Install.NT.Hw]}
         inf:                          AddReg=WDF.Registration  (1394.inf line 64)
         inf:                     {Install Inf Section [Generic.Install.NT.Hw] exit (0x00000000)}
         dvi:                     {Writing Device Properties}
         dvi:                          Provider name=Microsoft
         dvi:                          DriverDate 06/21/2006
         dvi:                          DriverVersion=6.1.7600.16385
         dvi:                          Class name=1394
         dvi:                          Manufacturer=Texas Instruments
         dvi:                          Matching DeviceID=pci\ven_104c&cc_0c0010
         dvi:                          Strong Name=1394.inf:TI.NTx86:Generic.Install:6.1.7600.16385:pci\ven_104c&cc_0c0010
         dvi:                     {Writing Device Properties - Complete}
         inf:                     {Install Inf Section [Generic.Install.NT.Services]}
         inf:                          AddService=1394ohci,2,Generic.AddService  (1394.inf line 70)
         inf:                          ServiceType=1  (1394.inf line 74)
         inf:                          StartType=3  (1394.inf line 75)
         inf:                          ErrorControl=1  (1394.inf line 76)
         inf:                          ServiceBinary=C:\Windows\system32\DRIVERS\1394ohci.sys  (1394.inf line 77)
         inf:                          DisplayName="1394 OHCI Compliant Host Controller"  (1394.inf line 73)
         dvi:                          Add Service: Modified existing service '1394ohci'.
         inf:                     {Install Inf Section [Generic.Install.NT.Services] exit(0x00000000)}
         dvi:                     Updated reflected section names for: 1394.inf
         dvi:                {Install DEVICE exit (0x00000000)}
         dvi:                Writing common driver property settings.
         dvi:                     DriverDescription=Texas Instruments 1394 OHCI Compliant Host Controller
         dvi:                     DeviceDisplayName=Texas Instruments 1394 OHCI Compliant Host Controller
         dvi:                Install Device: Restarting device. 21:56:28.589
         dvi:                Install Device: Restarting device completed. 21:56:28.854
    !!!  dvi:                Device not started: Device has problem: 0x0a: CM_PROB_FAILED_START.
         dvi:           Default installer: Exit
         dvi:      {DIF_INSTALLDEVICE - exit(0x00000000)} 21:56:28.854
         dvi:      {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 21:56:28.854
         dvi:           No class installer for 'Texas Instruments 1394 OHCI Compliant Host Controller'
         dvi:           Default installer: Enter 21:56:28.854
         dvi:           Default installer: Exit
         dvi:      {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 21:56:28.854
         ndv:      Device install status=0x00000000
         ndv:      Performing device install final cleanup...
    !    ndv:      Queueing up error report since device has a PnP problem...
         ndv: {Core Device Install - exit(0x00000000)} 21:56:29.119
         ump: Server install process exited with code 0x00000000 21:56:29.119
    <<<  Section end 2009/09/06 21:56:29.119
    <<<  [Exit status: SUCCESS]

    Monday, September 7, 2009 5:38 AM
  • Thanks.  I see the failure in there, but I'm not sure why this is happening.  I'll see if I can find someone that might know what's happening here.  May take me a few days before I follow up on this one.
    Want to know if your hardware will work on Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Microsoft Logo'd Hardware List**
    Monday, September 7, 2009 6:00 AM
  • Thank you!
    Tuesday, September 8, 2009 12:05 AM
  • Hi hecatol,

     

    You can try to run Windows Update to scan for updates. Make sure that the “Recommended updates” box in Windows Update->Change settings is chosen. Then click Check for updates, if the drivers for IEEE 1394 controllers are listed, please install them.

     

    If there is no proper driver, please have a look at the link below:

     

    Texas Instruments OHCI Compliant IEEE 1394 Host Controller driver

    Since the driver is for Windows XP, I suggest you install it in Windows XP compatible mode.

     

    Good luck.


    Cecilia Zhou
    Tuesday, September 8, 2009 8:20 AM
  • hecatol,
    The device is specifically listed in the Shuttle specs. Viewing the device at TI here would lead me to believe that the drivers may be altered from standards for the specific application of the integration of the device.

    In other words, try installing the Shuttle chipset Vista drivers, here,  which may include what is needed to resolve the issue. Then apply the Intel update.

    ASUS P4PE-P4 Extreme 3.4gHz-2gb G.Skill PC3200-XPSP3:55gb-Win7RC:17gb-DATA:500gb-ASUS N6800GT
    Tuesday, September 8, 2009 10:51 AM
  • I followed the advice from Nano Warp and installed the Intel Chipset package directly from the Shuttle website (Nov 2007) which in the installer is presented just as an earlier version (1.1.9) of the regular Intel Chipset Software Utility. I rebooted, then installed the current version from Intel (1.1.25), rebooted again, and sadly the IEEE controller is still in the same Code 10 state. Judging from the log, there was a check done after the second reboot to try and update the driver, but with no action:

    [Boot Session: 2009/09/09 19:17:14.375]

    >>>  [Device Install (DiShowUpdateDevice) - PCI\VEN_104C&DEV_8023&SUBSYS_51061297&REV_00\4&3B662B29&0&50F0]
    >>>  Section start 2009/09/09 19:30:51.922
          cmd: "C:\Windows\system32\mmc.exe" C:\Windows\system32\devmgmt.msc
         dvi: {DIF_UPDATEDRIVER_UI} 19:30:51.922
         dvi:      No class installer for 'Texas Instruments 1394 OHCI Compliant Host Controller'
         dvi:      Default installer: Enter 19:30:51.938
         dvi:      Default installer: Exit
         dvi: {DIF_UPDATEDRIVER_UI - exit(0xe000020e)} 19:30:51.938
         ndv: {Update Driver Software Wizard for PCI\VEN_104C&DEV_8023&SUBSYS_51061297&REV_00\4&3B662B29&0&50F0}
         inf:      Opened PNF: 'C:\Windows\INF\1394.inf' ([strings.0409])
         ndv: {Update Driver Software Wizard exit(00000000)}
    <<<  Section end 2009/09/09 19:31:04.621
    <<<  [Exit status: SUCCESS]


    >>>  [Device Install (Hardware initiated) - STORAGE\VolumeSnapshot\HarddiskVolumeSnapshot39]
    >>>  Section start 2009/09/10 16:10:14.160
         ump: Creating Install Process: DrvInst.exe 16:10:14.171
         ndv: Retrieving device info...
         ndv: Setting device parameters...
         ndv: Doing WU search last due to CM_DEVCAP_SILENTINSTALL flag.
         ndv: Searching Driver Store and Device Path...
         dvi: {Build Driver List} 16:10:14.522
         dvi:      Searching for hardware ID(s):
         dvi:           storage\volumesnapshot
         cpy:      Policy is set to make all digital signatures equal.
         dvi:      Enumerating INFs from path list 'C:\Windows\inf'
         inf:      Opened PNF: 'C:\Windows\System32\DriverStore\FileRepository\volsnap.inf_x86_neutral_42f862e05fcb0306\volsnap.inf' ([strings.0409])
         dvi:      Created Driver Node:
         dvi:           HardwareID   - STORAGE\VolumeSnapshot
         dvi:           InfName      - C:\Windows\System32\DriverStore\FileRepository\volsnap.inf_x86_neutral_42f862e05fcb0306\volsnap.inf
         dvi:           DevDesc      - Generic volume shadow copy
         dvi:           DrvDesc      - Generic volume shadow copy
         dvi:           Provider     - Microsoft
         dvi:           Mfg          - Microsoft
         dvi:           ModelsSec    - MSFT.NTx86
         dvi:           InstallSec   - volume_snapshot_install
         dvi:           ActualSec    - volume_snapshot_install.NTx86
         dvi:           Rank         - 0x00ff0000
         dvi:           Signer       - Microsoft Windows
         dvi:           Signer Score - INBOX
         dvi:           DrvDate      - 06/21/2006
         dvi:           Version      - 6.1.7600.16385
         inf:      Searched 1 potential matches in published INF directory
         inf:      Searched 35 INFs in directory: 'C:\Windows\inf'
         dvi: {Build Driver List - exit(0x00000000)} 16:10:14.675
         ndv: Selecting best match from Driver Store (including Device Path)...
         dvi: {DIF_SELECTBESTCOMPATDRV} 16:10:14.676
         dvi:      No class installer for 'Storage volume shadow copies'
         dvi:      No CoInstallers found
         dvi:      Default installer: Enter 16:10:14.745
         dvi:           {Select Best Driver}
         dvi:                Selected driver installs from section [volume_snapshot_install] in 'c:\windows\system32\driverstore\filerepository\volsnap.inf_x86_neutral_42f862e05fcb0306\volsnap.inf'.
         dvi:                Class GUID of device changed to: {533c5b84-ec70-11d2-9505-00c04f79deaf}.
         dvi:                Set selected driver complete.
         dvi:                Selected:
         dvi:                     Description - [Generic volume shadow copy]
         dvi:                     InfFile     - [c:\windows\system32\driverstore\filerepository\volsnap.inf_x86_neutral_42f862e05fcb0306\volsnap.inf]
         dvi:                     Section     - [volume_snapshot_install]
         dvi:                     Signer      - [Microsoft Windows]
         dvi:                     Rank        - [0x00ff0000]
         dvi:           {Select Best Driver - exit(0x00000000)}
         dvi:      Default installer: Exit
         dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 16:10:14.749
         inf: {SetupCopyOEMInf: C:\Windows\INF\volsnap.inf} 16:10:14.750
         inf:      Driver Store location: C:\Windows\System32\DriverStore\FileRepository\volsnap.inf_x86_neutral_42f862e05fcb0306\volsnap.inf
         inf:      Published Inf Path: C:\Windows\INF\volsnap.inf
         inf: {SetupCopyOEMInf exit (0x00000050)} 16:10:14.751
         dvi: Searching for hardware ID(s):
         dvi:      storage\volumesnapshot
         inf: Opened PNF: 'C:\Windows\System32\DriverStore\FileRepository\volsnap.inf_x86_neutral_42f862e05fcb0306\volsnap.inf' ([strings.0409])
         dvi: Selected driver installs from section [volume_snapshot_install] in 'c:\windows\system32\driverstore\filerepository\volsnap.inf_x86_neutral_42f862e05fcb0306\volsnap.inf'.
         dvi: Class GUID of device changed to: {533c5b84-ec70-11d2-9505-00c04f79deaf}.
         dvi: Set selected driver complete.
         ndv: Driver selected, now performing install...
         ndv: {Core Device Install} 16:10:14.756
         inf:      Opened PNF: 'C:\Windows\INF\volsnap.inf' ([strings.0409])
         inf:      Opened PNF: 'C:\Windows\INF\volsnap.inf' ([strings.0409])
         sig:      {_VERIFY_FILE_SIGNATURE} 16:10:14.781
         sig:           Key      = volsnap.inf
         sig:           FilePath = C:\Windows\INF\volsnap.inf
         sig:           Success: A valid signature was found in an installed catalog
         sig:           Cat: 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-Common-Drivers-Package~31bf3856ad364e35~x86~~6.1.7600.16385.cat'
         sig:      {_VERIFY_FILE_SIGNATURE exit(0x00000000)} 16:10:14.839
         inf:      Opened PNF: 'C:\Windows\INF\volsnap.inf' ([strings.0409])
         dvi:      {DIF_ALLOW_INSTALL} 16:10:14.840
         dvi:           No class installer for 'Generic volume shadow copy'
         dvi:           No CoInstallers found
         dvi:           Default installer: Enter 16:10:14.841
         dvi:           Default installer: Exit
         dvi:      {DIF_ALLOW_INSTALL - exit(0xe000020e)} 16:10:14.841
         ndv:      Installing files...
         dvi:      {DIF_INSTALLDEVICEFILES} 16:10:14.842
         dvi:           No class installer for 'Generic volume shadow copy'
         dvi:           Default installer: Enter 16:10:14.842
         dvi:                {Install FILES}
         inf:                     Opened PNF: 'c:\windows\system32\driverstore\filerepository\volsnap.inf_x86_neutral_42f862e05fcb0306\volsnap.inf' ([strings.0409])
         inf:                     {Install Inf Section [volume_snapshot_install.NTx86]}
         inf:                     {Install Inf Section [volume_snapshot_install.NTx86] exit (0x00000000)}
         dvi:                     Processing co-installer registration section [volume_snapshot_install.NTx86.CoInstallers].
         inf:                     {Install Inf Section [volume_snapshot_install.NTx86.CoInstallers]}
         inf:                     {Install Inf Section [volume_snapshot_install.NTx86.CoInstallers] exit (0x00000000)}
         dvi:                     Co-installers registered.
         dvi:                     {Install INTERFACES}
         dvi:                          Installing section [volume_snapshot_install.NTx86.Interfaces]
         dvi:                     {Install INTERFACES exit 00000000}
         dvi:                {Install FILES exit (0x00000000)}
         dvi:           Default installer: Exit
         dvi:      {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 16:10:14.846
         ndv:      Pruning file queue...
         dvi:      {_SCAN_FILE_QUEUE}
         flq:           ScanQ flags=620
         flq:                SPQ_SCAN_PRUNE_COPY_QUEUE
         flq:                SPQ_SCAN_FILE_COMPARISON
         flq:                SPQ_SCAN_ACTIVATE_DRP
         flq:           ScanQ number of copy nodes=0
         flq:           ScanQ action=200 DoPruning=32
         flq:           ScanQ end Validity flags=620 CopyNodes=0
         dvi:      {_SCAN_FILE_QUEUE exit(0, 0x00000000)}
         ndv:      Committing file queue...
         flq:      {_commit_file_queue}
         flq:           CommitQ DelNodes=0 RenNodes=0 CopyNodes=0
         flq:           CommitQ early exit: No nodes are queued
         flq:      {_commit_file_queue exit OK}
         ndv:      Registering CoInstallers...
         dvi:      {DIF_REGISTER_COINSTALLERS} 16:10:14.850
         dvi:           No class installer for 'Generic volume shadow copy'
         dvi:           Default installer: Enter 16:10:14.851
         inf:                Opened PNF: 'c:\windows\system32\driverstore\filerepository\volsnap.inf_x86_neutral_42f862e05fcb0306\volsnap.inf' ([strings.0409])
         inf:                {Install Inf Section [volume_snapshot_install.NTx86.CoInstallers]}
         inf:                {Install Inf Section [volume_snapshot_install.NTx86.CoInstallers] exit (0x00000000)}
         dvi:                Co-installers registered.
         dvi:           Default installer: Exit
         dvi:      {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 16:10:14.854
         ndv:      Installing interfaces...
         dvi:      {DIF_INSTALLINTERFACES} 16:10:14.854
         dvi:           No class installer for 'Generic volume shadow copy'
         dvi:           No CoInstallers found
         dvi:           Default installer: Enter 16:10:14.855
         dvi:                {Install INTERFACES}
         inf:                     Opened PNF: 'c:\windows\system32\driverstore\filerepository\volsnap.inf_x86_neutral_42f862e05fcb0306\volsnap.inf' ([strings.0409])
         dvi:                     Installing section [volume_snapshot_install.NTx86.Interfaces]
         dvi:                {Install INTERFACES exit 00000000}
         dvi:           Default installer: Exit
         dvi:      {DIF_INSTALLINTERFACES - exit(0x00000000)} 16:10:14.879
         ndv:      Installing device...
         dvi:      {DIF_INSTALLDEVICE} 16:10:14.880
         dvi:           No class installer for 'Generic volume shadow copy'
         dvi:           Default installer: Enter 16:10:14.880
         dvi:                {Install DEVICE}
         inf:                     Opened PNF: 'c:\windows\system32\driverstore\filerepository\volsnap.inf_x86_neutral_42f862e05fcb0306\volsnap.inf' ([strings.0409])
         dvi:                     Processing Registry/Property directives...
         inf:                     {Install Inf Section [volume_snapshot_install.NTx86]}
         inf:                     {Install Inf Section [volume_snapshot_install.NTx86] exit (0x00000000)}
         inf:                     {Install Inf Section [volume_snapshot_install.NTx86.Hw]}
         inf:                          Empty section
         inf:                     {Install Inf Section [volume_snapshot_install.NTx86.Hw] exit (0x00000000)}
         dvi:                     {Writing Device Properties}
         dvi:                          Provider name=Microsoft
         dvi:                          DriverDate 06/21/2006
         dvi:                          DriverVersion=6.1.7600.16385
         dvi:                          Class name=VolumeSnapshot
         dvi:                          Manufacturer=Microsoft
         dvi:                          Matching DeviceID=storage\volumesnapshot
         dvi:                          Strong Name=volsnap.inf:MSFT.NTx86:volume_snapshot_install:6.1.7600.16385:storage\volumesnapshot
         dvi:                     {Writing Device Properties - Complete}
         inf:                     {Install Inf Section [volume_snapshot_install.NTx86.Services]}
         inf:                          AddService=,2,  (volsnap.inf line 31)
    !    dvi:                          Add Service: NULL Controlling service.
         inf:                     {Install Inf Section [volume_snapshot_install.NTx86.Services] exit(0x00000000)}
         dvi:                     Updated reflected section names for: volsnap.inf
         dvi:                {Install DEVICE exit (0x00000000)}
         dvi:                Writing common driver property settings.
         dvi:                     DriverDescription=Generic volume shadow copy
         dvi:                     DeviceDisplayName=Generic volume shadow copy
         dvi:                Install Device: Removing device sub-tree. 16:10:14.900
         dvi:                Install Device: Removing device sub-tree completed. 16:10:15.002
         dvi:                Install Device: Restarting device. 16:10:15.002
         dvi:                Install Device: Restarting device completed. 16:10:15.111
         dvi:           Default installer: Exit
         dvi:      {DIF_INSTALLDEVICE - exit(0x00000000)} 16:10:15.112
         dvi:      {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 16:10:15.113
         dvi:           No class installer for 'Generic volume shadow copy'
         dvi:           Default installer: Enter 16:10:15.113
         dvi:           Default installer: Exit
         dvi:      {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 16:10:15.114
         ndv:      Device install status=0x00000000
         ndv:      Performing device install final cleanup...
         ndv: {Core Device Install - exit(0x00000000)} 16:10:15.117
         ump: Server install process exited with code 0x00000000 16:10:15.123
    <<<  Section end 2009/09/10 16:10:15.127
    <<<  [Exit status: SUCCESS]
     

    Sunday, September 13, 2009 5:43 PM
  • I noticed one other fix on the forum. From device manager, they forced it to take a choice of "legacy" driver from Windows. This was on a newer motherboard.
    ASUS P4PE-P4 Extreme 3.4gHz-2gb G.Skill PC3200-XPSP3:55gb-Win7RC:17gb-DATA:500gb-ASUS N6800GT
    Tuesday, September 15, 2009 3:24 PM
  • Hello hecatol

    Please run below steps to collect 1394 traces and send/upload.

    - copy instructions under 'to-enable' as enabletrace.cmd
    - copy instructions under 'to-disable' as disabletrace.cmd
    - run enabletrace.cmd with elevated credentials (ie: as local administrator)
    - reboot the machine
    - run 1394 problem repro steps and verify the error occurs.
    - run disabletrace.cmd with elevated credentials (ie: as local administrator)
    - reboot the machine
    - Copy or send the files 1394ohci.etl.xxx from %systemroot%\tracing

    Please note: This tracing facility is available only when 1394 driver is in win7(ie: default) mode and not when it's in legacy mode.

    TO-ENABLE:

    set binaryname=1394ohci
    set binaryguid=3979F0A6-8A10-4cfd-BF20-9E45279D6C19
    @REG ADD "HKLM\System\CurrentControlSet\Control\WMI\Autologger\%binaryname%\{%binaryguid%}" /v EnableFlags /t  REG_DWORD /d 0xffffffff /f
    @REG ADD "HKLM\System\CurrentControlSet\Control\WMI\Autologger\%binaryname%\{%binaryguid%}" /v EnableLevel /t  REG_DWORD /d 0xffffffff /f
    @REG ADD "HKLM\System\CurrentControlSet\Control\WMI\Autologger\%binaryname%\{%binaryguid%}" /v Enabled /t  REG_DWORD /d 0x1 /f
    @REG ADD "HKLM\System\CurrentControlSet\Control\WMI\Autologger\%binaryname%\{%binaryguid%}" /v Status /t  REG_DWORD /d 0 /f

    @REG ADD "HKLM\System\CurrentControlSet\Control\WMI\Autologger\%binaryname%" /v GUID /t  REG_SZ /d {%binaryguid%} /f
    @REG ADD "HKLM\System\CurrentControlSet\Control\WMI\Autologger\%binaryname%" /v FileName /t  REG_SZ /d %SystemRoot%\Tracing\%binaryname%.etl /f
    @REG ADD "HKLM\System\CurrentControlSet\Control\WMI\Autologger\%binaryname%" /v FileMax /t  REG_DWORD /d 1000 /f
    @REG ADD "HKLM\System\CurrentControlSet\Control\WMI\Autologger\%binaryname%" /v MaxFileSize /t  REG_DWORD /d 1000 /f
    @REG ADD "HKLM\System\CurrentControlSet\Control\WMI\Autologger\%binaryname%" /v LogFileMode /t  REG_DWORD /d 0x1202 /f
    @REG ADD "HKLM\System\CurrentControlSet\Control\WMI\Autologger\%binaryname%" /v Start /t  REG_DWORD /d 1 /f
    @REG ADD "HKLM\System\CurrentControlSet\Control\WMI\Autologger\%binaryname%" /v Status /t  REG_DWORD /d 0 /f
    @REG ADD "HKLM\System\CurrentControlSet\Control\WMI\Autologger\%binaryname%" /v FlushTimer /t REG_DWORD /d 1 /f

     

    TO-DISABLE:

    set binaryname=1394ohci
    @REG DELETE "HKLM\System\CurrentControlSet\Control\WMI\AutoLogger\1394ohci" /f

    Monday, September 21, 2009 9:46 PM
  • Hello, 

    I am running into the identical problem as hecatol on my Shuttle SG31G2. 28 entries for Texas Instruments 1394 OHCI Compliant Host Controller show up in my Device Manager under the IEEE 1394 Bus host controllers section. It looks like this thread has been quite for a couple months; was any solution discovered?

    Thanks in advance for any help,

    Sam
    Thursday, November 26, 2009 9:04 PM
  • There is no fix yet but a general answer to why. Basically it manifest as a lockup or multiple entries in device manager. Microsoft will need to work with TI to get a true compatible Win7 version for the TI 1394 OHCI chip set. The driver that ships with Win7 does not work. For now the best option is to disable not uninstall the entries in device manager for this device. Yes, that means no firewire for now. There are PCMCIA and Express card firewire adapters if you truly need firewire in the interum.
    http://social.technet.microsoft.com/Forums/en-US/w7itprohardware/thread/32be75ca-5cc2-4782-81c5-cec89768c11d/

    Wednesday, December 9, 2009 7:44 AM
  • The best way I found to get around this issue on my Shuttle SP35P2 running Windows 7 64bit was to install the latest Unibrain firewire drivers, which are available free from the Unibrain website. Before that I experienced many problems with the firewire device vanishing from device manager, and then re-appearing with numerous entries, none of which were working. It has been working for me for a month now with no problems.
    Monday, March 8, 2010 11:39 PM
  • I believe I have the same problem on an SP35P2.  I tried the Unibrain drivers (ubCore64_040110.exe) and they now appear in the device manager but with the same multiple failed entries. 

    Am I using the wrong drivers?

    Is there another fix out there?

    Sunday, September 12, 2010 6:34 PM
  • I have exactly the same problem as the topicstarter - only another computer, it is a custom build pc. At this very moment I tried all the suggestion written in this topic. The first time the problem was solved by removing all the "Texas instruments 1394 ohci compliant host controllers", but this time, I got a BSOD and removing all the controllers doesn't work, they all coming back.

    That's not my biggest problem. The biggest problem is, that due to those 32(!) controllers my M-audio device is not working anymore. This is a PCI audio device, but at the moment that the controllers appeared, my M-audio device disappeared.

    Is there already a (better) solution for this problem.

    Thanks in advance!

    Thursday, January 6, 2011 10:34 PM
  • I have the same issue with the Shuttle (Windows 7 64) and multiple Texas Instruments 1394 OHCI Compliant Host Controller entries, but ONLY when I have my Hauppauge 1600 tv tuner card installed.    It manifests itself whenever there are automated updates that take place after the box has been running for a while.  If I take the Hauppauge card out, reboot, etc. it clears the TI entries out, then I can reinstall the Hauppauge card and everything works fine for a while........

    I tried installing this card on other Windows 7 boxes and running Media Center, and it works fine.  Never see the TI issue there, so has to be something with the Shuttle.

    Very frustrating.  If anyone has an answer for this, love to hear it.    

    • Proposed as answer by Garyd43 Friday, March 18, 2011 4:12 PM
    Wednesday, March 16, 2011 4:45 PM
  • Went back (again) and tried this, which worked (for now at least).  In Device Manager uninstalled all instances of the Texas Instruments 1394 OHCI Compliant Host Controller and looked for the Video controller that was not working (in this case the Hauppauge 1600 TV Tuner card) which was found in another section.    I manually updated the device driver from the harddrive (not internet) and then rebooted.  Worked fine from then on.  Have to see when next Windows update takes place, but at least I can fix it quickly right now.
    • Proposed as answer by Garyd43 Friday, March 18, 2011 4:18 PM
    Friday, March 18, 2011 4:17 PM
  • The above link took me to a car dealer.

    Saturday, December 2, 2017 8:26 PM