Firewire PCI card undetectable after driver install.

[Bino5150]

OK, so clean install of W7 Ultimate x64 on my Optiplex 990. I have a VIA firewire PCI card installed in it. In the device manager, there were of course several things that weren't configured correctly for lack of drivers. My 1394 card showed there, with the yellow sign beside it, and in the properties it said "this device can not be started". I was assuming that was because the chipset drivers had not been installed yet. The manufacturer of the PCI card said that there were no drivers to download for W7/10 because they have the 1394 drivers built in.

I installed the chipset/motherboard drivers, and that cleared up everything in the device manager... *EXCEPT* now the 1394 card is not detectable at all. The IEEE 1394 branch is now absent from the device tree, like the card isn't there. I've reseated the card a few times, scanned for new hardware, all of that stuff, but nothing seems to work. There are no unknown devices, yellow signs, or any kind of conflicts in my Device manager. It just doesn't see the PCI card at all.

Any ideas why Windows isn't seeing the Firewire card?

 

[iko22]

Hello Bino5150

Did you know, Hidden Devices only show if Device Manager > View > Show Hidden Devices is ticked?

 

[Bino5150]

Hello Bino5150

Did you know, Hidden Devices only show if Device Manager > View > Show Hidden Devices is ticked?

Yes, but it's not there either. The only hidden device on my system is the PS/2 mouse port, which is not in use. My IEEE 1394 shouldn't be hidden anyway. Windows isn't detecting that the card even exists anymore, nor any devices plugged into it, which is creating quite a problem for me at the moment.

And I double checked that my PCI card is 3.3 volts and not 5 volt, since the 5v PCI 2.0 cards are not compatible with my motherboard.

I know the card works, and is supposed to be plug and play with no additional drivers required in W7. And it detected it before I installed the chipset drivers. It's really got me scratching my head with this one. I know Windows 7 had a lot of problems with Firewire back in the day, which is why I remained on XP for so many years. I run a recording studio, and could not afford for my $2,500 24 track firewire interface to not function, which is exactly what's happening right now. Makes me want to bang my head against the wall lol.

 

[Bino5150]

This is with "Show Hidden Devices" checked

 

[iko22]

Have a look in the Non-Plug and Play Drivers node of Device Manager. If it is there, delete it and then reboot.
If it is not there, open an Administrators Command Prompt window, and type:
SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
Press return, then return to Device Manager and see if any additional devices show up.

 

[Bino5150]

Have a look in the Non-Plug and Play Drivers node of Device Manager. If it is there, delete it and then reboot.
If it is not there, open an Administrators Command Prompt window, and type:
SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
Press return, then return to Device Manager and see if any additional devices show up.

nope, the device is still invisible.

 

[iko22]

It might be that the PCI card has given in.

Try a System Restore, to a Point in Time before you updated the motherboard drivers. If you succeed with the system restore, then check device manager again. If the device still does not show, I'd assume the card has died on you.

 

[Bino5150]

Nah, I know the card works. Thanks for trying though. I did order a new card, PCIe this time, so hopefully W7 will detect that. I'm walking a fine line between Firewire cards that Windows will play nice with, and Firewire cards with chipsets that function properly with my interface. After a lot of research and headaches, hopefully this new card will do both.

 

[Buckner]

and in the properties it said "this device can not be started".

I know this thread is from last year, but I wondered if OP figured this out as I have near identical issue. I have a Firewire PCI card that showed the exclaim point and "could not be started" message but it disappears and reappears (sometimes working) depending on if I relocate my graphics card (AMD Radeon HD 7500) to a different PCI slot, or pull it and switch to on-board graphics.

Seems like a conflict of resources but I can't figure out any further. This is on Windows 10 Enterprise 64 bit

 

[torchwood]

Hi Bucker,
based on your testing i would agree with your assessment.
However
1) you will get more support on our sister W10 site
2)the could not be started message will also have an error code, would be usefull to know it
3)Complete your computer specs, - be handy if you include Hwinfo details
4) as your running Enterprise, does your System Admin allow you to make changes

 

[sygnus21]

I know this thread is from last year, but I wondered if OP figured this out as I have near identical issue. I have a Firewire PCI card that showed the exclaim point and "could not be started" message but it disappears and reappears (sometimes working) depending on if I relocate my graphics card (AMD Radeon HD 7500) to a different PCI slot, or pull it and switch to on-board graphics.

Seems like a conflict of resources but I can't figure out any further. This is on Windows 10 Enterprise 64 bit

Just FYI... Getting your Nikon Coolscan to work on W7 x64 - Page 60 - Windows 10 Forums (sevenforums.com)

Point is I had one working on Windows 10. No longer using it now but I might be able to help.