Microsoft (R) Windows Debugger Version 10.0.22415.1002 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Opened \\.\pipe\ros_pipe Waiting to reconnect... (ntoskrnl\kd64\kdinit.c:74) ----------------------------------------------------- (ntoskrnl\kd64\kdinit.c:75) ReactOS 0.4.15-x86-dev (Build 20201205-0.4.15-dev-1413-gcbe88e2) (Commit cbe88e287f45ae0dead0d80f169a7e20e569480c) (ntoskrnl\kd64\kdinit.c:76) 1 System Processor [256 MB Memory] (ntoskrnl\kd64\kdinit.c:80) Command Line: DEBUG KDSERIAL DEBUGPORT=COM1 FIRSTCHANCE NOGUIBOOT (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 (Fri Aug 6 02:36:49.349 2021 (UTC + 2:00)), ptr64 FALSE Kernel Debugger connection established. ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows Server 2003 Kernel Version 3790 UP Checked x86 compatible Edition build lab: 20201205-0.4.15-dev-1413-gcbe88e2.MSVC_19.24.28314.0 Machine Name: Kernel base = 0x80400000 PsLoadedModuleList = 0x805972c0 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:136) 0x80000000 - 0x83000000 Boot Loaded Image (ntoskrnl\mm\mminit.c:140) 0xB0000000 - 0xB01C0000 PFN Database (ntoskrnl\mm\mminit.c:144) 0xB01C0000 - 0xB0998000 ARM3 Non Paged Pool (ntoskrnl\mm\mminit.c:148) 0xB9400000 - 0xBB400000 System View Space (ntoskrnl\mm\mminit.c:152) 0xBB400000 - 0xC0000000 Session Space (ntoskrnl\mm\mminit.c:155) 0xC0000000 - 0xC03FFFFF Page Tables (ntoskrnl\mm\mminit.c:158) 0xC0300000 - 0xC0300FFF Page Directories (ntoskrnl\mm\mminit.c:161) 0xC0400000 - 0xC07FFFFF Hyperspace (ntoskrnl\mm\mminit.c:164) 0xC1000000 - 0xE0FFFFFF System Cache (ntoskrnl\mm\mminit.c:168) 0xE1000000 - 0xED400000 ARM3 Paged Pool (ntoskrnl\mm\mminit.c:171) 0xF4C00000 - 0xFA20D000 System PTE Space (ntoskrnl\mm\mminit.c:174) 0xFA20D000 - 0xFFBE0000 Non Paged Pool Expansion PTE Space (ntoskrnl\config\cmcheck.c:25) CmCheckRegistry(0xB0940008, 2) is UNIMPLEMENTED! (hal\halx86\legacy\bussupp.c:623) 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 Bridge [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 VGA compatible controller [0300]: Unknown device [1234:1111] (rev 00) Subsystem: Unknown [0000:0000] Flags: medium devsel, latency 0 Memory at c0000000 (32-bit, prefetchable) [size=1024M] ====== PCI BUS DETECTION COMPLETE ======= PC Compatible Eisa/Isa HAL Detected WARNING: ArbInitializeArbiterInstance at sdk\lib\drivers\arbiter\arbiter.c:38 is UNIMPLEMENTED! WARNING: ArbInitializeArbiterInstance at sdk\lib\drivers\arbiter\arbiter.c:38 is UNIMPLEMENTED! WARNING: ArbInitializeArbiterInstance at sdk\lib\drivers\arbiter\arbiter.c:38 is UNIMPLEMENTED! WARNING: ArbInitializeArbiterInstance at sdk\lib\drivers\arbiter\arbiter.c:38 is UNIMPLEMENTED! WARNING: ArbInitializeArbiterInstance at sdk\lib\drivers\arbiter\arbiter.c:38 is UNIMPLEMENTED! (sdk\lib\rtl\image.c:171) Invalid base address: 00000000 (ntoskrnl\io\iomgr\driver.c:1683) '\Driver\sacdrv' initialization failed, status (0xc0000037) (ntoskrnl\io\iomgr\driver.c:66) Deleting driver object '\Driver\sacdrv' WARNING: NtNotifyChangeMultipleKeys at ntoskrnl\config\ntapi.c:1470 is UNIMPLEMENTED! Btrfs ERR : watch_registry : ZwNotifyChangeKey returned c0000002 (drivers\storage\class\ramdisk\ramdisk.c:2487) FIXME: Installing from RamDisk is UNSUPPORTED! (drivers\storage\port\scsiport\scsiport.c:984) Created device: \Device\ScsiPort0 (B093A978) (drivers\storage\port\scsiport\scsiport.c:2497) ZwOpenKey() failed with Status=0xC0000034 (hal\halx86\legacy\bussupp.c:1170) Slot assignment for 5 on bus 0 (hal\halx86\legacy\bus\pcibus.c:734) WARNING: PCI Slot Resource Assignment is FOOBAR (drivers\storage\port\scsiport\scsiport.c:984) Created device: \Device\ScsiPort0 (B0969038) (drivers\storage\port\scsiport\fdo.c:330) SCSIPORT: created lun device: B0957A08 Status: 0 (drivers\storage\port\scsiport\fdo.c:330) SCSIPORT: created lun device: B0916A08 Status: 0 (drivers\storage\port\scsiport\scsiport.c:984) Created device: \Device\ScsiPort1 (B0915038) (drivers\storage\port\scsiport\scsiport.c:2497) ZwOpenKey() failed with Status=0xC0000034 (drivers\storage\port\scsiport\scsiport.c:984) Created device: \Device\ScsiPort1 (B0915038) (drivers\storage\port\scsiport\fdo.c:330) SCSIPORT: created lun device: B0914A08 Status: 0 (drivers\storage\port\scsiport\fdo.c:330) SCSIPORT: created lun device: B0952038 Status: 0 (drivers\storage\port\scsiport\scsiport.c:984) Created device: \Device\ScsiPort2 (B08E1A78) (drivers\storage\port\scsiport\scsiport.c:2497) ZwOpenKey() failed with Status=0xC0000034 (drivers\storage\port\scsiport\scsiport.c:984) Created device: \Device\ScsiPort2 (B08E1A78) (drivers\storage\port\scsiport\scsiport.c:984) Created device: \Device\ScsiPort2 (B08E1A78) (ntoskrnl\io\iomgr\driver.c:396) IopLoadServiceModule(cdrom, 0xF9E1A908) called in ExpInTextModeSetup mode... (ntoskrnl\mm\ARM3\sysldr.c:3005) ZwOpenFile failed for '\SystemRoot\System32\drivers\cdrom.sys' with status 0xc000003a (ntoskrnl\io\iomgr\driver.c:396) IopLoadServiceModule(cdrom, 0xF9E1A908) called in ExpInTextModeSetup mode... (ntoskrnl\mm\ARM3\sysldr.c:3005) ZwOpenFile failed for '\SystemRoot\System32\drivers\cdrom.sys' with status 0xc000003a (drivers\storage\port\scsiport\scsiport.c:984) Created device: \Device\ScsiPort2 (B0950038) (ntoskrnl\io\iomgr\driver.c:1683) '\Driver\buslogic' initialization failed, status (0xc00000c0) (ntoskrnl\io\iomgr\driver.c:66) Deleting driver object '\Driver\buslogic' (ntoskrnl\io\iomgr\driver.c:396) IopLoadServiceModule(cdrom, 0xF9E1A908) called in ExpInTextModeSetup mode... (ntoskrnl\mm\ARM3\sysldr.c:3005) ZwOpenFile failed for '\SystemRoot\System32\drivers\cdrom.sys' with status 0xc000003a (sdk\lib\drivers\wdf\kmdf\src\core\fxbugcheckcallback.cpp:224) ReactOS KMDF: FxpGetImageBase not implemented WDFTrace: new WDFKEY object open failed, !STATUS! (ntoskrnl\io\pnpmgr\pnpinit.c:365) IopOpenRegistryKeyEx() failed for '{4D36E965-E325-11CE-BFC1-08002BE10318}' with status 0xc0000034 WDFTrace: new WDFKEY object open failed, !STATUS! WDFTrace: new WDFKEY object open failed, !STATUS! WDFTrace: new WDFKEY object open failed, !STATUS! WDFTrace: new WDFKEY object open failed, !STATUS! WDFTrace: new WDFKEY object open failed, !STATUS! WDFTrace: new WDFKEY object open failed, !STATUS! (drivers\storage\port\scsiport\ioctl.c:542) unknown ioctl code: 0x2D1C80 (drivers\storage\port\scsiport\ioctl.c:542) unknown ioctl code: 0x560038 (drivers\storage\port\scsiport\ioctl.c:542) unknown ioctl code: 0x4D0018 (drivers\storage\port\scsiport\ioctl.c:542) unknown ioctl code: 0x4DC010 (drivers\storage\port\scsiport\ioctl.c:542) unknown ioctl code: 0x4D0010 (drivers\storage\port\scsiport\ioctl.c:542) unknown ioctl code: 0x4D0004 (ntoskrnl\io\iomgr\driver.c:1683) '\Driver\floppy' initialization failed, status (0xc000000e) (ntoskrnl\io\iomgr\driver.c:66) Deleting driver object '\Driver\floppy' (drivers\storage\port\storport\storport.c:461) DriverEntry(B094CAB0 F9E1A9F0) (drivers\storage\port\scsiport\ioctl.c:542) unknown ioctl code: 0x4DC010 (drivers\storage\port\scsiport\ioctl.c:542) unknown ioctl code: 0x4D0010 Btrfs ERR : volume_arrival : IOCTL_DISK_GET_LENGTH_INFO returned c0000185 *** Fatal System Error: 0x0000007b (0xB0950EB8,0xC0000185,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. For analysis of this file, run !analyze -v nt!DbgBreakPointWithStatus+0x4: 80536ac8 cc int 3 kd> !analyze -v Connected to Windows Server 2003 3790 x86 compatible target at (Fri Aug 6 02:43:42.927 2021 (UTC + 2:00)), 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 ************* Symbol Loading Error Summary ************** Module name Error ntoskrnl The system cannot find the file specified You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded. You should also verify that your symbol search path (.sympath) is correct. ******************************************************************************* * * * 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: b0950eb8, Pointer to the device object or Unicode string of ARC name Arg2: c0000185, (reserved) Arg3: 00000000, (reserved) Arg4: 00000000, (reserved) Debugging Details: ------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_EPROCESS *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KTHREAD *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1265 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 34596 Key : Analysis.Init.CPU.mSec Value: 4671 Key : Analysis.Init.Elapsed.mSec Value: 472099 Key : Analysis.Memory.CommitPeak.Mb Value: 46 ADDITIONAL_DEBUG_TEXT: You can run '.symfix; .reload' to try to fix the symbol path and load symbols. WRONG_SYMBOLS_TIMESTAMP: 5fcc1809 WRONG_SYMBOLS_SIZE: 1e3000 FAULTING_MODULE: 80400000 nt BUGCHECK_CODE: 7b BUGCHECK_P1: ffffffffb0950eb8 BUGCHECK_P2: ffffffffc0000185 BUGCHECK_P3: 0 BUGCHECK_P4: 0 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. f9e1a134 80489baf 00000003 f9e1a9f4 f9e1aad8 nt!DbgBreakPointWithStatus+0x4 f9e1a4d4 80489580 0000007b b0950eb8 c0000185 nt!KeBugCheckEx+0x64f f9e1a4f4 80472ea0 0000007b b0950eb8 c0000185 nt!KeBugCheckEx+0x20 f9e1a5ac 80472398 b0950eb8 00000000 00000000 nt!IoVolumeDeviceToDosName+0xe40 f9e1a5d8 80461d4e b094f8f8 b0950eb8 f9e1a778 nt!IoVolumeDeviceToDosName+0x338 f9e1a738 804e85da b0950eb8 00000000 b09505e8 nt!IoUpdateShareAccess+0x2f2e f9e1a7dc 804e1a6b 00000000 f9e1a810 00000040 nt!ObQueryNameString+0x109a f9e1a834 804607bf f9e1aad8 00000000 00000000 nt!ObOpenObjectByName+0x15b f9e1a94c 8045e536 f9e1ab04 00000001 f9e1aad8 nt!IoUpdateShareAccess+0x199f f9e1a994 80464132 f9e1ab04 00000001 f9e1aad8 nt!IoCreateFile+0x46 f9e1a9d4 8051e83b f9e1ab04 00000001 f9e1aad8 nt!NtOpenFile+0x32 f9e1a9fc 8051c97c 80464100 f9e1aac0 00000018 nt!Kei386EoiHelper+0xa9b f9e1aa40 80403e0e f9e1ab0c 804019a5 badb0d00 nt!KiEoiHelper+0x82c f9e1aa48 804019a5 badb0d00 f9e1aac0 00000000 nt!WRITE_REGISTER_BUFFER_ULONG+0x1592 f9e1ab0c 805b6451 7665445c 5c656369 6f526443 nt!ZwOpenFile+0x11 f9e1ac78 805b26e7 80075000 74697472 206e6f69 nt!CcFastMdlReadWait+0xd609 f9e1ad80 8042ca5e 80075000 f9e1adc0 804ff194 nt!CcFastMdlReadWait+0x989f f9e1ad8c 804ff194 80075000 00063dc0 e000003b nt!HeadlessDispatch+0x18e f9e1adc0 8051bcb2 8042ca50 80075000 f9e1adf0 nt!PsWrapApcWow64Thread+0xb24 f9e1addc 804ff130 8042ca50 80075000 00000000 nt!KiDispatchInterrupt+0x482 f9e1ade0 8042ca50 80075000 00000000 0000027f nt!PsWrapApcWow64Thread+0xac0 f9e1ade4 80075000 00000000 0000027f 00000000 nt!HeadlessDispatch+0x180 f9e1ade8 00000000 0000027f 00000000 00000000 0x80075000 SYMBOL_NAME: nt_wrong_symbols!5FCC18091E3000 IMAGE_VERSION: 5.2.3790.3959 STACK_COMMAND: .thread ; .cxr ; kb EXCEPTION_CODE_STR: 5FCC1809 EXCEPTION_STR: WRONG_SYMBOLS PROCESS_NAME: ntoskrnl.wrong.symbols.exe IMAGE_NAME: ntoskrnl.wrong.symbols.exe MODULE_NAME: nt_wrong_symbols FAILURE_BUCKET_ID: WRONG_SYMBOLS_X86_20201205-0.4.15-dev-1413-gcbe88e2.MSVC_19.24.28314.0_TIMESTAMP_201205-233017_5FCC1809_nt_wrong_symbols!5FCC18091E3000 OSPLATFORM_TYPE: x86 OSNAME: Windows Server 2003 FAILURE_ID_HASH: {76c398e4-7e07-9041-7011-ce83aae2fb8b} Followup: MachineOwner --------- kd> kd f9e1a134 f9e1a4d4 f9e1a138 80489baf nt!KeBugCheckEx+0x64f f9e1a13c 00000003 f9e1a140 f9e1a9f4 f9e1a144 f9e1aad8 f9e1a148 0001003f f9e1a14c 00000000 f9e1a150 00000000 f9e1a154 00000000 f9e1a158 00000000 f9e1a15c ffff0ff0 f9e1a160 00000400 f9e1a164 00000001 f9e1a168 00000001 f9e1a16c 00000001 f9e1a170 00000001 f9e1a174 00000001 f9e1a178 00000000 f9e1a17c 00000000 f9e1a180 00000000 f9e1a184 00000000 f9e1a188 00000000 f9e1a18c 00000030 f9e1a190 00000023 f9e1a194 00000023 f9e1a198 00000000 f9e1a19c 00100094 f9e1a1a0 ffffffff f9e1a1a4 0000007f f9e1a1a8 805919cc nt!SeTokenObjectType+0x3884 f9e1a1ac 00000000 f9e1a1b0 80591990 nt!SeTokenObjectType+0x3848 f9e1a1b4 80536af6 nt!DbgBreakPointWithStatus+0x32 f9e1a1b8 00000008 f9e1a1bc 00200046 f9e1a1c0 80591988 nt!SeTokenObjectType+0x3840 f9e1a1c4 00000010 f9e1a1c8 00000000 f9e1a1cc 00000000 f9e1a1d0 00000000 f9e1a1d4 00000000 f9e1a1d8 00000030 f9e1a1dc 00000023 f9e1a1e0 00000023 f9e1a1e4 f9e1a9f4 f9e1a1e8 f9e1aad8 f9e1a1ec 00000000 f9e1a1f0 ffdff13c f9e1a1f4 ffdff120 f9e1a1f8 00000000 f9e1a1fc f9e1a4f4 f9e1a200 80489580 nt!KeBugCheckEx+0x20 f9e1a204 00000008 f9e1a208 00200286 f9e1a20c f9e1a4dc f9e1a210 00000010 f9e1a214 00000000 f9e1a218 00000000 f9e1a21c 00000000 f9e1a220 00000000 f9e1a224 00000000 f9e1a228 00000000 f9e1a22c 00000000 f9e1a230 805916e0 nt!SeTokenObjectType+0x3598 f9e1a234 8059168c nt!SeTokenObjectType+0x3544 f9e1a238 8051986f nt!KeRaiseUserException+0xbdf f9e1a23c 80000003 f9e1a240 00000000 f9e1a244 00000000 f9e1a248 80536af5 nt!DbgBreakPointWithStatus+0x31 f9e1a24c 00000003 f9e1a250 00000001 f9e1a254 80591798 nt!SeTokenObjectType+0x3650 f9e1a258 00000047 f9e1a25c 00000000 f9e1a260 00000000 f9e1a264 8059167c nt!SeTokenObjectType+0x3534 f9e1a268 80548ffc nt!wcsicmp+0x14fc f9e1a26c 8059174c nt!SeTokenObjectType+0x3604 f9e1a270 00000030 f9e1a274 00000000 f9e1a278 00000008 f9e1a27c 30000000 f9e1a280 80591738 nt!SeTokenObjectType+0x35f0 f9e1a284 80591738 nt!SeTokenObjectType+0x35f0 f9e1a288 80548556 nt!wcsicmp+0xa56 f9e1a28c 00000000 f9e1a290 805916c4 nt!SeTokenObjectType+0x357c f9e1a294 8051c0f5 nt!KiCheckForSListAddress+0x365 f9e1a298 80000003 f9e1a29c 00000000 f9e1a2a0 80536af5 nt!DbgBreakPointWithStatus+0x31 f9e1a2a4 00000003 f9e1a2a8 00000001 f9e1a2ac 80591798 nt!SeTokenObjectType+0x3650 f9e1a2b0 00000047 f9e1a2b4 00000001 f9e1a2b8 00000001 f9e1a2bc 00000001 f9e1a2c0 00000000 f9e1a2c4 00000000 f9e1a2c8 00000000 f9e1a2cc 0158d350 f9e1a2d0 8059171c nt!SeTokenObjectType+0x35d4 f9e1a2d4 804a8b10 nt!MmUnmapReservedMapping+0xd80 f9e1a2d8 8058d350 nt!KeNumberProcessors+0x30 f9e1a2dc 00000001 f9e1a2e0 00000001 f9e1a2e4 00000001 f9e1a2e8 00000001 f9e1a2ec 00000000 f9e1a2f0 00000001 f9e1a2f4 00000001 f9e1a2f8 00000000 f9e1a2fc 00000000 f9e1a300 00000000 f9e1a304 01000000 f9e1a308 805918ac nt!SeTokenObjectType+0x3764 f9e1a30c 00200246 f9e1a310 00200246 f9e1a314 00000000 f9e1a318 8058d328 nt!KeNumberProcessors+0x8 f9e1a31c ffdff000 f9e1a320 805918ac nt!SeTokenObjectType+0x3764 f9e1a324 804adf01 nt!MmFreeNonCachedMemory+0x4a31 f9e1a328 805918ac nt!SeTokenObjectType+0x3764 f9e1a32c 804adfa7 nt!MmFreeNonCachedMemory+0x4ad7 f9e1a330 80591a0c nt!SeTokenObjectType+0x38c4 f9e1a334 00000030 f9e1a338 00000000 f9e1a33c 00100094 f9e1a340 ffffffff f9e1a344 8059175c nt!SeTokenObjectType+0x3614 f9e1a348 00200246 f9e1a34c 80536af6 nt!DbgBreakPointWithStatus+0x32 f9e1a350 00000008 f9e1a354 00200246 f9e1a358 00063dc0 f9e1a35c 00000000 f9e1a360 80591778 nt!SeTokenObjectType+0x3630 f9e1a364 8052c482 nt!DbgSetDebugFilterState+0x82 f9e1a368 00000001 f9e1a36c 80591798 nt!SeTokenObjectType+0x3650 f9e1a370 00000047 f9e1a374 ffffffff f9e1a378 00000000 f9e1a37c 80591a1c nt!SeTokenObjectType+0x38d4 f9e1a380 8052c6dd nt!vDbgPrintExWithPrefix+0x1dd f9e1a384 805919f0 nt!SeTokenObjectType+0x38a8 f9e1a388 00000001 f9e1a38c 00000001 f9e1a390 00000001 f9e1a394 00100094 f9e1a398 00000000 f9e1a39c 6f746e28 f9e1a3a0 6e726b73 f9e1a3a4 6d6d5c6c f9e1a3a8 4d52415c f9e1a3ac 6d6d5c33 f9e1a3b0 74696e69 f9e1a3b4 313a632e f9e1a3b8 29323534 f9e1a3bc 4c414820 f9e1a3c0 4f2f4920 f9e1a3c4 70614d20 f9e1a3c8 676e6970 f9e1a3cc 20746120 f9e1a3d0 45464646 f9e1a3d4 30303030 f9e1a3d8 20736920 f9e1a3dc 61736e75 f9e1a3e0 000a6566 f9e1a3e4 00000031 f9e1a3e8 00000000 f9e1a3ec 80591814 nt!SeTokenObjectType+0x36cc f9e1a3f0 805280dc nt!except_handler3+0x392e f9e1a3f4 80591ab4 nt!SeTokenObjectType+0x396c f9e1a3f8 802011a0 f9e1a3fc 00000000 f9e1a400 80591835 nt!SeTokenObjectType+0x36ed f9e1a404 ffffffff f9e1a408 00000000 f9e1a40c 804ff884 nt!PsEstablishWin32Callouts+0xa4 f9e1a410 00000000 f9e1a414 00000000 f9e1a418 00000000 f9e1a41c b0950eb8 f9e1a420 00000000 f9e1a424 00050009 f9e1a428 b08ced30 f9e1a42c c0000185 f9e1a430 00000000 f9e1a434 804920ca nt!PsGetCurrentThread+0xa f9e1a438 f9e1a440 f9e1a43c 00200293 f9e1a440 00200293 f9e1a444 00000000 f9e1a448 00000001 f9e1a44c ffdff000 f9e1a450 00000001 f9e1a454 f9e1a400 f9e1a458 f9e1a464 f9e1a45c 80238a53 hal!KeReleaseInStackQueuedSpinLock+0x23 f9e1a460 f9e1a47c f9e1a464 f9e1a46c f9e1a468 80433cd4 nt!ExReleaseResourceForThreadLite+0x584 f9e1a46c f9e1a4f4 f9e1a470 80433cad nt!ExReleaseResourceForThreadLite+0x55d f9e1a474 805a5ac0 nt!KdEnteredDebugger+0x520 f9e1a478 f9e1a47c f9e1a47c 00000000 f9e1a480 805a5af4 nt!KdEnteredDebugger+0x554 f9e1a484 00200293 f9e1a488 00200293 f9e1a48c 00000000 f9e1a490 00000001 f9e1a494 ffdff000 f9e1a498 f9e1a4b4 f9e1a49c f9e1a400 f9e1a4a0 f9e1a4cc f9e1a4a4 00000000 f9e1a4a8 00000000 f9e1a4ac 00000001 f9e1a4b0 00000071 f9e1a4b4 ffdff120 f9e1a4b8 00000000 f9e1a4bc 00000000 f9e1a4c0 0000007b f9e1a4c4 00dff000 f9e1a4c8 00000000 f9e1a4cc 0000005d f9e1a4d0 8000466d f9e1a4d4 f9e1a4f4 f9e1a4d8 80489580 nt!KeBugCheckEx+0x20 f9e1a4dc 0000007b f9e1a4e0 b0950eb8 f9e1a4e4 c0000185 f9e1a4e8 00000000 f9e1a4ec 00000000 f9e1a4f0 00000000 f9e1a4f4 f9e1a5ac f9e1a4f8 80472ea0 nt!IoVolumeDeviceToDosName+0xe40 f9e1a4fc 0000007b f9e1a500 b0950eb8 f9e1a504 c0000185 f9e1a508 00000000 f9e1a50c 00000000 f9e1a510 00040000 f9e1a514 00000001 f9e1a518 f9e1a518 f9e1a51c f9e1a518 f9e1a520 c0000185 f9e1a524 00000000 f9e1a528 8049507d nt!KeUpdateRunTime+0x35d f9e1a52c f9e1a55c f9e1a530 00000001