Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

intel ethernet connection i218-v glitches on startup


  • Please log in to reply
3 replies to this topic

#1 Justin711

Justin711

  • Members
  • 76 posts
  • OFFLINE
  •  
  • Local time:12:08 PM

Posted 03 November 2016 - 05:29 PM

Every once and awhile my Intel Ethernet Connection i218-v glitches on startup, and i have to disable it and re-enable it. It's not a major problem, but is there a way to fix this? Thanks in advance.



BC AdBot (Login to Remove)

 


#2 technonymous

technonymous

  • Members
  • 2,516 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:08 AM

Posted 03 November 2016 - 05:46 PM

Hi, justin711,

 

Which Windows OS are you using? Sounds like you need a driver update. I would suggest first going to start | run and typing in devmgmt.msc open device manager. Under network adapaters right-click and choose uninstall. Reboot the system. See if that fixes it. If you still have problems you have to Google search for a driver.



#3 Justin711

Justin711
  • Topic Starter

  • Members
  • 76 posts
  • OFFLINE
  •  
  • Local time:12:08 PM

Posted 03 November 2016 - 05:51 PM

I'm on Windows 10. It worked on this reboot, if I get the problem again I'll post again. Thanks!


Edited by Justin711, 03 November 2016 - 05:51 PM.


#4 technonymous

technonymous

  • Members
  • 2,516 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:08 AM

Posted 03 November 2016 - 06:00 PM

Not a problem. If you upgraded to Win10, it was probably using a old driver that was causing things to go bonkers. Good luck!






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users