Home All Groups Group Topic Archive Search About

1394 Net Adapter Cannot Start (Error Code 10)

Author
18 Oct 2006 5:09 PM
Crushed Pickle Studio
Good morning:

I have just recently built a new PC with the following Specs:

2 - AMD Opteron 265
Tyan Tiger K8WE Motherboard (w/onboard 1394)
2 GB Corsair Ram
nVidia 6600 PCIe Graphics Card
WinXP Pro SP2

My issue lies in the fact that in the Device Manager under Network Adapters
there is the yellow "information" indicator telling me that there is some
sort of problem.  There have been a number of us that have built the exact
same machine (down to the letter) and it appears that all others are working
so far.  Aside from XP sp2, the only other installed drivers are the nVidia
Platform driver v6.70, and the nVidia Graphics drivers v81.98.  To my
knowledge the other machines that have been built have not applied any
hotfixes or anything...just the bare SP2 install.

The onboard 1394 is enabled in the BIOS and the Fireware Adapter shows no
conflicts.  There are no IRQ conflicts.

All indications show that it should be working, however, in  the Control
Panel under Network Connections, I only see my Ethernet Connection.  Should I
be seeing a connection for my 1394 card as well?  I did come across a MS KB
article (KB317812) that spoke to this, but I'm unsure if this is the same
issue or even related.

I look forward to a reply...hopefully the MS staff or other users can shed
some light on this.  My advance thanks to any and all that respond.

Regards,
Jeff Michel
Crushed Pickle Studio
Estevan, SK, Canada

Author
19 Oct 2006 1:26 PM
Lanwench [MVP - Exchange]
In news:7C686971-9C34-49F3-94B4-EEFA43B4DA84@microsoft.com,
Crushed Pickle Studio <crushedpickle(nospam)@sasktel.net> typed:
> Good morning:
>
> I have just recently built a new PC with the following Specs:
>
> 2 - AMD Opteron 265
> Tyan Tiger K8WE Motherboard (w/onboard 1394)
> 2 GB Corsair Ram
> nVidia 6600 PCIe Graphics Card
> WinXP Pro SP2
>
> My issue lies in the fact that in the Device Manager under Network
> Adapters there is the yellow "information" indicator telling me that
> there is some sort of problem.

What is it complaining about specifically?

Show quoteHide quote
> There have been a number of us that
> have built the exact same machine (down to the letter) and it appears
> that all others are working so far.  Aside from XP sp2, the only
> other installed drivers are the nVidia Platform driver v6.70, and the
> nVidia Graphics drivers v81.98.  To my knowledge the other machines
> that have been built have not applied any hotfixes or anything...just
> the bare SP2 install.
>
> The onboard 1394 is enabled in the BIOS and the Fireware Adapter
> shows no conflicts.  There are no IRQ conflicts.
>
> All indications show that it should be working, however, in  the
> Control Panel under Network Connections, I only see my Ethernet
> Connection.  Should I be seeing a connection for my 1394 card as
> well?

Yes, but do you actually need this at all?
Have you looked at the mobo mfr's website for drivers?


Show quoteHide quote
>  I did come across a MS KB article (KB317812) that spoke to
> this, but I'm unsure if this is the same issue or even related.
>
> I look forward to a reply...hopefully the MS staff or other users can
> shed some light on this.  My advance thanks to any and all that
> respond.
>
> Regards,
> Jeff Michel
> Crushed Pickle Studio
> Estevan, SK, Canada
Author
19 Oct 2006 2:30 PM
Crushed Pickle Studio
Lanwench:

> What is it complaining about specifically?

The error code that comes up is Error Code 10...telling me that the device
cannot start.  So if I was hoping to connect two machines together via
Firewire to form a mini-network within my home LAN, I couldn't due to the
fact that the Network adapter portion of my Firewire isn't running.

> Yes, but do you actually need this at all?
> Have you looked at the mobo mfr's website for drivers?

I don't necessarily need this functionality, however what I find strange is
that of the 10-15 others that have buit the exact same machine, no one else
has run into this error yet.  We all have been working off the exact same
parts list, exact same BIOS revision, and following the exact installation
steps.

