Introduction
Ever wondered which program has a particular file or directory open? Now you can find out. Process Explorer shows you information about which handles and DLLs processes have opened or loaded.
The Process Explorer display consists of two sub-windows. The top window always shows a list of the currently active processes, including the names of their owning accounts, whereas the information displayed in the bottom window depends on the mode that Process Explorer is in: if it is in handle mode you'll see the handles that the process selected in the top window has opened; if Process Explorer is in DLL mode you'll see the DLLs and memory-mapped files that the process has loaded. Process Explorer also has a powerful search capability that will quickly show you which processes have particular handles opened or DLLs loaded.
The unique capabilities of Process Explorer make it useful for tracking down DLL-version problems or handle leaks, and provide insight into the way Windows and applications work.
link: http://www.mediafire.com/file/z5kmmdmu1jj/ProcessExplorer.zip
Showing posts with label hardware interrupt. Show all posts
Showing posts with label hardware interrupt. Show all posts
Saturday, July 11, 2009
Thursday, June 11, 2009
Lousy Performance, High Hardware Interrupt Usage
My system has been dog too slow since I did a reinstall a couple weeks back. Process Explorer was showing some outrageous hardware interrupt rates, on occasion as high as 50% and regularly at 20%.
I’d let it roll for a couple weeks simply because it was low on my frustration list and I was trying to roll through other things. It finally pissed me off enough tonight that I spent some time nailing it down. Turns out ATA/IDE controllers will often revert back to PIO mode instead of Ultra-DMA.
After the Windows IDE/ATAPI Port driver (Atapi.sys) receives a cumulative total of six time-out or cyclical redundancy check (CRC) errors, the driver reduces the communications speed (the transfer mode) from the highest Direct Memory Access (DMA) mode to lower DMA modes in steps. If the driver continues to receive time-out or CRC errors, the driver eventually reduces the transfer mode to the slowest mode (PIO mode).
Check the problem by examining the controller’s Primary and Secondary IDE settings: Device Manager -> IDE ATA/ATAPI controllers -> Primary or Secondary IDE Channel -> Properties -> Advanced Settings. Look at the Current Transfer Mode field. If it’s “PIO” then it’s a FUBAR PITA and you’ll need to uninstall the driver, reboot and let XP do its magic reinstall.
I’d let it roll for a couple weeks simply because it was low on my frustration list and I was trying to roll through other things. It finally pissed me off enough tonight that I spent some time nailing it down. Turns out ATA/IDE controllers will often revert back to PIO mode instead of Ultra-DMA.
After the Windows IDE/ATAPI Port driver (Atapi.sys) receives a cumulative total of six time-out or cyclical redundancy check (CRC) errors, the driver reduces the communications speed (the transfer mode) from the highest Direct Memory Access (DMA) mode to lower DMA modes in steps. If the driver continues to receive time-out or CRC errors, the driver eventually reduces the transfer mode to the slowest mode (PIO mode).
Check the problem by examining the controller’s Primary and Secondary IDE settings: Device Manager -> IDE ATA/ATAPI controllers -> Primary or Secondary IDE Channel -> Properties -> Advanced Settings. Look at the Current Transfer Mode field. If it’s “PIO” then it’s a FUBAR PITA and you’ll need to uninstall the driver, reboot and let XP do its magic reinstall.
Subscribe to:
Posts (Atom)