STOP: 0x0000007B (0x81FF6DB0, 0xC0000006, 0x00000000, 0x00000000)

G

Guest

Please Help!!!

I receive the following blue screen error when booting Windows 2000 Server:
STOP: 0x0000007B (0x81FF6DB0, 0xC0000006, 0x00000000, 0x00000000).

I have no idea what caused this as the server was working perfectly well one
day, and the next this error appeared.
 
J

Jim Howes

NewbieLee said:
Please Help!!!

I receive the following blue screen error when booting Windows 2000 Server:
STOP: 0x0000007B (0x81FF6DB0, 0xC0000006, 0x00000000, 0x00000000).

I have no idea what caused this as the server was working perfectly well one
day, and the next this error appeared.

STOP 7B errors are 'Inaccessible Boot Device' problems. This means that your
system has managed to boot the windows loader, but the windows loader cannot
find the rest of Windows.

Typical causes are driver problems relating to hard disk drivers; changes in
hardware configuration (have you enabled/changed any RAID functions on your
system?); or possibly flaky hardware.

Roxio Easy CD Creator has been linked with STOP 7B errors, see KB811408

Virus activity is another possible cause.

Have you changed the physical location of any discs, or changed
controller/master/slave settings on IDE devices?

Failing that, you could place your boot drive in another machine so you can
examine it for errors (using the manufacturers' diagnostic tools, chkdsk, etc.).
Given the cost of hard drives vs. the value of data stored on them, any tiny
problem with a drive should be cause for it's immediate replacement.

Jim
 
D

Dave Patrick

Try creating a boot disk. For the floppy to successfully boot Windows 2000
the disk must contain the "NT" boot sector. Format a diskette (on a Windows
2000 machine, not a DOS/Win9x, so the NT boot sector gets written to the
floppy), and copy Windows 2000 versions of ntldr, ntdetect.com, and boot.ini
to it. Edit the boot.ini to give it a correct ARC path for the machine you
wish to boot. Below is an example of boot.ini. The default is to start the
operating system located on the first partition of the primary or first
drive (drive0). Then drive0 partition 2 and so on.

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows 2000 0,1"
multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows 2000 0,2"
multi(0)disk(0)rdisk(1)partition(1)\WINNT="Windows 2000 1,1"
multi(0)disk(0)rdisk(1)partition(2)\WINNT="Windows 2000 1,2"

Another possibility is to try loading the controller driver also from
floppy. For the floppy to successfully boot Windows 2000 the disk must
contain the "NT" boot sector. Format a diskette (on a Windows 2000 machine,
not a DOS/Win9x, so the "NT" boot sector gets written to the floppy), then
copy ntldr, ntdetect.com, and boot.ini to it. Edit the boot.ini to give it a
correct ARC path for the machine you wish to boot.

In order for this to work you'll want to change the arc path in boot.ini
from multi syntax to scsi syntax to indicate that Windows 2000 will load a
boot device driver and use that driver to access the boot partition. Then
also copy the correct manufacturer scsi driver to the floppy but renamed to
ntbootdd.sys


Something like this below;

[boot loader]
timeout=10
default=scsi(0)disk(0)rdisk(0)partition(1)\windows
[operating systems]
scsi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows 2000 0,1"
scsi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows 2000 0,2"
scsi(0)disk(1)rdisk(0)partition(1)\WINNT="Windows 2000 1,1"
scsi(0)disk(1)rdisk(0)partition(2)\WINNT="Windows 2000 1,2"


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Please Help!!!
|
| I receive the following blue screen error when booting Windows 2000
Server:
| STOP: 0x0000007B (0x81FF6DB0, 0xC0000006, 0x00000000, 0x00000000).
|
| I have no idea what caused this as the server was working perfectly well
one
| day, and the next this error appeared.
|
 
G

Guest

Thanks, I'll try placing the boot disk in another computer and checking it..I
haven't made any changes to the RAID functions on the system so I assume it
has something to do with the hardware.
 

Ask a Question

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.

Ask a Question

Top