System Will Not Boot

Brian

Distinguished
Sep 9, 2003
1,371
0
19,280
Archived from groups: microsoft.public.win2000.general (More info?)

Help!

We came into the office this morning and one of our Windows 2000 PC will not
boot. We get a blue screen error during boot that says:

STOP 0X0000007B (0XFCDAD030, 0XC0000032, 0X00000000, 0X00000000)
INACCESSIBLE_BOOT_DEVICE

We do not have a bootable virus checker disk and the machine will not boot
into safe mode.

Any suggestions beyond a rebuild?

Thanks,
Brian
 
G

Guest

Guest
Archived from groups: microsoft.public.win2000.general (More info?)

Brian wrote:

>Help!
>
>We came into the office this morning and one of our Windows 2000 PC will not
>boot. We get a blue screen error during boot that says:
>
>STOP 0X0000007B (0XFCDAD030, 0XC0000032, 0X00000000, 0X00000000)
>INACCESSIBLE_BOOT_DEVICE
>
>We do not have a bootable virus checker disk and the machine will not boot
>into safe mode.
>
>Any suggestions beyond a rebuild?
>

Boot from the install CD? Or got another HD you can put in and boot
from (not that big a deal for your computer nerd)? Do a repair,
scandisk, whatever from there.

If not possible, obviously you have something on the internet. Get to
http://www.bootdisk.com/ and get a boot disk image of some kind,
anything that can let you look at the primary HD of that system. If you
have NTFS disk format there it requires the w2k, NT, or XP boot disks to
look at the disk, if FAT32 then almost any MS disk will do. You want to
do a chkdsk or scandisk, see if you can repair the damage.

By chance was that disk ever run with win98? Is it over 64 gigs? Win98
would format those assuming a 64 gig limit, and slop over so that the
part beyond 64 gig would overwrite the first part of the partition, and
you could operate for years without knowing it, till one day the disk
got full enough to use that area, and of course the first thing it will
overwrite will be system files, boot information, etc. If this were the
case, a wipe, fdisk, and repartition is a good idea, with NTFS if you
have no multi-boot need.

All this may not give you any result, but it's what I would try first.
Then look at virus/trojan/worm problems, any kind of drivers screwed up,
programs messed up, and if you don't find a cause, well it may be time
to backup, fdisk, repartition, and reinstall. Save that nuclear option
for last.

--
A sufficiently advanced computer network protective attitude is indistinguishable from paranoia.
 
G

Guest

Guest
Archived from groups: microsoft.public.win2000.general (More info?)

Quaestor wrote:

> Brian wrote:
>

BTW, one of the first things you want to do when you got a situation
like this is disconnect this machine from the network. Pull the plug.
If it is an infection problem you don't want whatever is there getting
out, or wherever it got in from sending the same thing back in again.


--
A sufficiently advanced computer network protective attitude is indistinguishable from paranoia.
 

Brian

Distinguished
Sep 9, 2003
1,371
0
19,280
Archived from groups: microsoft.public.win2000.general (More info?)

Thanks! I booted from the Win 2000 disk, went into repair console and ran
chkdsk /r and it is back up now.

Thanks!

"Quaestor" <no.spam@my.place> wrote in message
news:118jp2n3ljo9r97@news.supernews.com...
> Brian wrote:
>
>>Help!
>>
>>We came into the office this morning and one of our Windows 2000 PC will
>>not boot. We get a blue screen error during boot that says:
>>
>>STOP 0X0000007B (0XFCDAD030, 0XC0000032, 0X00000000, 0X00000000)
>>INACCESSIBLE_BOOT_DEVICE
>>
>>We do not have a bootable virus checker disk and the machine will not boot
>>into safe mode.
>>
>>Any suggestions beyond a rebuild?
>>
>
> Boot from the install CD? Or got another HD you can put in and boot from
> (not that big a deal for your computer nerd)? Do a repair, scandisk,
> whatever from there.
>
> If not possible, obviously you have something on the internet. Get to
> http://www.bootdisk.com/ and get a boot disk image of some kind, anything
> that can let you look at the primary HD of that system. If you have NTFS
> disk format there it requires the w2k, NT, or XP boot disks to look at the
> disk, if FAT32 then almost any MS disk will do. You want to do a chkdsk
> or scandisk, see if you can repair the damage.
>
> By chance was that disk ever run with win98? Is it over 64 gigs? Win98
> would format those assuming a 64 gig limit, and slop over so that the part
> beyond 64 gig would overwrite the first part of the partition, and you
> could operate for years without knowing it, till one day the disk got full
> enough to use that area, and of course the first thing it will overwrite
> will be system files, boot information, etc. If this were the case, a
> wipe, fdisk, and repartition is a good idea, with NTFS if you have no
> multi-boot need.
>
> All this may not give you any result, but it's what I would try first.
> Then look at virus/trojan/worm problems, any kind of drivers screwed up,
> programs messed up, and if you don't find a cause, well it may be time to
> backup, fdisk, repartition, and reinstall. Save that nuclear option for
> last.
>
> --
> A sufficiently advanced computer network protective attitude is
> indistinguishable from paranoia.
 
G

Guest

Guest
Archived from groups: microsoft.public.win2000.general (More info?)

Brian wrote:

>Thanks! I booted from the Win 2000 disk, went into repair console and ran
>chkdsk /r and it is back up now.
>
>Thanks!
>
>"Quaestor" <no.spam@my.place> wrote in message
>
>

Great. Do a thorough sweep with anti-virus, spyware, adware, and make
sure the system and network are clean. w2k does this kind of thing a
lot, but something caused it, it didn't just happen.

I recommend AVAST!, SpybotSD, and Ad-Aware, all freeware and very good.

Good luck.


--
A sufficiently advanced computer network protective attitude is indistinguishable from paranoia.