Crashes fixed! Apparently caused by Indexing Service.

[Robbie Hatley]

Well, I finally seem to have put a stop to those ongoing

crashes that I've been yammering about in here for weeks.

(To recap: a couple times a day, my Win2K system would

crash. First, optical USB mouse, sound, and networking would

go offline, followed a few minutes later by everything else.)



I started disabling stuff, one thing at a time. Finally,

when I disabled my "Indexing Service", the crashes stopped.

The system hasn't crashed in about 4 days now.



This is very odd, as it is a built-in part of the Windows2000

operating system. Has anyone else here had problems with

the Indexing Service causing crashes?



Or perhaps the Indexing Service on my machine is simply

corrupted? If it's not a file that gets updated by

service packs and updates, then it may have been bad

from the get-go. (It might even be corrupt on my Win2K

install disk just one bad bit is all it would take.)



In the meantime, I'm slowly adding the stuff I disabled

back in, to make sure that they played no part in the

problem. Hopefully this disaster is now over.



--

Relieved, but puzzled,

Robbie Hatley

lonewolf at well dot com

www dot well dot com slant tilde lonewolf slant

 

[Sid Elbow]

Robbie Hatley wrote:



> This is very odd, as it is a built-in part of the Windows2000

> operating system. Has anyone else here had problems with

> the Indexing Service causing crashes?



No ... but then it's the first thing I turn off in any new Windows

installation. I can't imagine why MS thinks this needs to be turned on

by default.

 

[Andrew Rossmann]

In article ,

see.my.signature@for.my.contact.info says...

>

> Well, I finally seem to have put a stop to those ongoing

> crashes that I've been yammering about in here for weeks.

> (To recap: a couple times a day, my Win2K system would

> crash. First, optical USB mouse, sound, and networking would

> go offline, followed a few minutes later by everything else.)

>

> I started disabling stuff, one thing at a time. Finally,

> when I disabled my "Indexing Service", the crashes stopped.

> The system hasn't crashed in about 4 days now.



Have you run a CHKDSK on the drive, especially with the /R switch? It's

remotely possible the Index file has a bad sector.



--

If there is a no_junk in my address, please REMOVE it before replying!

All junk mail senders will be prosecuted to the fullest extent of the

law!!

http://home.comcast.net/~andyross

 

[Stubby]

Crashes fixed! Apparently caused by Indexing Service.

On Feb 28, 9:03 am, Andrew Rossmann

wrote:

> In article ,

> see.my.signat...@for.my.contact.info says...

>

>

>

> > Well, I finally seem to have put a stop to those ongoing

> > crashes that I've been yammering about in here for weeks.

> > (To recap: a couple times a day, my Win2K system would

> > crash.  First, optical USB mouse, sound, and networking would

> > go offline, followed a few minutes later by everything else.)

>

> > I started disabling stuff, one thing at a time.  Finally,

> > when I disabled my "Indexing Service", the crashes stopped.

> > The system hasn't crashed in about 4 days now.

>

> Have you run a CHKDSK on the drive, especially with the /R switch? It's

> remotely possible the Index file has a bad sector.

>

> --

> If there is a no_junk in my address, please REMOVE it before replying!

> All junk mail senders will be prosecuted to the fullest extent of the

> law!!http://home.comcast.net/~andyross



I've had to cope with this sort of thing in the past. Note that you

will have to run CHKDSK /r from the Repair Console that you reach by

booting your installation disk. If you try to run it from an

ordinary system boot, Windows with see the disk as "in use" and refuse

to run CHKDSK. And, the "do it at the next boot" option doesn't work.

 

[John John - MVP]

Crashes fixed! Apparently caused by Indexing Service.

Stubby wrote:

> On Feb 28, 9:03 am, Andrew Rossmann

> wrote:

>> In article ,

>> see.my.signat...@for.my.contact.info says...

>>

>>

>>

>>> Well, I finally seem to have put a stop to those ongoing

>>> crashes that I've been yammering about in here for weeks.

>>> (To recap: a couple times a day, my Win2K system would

>>> crash. First, optical USB mouse, sound, and networking would

>>> go offline, followed a few minutes later by everything else.)

>>> I started disabling stuff, one thing at a time. Finally,

>>> when I disabled my "Indexing Service", the crashes stopped.

>>> The system hasn't crashed in about 4 days now.

>> Have you run a CHKDSK on the drive, especially with the /R switch? It's

>> remotely possible the Index file has a bad sector.

>>

>> --

>> If there is a no_junk in my address, please REMOVE it before replying!

>> All junk mail senders will be prosecuted to the fullest extent of the

>> law!!http://home.comcast.net/~andyross

>

> I've had to cope with this sort of thing in the past. Note that you

> will have to run CHKDSK /r from the Repair Console that you reach by

> booting your installation disk. If you try to run it from an

