IEE1394 Bus Host Controller has! in device mgr.

In device manager, under IEE1394 Bus Host Controller, I have the ! caution. Properties says "device cannot start "

Some of the time the caution is not there Properties says device is functioning properly and a 1394 connection appears in control panel "network" as an operating network.

I doesn't seem to impact either my local network or my internet connection if it cannot start or it is functioning properly as far as I can tell.

I don't even know what this is, what it does and why it is ok sometimes and not others.

Anybody help on this??

 

Hi martin- It is referring to your Firewire bus. My first instinct is to tell you to remove it in Device Manager and let Windows reinstall it, but would like to know if there is an error code associated with the ! ? Are there networked Firewire devices? Please post back with a little more info so someone can give you a hand. Clydeo22

 

Hi Clydeo: Frustrating. I go to look for error code in device manager this AM after boot & reading your post, ! caution gone, device working, check drivers, all MSFT from System 32\ as follows: 1394bus.sys; arp1394.sys; enum1394.sys; nic1394.sys; ohci1394.sys

Network in contol panel now shows "1394 connection ", with network bridge, Bridge not there w/o 1394. something to do with "nic1394.sys" ?

I had tried the uninstall/re-install routine several times last night while ! still there, used Device mgr "install new hardware" while uninstalled, both with and without shutdown in between. "Install new Hardware" finds disabled 1394, shows MSFT WHQL drivers, click continue, seems to go ok but device mgr still !. "Update Drivers" says "Cant find better......"

Ive done this at other times over the last couple of weeks, same results, can't get rid of !.

Copied 1394.inf from system 32 to desktop, pointed windows at it, no help.

Two other computers on network, neither has firewire. No networked 1394 devices.

This board (Soyo KT400 Dragon Ultra Platinum) has onboard firewire, also installed firewire PCI card. Maybe 3 ports confusing Windows?? Device Manager shows only one device in category.

Like I said, sometimes ok, sometimes not, it happens and unhappens (coined a new word?) with no apparent cause and no apparent effect. I just can't stand something apparently amiss.

Next time, if it happens again, I'll plug my video camera into board port, then PCI card port, see if one or the other (or both) is disabled.

Appreciate the help, I did know that the 1394 is the firewire, just having it in networks got me confused. You can network a 1394 device? Maybe something in my shared files?

Martin

Edit: Forgot to say thanks, Thanks for your help!

 

Hi Martin- Can you check to see if you have a resource conflict between the onboard Firewire and the add-in card? In particular IRQs. Also, check the documentation that came with the card and see if it is necessary to disable the onboard Firewire to avoid conflicts and we'll struggle on from there. Clydeo22

 

checking away, will post results.

 

Only one device (1394) listed in device manager, reports no conflicts.

Documentation for card long gone the way of the Dodo bird, don't even remember who made it. Will have to pull it from machine to identify-go to website for documentation. Not sure I'm ready to do that.

Aida32 lists 1394 host controller in 3 places. Windows Devices, Physical Devices, Device Resources.

Physical Devices says ATT/Lucent Bus 0 Device 12, Function 0.

Windows Devices says same as device mgr.

Device Resources says IRQ 10, Shared.

Will look in BIOS, disable on board, restart & see what happens. May be diabled already for all I know.

Before I do that, Since I have not used the onboard firewire port, but have been using the card ports, I'll plug my video camera in the board, see if it works.

! still gone from Device Manager. Should only stay that way.

Big day tomorrow, going to bed now.

Martin

 

Hi Martin- as long as you're experimenting, try plugging something into the onboard port and then check Device Manager and see if everything shows up. Then try plugging something into the card and see what happens then. If it's still working even with the few times with the !, I would leave it alone. I know it's annoying to have to live with and unresolved problem but it may just be one of those things. I've had one on my computer ever since I got it and finally gave up on trying to resolve the thing as it works fine even with the !. Regards, Clydeo22

 

Jeeze, I'm so embarrassed. When I went to plug camera to onboard 1394 port, there wasn't one. I could have, probably would have sworn that there was an on board firewire port. I guess all those USB ports got me confused, thought two of four were firewire.

Beyond that, I plugged the camera to the card, seems to work ok, ! gone from device manager on first boot this morning, it was there when I shut down last night.

1394 still shows up in network. I wish I knew what that was all about.

Thanks for the help. If the camera stops working through the firewire port, I'll be back.

Martin

 

AARRGH!

Got ready to burn some video to DVD, Assemble DVI tapes, gather blank DVD disks insert tape in camera, plug camera to Firewire port on PCI card, no reaction from machine. Camera not recognized. No camera in "My Computer "

Go to device manager, find "IEEE 1394 host controller" and underneath it with yellow caution and!: "OHCI Compliant IEEE 1394 Host Controller" and in properties "this device cannot start" and, "Code 10 "

Driver details list all native Windows System 32 drivers as stated previously.

Try numerous times, uninstall/reinstall, update drivers, uninstall shut down, restart, install new hardware numerous times, Nothing will get it to work. Install finds new hardware, IEE1394 Host controller with yellow caution, installs as no working device.

