Elk merkt u van tijd tot tijd op dat uw harde aandrijving extra hard werkt voor wat als geen reden schijnt. Een achtergrondproces heeft uw harde aandrijvingsgijzelaar genomen, die het dwingt om luid te geselen aangezien het om omhoog met het hoge tarief van worstelt te houden leest en schrijft. Uw computer antwoordt langzaam aangezien het proces de fysieke beperkingen van uw aandrijving overbelast. Wat bent u om te doen?

De oplossing is eenvoudig, hoewel een weinig netelig af en toe: identificeer en houd het proces tegen dat uw aandrijving doodt. Er zijn twee methodes en hulpmiddelen die u kunt gebruiken om het proces te identificeren. (meer…)

computer, schijf verrichtingen, de ontdekkingsreiziger van het downloadproces, onderaan pijl, Bestuurders, ontdekkingsreiziger 2, Hardware, harde aandrijving, gijzelaar, menubar, prestaties lusje, processen, betrouwbaarheid, antwoordt, strijd, sysinternals

Eerder (Deel 1: Inleiding - wat gebruikt mijn cpu?), schopte ik van wat ik verwacht dat is een meerdelige reeks bij het bepalen van wat de bovenmatige consumptie van cpu veroorzaakt, buiten normaal „die het proces de hoogste waarde in de kolom van cpu in de Manager van de Taak“ heeft.

Alvorens ik in dingen krijg, kan een weinig achtergrond nuttig blijken of mild onderhoudend. Over op „Forums Sysinternals“, waren er onlangs twee gelijkaardige problemen die beide het geïmpliceerdez bovenmatige gebruik van cpu dat niet toe te schrijven aan een specifiek proces was. I became involved in both problems and attempted to use similar techniques to get additional information with the hopes of ultimately being able to pinpoint the problem. What may make this mildly entertaining is that in both cases, there was limited or no success in detetmining the cause of or solution to the problem. In the end, one problem was resolved by disabling the floppy disk controller, and the other problem appears to be as of yet unresolved. (In the latter case, the poster did admit that the system was experiencing hardware problems - the chipset fan was dying and there...

Recently, I have been involved in attempting to diagnose problems with excessive CPU utilization. Often times, this type of thing is relatively easy to identify - at least as far as pointing the finger at the thing that is consuming CPU cycles. Task Manager can be used for this - simply sort the "CPU" column in descending order and note the process that is at the top of the list. One can use a similar technique with Process Explorer.

In the past (here and here), I've given examples that demonstrate various techniques that can be used to try to determine what a process is doing when it is consuming so much CPU. Sometimes, you can do something about it - if you have the debugging symbols, perhaps there is something in the stack of the thread or threads in the process that is consuming the CPU that will lead you to some setting, feature, or configuration piece that can be manipulated so as to avoid the problem. Or perhaps just knowing the module name is enough information to identify the problem software - a recently installed add-in / plug-in, or a new utility,...

I've written about Sysinternals' Process Monitor utility before:

• Microsoft / Sysinternals Process Monitor
• Using Process Monitor to Troubleshoot Internet Explorer 7 Performance Issues

I have had a few months now to work with Process Monitor, and it certainly is amazing. The filtering capabilities are great, and the fact that the filters are not destructive makes slicing and dicing the data many ways quite simple. The ability to capture all of the data that the utility can capture makes it quite powerful, and the ability to get stack traces for each event is extremely useful.

Going off the observation that Process Monitor is currently at version 1.01, and the assumption that the utility will see further development, I have hopes that the following relatively small ideas will be taken into consideration for future releases, and that further discussion and conversation is sparked.

1) Allow for the use of CTRL+C to copy selected data to the clipboard. Some data can be copied in this fashion, but from my experience not much. In many cases, one can right-click and choose "Copy" from the context menu, but that's inconvenient. For example, on Event properties, on the Event...