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.


Windows 2000 Pro (as server) looses Network Connection

  • Please log in to reply
1 reply to this topic

#1 Shandley


  • Members
  • 166 posts
  • Local time:04:24 AM

Posted 28 March 2013 - 09:15 AM



I have a Windows 2000 Pro machine (SP...4 or whatever the latest is) that will suddenly without cause (so it seems) drop a load of Event ID: 2019 every minute on the second.


Actually what I first noticed was the error 2021 at 4:31:33, then error 2019 at 4:32:33, then 2021 the next minute, then 2019 the next minute. This happened 11 times each before it was strictly 2019. These errors stopped at 5:28:33.


I use this machine as a server and nothing else. Nothing domain, just users.


I'm curious to know what would cause this. Reading the microsoft articles, I seem to have everything in check but just in case, if you have one in mind you didn't randomly pull up on google, fire away!


No one was logged in and using at that time.


Any ideas?


Thanks in advance,


BC AdBot (Login to Remove)


#2 Sneakycyber


    Network Engineer

  • BC Advisor
  • 6,136 posts
  • Gender:Male
  • Location:Ohio
  • Local time:07:24 AM

Posted 08 April 2013 - 08:26 PM

Since I wasn't familiar with the exact error code and without any additional information. My google search lead me to a possible memory leak, or bad memory. There is an extensive blog on MSDN located HERE that goes in depth on how to locate the offending driver/resource. I would also run http://www.memtest.org/ To rule out an actual memory problem. If you have more information from the eventviewer logs that point to a different problem, or you yourself have read the above mentioned article and found it not helpful Please let me know :thumbsup2:

Edited by Sneakycyber, 08 April 2013 - 08:28 PM.

Chad Mockensturm 
Network Engineer
Certified CompTia Network +, A +

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users