My CPU usage is constantly at 100% becuase of cisvc.exe.

I have a similar problem .. cpu at 100% with ANy browser. IE7&8, Safar, Firefox,  Win Media plays so slow it is not watchable.  Even Flash movies too slow to watch.  Pentium 4, 3.2 ghz,  2 gig system RAM,  7200 RPM SATA disk.   Flushed browser caches, cleaned registry, removed all unneeded programs,  ran diagnostics on disk .. speed good,  diagnostic on RAM says speed is good.   Task manager always shows the browser hogging the CPU.  Device manager shows all devices healthy.  Even running Win Media outside of a browser,  movies are very slow -- and the CPU is NOT at 100%.   My conclusion ..    XP has a problem that none of the diags are going to find it.    I am stuck re-loading the OS to fix it.

My PC is configured as a Digital Audio Workstation (DAW). My Sequencer SW, requires the Indexing Srvc for many of it's recording & MIDI Instrument features.  W/O Indexing, my DAW over-works & exhausts CPU usage, as well as hang & crash. As such, this is not a solution for me.

Your DAW needs MS Indexing Service? I've been using Cubase 4/5 for a few years now and haven't seen any problem like this. I'm reasonably certain that I never turned the indexing service for XP on for the following reasons:

1. I'm pretty sure most people have to actually go into services and enable the service themselves unless they install a program that turns the XP Indexing Service on for them.
2. I don't like the name of the Microsoft Windows XP Indexing Service.  If I am not mistaken, the name of that service closely resembles the names of UNIX background drivers and I am a little upset with the UNIX community right now.

Hi All,

I've been using this disable work-around for over a year but had to re-enable the service. It took a while, but I discovered some (at least 1) 3rd party Apps require Index Srvc to run.

My PC is configured as a Digital Audio Workstation (DAW). My Sequencer SW, requires the Indexing Srvc for many of it's recording & MIDI Instrument features.  W/O Indexing, my DAW over-works & exhausts CPU usage, as well as hang & crash. As such, this is not a solution for me.

Anyone have other ideas or know of other work-arounds? Seems to me this is NOT a new problem. SP2 & 3SP3 have been around for sometime & this problem came with SP2. M.S. had pleanty of time to have addressed it.

M.S. advocates brand loyalty but, one of my hesitations to upgrade anymore is the reluctance of M.S. to fix it's bugs while opting to merely make a new Windows for the consumer to have to buy. If Windows x has a bug, buy throw it away, spend more money & buy M.S. Windows NewX...very discouraging scnenario.

Thanks in advance.

-Mo

Mr. DBPickett has valid points and I tend to agree with him that the indexing service should not take up so many reasources, but I didn't mean killing the indexing service in a one time Task Manager attempt. I meant to permanently disable it.

Killing it is a sad excuse, and next boot, it is back.

I "think" it is possible to permanently disable the Indexing Service.

In Classic View:

1. Start->Control Panel->Services->Indexing Service
2. Right Click->Properties
3. Choose Disabled for Startup Type

I'm pretty sure that the indexing service never runs on my PC.

Just as a wild guess, I wonder if Sold State Hard Drives will make indexing less necessary in the future.  While Solid State HDs aren't inherently good for streaming, they are inherently good for large numbers of random accesses reads, so a Solid State HD might perform better at finding files than a mechanical HD would.

Note:

I believe Solid State Hard Drives are now implemented in RAID like configurations of Flash Cells with some advanced caching mechanisms to overcome the problems with sequential access from Flash Cells and the wear out that occurs during writes, so a well designed Solid State Hard Drive might very well outperform and Mechanical HD even the areas that are traditionally weak for Flash Memory.

I though the hundreds of terabytes of other I/O showing on task manager was pretty amazing.  The process that cisvc.exe is supposedly monitoring seems to be not running.  Whatever it needs to do for monitoring should not use over 1%.  Turning off the indexing is good for a lot of reasons for many, but it should have worked originally, and should not be a problem like this.  Killing it is a sad excuse, and next boot, it is back.