Disgusted after two hours of trying to get the device to work, shut down machine, too agrevated and tired to do this post, walk away.

Same day, today, after daughter's baskeball practice, after supper, hours later, boot machine. Hear familiar bing/bong sound of video camera recognition from machine, had forgotten to turn it off and unplug it. Camera recognized by machine, Camera in "My Computer "

Go to device manager. Yellow caution gone, properties says "this device is working properly" Driver details list same Windows system 32 drivers.

Go to "Network "Connections" and sure enough, in network connections, along with internet and local area, is "1394 Connection "

I had Firewire long prior to network, never a problem. Why is it showing up as a network connection? I have no networked Firewire devices.

It's appearance/dissapearance in network connections has no impact on LAN or Internet connections.

Can somebody please tell me what is going on here, what the heck is killing this Firewire port and how do I get it to stop. Or get it to run with some degree of reliability, I should say.

The firewire port is currently ok, camera is recognized, until next time?? When I want to use it??

It is things like this that give me that AARRGH!! feeling.

Martin

 

Don't worry about it. It's supposed to show up there. It's perfectly normal.
What is a 1394 network connection?

 

Ok Zander, thanks. One mystery solved.

But why the intermittant failure? With all drivers XP natives?

And I'll bet if I disable that connection, as suggested in the windows.network site, that will be the end of the Video Camera connection as well.

I'll not try that until I get these videos transfered to HDD.

I have not shut down since connection re-enabled itself.

What to do the next time it fails?? Nothing I have tried will re-enable the connection. AARRGH! Just wait patiently while it decides whether to work or not??

AARRGH!

Martin

 

I don't know what to tell you. I wonder however, if it isn't a hardware related problem as opposed to a software (drivers) one. If it were me I'd try updating the bios and see if that helps. Also, if you have a "Plug and Play OS" entry in your bios I'd try setting it to no if it isn't already. If it would happen to be an IRQ conflict of some sort maybe the bios can sort it out better than the OS can. I kinda doubt that's the problem though, as it works at times and not at others. I'll do some searching and see if I can come up with anything for you.

 

Thanks Zander: Got a clue where to look, I don't mind searching myself, just where to look?

I'm going to try system file checker later, maybe a corrupted driver. First I want to get about 20 tapes onto hard drive before I ***** 1394 worse.

Thanks again,

Martin

 

Hi Martin- Sorry to hear that you are still beset with gremlins. From what I am finding, it is an enumeration problem where all devices are not being found by Windows. The solution posted is to update the drivers. I did a search for "Device Manager Code 10 errors in Google and came up with quite a few hits all pretty much saying the same thing. Microsoft addressed this issue, although not specifically for Firewire here:http://support.microsoft.com/default.aspx?kbid=125174
I found another page that points to a patch, but they are recommending that users wait until the next 2000/XP patch. If you get the error again, while in Device Manager, double click on My Computer and view the resources allocated to all devices in the separate categories, i.e. IRQs, I/o addresses and see what the distribution of the resources and the possible conflicts are so that we can rule out a configuration problem. You can also try rebooting, go into setup and reset PnP configuration to yes and have Windows try to sort it out. Happy Thanksgiving. Clydeo22

 

If it's already set to yes I still say to give no a try. One of the first things I have always done on a new puter is set that to no. I've never had a bit of trouble. On other peoples that were having troubles of this sort setting it to no would often times take care of the problem. I've come to think that the bios can sort things out better than windows. Maybe XP is different than previous versions though.

 

Setting it to Yes will only last for that bootup. The next time he boots, it will revert to No and stay there unless manually set to Yes again. It just forces Windows to look at how the resources are distributed and shuffle them if necessary. Clydeo22

 

ClydeO22 & Zander: I'll try it both ways see if either work.

On this MOBO, if set to yes on PNP, sometimes it stays that way, does not change on reboot on every time, but does change to no occasionaly, have no Idea why.

Went to the MSFT site you posted, I agree not much help there, Code 10 still mysterious.

When checking for device conflicts when connection working, get "no conflicts" don't remember for sure if I checked when not working, but iI think so and it must have said "no conflicts also or I surely would remember it. (I think )
Also, you have given me some food for thought, on reboot when connection not working, will set MOBO BIOS to check device configuration w/o PNP enabled, see what happens.

I want to thank all for helping, you give me the energy to keep working on the problem, otherwise I think I'd just throw up my hands and walk away. Or just throw up.

So, thanks again, I'm very greateful for your dedication to helping others.

Martin

 

Hmmm. Mine have always stayed set to no year after year after.....

 

Hi Zander- I guess that is the point I was trying to make. It will stay set to No unless manually set to Yes. It should then reset to No on the next boot and stay that way unless set to Yes again. It's something to try when nothing else seems to work and I think we are just about there. Thanks for posting back so I could clarify a bit. Happy Thanksgiving. Clydeo22.

 

OOPS! Guess I read your post wrong. None the less, it seems to me that while messing around with them in the past they've always stayed set to whatever I set them to regardless of the setting. Oh well. Happy Thanksgiving to you too!