![]() ![]() This is the service host, a process that's used to run several Windows services. ![]() Your list of processes should contain many called svchost.exe (if not, then you've not clicked "Show processes from all users"). RAM HOGS: Find out which programs are hogging your RAM in seconds You'll immediately get a good feel for where your RAM is going, and which programs (if any) you need to close or tweak to get some of it back. Now click the "Memory (Private Working Set)" column header so the largest figures are at the top. It's a little more reliable than the Working Set alone, but really you need to see both. It will almost certainly consume additional RAM, though, so this figure tends to underestimate memory use. The second, "Memory - Private Working Set" shows you how much physical memory this process alone is using (that is, it can't shared with anyone else). Some of this RAM may be shared by other processes, though (shared DLLS, for instance) so this figure tends to overestimate memory use. The first, "Memory - Working Set" shows you how much physical memory is currently being taken up by each process. You'll now see two estimates for your processes use of RAM. To find out, click the Processes tab, then click View > Select Columns, and ensure Memory - Working Set and Memory - Private Working Set are checked. It's often interesting to see which programs are using all your RAM. Don't use the "End Process" on anything unless you're 110% sure that it's safe to do so, though - terminating something system-critical can lock up or crash your PC immediately. Much the same problem can happen with other applications, so if something won't start, or is just misbehaving, then it's always a good idea to look for previous instances of the program. Right-click it in Task Manager, select End Process, and once it's shut down you should be able to start Media Player as normal. If you find one, and there's no window, then it's probably crashed. If you find Windows Media Player won't launch, then, fire up Task Manager, click the Processes tab and look for a WMPlayer.exe process. Then, when you come to restart the program, nothing will happen because it's blocked by the crashed copy in RAM. Occasionally it'll crash without having any visible window, though, so you won't see there's a problem. ![]() ![]() Windows Media Player is known to crash from time to time (you may have noticed this). ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |