Discussion Locked

Can't figure out what caused error

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Howdy,

Earlier we had a storm roll over and caused a power clicker, when the computer was loading again, it would begin to load Windows 2000 and then would quit and go to the blue screen which gave the error:

STOP: 0x0000007B (x820916b0, 0xc0000032, 0x00000000, 0x00000000)
Inaccessible Boot Device

I typically thought that this meant I had to deal with a bad hard drive, but I went to Western Digitals Website and downloaded their HD utility and it came out clean with no errors. Does anyone have any suggestions on how I can fix this problem?

Thanks

7 replies

by dmiles

When attempting to boot a Windows 2000 Professional system, a blue screen error "" occurs.

Exact Error Message

Details:
Backup Exec Desktop Edition for Windows 2000 has been seen to cause an error if the product driver DRVMCDB.SYS file was removed or renamed. To prevent this error, the driver DRVMCDB.SYS must be replaced in its original location ("C:\WINNT\SYSTEM32\DRIVERS"). If the driver is not available, please contact VERITAS Technical Support.

In FAT16 or FAT 32:
Use a boot diskette to get to a DOS prompt and copy the driver DRVMCDB.SYS to the "C:\WINNT\SYSTEM32\DRIVERS" directory.

In NTFS:
The Windows 2000 Boot diskettes must be used. When prompted, choose Repair and Console. Copy the driver DRVMCDB.SYS to the "C:\WINNT\SYSTEM32\DRIVERS" directory.

by jdelgado

It didn't help me because all i had avaialble was the Win2000 Install CD and that didn't seem to have the driver

by sgt_shultz

maybe the file system got hosed.
if file system error hosed the hard disk controller driver you couldl maybe get chkdsk to fix it without replacing file.
use Recovery Console to run chkdsk. see support.microsoft.com for great instructions. (hmmm, wonder if Windows CD Setup/repair existing installation would work for this? give you a chance to insert floppy with driver maybe)
or
how about this idea: move drive to computer with 2000 on it (so it's is not the boot drive, see?) and run chkdsk on it. if you are lucky, it will find and fix the error and you're done.

This discussion is closed to new replies.