all networking devices - code 31 (device manager)

  • Thread starter Thread starter Marco Della Rocca
  • Start date Start date
M

Marco Della Rocca

Hi all,

I'm on vacation and at home all computers seem to run mad ;) -- and
hopefully someone can help me, to solve this, so I do not have to end my
vacation before time....

A windows 2000 machine crashed two days ago (normaly stable as a rock and
24/7 running with restarts only after updates). After restart, all
networking devices had a yellow exclamation mark in device manager and
stated error code 31 (a depending driver could not be started, I think).

OK, my first suggestion was, to install a different NIC (3COM 905TX).
Without a problem this was added and drivers were added automatically, but
like all other devices, this one shows a yellow exclamation mark with error
code 31. - So reinstallation of drivers seems to be no option.

I think the problem lies somewhere in the registry.

I've found error 31 on the net mostly in combination with non working CD /
DVD devices (registry problem in combination with some burning software) and
solutions for this. But I found also some cases with affected networking
devices, but not a single solution for this, only questions, no answers.

This computer needs to be on the net and reinstallation is not an option, as
long, as I'm not in office. So every offer for a solution (even commercial
ones) are very much appreciated.


Best regards

Marco Della Rocca

(- temporary vacation mail address -)
http://www.digi-buy.de
http://www.digital-freedom.de
 
Try deleting all network adapters in Device Manager and rebooting. When
it it reboots it will automatically find the 'new' hardware and install
drivers. I've used this on several computers to cure various file
sharing, etc. network access issues including one last week where it was
only one computer that it couldn't find, others on the network were
fine. Of course the one it couldn't find was the one that had shared
files on it that were required.
Hi all,

I'm on vacation and at home all computers seem to run mad ;) -- and
hopefully someone can help me, to solve this, so I do not have to end my
vacation before time....

A windows 2000 machine crashed two days ago (normaly stable as a rock and
24/7 running with restarts only after updates). After restart, all
networking devices had a yellow exclamation mark in device manager and
stated error code 31 (a depending driver could not be started, I think).

OK, my first suggestion was, to install a different NIC (3COM 905TX).
Without a problem this was added and drivers were added automatically, but
like all other devices, this one shows a yellow exclamation mark with error
code 31. - So reinstallation of drivers seems to be no option.

I think the problem lies somewhere in the registry.

I've found error 31 on the net mostly in combination with non working CD /
DVD devices (registry problem in combination with some burning software) and
solutions for this. But I found also some cases with affected networking
devices, but not a single solution for this, only questions, no answers.

This computer needs to be on the net and reinstallation is not an option, as
long, as I'm not in office. So every offer for a solution (even commercial
ones) are very much appreciated.


Best regards

Marco Della Rocca

(- temporary vacation mail address -)
http://www.digi-buy.de
http://www.digital-freedom.de
Click to expand...
 
Thanks Rod,

but reinstallation of drivers is not a working option in this case, just the
same like adding completely new adapters. Drivers will install without a
problem, but all networking devices still show error code 31, it must be a
problem somewhere deeper (the registry could be corrupted, I think).

Best regards

Marco Della Rocca

(- temporary vacation mail address -)
http://www.digi-buy.de
http://www.digital-freedom.de
 
I am having exactly the same problem with my Windows 2000 Server
installation, Marco. My own searching turned up Knowledgebase article
#306983 which advises deleting several registry entries related to installed
network adapters. In my case, the same problems persist even after doing so.
If you have found a solution, please post!
 
MS networking blackbelts:
Any other ideas about how to troubleshoot this show-stopping problem?
 
Back
Top