Code 10

[__earth]

My ethernet card suddenly died out on me about a day ago. I'm not sure what happened but it gives out a code 10 (the device can't start).

I've uninstalled and reinstalled but that doesn't work. Planning to physically remove the card and then install it back soon. Not sure that will work.

i've read somewhere that I need to do something with the bios but I think that's too much. Also, some other forum says code 10 is not really descriptive in nature, which is a big problem.

Any of you familiar with this issue?

If this doesn't work, I'm planning to get a new ethernet card since that card is usually cheap.

[Thirdshifter]

its the driver. do you an older version of the driver? window will keep installing the new screwed up driver. you have to manually locate the driver to installed.

[__earth]

done that and it won't work. and i dont think its the driver because the driver itself is the latest.

[digimushu]

could be irq conflict. switch PCI slots and see whether it will work.

[Thirdshifter]

done that and it won't work. and i dont think its the driver because the driver itself is the latest.

What i meant was, install the last working driver. Try resitting the Card this might do the trick as well.

Take the card out, reboot windows. Shutdown, put card back in and reboot window. Add new hardware.

[qedx]

heh i thought the topic was about the hair cream :D. maybe a power surge knocked it out... i have been a bit paranoid about power surges the last few days, sorry.

get a new one. it's gonna set you back mmm $10?

[__earth]

could be irq conflict. switch PCI slots and see whether it will work.

If I switched, the whole system won't start, of which, is not fun.

What i meant was, install the last working driver. Try resitting the Card this might do the trick as well.

Take the card out, reboot windows. Shutdown, put card back in and reboot window. Add new hardware.

Done that too. that error won't go away.

get a new one. it's gonna set you back mmm $10?

Done that. Placed the order two days ago.

And now I realized how internet-dependent I am. I can't do anything without the internet. Even my accounting homework is messed out without the internet. I almost missed an appointment with my professor. I almost missed student meetings. I can't even loiter at wikipedia!

It's like missing a limp or something. or \maybe I should get out more but it's snowing outside! It's not that I have an option!

[__earth]

Got a new card. The card seems to be working but I'm not sure whether it was the slot or the old card.

When I first stuck the new card up the old slot's throat, the system didn't recognize it. After a new reboot, it was the same thing. Then, I switched slot, it was the same thing yet again until I hard reboot it.

Problem solved, not the problem is still unknown. =|

hey digi, could you explain more about the IRQ thing?

[digimushu]

every hardware device on yur comp is assigned an IRQ...

from microsoft, about how OSs 'share' IRQs...


In Windows, some or all of the devices on your ACPI motherboard may be listed when you view the resources in Device Manager as using the same IRQ (IRQ 9) (to view the list of resources click either Resources by type, or Resources by connection on the View menu). You cannot change the IRQ setting because the setting is unavailable. This occurs because Windows takes advantage of the ACPI features of the motherboard, including advanced PCI sharing. IRQ 9 is used by the PCI bus for IRQ steering. This feature lets you add more devices without generating IRQ conflicts.

Note that Windows 2000 does not have the ability to rebalance resources in the same way that Microsoft Windows 98 does. After PCI resources are set, they generally cannot be changed. If you change to an invalid IRQ setting or I/O range for the bus that a device is on, Windows 2000 cannot rebalance the resource it assigned to that bus to compensate. Windows 2000 does not have this ability because of the more complex hardware schemas it is designed to support. Windows 98 does not have to support IOAPICs, multiple root PCI buses, multiple-processor systems, and so on. Rebalancing becomes risky when you are dealing with these hardware schemas, and will not be implemented in Windows 2000 except for very specific scenarios. However, PCI devices are required to be able to share IRQs. The ability to share IRQs should not prevent any hardware from working in general.

The Plug and Play operating system settings in the computer's BIOS should not affect how Windows handles the hardware in general. However, Microsoft recommends that you set this setting to "No" or "Disabled" in the computer's BIOS. For information about viewing or modifying your computer's BIOS settings, consult your computer's documentation or manufacturer.

Manually assigning IRQs to PCI slots in the System BIOS as a troubleshooting method may work on some non-ACPI systems when using a standard PC HAL, but these settings are ignored by Plug and Play in Windows if ACPI support is enabled. If you need to manually assign IRQ addresses through the BIOS to a device on an ACPI motherboard, you will need to re-install Windows to force the installation to use a Standard PC HAL. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:


...unfortunately IRQ conflicts still happens