Wesley Vogel said:If you really use and need the Indexing service, ignore the rest of this.
To resolve the issue, turn off the Indexing service.
Windows XP may run slowly and you may see multiple symptoms in Windows Task
Manager
http://support.microsoft.com/kb/899869
cisvc.exe = Content Index SerViCe or Indexing service.
cidaemon.exe = Content Indexing service filter Daemon
The Indexing service uses the Cidaemon.exe process to index files. The
Cidaemon.exe process builds and updates the Index catalog.
Indexing Service starts automatically the first time you use Search,
unless it has been disabled.
Before disabling the Indexing Service, uninstall it in Add or Remove
Programs Control Panel applet.
Start | Settings | Control Panel | Add or Remove Programs |
Add/Remove Windows Components button on left hand side|
Scroll down to and UNCheck: Indexing Service | Finish |
Close Add or Remove Programs
Turn off the Indexing Service.
Start | Run | Type: services.msc | Click OK |
Scroll down to and double click: Indexing Service |
Click the Stop button | In the Startup Type field,
select Disabled | Click Apply | Click OK
After you restart your machine it will stay disabled.
Indexing Service
[[Indexes contents and properties of files on local and remote computers;
provides rapid access to files through flexible querying language.]]
[[Indexing service is a small program that hogs HUGE amounts of RAM and can
often make a computer endlessly loud and noisy. This system process
indexing and updates lists of the files on your system, so you can search
for them quickly, but it's completely unnecessary.]]
Indexing Service
[[This service always has been a major resource hog. I NEVER recommend
having this service enabled. Remove the function via the "Add / Remove
Programs" icon in the control panel (Windows Setup Programs). It uses about
500 K to 2 MB in an idle state, not to mention the amount of memory and CPU
resources it takes to INDEX the drives. I have had people (and witnessed it
on other people's computers) report to me that the Indexing Service
sometimes starts up EVEN while the system is NOT idle... as in the middle of
a game. You may feel, as I do, that this is unacceptable. If your computer
suddenly seems "sluggish," Indexing Service is usually the cause of it.
Safe Setting: Disabled
Service name (registry): cisvc ]]
http://www.blackviper.com/WinXP/service411.htm#Indexing_Service
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
InSamantha''''''''s Dad said:I'm getting the cidaemon.exe application error and I have Windows XP Pro
SP2. "The instruction at 0x0000000 referenced memory at '0x0000000. The
memory could not be 'written'.
I thought this only happened in Win2000 SP4 & Win Server 2003.
Please help.
Thanks in advance.
Samantha''''''''s Dad said:Wesley,
Thank you for such a thurough answer. I truly appreciate it!
I had already figured out that stopping & disabling the Indexing Service,
knowing that I had Google Desktop anyway, would (and did) kill the error
but I didn't want to uninstall/reinstall if I didn't absolutely have to.
But, noticing a nice preformance improvement had decided to just leave it
disabled either way.
I will follow your advice and just get rid of the albatross altogether
seeing that there's no way else to fix it and just rely on Google Desktop.
Anyway thanks again for your time, knowledge & effort in getting back to
me so quickly. As I said, I truly appreciate it!
--
Peter D. Sheran
Wesley Vogel said:If you really use and need the Indexing service, ignore the rest of this.
To resolve the issue, turn off the Indexing service.
Windows XP may run slowly and you may see multiple symptoms in Windows
Task Manager
http://support.microsoft.com/kb/899869
cisvc.exe = Content Index SerViCe or Indexing service.
cidaemon.exe = Content Indexing service filter Daemon
The Indexing service uses the Cidaemon.exe process to index files. The
Cidaemon.exe process builds and updates the Index catalog.
Indexing Service starts automatically the first time you use Search,
unless it has been disabled.
Before disabling the Indexing Service, uninstall it in Add or Remove
Programs Control Panel applet.
Start | Settings | Control Panel | Add or Remove Programs |
Add/Remove Windows Components button on left hand side|
Scroll down to and UNCheck: Indexing Service | Finish |
Close Add or Remove Programs
Turn off the Indexing Service.
Start | Run | Type: services.msc | Click OK |
Scroll down to and double click: Indexing Service |
Click the Stop button | In the Startup Type field,
select Disabled | Click Apply | Click OK
After you restart your machine it will stay disabled.
Indexing Service
[[Indexes contents and properties of files on local and remote computers;
provides rapid access to files through flexible querying language.]]
[[Indexing service is a small program that hogs HUGE amounts of RAM and
can often make a computer endlessly loud and noisy. This system process
indexing and updates lists of the files on your system, so you can search
for them quickly, but it's completely unnecessary.]]
Indexing Service
[[This service always has been a major resource hog. I NEVER recommend
having this service enabled. Remove the function via the "Add / Remove
Programs" icon in the control panel (Windows Setup Programs). It uses
about 500 K to 2 MB in an idle state, not to mention the amount of
memory and CPU resources it takes to INDEX the drives. I have had people
(and witnessed it on other people's computers) report to me that the
Indexing Service sometimes starts up EVEN while the system is NOT
idle... as in the middle of a game. You may feel, as I do, that this is
unacceptable. If your computer suddenly seems "sluggish," Indexing
Service is usually the cause of it.
Safe Setting: Disabled
Service name (registry): cisvc ]]
http://www.blackviper.com/WinXP/service411.htm#Indexing_Service
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
InSamantha''''''''s Dad said:I'm getting the cidaemon.exe application error and I have Windows XP Pro
SP2. "The instruction at 0x0000000 referenced memory at '0x0000000. The
memory could not be 'written'.
I thought this only happened in Win2000 SP4 & Win Server 2003.
Please help.
Thanks in advance.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.