Solved Internet problem after Windows 8.1 "Upgrade"

Greetings computer Gods and technology Wizards.
I have been getting intermittent internet connection problems after my computer "automatically" upgraded to windows 8.1
It occurs at very random times and I don't really notice a "trigger" that starts it to happen. I've taken screenshots and will post them below:



^ This is what I sometimes get when I try to load websites.
Opening up the details get me this:

I open up the troubleshooting tool and diagnose every option. Once I get to Hardware and Devices

I get this window

...
I've tried the DISM /Online /Cleanup-Image /Scanhealth thingy but it found nothing.
sfc scannnow didn't find anything either...
Has anybody encountered this yet?
Any possible fixes?

Looks like you've got some driver issues to sort out. Try that first and then come back if the problem doesn't go away.

Hi asvent. Thanks for replying. I have tried what you recommended and will test it out for a few days.
I will mark the thread as solved when the problem is gone.
And sorry if I started this thread in the wrong section... I didn't see the network sharing forum.

Error 4227

I've been battling the same problem for quite a while. The only way I've re-established the internet connection is by logging out of the Win user account, then log back in (reboot not necessary). Highly annoying.

Please go to your event viewer and see if it lists Error 4227 around the time of the interruption. That error lists this message:

TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. This error typically occurs when outgoing connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection. To minimize the risk of data corruption, the TCP/IP standard requires a minimum time period to elapse between successive connections from a given local endpoint to a given remote endpoint.

Click to expand...

Unfortunately I don't have much help at this point. I've done some research including this old Windows 8 thread that was never resolved.
http://www.eightforums.com/network-...ps-allowing-new-connections-3.html#post306663

No resolution at DSLR Reports, but interesting registry info:
[Windows] TCP/IP Error with Event ID 4227 - Networking | DSLReports Forums

Reducing the registry setting for TcpTimedWaitDelay sounded promising in the next link, but that setting does not appear in Win 8.1 registry.
Windows Server tcp port starvation problem | IT training day

So I'm also asking the computer Gods and technology Wizards for help with the same situation....

On edit: Researching this further, the following link may provide access to the required registry settings. I haven't tried it yet. Will be adding lots of System Restore points for these fixes. Possibly a disc image too, this may be over my head... Anyone have experience with these registry tweaks?
Event ID 4227 | The Regime

Hi LanDroid. I have checked my event viewer and noticed that I get Event ID "1014 DNS Client Events" whenever the internet stops connecting. I didn't see see Event ID 4227 in event viewer. Though with my particular case; the internet eventually starts working again if I wait a few minutes.

Well I s'pose you're lucky if it comes back that quickly, mine does not. I've been ignoring this for too long my family informs me (more on that later perhaps) so I'll keep chipping away at it...

I've battled many viruses, malware, spybots, trojans, phishers and infections before. I'm currently on my second laptop. I'm not always lucky. I'll pay that thread a visit so this one doesn't go off topic.

So back to my internet problem. After researching Tweakbit Driver Updater I found some negative reviews about it like "all drivers being miraculously being up to date after paying $30". I've asked my tech savvy cousin about it, he said he's never heard of it and advised me to try spybot search and destroy first. Paying $30 to update all my drivers is something I'll leave as a last resort. Plus my HP support assistant says everything is up to date. Driver Updater says otherwise. That discrepancy in information is making feel cautious. Have you tested this product before, asvent?
Driver update and Driver updater are two different things, right?

Update: SpyBot Search and Destroy fixed the problem. Turns out some tracking cookies were messing with my computer processes[mainly internet connectivity].

Thanks to everybody who helped me.

Error 4227

Well I finally worked up the nerve to mod the registry per the following instructions, using a value of 30 for the added key TcpTimedWaitDelay. (After restore point and registry back up.) We'll see if that stops my problem with Error 4227.

• Reduce the client TCP/IP socket connection timeout value from the default value of 240 seconds
  • Start Registry Editor.
  • Browse to, and then click the following key in the registry:
    
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
  • On the Edit menu, click New, DWORD Value, and then add the following registry value to reduce the length of time that a connection stays in the TIME_WAIT state when the connection is being closed. While a connection is in the TIME_WAIT state, the socket pair cannot be reused:
    
    

    Value name	TcpTimedWaitDelay
    Value data	<Enter a decimal value between 30 and 240 here>

  • Close Registry Editor.
    
    

    You must restart your computer for this change to take effect.

  • The valid range of this value is 30 through 300 (decimal). The default value is 240.
  • Source: Avoiding TCP/IP Port Exhaustion

Click to expand...