Dieses ist nicht, was ich ungefähr schreiben möchte. Aber eine Neuentdeckung zwingt mich, so zu tun. So habe ich entschieden, dieses ein Experiment zu bilden und Ihre Entschuldigungen bitte, daß dieses nicht viel technischen Verdienst trotz des Titels hat.

Nach dem letzten Pfosten, Legen Sie die Priorität eines Prozesses namentlich automatisch, in Vista fest (das viel besseres vermutlich genannt worden sein könnte), entdeckte ich, daß der Pfosten seine Weise zu einigen anderen Aufstellungsorten gebildet hatte. Diese Aufstellungsorte scheinen, Inhalt von ganz über dem Netz zu ziehen, verpacken es oben als ihre Selbst und werfen ADS ganz über ihm. Eins ist wenn die gleichmäßigen Hinweise des Aufstellungsortes der ursprüngliche Autor oder die Verbindungen zurück zu der ursprünglichen Position des Pfostens glücklich. Es frustriert, um die wenigen zu sagen. Aller ich bin für Verteilung des Wissens und der dergleichen, aber der nimmt sie zu weit. Möglicherweise sollte ich nicht auf diese Weise glauben, aber I (wie andere) setzte Gehirnschweiß und -zeit in die Arbeit, die ich erledige, und es würde nett sein, wenn die Quelle der Informationen mindestens zitiert würde, wenn sie sie ohne die Zustimmung des Autors neu auflegen werden.

So besichtigte ich zwei dieser Aufstellungsorte (die ich habe

…

Der andere Tag spielte ich herum mit Bild-Akte Durchführung Wahlen und Sysinternals' Prozeßmonitor, in Vista. Ich sah eine interessante Frage stattzufinden. Mit notepad.exe als Beispiel, sah ich eine Frage für einen Schlüssel, der „PerfOptions“ in genannt wurde [HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ Bild-Akte Durchführung Wahlen \ notepad.exe] als ich Notizblock laufen ließ. Das Resultat war NAMENSgefunden NICHT, also entschied ich, den zu korrigieren. Das Addieren eines Schlüssels, der „PerfOptions“ genannt wurde, lief ich Notizblock wieder nach. Im Prozeßmonitor sah ich Fragen für vier Werte:

• IoPriority
• PagePriority
• CpuPriorityClass
• WorkingSetLimitInKB

Because of recent explorations with process priorities*, CpuPriorityClass grabbed me right away. Looking at the SetPriorityClass function, one can see the different values for the dwPriorityClass parameter. I created a REG_DWORD named CpuPriorityClass in PerfOptions, and set the value to 0×80 in the hopes that notepad would launch with “HIGH_PRIORITY_CLASS”. Instead, it launched with a priority of NORMAL_PRIORITY_CLASS (8) - the setting had not made any impact. Then, I set the value to 8 and launched notepad. Notepad launched with a priority of 8. I changed the value to 4, and that had no impact. I changed the value to 0 - no impact. I tried 10 - no impact. I couldn’t see any

…

Every once in a while you notice that your hard drive is working extra hard for what seems like no reason. A background process has taken your hard drive hostage, forcing it to thrash loudly as it struggles to keep up with the high rate of reads and writes. Your computer responds slowly as the process overloads the physical limitations of your drive. What are you to do?

The solution is simple, although a little tricky at times: identify and stop the process that is killing your drive. There are two methods and tools that you can use to identify the process. (more…)

computer, disk operations, download process explorer, down arrow, Drivers, explorer 2, Hardware, hard drive, hostage, menubar, performance tab, processes, reliability, responds, struggles, sysinternals

Previously (Part 1: Introduction - What’s using my CPU?), I kicked off what I expect to be a multi-part series on determining what is causing excessive CPU consumption, outside of the normal “which process has the highest value in the CPU column in Task Manager”.

Before I get into things, a little bit of background may prove useful or mildly entertaining. Over on “Sysinternals Forums”, there were recently two similar problems that both involved excessive CPU utilization that was not attributable to a specific process. 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…