Resource hogging is a term when one single application or few of them are taking all system resources for themself causing extreme slow down in the computer and nonresponsiveness. It can be a very frustrating and time-consuming experience and it can cost you money if you can not finish work on time due to this effect.
I believe that everyone has experienced at least one slowdown in their IT carrier because of resource-hogging applications and most users do not know how to deal with this. We are here to help you with this issue.
Just to be aware that this method shown here is not a method to miraculously speed up your PC or anything similar, this is to be able to detect and recover from extreme slowdowns. Hardware components are still very important and if you can upgrade your computer if it is outdated, please do it because new applications will require a more modern system, and not any kind of tips and tricks will save you from outdated hardware.
Now when we got that out of the way let's talk about slowdowns, it is no secret that sometimes an application has bugs and memory leaks that can cause this kind of behavior, and sometimes the application simply takes up too much memory for any other application to work normally. The most simple and straightforward way is to bring up a Windows task manager and inspect running applications and services.
You can bring task manager by the key combination of CTRL + SHIFT + ESC
If the system is in deep memory deficit you will have to wait for the task manager to open and show itself on-screen. Once opened, click on more details if that view is not opened by default. Once the view expands you will see all running applications with how much RAM memory have they taken and how much CPU they are using.
Now you are presented with a choice on what to do with the problematic application. If you press the end task button on the bottom right, Windows will kill the application and its processes but any unsaved work inside the application will be lost and unrecoverable in most cases. Or you can try to remove smaller applications running to free up more memory and CPU in order for the computer to catch up.
Any choice you make is up to you, but be very careful not to kill Windows essential service by mistake, that will cause immediate system instability with high chances of a system crash.

Restart graphic drivernet stop wuauserv net start cryptSvc net start bits net start msiserver
net start wuauserv net start cryptSvc net start bits net start msiserver


The true cause is that there is no working Border Gateway Protocol (BGP) routes into Facebook's sites. BGP is the standardized exterior gateway protocol used to exchange routing and reachability information between the internet top-level autonomous systems (AS). Most people, indeed most network administrators, never need to deal with BGP.
Cloudflare VP Dane Knecht was the first to report the underlying BGP problem. This meant, as Kevin Beaumont, former Microsoft's Head of Security Operations Centre, tweeted,
"By not having BGP announcements for your DNS name servers, DNS falls apart = nobody can find you on the internet. Same with WhatsApp btw. Facebook has basically de-platformed themselves from their own platform."
Many people are very annoyed by this and with the fact that they cannot use their social media platforms but it seems that Facebook employees are in even bigger annoyance as it was reported that Facebook employees can't enter their buildings because their "smart" badges and doors were also disabled by this network failure. If true, Facebook's people literally can't enter the building to fix things.
Reddit user u/ramenporn, who claimed to be a Facebook employee working on bringing the social network back from the dead, reported, before he deleted his account and his messages:
"DNS for FB services has been affected and this is likely a symptom of the actual issue, and that's that BGP peering with Facebook peering routers has gone down, very likely due to a configuration change that went into effect shortly before the outages happened (started roughly 1540 UTC). There are people now trying to gain access to the peering routers to implement fixes, but the people with physical access is separate from the people with knowledge of how to actually authenticate to the systems and people who know what to actually do, so there is now a logistical challenge with getting all that knowledge unified. Part of this is also due to lower staffing in data centers due to pandemic measures."
Ramenporn also stated that it wasn't an attack, but a mistaken configuration change made via a web interface.
Both BGP and DNS are down, the "connection to the outside world is down, remote access to those tools don't exist anymore, so the emergency procedure is to gain physical access to the peering routers and do all the configuration locally."
Technicians on site don't know how to do that and senior network administrators aren't on site.
It seems that it will all be down for a couple of more hours before the issue is resolved. chkdsk /f /r