None of us have installed any of the motherboard's drivers as they seem to
introduce conflicts.  Strangely enough the CD that comes with the mobo
doesn't contain the the proper nVidia chipset drivers.

Because these machines are being built for Digital Recording Studios,
stability is of the utmost importance and before I start to install the
remaining apps, I want to make sure I have an error and conflict-free OS.

Can you look into the hotfix listed in KB317812 and see if it would apply to
this situation...if nothing else I may be interested in downloading it to try
it out, but it isn't available for public download.

I look forward to your reply.

Regards,
Jeff Michel
Crushed Pickle Studio
Estevan, SK, Canada


Show quoteHide quote
"Lanwench [MVP - Exchange]" wrote:

> In news:7C686971-9C34-49F3-94B4-EEFA43B4DA84@microsoft.com,
> Crushed Pickle Studio <crushedpickle(nospam)@sasktel.net> typed:
> > Good morning:
> >
> > I have just recently built a new PC with the following Specs:
> >
> > 2 - AMD Opteron 265
> > Tyan Tiger K8WE Motherboard (w/onboard 1394)
> > 2 GB Corsair Ram
> > nVidia 6600 PCIe Graphics Card
> > WinXP Pro SP2
> >
> > My issue lies in the fact that in the Device Manager under Network
> > Adapters there is the yellow "information" indicator telling me that
> > there is some sort of problem.
>
> What is it complaining about specifically?
>
> > There have been a number of us that
> > have built the exact same machine (down to the letter) and it appears
> > that all others are working so far.  Aside from XP sp2, the only
> > other installed drivers are the nVidia Platform driver v6.70, and the
> > nVidia Graphics drivers v81.98.  To my knowledge the other machines
> > that have been built have not applied any hotfixes or anything...just
> > the bare SP2 install.
> >
> > The onboard 1394 is enabled in the BIOS and the Fireware Adapter
> > shows no conflicts.  There are no IRQ conflicts.
> >
> > All indications show that it should be working, however, in  the
> > Control Panel under Network Connections, I only see my Ethernet
> > Connection.  Should I be seeing a connection for my 1394 card as
> > well?
>
> Yes, but do you actually need this at all?
> Have you looked at the mobo mfr's website for drivers?
>
>
> >  I did come across a MS KB article (KB317812) that spoke to
> > this, but I'm unsure if this is the same issue or even related.
> >
> > I look forward to a reply...hopefully the MS staff or other users can
> > shed some light on this.  My advance thanks to any and all that
> > respond.
> >
> > Regards,
> > Jeff Michel
> > Crushed Pickle Studio
> > Estevan, SK, Canada
>
>
>
>
Author
19 Oct 2006 3:10 PM
Lanwench [MVP - Exchange]
In news:6322A3B6-CC1B-4291-96E5-9DA04F7E7A34@microsoft.com,
Crushed Pickle Studio <crushedpickle(nospam)@sasktel.net> typed:
> Lanwench:
>
>> What is it complaining about specifically?
>
> The error code that comes up is Error Code 10...telling me that the
> device cannot start.  So if I was hoping to connect two machines
> together via Firewire to form a mini-network within my home LAN

Why not use Ethernet cards for this, just out of curiosity?

Show quoteHide quote
> , I
> couldn't due to the fact that the Network adapter portion of my
> Firewire isn't running.
>
>> Yes, but do you actually need this at all?
>> Have you looked at the mobo mfr's website for drivers?
>
> I don't necessarily need this functionality, however what I find
> strange is that of the 10-15 others that have buit the exact same
> machine, no one else has run into this error yet.  We all have been
> working off the exact same parts list, exact same BIOS revision, and
> following the exact installation steps.
>
> None of us have installed any of the motherboard's drivers as they
> seem to introduce conflicts.  Strangely enough the CD that comes with
> the mobo doesn't contain the the proper nVidia chipset drivers.
>
> Because these machines are being built for Digital Recording Studios,
> stability is of the utmost importance and before I start to install
> the remaining apps, I want to make sure I have an error and
> conflict-free OS.
>
> Can you look into the hotfix listed in KB317812 and see if it would
> apply to this situation...if nothing else I may be interested in
> downloading it to try it out, but it isn't available for public
> download.

Hmmm - I've never seen this myself, and for any hotfix like this you'd need
to call MS to get it.

