Microsoft (R) Windows Debugger Version 10.0.15063.468 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Opened \\.\pipe\bochs-com Waiting to reconnect... (..\ntoskrnl\kd64\kdinit.c:378) ----------------------------------------------------- (..\ntoskrnl\kd64\kdinit.c:379) ReactOS 0.5-SVN (Build 20170813-r75532) (..\ntoskrnl\kd64\kdinit.c:381) 1 System Processor [511 MB Memory] (..\ntoskrnl\kd64\kdinit.c:384) Command Line: NOGUIBOOT KDSERIAL DEBUGPORT=COM1 FIRSTCHANCE (..\ntoskrnl\kd64\kdinit.c:388) ARC Paths: multi(0)disk(0)rdisk(0)partition(1) \ multi(0)disk(0)rdisk(0)partition(1) \reactos\ Connected to Windows Server 2003 3790 x86 compatible target at (Tue Aug 15 22:01:41.047 2017 (UTC + 2:00)), ptr64 FALSE Kernel Debugger connection established. ************* Symbol Path validation summary ************** Response Time (ms) Location OK D:\ReactOS-Trunk\reactos\output-VS-i386\msvc_pdb Symbol search path is: D:\ReactOS-Trunk\reactos\output-VS-i386\msvc_pdb Executable search path is: Windows Server 2003 Kernel Version 3790 UP Checked x86 compatible Built by: 20170813-r75532.MSVC_19.10.25019.0 Machine Name: Kernel base = 0x80400000 PsLoadedModuleList = 0x805af340 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:1442) HAL I/O Mapping at FFFE0000 is unsafe (..\ntoskrnl\mm\mminit.c:134) 0x80000000 - 0x83000000 Boot Loaded Image (..\ntoskrnl\mm\mminit.c:138) 0xB0000000 - 0xB0380000 PFN Database (..\ntoskrnl\mm\mminit.c:142) 0xB0380000 - 0xB1358000 ARM3 Non Paged Pool (..\ntoskrnl\mm\mminit.c:146) 0xB9400000 - 0xBB400000 System View Space (..\ntoskrnl\mm\mminit.c:150) 0xBB400000 - 0xC0000000 Session Space (..\ntoskrnl\mm\mminit.c:153) 0xC0000000 - 0xC03FFFFF Page Tables (..\ntoskrnl\mm\mminit.c:156) 0xC0300000 - 0xC0300FFF Page Directories (..\ntoskrnl\mm\mminit.c:159) 0xC0400000 - 0xC07FFFFF Hyperspace (..\ntoskrnl\mm\mminit.c:163) 0xE1000000 - 0xEDC00000 ARM3 Paged Pool (..\ntoskrnl\mm\mminit.c:166) 0xEDC00000 - 0xF8BB8000 System PTE Space (..\ntoskrnl\mm\mminit.c:169) 0xF8BB8000 - 0xFFBE0000 Non Paged Pool Expansion PTE Space (..\ntoskrnl\config\cmhvlist.c:158) CmpAddToHiveFileList: Creation or opening of the hive list failed, status = 0xc0000034 (..\hal\halx86\legacy\bussupp.c:717) 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 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! Device is an Intel UHCI (USB) Controller. Turn off Legacy USB in your BIOS! 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! ====== PCI BUS DETECTION COMPLETE ======= PC Compatible Eisa/Isa HAL Detected (..\ntoskrnl\io\pnpmgr\pnpinit.c:62) WARNING!! In PiInitCacheGroupInformation, using ReactOS HACK for SETUPLDR!! (..\ntoskrnl\io\pnpmgr\pnpmgr.c:3288) ZwOpenKey(\Registry\Machine\SYSTEM\CURRENTCONTROLSET\Control\Pnp) failed with status 0xc0000034 (..\ntoskrnl\ps\apphelp.c:318) SHIMS: ApphelpCacheRead could not even open Session Manager\AppCompatCache (0xc0000034) (..\ntoskrnl\wmi\wmi.c:72) IoWMIRegistrationControl() called for DO B132AF18, requesting 1 action, returning success (..\sdk\lib\rtl\image.c:171) Invalid base address: 00000000 (..\ntoskrnl\io\iomgr\driver.c:1576) '\Driver\sacdrv' initialization failed, status (0xc0000037) (..\ntoskrnl\io\iomgr\driver.c:64) Deleting driver object '\Driver\sacdrv' (..\drivers\storage\scsiport\scsiport.c:5859) ZwOpenKey() failed with Status=0xC0000034 (..\hal\halx86\legacy\bussupp.c:1253) 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:1576) '\Driver\buslogic' initialization failed, status (0xc00000c0) (..\ntoskrnl\io\iomgr\driver.c:64) Deleting driver object '\Driver\buslogic' (..\drivers\storage\class\disk\disk.c:2257) HACK: Handling partition 0 request! (..\ntoskrnl\io\iomgr\driver.c:1576) '\Driver\floppy' initialization failed, status (0xc000000e) (..\ntoskrnl\io\iomgr\driver.c:64) Deleting driver object '\Driver\floppy' (..\drivers\storage\class\ramdisk\ramdisk.c:2438) FIXME: Installing from RamDisk is UNSUPPORTED! Ext2Fsd -- Version 0.68 Checked -- Aug 13 2017 18:19:54. Ext2Fsd:~0: 22:04:14:966 b1308940: Ext2QueryParameters: CodePage not specified. Ext2Fsd:~0: 22:04:14:981 b1308940: Ext2QueryParameters: HidingPrefix not specified. Ext2Fsd:~0: 22:04:14:996 b1308940: Ext2QueryParameters: HidingSuffix not specified. (..\ntoskrnl\ex\work.c:351) EX: Work Queue Deadlock detected: 1 (..\ntoskrnl\ex\work.c:353) Dynamic threads queued 1 Btrfs ERR : read_mappings : ZwCreateKey returned c0000034 Btrfs ERR : read_registry : ZwCreateKey returned c0000034 Rfsd 0.26 read-only checked Aug 13 2017 18:19:59 Copyright (C) 1999-2015 Mark Piper, Matt Wu, Bo Branten. Rfsd: RfsdQueryParameters: WritingSupport=0h Rfsd: RfsdQueryParameters: CheckingBitmap=0h Rfsd: RfsdQueryParameters: Ext3ForceWriting=0h Rfsd: RfsdQueryParameters: CodePage not specified. RfsdLoadAllNls: succeed to load all codepages ... Rfsd: User specified codepage (default) was not found. Defulat system OEM codepage will be adopted. ffsdrv -- Version 0.5.2 (ReadOnly) Checked - Built at Aug 13 2017 18:19:52. FFS: 22:04:16:946 b1308940: FFSQueryParameters: WritingSupport=0h FFS: 22:04:16:976 b1308940: FFSQueryParameters: CheckingBitmap=0h FFS: 22:04:16:991 b1308940: FFSQueryParameters: PartitionNumber=0h (..\ntoskrnl\io\iomgr\file.c:554) Using IopParseDevice() hack. Requested invalid attributes: 0 (..\drivers\storage\class\disk\disk.c:2257) HACK: Handling partition 0 request! (..\ntoskrnl\io\iomgr\iorsrce.c:725) Failed to open symlink \Device\Harddisk0\Partition1, Status=c0000024 (..\ntoskrnl\io\iomgr\file.c:554) Using IopParseDevice() hack. Requested invalid attributes: 0 (..\ntoskrnl\io\iomgr\file.c:554) Using IopParseDevice() hack. Requested invalid attributes: 1 (..\ntoskrnl\io\iomgr\file.c:554) Using IopParseDevice() hack. Requested invalid attributes: 0 (..\drivers\storage\class\disk\disk.c:2257) HACK: Handling partition 0 request! FFSLoadDiskLabel() No BSD disklabel found, trying to find BSD file system on "normal" partition. FFSLoadDiskLabel() No BSD file system was found on the "normal" partition. *** Fatal System Error: 0x0000007b (0xB12A2038,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 (Tue Aug 15 22:01:47.139 2017 (UTC + 2:00)), ptr64 FALSE Loading Kernel Symbols .............................. Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7B, {b12a2038, c000014f, 0, 0} Probably caused by : ntoskrnl.exe ( nt!IopMountVolume+760 ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 80523e48 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: b12a2038, Pointer to the device object or Unicode string of ARC name Arg2: c000014f, (reserved) Arg3: 00000000, (reserved) Arg4: 00000000 Debugging Details: ------------------ DUMP_CLASS: 1 DUMP_QUALIFIER: 0 BUILD_VERSION_STRING: 20170813-r75532.MSVC_19.10.25019.0 DUMP_TYPE: 0 BUGCHECK_P1: ffffffffb12a2038 BUGCHECK_P2: ffffffffc000014f BUGCHECK_P3: 0 BUGCHECK_P4: 0 CPU_COUNT: 1 CPU_MHZ: 4 CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 3 CPU_STEPPING: 3 DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO BUGCHECK_STR: 0x7B PROCESS_NAME: System CURRENT_IRQL: 0 ANALYSIS_SESSION_HOST: COLINT470P ANALYSIS_SESSION_TIME: 08-15-2017 22:02:14.0039 ANALYSIS_VERSION: 10.0.15063.468 amd64fre LAST_CONTROL_TRANSFER: from 8047e528 to 80523e48 STACK_TEXT: f8739220 8047e528 00000003 f8739530 ffdff408 nt!RtlpBreakWithStatusInstruction f8739250 8047dadf 00000003 f8739a4c f8739b2c nt!KiBugCheckDebugBreak+0x38 [d:\reactos-trunk\reactos\ntoskrnl\ke\bug.c @ 538] f87395f0 8047d4b0 0000007b b12a2038 c000014f nt!KeBugCheckWithTf+0x58f [d:\reactos-trunk\reactos\ntoskrnl\ke\bug.c @ 1101] f8739610 8046d710 0000007b b12a2038 c000014f nt!KeBugCheckEx+0x20 [d:\reactos-trunk\reactos\ntoskrnl\ke\bug.c @ 1462] f87396c8 8046cc14 b12a2038 00000000 00000000 nt!IopMountVolume+0x760 [d:\reactos-trunk\reactos\ntoskrnl\io\iomgr\volume.c @ 774] f87396f4 8045d371 b1315818 b12a2038 f8739868 nt!IopCheckVpbMounted+0x94 [d:\reactos-trunk\reactos\ntoskrnl\io\iomgr\volume.c @ 105] f8739830 804d811a b12a2038 00000000 b1338008 nt!IopParseDevice+0x771 [d:\reactos-trunk\reactos\ntoskrnl\io\iomgr\file.c @ 603] f87398c4 804d0fab 00000000 f87398f8 00000040 nt!ObpLookupObjectName+0x7da [d:\reactos-trunk\reactos\ntoskrnl\ob\obname.c @ 860] f873991c 8045be10 f8739b2c 00000000 00000000 nt!ObOpenObjectByName+0x15b [d:\reactos-trunk\reactos\ntoskrnl\ob\obhandle.c @ 2602] f87399a4 8045a696 f8739b58 00000001 f8739b2c nt!IopCreateFile+0x9a0 [d:\reactos-trunk\reactos\ntoskrnl\io\iomgr\file.c @ 2477] f87399ec 8045f0d2 f8739b58 00000001 f8739b2c nt!IoCreateFile+0x46 [d:\reactos-trunk\reactos\ntoskrnl\io\iomgr\file.c @ 2647] f8739a2c 805081bb f8739b58 00000001 f8739b2c nt!NtOpenFile+0x32 [d:\reactos-trunk\reactos\ntoskrnl\io\iomgr\file.c @ 3530] f8739a54 805063ff 8045f0a0 f8739b14 00000018 nt!KiSystemCallTrampoline+0x1b [d:\reactos-trunk\reactos\ntoskrnl\include\internal\i386\ke.h @ 748] f8739a94 80403d96 f8739b60 804019a5 badb0d00 nt!KiSystemServiceHandler+0x22f [d:\reactos-trunk\reactos\ntoskrnl\ke\i386\traphdlr.c @ 1815] f8739a94 804019a5 f8739b60 804019a5 badb0d00 nt!KiInterruptTemplateDispatch+0x60 f8739b0c 804e3b69 f8739b58 00000001 f8739b2c nt!ZwOpenFile+0x11 f8739b60 8053dc86 7665445c 5c656369 64726148 nt!PsLocateSystemDll+0x49 [d:\reactos-trunk\reactos\ntoskrnl\ps\psmgr.c @ 294] f8739c84 8042cbb9 8007a000 750539e8 1e8b662a nt!IoInitSystem+0x486 [d:\reactos-trunk\reactos\ntoskrnl\io\iomgr\iomgr.c @ 636] f8739d80 8042c1fe 8007a000 f8739dc0 804ec304 nt!Phase1InitializationDiscard+0x9a9 [d:\reactos-trunk\reactos\ntoskrnl\ex\init.c @ 1801] f8739d8c 804ec304 8007a000 00007754 e000003b nt!Phase1Initialization+0xe [d:\reactos-trunk\reactos\ntoskrnl\ex\init.c @ 2018] f8739dc0 80505a12 8042c1f0 8007a000 f8739df0 nt!PspSystemThreadStartup+0x64 [d:\reactos-trunk\reactos\ntoskrnl\ps\thread.c @ 158] f8739ddc 804ec29f 8042c1f0 8007a000 a366e300 nt!KiThreadStartup+0x42 [d:\reactos-trunk\reactos\ntoskrnl\ke\i386\thrdini.c @ 81] f8739de0 8042c1ef 8007a000 a366e300 0000027f nt!PspCreateThread+0xa5f f8739de4 8007a000 a366e300 0000027f 00000000 nt!ExpLoadInitialProcess+0x45f WARNING: Frame IP not in any known module. Following frames may be wrong. f8739de8 a366e300 0000027f 00000000 00000000 0x8007a000 f8739dec 00000000 00000000 00000000 00000000 0xa366e300 STACK_COMMAND: kb THREAD_SHA1_HASH_MOD_FUNC: 84f397a0a5db36ff995b92869184251239b83b8f THREAD_SHA1_HASH_MOD_FUNC_OFFSET: a1136b5a72d7cefa9f8fc3a29193048a4d38d0d4 THREAD_SHA1_HASH_MOD: ef0b9811d1c3c2b0b400d0c8a17067df59efd56d FOLLOWUP_IP: nt!IopMountVolume+760 [d:\reactos-trunk\reactos\ntoskrnl\io\iomgr\volume.c @ 774] 8046d710 8b45fc mov eax,dword ptr [ebp-4] FAULT_INSTR_CODE: 8bfc458b FAULTING_SOURCE_LINE: d:\reactos-trunk\reactos\ntoskrnl\io\iomgr\volume.c FAULTING_SOURCE_FILE: d:\reactos-trunk\reactos\ntoskrnl\io\iomgr\volume.c FAULTING_SOURCE_LINE_NUMBER: 774 FAULTING_SOURCE_CODE: 770: 0); 771: } 772: 773: /* Return the mount status */ > 774: return Status; 775: } 776: 777: /* 778: * @implemented 779: */ SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: nt!IopMountVolume+760 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntoskrnl.exe DEBUG_FLR_IMAGE_TIMESTAMP: 59907c45 IMAGE_VERSION: 5.2.3790.3959 FAILURE_BUCKET_ID: 0x7B_nt!IopMountVolume+760 BUCKET_ID: 0x7B_nt!IopMountVolume+760 PRIMARY_PROBLEM_CLASS: 0x7B_nt!IopMountVolume+760 TARGET_TIME: 2017-08-15T22:04:20.000Z OSBUILD: 3790 OSSERVICEPACK: 3959 SERVICEPACK_NUMBER: 3 OS_REVISION: 0 SUITE_MASK: 0 PRODUCT_TYPE: 0 OSPLATFORM_TYPE: x86 OSNAME: Windows Server 2003 OSEDITION: Windows Server 2003 OS_LOCALE: USER_LCID: 0 OSBUILD_TIMESTAMP: 2017-08-13 18:20:21 BUILDDATESTAMP_STR: 0 BUILDLAB_STR: 25019 BUILDOSVER_STR: 5.2.20170813-r75532.MSVC_19.10.25019.0 ANALYSIS_SESSION_ELAPSED_TIME: 8e ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x7b_nt!iopmountvolume+760 FAILURE_ID_HASH: {c3e15546-31cc-7831-b2fd-352aa5e47c29} Followup: MachineOwner ---------