petada hase P2V


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Opened \\.\com1
Waiting to reconnect...
Connected to Windows Server 2003 3790 x86 compatible target at (Thu Aug 11 08:48:40.280 2011 (GMT-7)), ptr64 FALSE
Kernel Debugger connection established.
WARNING: Inaccessible path: 'c:\symbols\local_symbols'
WARNING: Whitespace at end of path element
Symbol search path is: c:\symbols\local_symbols;SRV*c:\symbols\websymbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows Server 2003 Kernel Version 3790 MP (1 procs) Free x86 compatible
Built by: 3790.srv03_sp2_qfe.101019-0340
Machine Name:
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a8ee8
System Uptime: not available

*** Fatal System Error: 0x0000007b
                       (0xF78A6A94,0xC0000034,0x00000000,0x00000000)

Break instruction exception - code 80000003 (first chance)

A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.

A fatal system error has occurred.

Connected to Windows Server 2003 3790 x86 compatible target at (Thu Aug 11 08:51:58.478 2011 (GMT-7)), ptr64 FALSE
Loading Kernel Symbols
.........

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.......................
Loading User Symbols

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7B, {f78a6a94, c0000034, 0, 0}

Probably caused by : ntkrpamp.exe ( nt!IopMarkBootPartition+f7 )

Followup: MachineOwner
---------

nt!RtlpBreakWithStatusInstruction:
80873588 cc              int     3
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: f78a6a94, Pointer to the device object or Unicode string of ARC name
Arg2: c0000034
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------


DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR:  0x7B

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 80826afb to 80873588

STACK_TEXT:
f78a6644 80826afb 00000003 00000000 00000000 nt!RtlpBreakWithStatusInstruction
f78a6690 80827a08 00000003 00000000 80087000 nt!KiBugCheckDebugBreak+0x19
f78a6a28 80827e01 0000007b f78a6a94 c0000034 nt!KeBugCheck2+0x5ea
f78a6a48 80a0981d 0000007b f78a6a94 c0000034 nt!KeBugCheckEx+0x1b
f78a6bb0 80a0bcf3 80087000 00000000 80087000 nt!IopMarkBootPartition+0xf7
f78a6c00 80a085b1 80087000 f78a6c44 00000000 nt!IopInitializeBootDrivers+0x4bb
f78a6c70 80a0672a 80087000 00000000 86ba13d8 nt!IoInitSystem+0x641
f78a6da0 808eab33 80087000 f78a6ddc 8094c0ac nt!Phase1InitializationDiscard+0xad0
f78a6dac 8094c0ac 80087000 00000000 00000000 nt!Phase1Initialization+0xd
f78a6ddc 8088fd5e 808eab26 80087000 00000000 nt!PspSystemThreadStartup+0x2e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!IopMarkBootPartition+f7
80a0981d 8d85e0feffff    lea     eax,[ebp-120h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!IopMarkBootPartition+f7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4cbd93bc

FAILURE_BUCKET_ID:  0x7B_nt!IopMarkBootPartition+f7

BUCKET_ID:  0x7B_nt!IopMarkBootPartition+f7

Followup: MachineOwner
---------