> ordinary system boot, Windows with see the disk as "in use" and refuse

> to run CHKDSK. And, the "do it at the next boot" option doesn't work.



Something must be wrong with your Windows 2000 installation, Chkdsk runs

at boot time when it is properly scheduled to do so.



John

 

[Dave Patrick]

Crashes fixed! Apparently caused by Indexing Service.

If you get an error something to the effect "cannot open volume for direct

access" There is some system/boot start device that is reading/writing to

the drive before chkdsk can get a lock on the drive. Some anti-virus

applications do this.



You can also run

chkdsk /r

from the recovery console command line. (/r implies /f and /p)



To start the Recovery Console, start the computer from the Windows 2000

Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup

floppy disks and your computer cannot start from the Windows 2000 Setup CD,

use another Windows 2000-based computer to create the Setup floppy disks.

Press ENTER at the "Setup Notification" screen. Press R to repair a Windows

2000 installation, and then press C to use the Recovery Console. The

Recovery Console then prompts you for the administrator password. If you do

not have the correct password, Recovery Console does not allow access to the

computer. If an incorrect password is entered three times, the Recovery

Console quits and restarts the computer. Once the password has been

validated, you have full access to the Recovery Console, but limited access

to the hard disk. You can only access the following folders on your

computer: %systemroot% and %windir%





--



Regards,



Dave Patrick ....Please no email replies - reply in newsgroup.

Microsoft Certified Professional

Microsoft MVP [Windows]

http://www.microsoft.com/protect



"Stubby" wrote:

I've had to cope with this sort of thing in the past. Note that you

will have to run CHKDSK /r from the Repair Console that you reach by

booting your installation disk. If you try to run it from an

ordinary system boot, Windows with see the disk as "in use" and refuse

to run CHKDSK. And, the "do it at the next boot" option doesn't work.

 

[Robbie Hatley]

Crashes have resumed. Not caused by Indexing Service.

"Andrew Rossmann" wrote:



> Have you run a CHKDSK on the drive, especially with the

> /R switch?



Nope, and I should, seeing as how the crashes have now RESUMED,

and were NOT due to Indexing Service after all.



> It's remotely possible the Index file has a bad sector.



Yes, could be a bad disk sector someplace catastrophic, such as

the MFT, or the registry, or some such thing.



Or it could be bad RAM, or a bad southbridge chip, or a bad CPU,

or a bad MB, or a bad peripheral, or a loose wire, or a driver

conflict, or service or other background daemon over-writing

drivers in memory, or other things I haven't even thought of.



I hate "intermittant" problems like this because they take

bloody ages to troubleshoot. (I think this problem started

kicking up around 2003... and I *STILL* haven't fixed it.

Sigh. I'll likely replace the whole damn computer with

a 64-bit model running Windows 7 professional long before

I get this zarking bug squashed. Grrrr.)



Ok, I'll go run "chkdsk C: /r" and see what happens.

Thanks for the tip.



--

Cheers,

Robbie Hatley

lonewolf at well dot com

www dot well dot com slant tilde lonewolf slant

 

[Robbie Hatley]

Nope, disk does not appear to have problem.

"Andrew Rossmann" had written:



> Have you run a CHKDSK on the drive, especially with the /R switch?

> It's remotely possible the Index file has a bad sector.



and I had replied back:



> Yep, I'll try that, thanks for the tip.





Well, I did that, and got:





Event Type: Information

Event Source: Winlogon

Event Category: None

Event ID: 1001

Date: 2010-03-08

Time: 12:04:29 AM

User: N/A

Computer: [removed for security reasons]

Description:

Checking file system on C:

The type of the file system is NTFS.

Volume label is [removed for security reasons].

A disk check has been scheduled.

Windows will now check the disk.

Cleaning up minor inconsistencies on the drive.

Cleaning up 50 unused index entries from index $SII of file 0x9.

Cleaning up 50 unused index entries from index $SDH of file 0x9.

Cleaning up 50 unused security descriptors.

CHKDSK is verifying Usn Journal...

Usn Journal verification completed.

CHKDSK is verifying file data (stage 4 of 5)...

File data verification completed.

CHKDSK is verifying free space (stage 5 of 5)...

Free space verification is complete.

40973782 KB total disk space.

22084560 KB in 111196 files.

49020 KB in 13591 indexes.

0 KB in bad sectors.

211922 KB in use by the system.

65536 KB occupied by the log file.

18628280 KB available on disk.

4096 bytes in each allocation unit.

10243445 total allocation units on disk.

4657070 allocation units available on disk.

Windows has finished checking your disk.

Please wait while your computer restarts.







So nope, that aint it. It was worth checking out, though,

even though it was a long-shot.







--

Cheers,

Robbie Hatley

lonewolf at well dot com

www dot well dot com slant tilde lonewolf slant