Re: During the debug setup phase, blue screen
- From: "David Craig" <drivers@xxxxxxxxxx>
- Date: Mon, 19 May 2008 18:26:46 -0700
Did you provide a floppy disk with the disk driver and press F6 during the
boot of the OS? If it was Vista or Server 2008 you could prepare an install
image with the driver incorporated into the install OS boot and the OS that
would be installed using the WAIK. You might be able to do it with Server
2003, but read the docs that come with the WAIK (Windows Automated/ic
Install Kit).
"May" <May@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C6A2997E-CCB1-47EA-9377-A054B87BB057@xxxxxxxxxxxxxxxx
Hi,
I am trying to install a 2003 Enterprise server to a Dell Optiplex 755
computer. I have tried to install free build and checked build, both of
them
I got blue screen during the Windows start up during the install.
So I am using WINNT32.exe to do a txt setup on WIndows XP, I successfully
connect checked build setup to WinDbg. I got following info in the debug:
Break instruction exception - code 80000003 (first chance)
A fatal system error has occurred.
Connected to Windows Server 2003 3790 x86 compatible target, ptr64 FALSE
Loading Kernel Symbols
......................................................................................................
Loading User Symbols
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7B, {f789ea88, c0000034, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!IopMarkBootPartition+f7 )
Followup: MachineOwner
---------
nt!RtlpBreakWithStatusInstruction:
811507b4 cc int 3
0: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
INACCESSIBLE_BOOT_DEVICE (7b)
During the initialization of the I/O system, it is possible that the
driver
for the boot device failed to initialize the device that the system is
attempting to boot from, or it is possible for the file system that is
supposed to read that device to either fail its initialization or to
simply
not recognize the data on the boot device as a file system structure that
it recognizes. In the former case, the argument (#1) is the address of a
Unicode string data structure that is the ARC name of the device from
which
the boot was being attempted. In the latter case, the argument (#1) is
the
address of the device object that could not be mounted.
If this is the initial setup of the system, then this error can occur if
the system was installed on an unsupported disk or SCSI controller. Note
that some controllers are supported only by drivers which are in the
Windows
Driver Library (WDL) which requires the user to do a custom install. See
the Windows Driver Library for more information.
This error can also be caused by the installation of a new SCSI adapter or
disk controller or repartitioning the disk with the system partition. If
this is the case, on x86 systems the boot.ini file must be edited or on
ARC
systems setup must be run. See the "Advanced Server System
Administrator's
User Guide" for information on changing boot.ini.
If the argument is a pointer to an ARC name string, then the format of the
first two (and in this case only) longwords will be:
USHORT Length;
USHORT MaximumLength;
PWSTR Buffer;
That is, the first longword will contain something like 00800020 where 20
is the actual length of the Unicode string, and the next longword will
contain the address of buffer. This address will be in system space, so
the high order bit will be set.
If the argument is a pointer to a device object, then the format of the
first
word will be:
USHORT Type;
That is, the first word will contain a 0003, where the Type code will
ALWAYS
be 0003.
Note that this makes it immediately obvious whether the argument is a
pointer
to an ARC name string or a device object, since a Unicode string can never
have an odd number of bytes, and a device object will always have a Type
code of 3.
Arguments:
Arg1: f789ea88, Pointer to the device object or Unicode string of ARC name
Arg2: c0000034
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x7B
PROCESS_NAME: System
CURRENT_IRQL: 1f
LAST_CONTROL_TRANSFER: from 8103716d to 811507b4
STACK_TEXT:
f789e638 8103716d 00000004 ffdff408 00000000
nt!RtlpBreakWithStatusInstruction
f789e684 810384c8 00000004 80076000 e105b740 nt!KiBugCheckDebugBreak+0x19
f789ea1c 81038519 0000007b f789ea88 c0000034 nt!KeBugCheck2+0x9b0
f789ea3c 814e9127 0000007b f789ea88 c0000034 nt!KeBugCheckEx+0x1b
f789eba4 814ec398 80076000 00000000 80076000 nt!IopMarkBootPartition+0xf7
f789ebf4 814e7ba2 80076000 f789ec38 00034000
nt!IopInitializeBootDrivers+0x542
f789ec68 814e50ff 80076000 00000000 8a097020 nt!IoInitSystem+0x730
f789eda0 812f0211 80076000 f789eddc 813b5d7c
nt!Phase1InitializationDiscard+0xc89
f789edac 813b5d7c 80076000 00000000 00000000 nt!Phase1Initialization+0xd
f789eddc 81174ed6 812f0204 80076000 00000000
nt!PspSystemThreadStartup+0x2e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!IopMarkBootPartition+f7
814e9127 8d85e0feffff lea eax,[ebp-120h]
SYMBOL_STACK_INDEX: 4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 42435c1a
SYMBOL_NAME: nt!IopMarkBootPartition+f7
FAILURE_BUCKET_ID: 0x7B_nt!IopMarkBootPartition+f7
BUCKET_ID: 0x7B_nt!IopMarkBootPartition+f7
Followup: MachineOwner
---------
If I type 'g' at Windbg command, I will get blue screen. I couldn't
continue
to install. How can I solve this problem?
Thanks,
May
.
- References:
- Prev by Date: Microsoft USB OS Descriptors
- Next by Date: Re: driver for Mouse like device
- Previous by thread: During the debug setup phase, blue screen
- Next by thread: Microsoft USB OS Descriptors
- Index(es):
Relevant Pages
|
Loading
