G
GDavisCT
Ouch: this problem is will not let go of me on a Dual
booting Win98 / Win2k installation, updated to SP3
Blue screen of death during WIN2k boot up; occurs after
the NT2kPro opening full screen color, and before the
transision to "the loading Windows" box on a blank screen
STOP: 0x0000007B (0x81881D70, 0xC0000006, 0x00000000,
0x00000000)
INACCESSIBLE_BOOT_DEVICE
The MS knowledge base comes very close to the description
of this fault, however, the specific parameter 1 & 2 ID's
are not covered.
Attempts to repair via Repair console, Alternate drivers,
and ERD procedures has made things slightly worse.
The system will boot in Win2k Safe mode.
The very first bootup after installing Win2k hit this blue
screen error.
Rebooted to Win98, all OK.
Rebooted to Win2k, all OK.
Then the W2k blue screen error returned with a vengence
after installing Win98 apps (QuickTime & REALplayer)
The system will hit the Stop error when booting to Win2k
Safe + Networking.
When booted to Safe Mode, Device Manager recognizes that
the ethernet controller is not loaded with the yellow
question mark.
When booted to Win2K Safe Mode, the Device Manager reads
the Disk Drives with an inconsistent Location address
report:
Fuji at Location 0(0)
1st WD HDD at Location 0(0)
CDROM at Location Location 1(1)
1st WD HDD at Locaiton 0(0)
2nd WD HDD at Locaiton 1(1)
Win2k Explorer reports the drive letters and volume titles
differently than Win98: all FAT32 unless noted:
The FDISK "Active" Partition setting in WIN98 apparently
is not reflected in WIN2k
WIN
2K WIN98
C: MS-DOS_6 (FAT16) MS-DOS_6 (FAT16)
D: NTFS-W2K (NTFS) unrecognized
E: MS-DOS_6 SYS-DATA
1stWD 1st Partition
F: Compact Disc (SCSI CDRW) SYS-WIN9XPGM 1st WD
2nd Partition
G: SYS-DATA SYS-ALTOS
H: SYS-W9XPRGM SYS-UTIL
I: SYS-ALTOS SYS-UTIL
J: SYS-UTIL SYS-DATA
K: SYS-DATA SYS-
WIN9XPGM
L: SYS-W9XPRGM SYS-WIN9XPGM
M: SYS-W9XPRGM Compact disc
(SCSI CDRW)
Z: CD-rom CD ROM
Actual Physical Settings:
Note: the only FDISK Active partition setting is for 1st
Drive, 1st partition.
HDD Primary IDE 40-way MBD Connector
Physical Drive 0 Fujitsu 20GB; Master Jumper Setting
1st Partition 2GB FAT16, DOS6.6 OS Win2k:
2nd Partition 18GB; Win2k NTFS
CDROM, Slave Jumper Setting
HDD Secondary IDE 40-Way MBD connector:
Physical Drive 1: Western Digital 27GB Master Jumper
Setting
1st Partition 8GB FAT32
2nd Partition 8 GB FAT32
3rd Partition 8 GB FAT32
4th Partition 2 GB FAT32
Physical Drive 2: Western Digital 27Gb Slave Jumper
Setting
(Note: This drive is used only for Backup with GHOST
Partition Image)
1st Partition 2GB FAT16
2nd Partition 8GB FAT32
3rd Partition 8GB FAT32
4rth Partition 8GB FAT32
On one Win2k Bootup, the CHKDSK was initiated. After the
CHKDSK ran, WIN2k booted correctly.
Futher attempts to run CHKDSK from Safe mode command
prompt do not work, as the Drive is Locked.
Attempts to sechedule CHKDSK at the next WIN2k boot, do
not work.
MY QUESTIONS:
1. IS the system attempting to boot from a network drive
and not finding it?
2. Is the system being confused from a residual multiboot
install, System Commander;
all the Win98 code lives on the E: drive; the MBR is re-
written by system commander for the selected OP system
at boot time. Sys commander boot interrupt is currently
not active, and the last Win98 book code is written to
the MBR, which redirects bootup to the code on the E:
drive.
3. What is the cure; As WIN2k was booting correctly for
a while, prior to some WIN98 apps installs.
4. Is there just no support for this dilemma?
booting Win98 / Win2k installation, updated to SP3
Blue screen of death during WIN2k boot up; occurs after
the NT2kPro opening full screen color, and before the
transision to "the loading Windows" box on a blank screen
STOP: 0x0000007B (0x81881D70, 0xC0000006, 0x00000000,
0x00000000)
INACCESSIBLE_BOOT_DEVICE
The MS knowledge base comes very close to the description
of this fault, however, the specific parameter 1 & 2 ID's
are not covered.
Attempts to repair via Repair console, Alternate drivers,
and ERD procedures has made things slightly worse.
The system will boot in Win2k Safe mode.
The very first bootup after installing Win2k hit this blue
screen error.
Rebooted to Win98, all OK.
Rebooted to Win2k, all OK.
Then the W2k blue screen error returned with a vengence
after installing Win98 apps (QuickTime & REALplayer)
The system will hit the Stop error when booting to Win2k
Safe + Networking.
When booted to Safe Mode, Device Manager recognizes that
the ethernet controller is not loaded with the yellow
question mark.
When booted to Win2K Safe Mode, the Device Manager reads
the Disk Drives with an inconsistent Location address
report:
Fuji at Location 0(0)
1st WD HDD at Location 0(0)
CDROM at Location Location 1(1)
1st WD HDD at Locaiton 0(0)
2nd WD HDD at Locaiton 1(1)
Win2k Explorer reports the drive letters and volume titles
differently than Win98: all FAT32 unless noted:
The FDISK "Active" Partition setting in WIN98 apparently
is not reflected in WIN2k
WIN
2K WIN98
C: MS-DOS_6 (FAT16) MS-DOS_6 (FAT16)
D: NTFS-W2K (NTFS) unrecognized
E: MS-DOS_6 SYS-DATA
1stWD 1st Partition
F: Compact Disc (SCSI CDRW) SYS-WIN9XPGM 1st WD
2nd Partition
G: SYS-DATA SYS-ALTOS
H: SYS-W9XPRGM SYS-UTIL
I: SYS-ALTOS SYS-UTIL
J: SYS-UTIL SYS-DATA
K: SYS-DATA SYS-
WIN9XPGM
L: SYS-W9XPRGM SYS-WIN9XPGM
M: SYS-W9XPRGM Compact disc
(SCSI CDRW)
Z: CD-rom CD ROM
Actual Physical Settings:
Note: the only FDISK Active partition setting is for 1st
Drive, 1st partition.
HDD Primary IDE 40-way MBD Connector
Physical Drive 0 Fujitsu 20GB; Master Jumper Setting
1st Partition 2GB FAT16, DOS6.6 OS Win2k:
2nd Partition 18GB; Win2k NTFS
CDROM, Slave Jumper Setting
HDD Secondary IDE 40-Way MBD connector:
Physical Drive 1: Western Digital 27GB Master Jumper
Setting
1st Partition 8GB FAT32
2nd Partition 8 GB FAT32
3rd Partition 8 GB FAT32
4th Partition 2 GB FAT32
Physical Drive 2: Western Digital 27Gb Slave Jumper
Setting
(Note: This drive is used only for Backup with GHOST
Partition Image)
1st Partition 2GB FAT16
2nd Partition 8GB FAT32
3rd Partition 8GB FAT32
4rth Partition 8GB FAT32
On one Win2k Bootup, the CHKDSK was initiated. After the
CHKDSK ran, WIN2k booted correctly.
Futher attempts to run CHKDSK from Safe mode command
prompt do not work, as the Drive is Locked.
Attempts to sechedule CHKDSK at the next WIN2k boot, do
not work.
MY QUESTIONS:
1. IS the system attempting to boot from a network drive
and not finding it?
2. Is the system being confused from a residual multiboot
install, System Commander;
all the Win98 code lives on the E: drive; the MBR is re-
written by system commander for the selected OP system
at boot time. Sys commander boot interrupt is currently
not active, and the last Win98 book code is written to
the MBR, which redirects bootup to the code on the E:
drive.
3. What is the cure; As WIN2k was booting correctly for
a while, prior to some WIN98 apps installs.
4. Is there just no support for this dilemma?