I'm not sure this will resolve your problem, tho. The device is not showing
up properly in device manager, which to me, indicates a driver problem - or,
a hardware problem. Perhaps your mobo is not 100% identical to the ones
you've compared it to.... or, perhaps you've got gremlins. It's hard to say.

If you're incredibly wary about changing *anything* after all the work
you've put into the install already, what about imaging the system (I like
Acronis, a lot) and then installing the (correct) driver? Of course, you can
roll back a driver change, and you also have system restore, but if you're a
belt-and-suspenders fellow, an image backup might be a good plan.

Show quoteHide quote
>
> I look forward to your reply.
>
> Regards,
> Jeff Michel
> Crushed Pickle Studio
> Estevan, SK, Canada
>
>
> "Lanwench [MVP - Exchange]" wrote:
>
>> In news:7C686971-9C34-49F3-94B4-EEFA43B4DA84@microsoft.com,
>> Crushed Pickle Studio <crushedpickle(nospam)@sasktel.net> typed:
>>> Good morning:
>>>
>>> I have just recently built a new PC with the following Specs:
>>>
>>> 2 - AMD Opteron 265
>>> Tyan Tiger K8WE Motherboard (w/onboard 1394)
>>> 2 GB Corsair Ram
>>> nVidia 6600 PCIe Graphics Card
>>> WinXP Pro SP2
>>>
>>> My issue lies in the fact that in the Device Manager under Network
>>> Adapters there is the yellow "information" indicator telling me that
>>> there is some sort of problem.
>>
>> What is it complaining about specifically?
>>
>>> There have been a number of us that
>>> have built the exact same machine (down to the letter) and it
>>> appears that all others are working so far.  Aside from XP sp2, the
>>> only other installed drivers are the nVidia Platform driver v6.70,
>>> and the nVidia Graphics drivers v81.98.  To my knowledge the other
>>> machines that have been built have not applied any hotfixes or
>>> anything...just the bare SP2 install.
>>>
>>> The onboard 1394 is enabled in the BIOS and the Fireware Adapter
>>> shows no conflicts.  There are no IRQ conflicts.
>>>
>>> All indications show that it should be working, however, in  the
>>> Control Panel under Network Connections, I only see my Ethernet
>>> Connection.  Should I be seeing a connection for my 1394 card as
>>> well?
>>
>> Yes, but do you actually need this at all?
>> Have you looked at the mobo mfr's website for drivers?
>>
>>
>>>  I did come across a MS KB article (KB317812) that spoke to
>>> this, but I'm unsure if this is the same issue or even related.
>>>
>>> I look forward to a reply...hopefully the MS staff or other users
>>> can shed some light on this.  My advance thanks to any and all that
>>> respond.
>>>
>>> Regards,
>>> Jeff Michel
>>> Crushed Pickle Studio
>>> Estevan, SK, Canada
Author
19 Oct 2006 5:10 PM
Crushed Pickle Studio
As a matter of fact, I have Acronis TrueImage and have been making images of
the install thus far.  Funny that you would mention that.

As for the ethernet connectivity issue...I would be more inclined to use
ethernet to network machines, but I just figured that everything whould work
out of the box.  (And yes, in my world the sky is blue, too...hehe)

If all else fails, I can disable the onboard 1394 and purchase a standalone
network adapter from SIIG or ADS.  Those are the only two tested to work with
the software that I'll be using.

I will contact MS about the hotfix and see if that helps any.  There's no
way that you can provide that for me?

Thank you for you assistance.

Regards,
Jeff Michel
Crushed Pickle Studio
Estevan, SK, Canada


Show quoteHide quote
"Lanwench [MVP - Exchange]" wrote:

