Hi Slobodan,
So in last attempt you did not used any of components provided by TA/TAP,
right? This is good since you now know at least that inf files pulled by
these components is not causing failure.
That's right.
Also what chipset do you use. Or what platform?
It is a AOpen MX4SGI-4DN2 and uses the Intel 865G chipset.
http://asia.aopen.com.tw/Products/mb/MX4SGI-4DN2;MX4SGI-4DN2(P).htm
Do you have an RS-232 or 1394 cable for establishing remote debugging from
your targed machine? This would give you insight where is the problem.
In windbg just type.
1. !devnode 0 1
2. !analyze -v
And send us these results.
I have never used KD or windbg before and am having problems getting it to
work. Here are the results:
kd> !devnode 0 1
Error retrieving address of IopRootDeviceNode
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: f8950524, Pointer to the device object or Unicode string of ARC name
Arg2: c0000034
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x7B
LAST_CONTROL_TRANSFER: from 8053771f to 804e30d9
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f89500d8 8053771f 00000004 00000000 80087000 nt!DbgBreakPointWithStatus+0x4
f89504b8 80537832 0000007b f8950524 c0000034 nt!KeDeregisterBugCheckReasonCallback+0xbc8
f89504d8 806ce5b4 0000007b f8950524 c0000034 nt!KeBugCheckEx+0x1b
f8950640 806bcefb 80087000 00000000 80087000 nt!KeFindConfigurationNextEntry+0x115fd
f8950690 806b2f69 80087000 f89506ac 00034000 nt!KeFindConfigurationEntry+0x4fd2
f8950838 806b3fea 80087000 00000000 81fc8958 nt!SeTokenObjectType+0x16089
f8950dac 80576b24 80087000 00000000 00000000 nt!SeTokenObjectType+0x1710a
f8950ddc 804eed86 806b3797 80087000 00000000 nt!PsCreateSystemThread+0x70
00000000 00000000 00000000 00000000 00000000 nt!KeInitializeTimerEx+0x1eb
FOLLOWUP_IP:
nt!KeDeregisterBugCheckReasonCallback+bc8
8053771f 8b4dfc mov ecx,[ebp-0x4]
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KeDeregisterBugCheckReasonCallback+bc8
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 41107faa
STACK_COMMAND: kb
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner