Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Waiting for pipe \\.\pipe\rosdbg Waiting to reconnect... (ntoskrnl\kd64\kdinit.c:74) ----------------------------------------------------- (ntoskrnl\kd64\kdinit.c:75) ReactOS 0.4.13-dev (Build 20190624-0.4.13-dev-547-g99fa388) (Commit 99fa38809fd8ed38d4d59fa1fcf3babb3216b895) (ntoskrnl\kd64\kdinit.c:76) 1 System Processor [512 MB Memory] (ntoskrnl\kd64\kdinit.c:80) Command Line: NOGUIBOOT KDSERIAL DEBUGPORT=COM1 FIRSTCHANCE (ntoskrnl\kd64\kdinit.c:81) ARC Paths: multi(0)disk(0)cdrom(96) \ multi(0)disk(0)cdrom(96) \reactos\ Connected to Windows Server 2003 3790 x86 compatible target at (Mon Jun 24 23:45:49.138 2019 (UTC + 3:00)), ptr64 FALSE Kernel Debugger connection established. Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Windows Server 2003 Kernel Version 3790 UP Checked x86 compatible Built by: 20190624-0.4.13-dev-547-g99fa388.MSVC_19.21.27702.2 Machine Name: Kernel base = 0x80400000 PsLoadedModuleList = 0x805b8280 System Uptime: not available (ntoskrnl\ke\i386\cpu.c:450) Supported CPU features : KF_V86_VIS KF_RDTSC KF_CR4 KF_CMOV KF_GLOBAL_PAGE KF_LARGE_PAGE KF_MTRR KF_CMPXCHG8B KF_MMX KF_PAT KF_FXSR KF_FAST_SYSCALL KF_XMMI KF_XMMI64 KF_NX_BIT (ntoskrnl\ke\i386\cpu.c:722) Prefetch Cache: 32 bytes L2 Cache: 131072 bytes L2 Cache Line: 64 bytes L2 Cache Associativity: 4 (ntoskrnl\mm\ARM3\mminit.c:1452) HAL I/O Mapping at FFFE0000 is unsafe (ntoskrnl\mm\mminit.c:131) 0x80000000 - 0x83000000 Boot Loaded Image (ntoskrnl\mm\mminit.c:135) 0xB0000000 - 0xB0380000 PFN Database (ntoskrnl\mm\mminit.c:139) 0xB0380000 - 0xB1360000 ARM3 Non Paged Pool (ntoskrnl\mm\mminit.c:143) 0xB9400000 - 0xBB400000 System View Space (ntoskrnl\mm\mminit.c:147) 0xBB400000 - 0xC0000000 Session Space (ntoskrnl\mm\mminit.c:150) 0xC0000000 - 0xC03FFFFF Page Tables (ntoskrnl\mm\mminit.c:153) 0xC0300000 - 0xC0300FFF Page Directories (ntoskrnl\mm\mminit.c:156) 0xC0400000 - 0xC07FFFFF Hyperspace (ntoskrnl\mm\mminit.c:159) 0xC1000000 - 0xE0FFFFFF System Cache (ntoskrnl\mm\mminit.c:163) 0xE1000000 - 0xEDC00000 ARM3 Paged Pool (ntoskrnl\mm\mminit.c:166) 0xEDC00000 - 0xF8BC0000 System PTE Space (ntoskrnl\mm\mminit.c:169) 0xF8BC0000 - 0xFFBE0000 Non Paged Pool Expansion PTE Space (ntoskrnl\config\cmcheck.c:25) CmCheckRegistry(0xB1304008, 2) is UNIMPLEMENTED! (hal\halx86\legacy\bussupp.c:728) Found parent bus (indicating PCI Bridge). PCI devices may fail! ====== PCI BUS HARDWARE DETECTION ======= 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 00) Subsystem: Unknown [0000:0000] Flags: bus master, medium devsel, latency 0 Device has Extended Address Decoding. It may fail to work on older BIOSes! 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] [8086:7000] (rev 00) Subsystem: Unknown [0000:0000] Flags: bus master, medium devsel, latency 0 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] [8086:7010] (rev 00) Subsystem: Unknown [0000:0000] Flags: medium devsel, latency 0 I/O ports at c000 [size=16K] 00:01.2 USB controller [0c03]: Intel Corporation 82371SB PIIX3 USB [Natoma/Triton II] [8086:7020] (rev 01) Subsystem: Unknown [0000:0000] Flags: bus master, medium devsel, latency 32, IRQ 09 I/O ports at c020 [size=32] Device is using IRQ 9! ISA Cards using that IRQ may fail! 00:01.3 Secondary bus towards host CPU [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 03) Subsystem: Unknown [0000:0000] Flags: medium devsel, latency 0, IRQ 09 Device is using IRQ 9! ISA Cards using that IRQ may fail! 00:02.0 USB controller [0c03]: LSI Corporation USS-344S USB Controller [11c1:5803] (rev 11) Subsystem: Unknown [11c1:5803] Flags: bus master, medium devsel, latency 64, IRQ 11 Memory at c0000000 (32-bit, non-prefetchable) [size=1024M] Device is using IRQ 11! ISA Cards using that IRQ may fail! ====== PCI BUS DETECTION COMPLETE ======= PC Compatible Eisa/Isa HAL Detected (sdk\lib\rtl\image.c:172) Invalid base address: 00000000 (ntoskrnl\io\iomgr\driver.c:1635) '\Driver\sacdrv' initialization failed, status (0xc0000037) (ntoskrnl\io\iomgr\driver.c:64) Deleting driver object '\Driver\sacdrv' Btrfs ERR : add_group_mapping : invalid SID WARNING: NtNotifyChangeMultipleKeys at ntoskrnl\config\ntapi.c:1450 is UNIMPLEMENTED! Btrfs ERR : watch_registry : ZwNotifyChangeKey returned c0000002 (drivers\storage\class\ramdisk\ramdisk.c:2486) FIXME: Installing from RamDisk is UNSUPPORTED! (drivers\storage\scsiport\scsiport.c:5859) ZwOpenKey() failed with Status=0xC0000034 (hal\halx86\legacy\bussupp.c:1243) Slot assignment for 5 on bus 0 (hal\halx86\legacy\bus\pcibus.c:727) WARNING: PCI Slot Resource Assignment is FOOBAR (ntoskrnl\io\iomgr\iorsrce.c:874) IoReportResourceUsage is halfplemented! (ntoskrnl\io\iomgr\iorsrce.c:874) IoReportResourceUsage is halfplemented! (ntoskrnl\io\iomgr\driver.c:1635) '\Driver\buslogic' initialization failed, status (0xc00000c0) (ntoskrnl\io\iomgr\driver.c:64) Deleting driver object '\Driver\buslogic' (drivers\storage\port\storport\storport.c:960) StorPortInitialize(B12DBF38 F88E59F0 F88E583C 00000000) (drivers\storage\port\storport\storport.c:962) HwInitializationDataSize: 84 (drivers\storage\port\storport\storport.c:963) AdapterInterfaceType: 5 (drivers\storage\port\storport\storport.c:964) HwInitialize: F8B08810 (drivers\storage\port\storport\storport.c:965) HwStartIo: F8B08BF0 (drivers\storage\port\storport\storport.c:966) HwInterrupt: F8B08900 (drivers\storage\port\storport\storport.c:967) HwFindAdapter: F8B08250 (drivers\storage\port\storport\storport.c:968) HwResetBus: F8B08B50 (drivers\storage\port\storport\storport.c:969) HwDmaStarted: 00000000 (drivers\storage\port\storport\storport.c:970) HwAdapterState: 00000000 (drivers\storage\port\storport\storport.c:971) DeviceExtensionSize: 75584 (drivers\storage\port\storport\storport.c:972) SpecificLuExtensionSize: 0 (drivers\storage\port\storport\storport.c:973) SrbExtensionSize: 1320 (drivers\storage\port\storport\storport.c:974) NumberOfAccessRanges: 6 (drivers\storage\port\storport\storport.c:1000) No driver object extension! (drivers\storage\port\storport\storport.c:1012) Driver object extension created! (drivers\storage\port\storport\storport.c:31) PortAddDriverInitData() (drivers\storage\port\storport\storport.c:1043) StorPortInitialize() done (Status 0x00000000) (ntoskrnl\io\iomgr\driver.c:1635) '\Driver\floppy' initialization failed, status (0xc000000e) (ntoskrnl\io\iomgr\driver.c:64) Deleting driver object '\Driver\floppy' (drivers\storage\port\storport\storport.c:460) DriverEntry(B12A8280 F88E59F0) (drivers\storage\scsiport\scsiport.c:2894) unknown ioctl code: 0x24054 (drivers\storage\scsiport\scsiport.c:2894) unknown ioctl code: 0x24000 (drivers\storage\scsiport\scsiport.c:2894) unknown ioctl code: 0x24038 (drivers\storage\scsiport\scsiport.c:2894) unknown ioctl code: 0x24054 *** Fatal System Error: 0x0000007b (0xB12A9A98,0xC000014F,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 (Mon Jun 24 23:46:01.297 2019 (UTC + 3:00)), ptr64 FALSE Loading Kernel Symbols ............................ nt!RtlpBreakWithStatusInstruction: 805354d8 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: b12a9a98, Pointer to the device object or Unicode string of ARC name Arg2: c000014f 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 804862e8 to 805354d8 STACK_TEXT: f88e5110 804862e8 00000003 f88e5420 ffdff408 nt!RtlpBreakWithStatusInstruction f88e5140 8048582f 00000003 f88e59f4 f88e5ad8 nt!KiBugCheckDebugBreak+0x38 [C:\rosgit\ntoskrnl\ke\bug.c @ 538] f88e54e0 80485200 0000007b b12a9a98 c000014f nt!KeBugCheckWithTf+0x58f [C:\rosgit\ntoskrnl\ke\bug.c @ 1099] f88e5500 804734a0 0000007b b12a9a98 c000014f nt!KeBugCheckEx+0x20 [C:\rosgit\ntoskrnl\ke\bug.c @ 1458] f88e55b8 80472998 b12a9a98 00000000 00000000 nt!IopMountVolume+0x760 [C:\rosgit\ntoskrnl\io\iomgr\volume.c @ 782] f88e55e4 8046237e b131c520 b12a9a98 f88e577c nt!IopCheckVpbMounted+0x98 [C:\rosgit\ntoskrnl\io\iomgr\volume.c @ 105] f88e5744 804e3af3 b12a9a98 00000000 b130e300 nt!IopParseDevice+0x73e [C:\rosgit\ntoskrnl\io\iomgr\file.c @ 634] f88e57dc 804dd30b 00000000 f88e5810 00000040 nt!ObpLookupObjectName+0x863 [C:\rosgit\ntoskrnl\ob\obname.c @ 986] f88e5834 80460def f88e5ad8 00000000 00000000 nt!ObOpenObjectByName+0x15b [C:\rosgit\ntoskrnl\ob\obhandle.c @ 2609] f88e594c 8045eb66 f88e5b04 00000001 f88e5ad8 nt!IopCreateFile+0x10cf [C:\rosgit\ntoskrnl\io\iomgr\file.c @ 2872] f88e5994 80464762 f88e5b04 00000001 f88e5ad8 nt!IoCreateFile+0x46 [C:\rosgit\ntoskrnl\io\iomgr\file.c @ 3042] f88e59d4 80518deb f88e5b04 00000001 f88e5ad8 nt!NtOpenFile+0x32 [C:\rosgit\ntoskrnl\io\iomgr\file.c @ 3973] f88e59fc 80516d7c 80464730 f88e5ac0 00000018 nt!KiSystemCallTrampoline+0x1b [C:\rosgit\ntoskrnl\include\internal\i386\ke.h @ 766] f88e5a40 80403d16 f88e5b0c 804019a5 badb0d00 nt!KiSystemServiceHandler+0x25c [C:\rosgit\ntoskrnl\ke\i386\traphdlr.c @ 1833] f88e5a40 804019a5 f88e5b0c 804019a5 badb0d00 nt!KiSystemService+0x60 f88e5ab8 80567179 f88e5b04 00000001 f88e5ad8 nt!ZwOpenFile+0x11 f88e5b0c 8055c771 7665445c 5c656369 6f526443 nt!PsLocateSystemDll+0x49 [C:\rosgit\ntoskrnl\ps\psmgr.c @ 294] f88e5c78 80558ad7 80073000 74697472 206e6f69 nt!IoInitSystem+0x7a1 [C:\rosgit\ntoskrnl\io\iomgr\iomgr.c @ 643] f88e5d80 8042c80e 80073000 f88e5dc0 804fa134 nt!Phase1InitializationDiscard+0x9d7 [C:\rosgit\ntoskrnl\ex\init.c @ 1805] f88e5d8c 804fa134 80073000 00061210 e000003b nt!Phase1Initialization+0xe [C:\rosgit\ntoskrnl\ex\init.c @ 2022] f88e5dc0 80516332 8042c800 80073000 f88e5df0 nt!PspSystemThreadStartup+0x64 [C:\rosgit\ntoskrnl\ps\thread.c @ 158] f88e5ddc 804fa0cf 8042c800 80073000 00000000 nt!KiThreadStartup+0x42 [C:\rosgit\ntoskrnl\ke\i386\thrdini.c @ 81] f88e5de0 8042c7ff 80073000 00000000 0000027f nt!PspCreateThread+0xa5f f88e5de4 80073000 00000000 0000027f 00000000 nt!RtlStringVPrintfWorkerA+0x8f WARNING: Frame IP not in any known module. Following frames may be wrong. f88e5de8 00000000 0000027f 00000000 00000000 0x80073000 STACK_COMMAND: kb FOLLOWUP_IP: nt!IopMountVolume+760 [C:\rosgit\ntoskrnl\io\iomgr\volume.c @ 782] 804734a0 8b45fc mov eax,dword ptr [ebp-4] FAULTING_SOURCE_CODE: 778: 0); 779: } 780: 781: /* Return the mount status */ > 782: return Status; 783: } 784: 785: /* 786: * @implemented 787: */ SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: nt!IopMountVolume+760 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntoskrnl.exe DEBUG_FLR_IMAGE_TIMESTAMP: 5d113478 FAILURE_BUCKET_ID: 0x7B_nt!IopMountVolume+760 BUCKET_ID: 0x7B_nt!IopMountVolume+760 Followup: MachineOwner ---------