Networking & Wireless forum

General discussion

Network controller suddenly stops working

Hi all. I turned on my computer this morning and was greeted by the new found hardware wizard. Apparently XP decided to stop recognizing my network card. Device manager showed the yellow question mark. I resolved the issue but my curiosity got the best of me. I can't help but wonder what happened since I was last at my computer. I didn't install any new programs or hardware, and don't even use the card. Any ideas?

Discussion is locked
You are posting a reply to: Network controller suddenly stops working
The posting of advertisements, profanity, or personal attacks is prohibited. Please refer to our CNET Forums policies for details. All submitted content is subject to our Terms of Use.
Track this discussion and email me when there are updates

If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.

You are reporting the following post: Network controller suddenly stops working
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
Collapse -

In reply to: Network controller suddenly stops working

I guess I'm just wondering if it's common or known for windows to just all of a sudden stop recognizing a component/driver for no apparent reason. As I mentioned, I did finally solve the problem but I'd really like to know what caused it. I'm a bit of a compulsive :/

Collapse -
I've had similar happen

In reply to: .

You said you solved it but didn't mention how. That might be the best clue you could offer to get an answer. Any such will be speculative. A corrupt driver, something in the BIOS that's changed, even an automatic driver update that happened without your knowing, if it was the wrong driver, could cause this. You could look for a clue in Start/Settings/Network Connections and see if the name is different. It might say something like "Local Area Connection2" rather than "Local Area Connection".

Popular Forums

Computer Newbies 10,686 discussions
Computer Help 54,365 discussions
Laptops 21,181 discussions
Networking & Wireless 16,313 discussions
Phones 17,137 discussions
Security 31,287 discussions
TVs & Home Theaters 22,101 discussions
Windows 7 8,164 discussions
Windows 10 2,657 discussions


Best Black Friday Deals

CNET editors are busy culling the list and highlighting what we think are the best deals out there this holiday season.