Hi, I am having simuler problum with a pcm-9575 SBC. I dont now if this helps but hear is my Bugcheck Analysis:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d4000 PsLoadedModuleList = 0x80557b20
Debug session time: Sun Jul 2 06:32:25.980 2006 (GMT-7)
System Uptime: 0 days 0:00:07.540
Break instruction exception - code 80000003 (first chance)
A fatal system error has occurred.
Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Loading Kernel Symbols
...................
Loading User Symbols
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7B, {f9943528, c0000034, 0, 0}
Probably caused by : ntoskrnl.exe ( nt!IopMarkBootPartition+113 )
Followup: MachineOwner
---------
nt!RtlpBreakWithStatusInstruction:
804e0b25 cc int 3
kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* 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: f9943528, 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
LAST_CONTROL_TRANSFER: from 8052f8e7 to 804e0b25
STACK_TEXT:
f9943090 8052f8e7 00000004 ffdff408 00000000 nt!RtlpBreakWithStatusInstruction
f99430dc 8053089b 00000004 00000000 80088000 nt!KiBugCheckDebugBreak+0x19
f99434bc 805309ae 0000007b f9943528 c0000034 nt!KeBugCheck2+0xa51
f99434dc 806b5c94 0000007b f9943528 c0000034 nt!KeBugCheckEx+0x1b
f9943644 806a6093 80088000 00000000 80088000 nt!IopMarkBootPartition+0x113
f9943694 8069c714 80088000 f99436b0 00034000 nt!IopInitializeBootDrivers+0x4ba
f994383c 8069dab0 80088000 00000000 80f42218 nt!IoInitSystem+0x712
f9943dac 8057afed 80088000 00000000 00000000 nt!Phase1Initialization+0x9b5
f9943ddc 804f7477 8069d33e 80088000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!IopMarkBootPartition+113
806b5c94 8d85e4feffff lea eax,[ebp-0x11c]
FAULTING_SOURCE_CODE:
SYMBOL_STACK_INDEX: 4
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!IopMarkBootPartition+113
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 41108004
FAILURE_BUCKET_ID: 0x7B_nt!IopMarkBootPartition+113
BUCKET_ID: 0x7B_nt!IopMarkBootPartition+113
Followup: MachineOwner
---------
