Mass Inaccessible boot device messages

[Dolemite]

I work for a company that currently supports over 4000 Windows 2000
proffessional computers in a business network environment. As of late
we have been receiving at least 5-10 tickets a day on computers out in
the field with a BSOD Inaccessible Boot Device Error. Now if we have
the users hit f8 and choose Last Known Good everything seems to go back
to normal, but this is only if the users have not tried rebooting a
number of times before hand. If they have rebooted over and over again
we are able to go out and run the Windows 2000 recovery console from
the Win2k Install CD, to quickly repair the error and get windows back
up and running.

The only thing that has changed on our network is that we have gone to
Microsoft's SuS system to push out OS updates. This happened about two
months ago, previous to SuS we were using Patch Manager. We did turn
off the Win2K rollup pack that had the known BSOD error, but even still
the computers are still coming in as I said 5-10 a day with the
Inaccessible Boot Device BSOD Error.

Our computers are all MS Windows 2000 Proffessional, the models are a
variation of Dell Optiplex Desktop machines, I have seen the problem on
the GX240, GX260, and GX270 model so far. All computers are up to
Service Pack 4 and run in a DHCP domain environment. We are running
Etrust 7.1.192. Is anybody else seeing this or have any idea what could
be going on here? This is pretty much new to us as up to about 2 months
ago we rarely had any of these BSOD errors coming in unless it was
Hardware related. Oh and all these machines the Hardrive Diagnostics
pretty much check out ok.

 

[Adam Raff]

Hi Dolemite,

I am far from an expert on this but perhaps I can help a little. When you
get a BSOD you normally see, what file is causing the error. This may lead
to what is happening on your system. Also there are other numbers that come
up, you may also want to post them as they may lead to some info. You can go
to Microsoft web site and do a search on them if you have not done so. You
can also post this info on the board which may help others with your problem

It could be third party related such as a bad virus def.

If the problem is really bad you can get the dump file and call Microsoft
and they can analyze the info and perhaps give you an idea what can be
fixed. I am not sure if this is a cost issue or not since it may be related
to security updates or SUS.

Hope this helps a little
Adam Raff