> In news:6322A3B6-CC1B-4291-96E5-9DA04F7E7A34@microsoft.com,
> Crushed Pickle Studio <crushedpickle(nospam)@sasktel.net> typed:
> > Lanwench:
> >
> >> What is it complaining about specifically?
> >
> > The error code that comes up is Error Code 10...telling me that the
> > device cannot start.  So if I was hoping to connect two machines
> > together via Firewire to form a mini-network within my home LAN
>
> Why not use Ethernet cards for this, just out of curiosity?
>
> > , I
> > couldn't due to the fact that the Network adapter portion of my
> > Firewire isn't running.
> >
> >> Yes, but do you actually need this at all?
> >> Have you looked at the mobo mfr's website for drivers?
> >
> > I don't necessarily need this functionality, however what I find
> > strange is that of the 10-15 others that have buit the exact same
> > machine, no one else has run into this error yet.  We all have been
> > working off the exact same parts list, exact same BIOS revision, and
> > following the exact installation steps.
> >
> > None of us have installed any of the motherboard's drivers as they
> > seem to introduce conflicts.  Strangely enough the CD that comes with
> > the mobo doesn't contain the the proper nVidia chipset drivers.
> >
> > Because these machines are being built for Digital Recording Studios,
> > stability is of the utmost importance and before I start to install
> > the remaining apps, I want to make sure I have an error and
> > conflict-free OS.
> >
> > Can you look into the hotfix listed in KB317812 and see if it would
> > apply to this situation...if nothing else I may be interested in
> > downloading it to try it out, but it isn't available for public
> > download.
>
> Hmmm - I've never seen this myself, and for any hotfix like this you'd need
> to call MS to get it.
>
> I'm not sure this will resolve your problem, tho. The device is not showing
> up properly in device manager, which to me, indicates a driver problem - or,
> a hardware problem. Perhaps your mobo is not 100% identical to the ones
> you've compared it to.... or, perhaps you've got gremlins. It's hard to say.
>
> If you're incredibly wary about changing *anything* after all the work
> you've put into the install already, what about imaging the system (I like
> Acronis, a lot) and then installing the (correct) driver? Of course, you can
> roll back a driver change, and you also have system restore, but if you're a
> belt-and-suspenders fellow, an image backup might be a good plan.
>
> >
> > I look forward to your reply.
> >
> > Regards,
> > Jeff Michel
> > Crushed Pickle Studio
> > Estevan, SK, Canada
> >
> >
> > "Lanwench [MVP - Exchange]" wrote:
> >
> >> In news:7C686971-9C34-49F3-94B4-EEFA43B4DA84@microsoft.com,
> >> Crushed Pickle Studio <crushedpickle(nospam)@sasktel.net> typed:
> >>> Good morning:
> >>>
> >>> I have just recently built a new PC with the following Specs:
> >>>
> >>> 2 - AMD Opteron 265
> >>> Tyan Tiger K8WE Motherboard (w/onboard 1394)
> >>> 2 GB Corsair Ram
> >>> nVidia 6600 PCIe Graphics Card
> >>> WinXP Pro SP2
> >>>
> >>> My issue lies in the fact that in the Device Manager under Network
> >>> Adapters there is the yellow "information" indicator telling me that
> >>> there is some sort of problem.
> >>
> >> What is it complaining about specifically?
> >>
> >>> There have been a number of us that
> >>> have built the exact same machine (down to the letter) and it
> >>> appears that all others are working so far.  Aside from XP sp2, the
> >>> only other installed drivers are the nVidia Platform driver v6.70,
> >>> and the nVidia Graphics drivers v81.98.  To my knowledge the other
> >>> machines that have been built have not applied any hotfixes or
> >>> anything...just the bare SP2 install.
> >>>
> >>> The onboard 1394 is enabled in the BIOS and the Fireware Adapter
> >>> shows no conflicts.  There are no IRQ conflicts.
> >>>
> >>> All indications show that it should be working, however, in  the
> >>> Control Panel under Network Connections, I only see my Ethernet
> >>> Connection.  Should I be seeing a connection for my 1394 card as
> >>> well?
> >>
> >> Yes, but do you actually need this at all?
> >> Have you looked at the mobo mfr's website for drivers?
> >>
> >>
> >>>  I did come across a MS KB article (KB317812) that spoke to
> >>> this, but I'm unsure if this is the same issue or even related.
> >>>
> >>> I look forward to a reply...hopefully the MS staff or other users
> >>> can shed some light on this.  My advance thanks to any and all that
> >>> respond.
> >>>
> >>> Regards,
> >>> Jeff Michel
> >>> Crushed Pickle Studio
> >>> Estevan, SK, Canada
>
>
>
>