Dietmar
-
Posts
91 -
Joined
-
Last visited
-
Days Won
9
Content Type
Profiles
Forums
Events
Posts posted by Dietmar
-
-
Yes to all.
The other cards have also other drivers.
So, this one is with best chance
Dietmar
-
This card Lindy 2S 16C950 is also connected via PCI bridge, but shown as normal COM3 and COM4 port.
I think, that this bridge is needed, because card sits in a PCIe slot.
The COM 2 port is the onboard COM connector. It is connected via PCI-Standard Isa bridge
This is the only card, where in Flags: not "Busmaster" is listed, only fast devsel and IRQ.
As far as I remember, this card also does not work with Windbg,
only some success with freeldr (Fat32) and ntldr_debug
Dietmar
-
First here is output from all of my 4 different cards
Dietmar
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.C:\Dokumente und Einstellungen\Administrator>cd C:\pciutils-3.5.5-win32
C:\pciutils-3.5.5-win32>lspci
00:00.0 Host bridge: Intel Corporation Device 4660 (rev 02)
00:01.0 PCI bridge: Intel Corporation Device 460d (rev 02)
00:01.1 PCI bridge: Intel Corporation Device 462d (rev 02)
00:0a.0 Signal processing controller: Intel Corporation Device 467d (rev 01)
00:14.0 USB controller: Intel Corporation Device 7ae0 (rev 11)
00:14.2 RAM memory: Intel Corporation Device 7aa7 (rev 11)
00:15.0 Serial bus controller [0c80]: Intel Corporation Device 7acc (rev 11)
00:15.1 Serial bus controller [0c80]: Intel Corporation Device 7acd (rev 11)
00:16.0 Communication controller: Intel Corporation Device 7ae8 (rev 11)
00:17.0 SATA controller: Intel Corporation Device 7ae2 (rev 11)
00:1c.0 PCI bridge: Intel Corporation Device 7abc (rev 11)
00:1c.7 PCI bridge: Intel Corporation Device 7abf (rev 11)
00:1d.0 PCI bridge: Intel Corporation Device 7ab4 (rev 11)
00:1f.0 ISA bridge: Intel Corporation Device 7a84 (rev 11)
00:1f.3 Audio device: Intel Corporation Device 7ad0 (rev 11)
00:1f.4 SMBus: Intel Corporation Device 7aa3 (rev 11)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 7aa4 (rev 11)
01:00.0 VGA compatible controller: NVIDIA Corporation GK208 [GeForce GT 730] (re
v a1)
01:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1)02:00.0 Serial controller: MosChip Semiconductor Technology Ltd. MCS9922 PCIe Mu
lti-I/O Controller
02:00.1 Serial controller: MosChip Semiconductor Technology Ltd. MCS9922 PCIe Mu
lti-I/O Controller
03:00.0 SATA controller: ASMedia Technology Inc. Device 1064 (rev 02)
04:00.0 Ethernet controller: Intel Corporation Device 15f3 (rev 03)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 P
CI Express Gigabit Ethernet Controller (rev 06)C:\pciutils-3.5.5-win32>lspci -s 02:00.0 -v
02:00.0 Serial controller: MosChip Semiconductor Technology Ltd. MCS9922 PCIe Mu
lti-I/O Controller (prog-if 02 [16550])
Subsystem: Device a000:1000
Flags: bus master, fast devsel, latency 0, IRQ 10
I/O ports at 4010
Memory at 3b603000 (32-bit, non-prefetchable)
Memory at 3b602000 (32-bit, non-prefetchable)
Capabilities: [50] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [78] Power Management version 3
Capabilities: [80] Express Legacy Endpoint, MSI 00
C:\pciutils-3.5.5-win32>lspci -s 02:00.1 -v
02:00.1 Serial controller: MosChip Semiconductor Technology Ltd. MCS9922 PCIe Mu
lti-I/O Controller (prog-if 02 [16550])
Subsystem: Device a000:1000
Flags: bus master, fast devsel, latency 0, IRQ 5
I/O ports at 4000
Memory at 3b601000 (32-bit, non-prefetchable)
Memory at 3b600000 (32-bit, non-prefetchable)
Capabilities: [50] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [78] Power Management version 3
Capabilities: [80] Express Legacy Endpoint, MSI 00
C:\pciutils-3.5.5-win32>lspci -s 00:15.0 -v
00:15.0 Serial bus controller [0c80]: Intel Corporation Device 7acc (rev 11)
Subsystem: Biostar Microtech Int'l Corp Device 3118
Flags: fast devsel, IRQ 255
Memory at <unassigned> (64-bit, non-prefetchable) [disabled]
Capabilities: [80] Power Management version 3
Capabilities: [90] Vendor Specific Information: Len=14 <?>
C:\pciutils-3.5.5-win32>lspci -s 00:15.1 -v
00:15.1 Serial bus controller [0c80]: Intel Corporation Device 7acd (rev 11)
Subsystem: Biostar Microtech Int'l Corp Device 3118
Flags: fast devsel, IRQ 255
Memory at <unassigned> (64-bit, non-prefetchable) [disabled]
Capabilities: [80] Power Management version 3
Capabilities: [90] Vendor Specific Information: Len=14 <?>
C:\pciutils-3.5.5-win32>lspci -s 00:1f.5 -v
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 7aa4 (rev 11)
Subsystem: Biostar Microtech Int'l Corp Device 3118
Flags: fast devsel
Memory at fe010000 (32-bit, non-prefetchable) [disabled]
C:\pciutils-3.5.5-win32>lspci
00:00.0 Host bridge: Intel Corporation Device 4660 (rev 02)
00:01.0 PCI bridge: Intel Corporation Device 460d (rev 02)
00:01.1 PCI bridge: Intel Corporation Device 462d (rev 02)
00:0a.0 Signal processing controller: Intel Corporation Device 467d (rev 01)
00:14.0 USB controller: Intel Corporation Device 7ae0 (rev 11)
00:14.2 RAM memory: Intel Corporation Device 7aa7 (rev 11)
00:15.0 Serial bus controller [0c80]: Intel Corporation Device 7acc (rev 11)
00:15.1 Serial bus controller [0c80]: Intel Corporation Device 7acd (rev 11)
00:16.0 Communication controller: Intel Corporation Device 7ae8 (rev 11)
00:17.0 SATA controller: Intel Corporation Device 7ae2 (rev 11)
00:1c.0 PCI bridge: Intel Corporation Device 7abc (rev 11)
00:1c.7 PCI bridge: Intel Corporation Device 7abf (rev 11)
00:1d.0 PCI bridge: Intel Corporation Device 7ab4 (rev 11)
00:1f.0 ISA bridge: Intel Corporation Device 7a84 (rev 11)
00:1f.3 Audio device: Intel Corporation Device 7ad0 (rev 11)
00:1f.4 SMBus: Intel Corporation Device 7aa3 (rev 11)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 7aa4 (rev 11)
01:00.0 VGA compatible controller: NVIDIA Corporation GK208 [GeForce GT 730] (re
v a1)
01:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1)02:00.0 Serial controller: Oxford Semiconductor Ltd Device c138
03:00.0 SATA controller: ASMedia Technology Inc. Device 1064 (rev 02)
04:00.0 Ethernet controller: Intel Corporation Device 15f3 (rev 03)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 P
CI Express Gigabit Ethernet Controller (rev 06)C:\pciutils-3.5.5-win32>lspci -s 02:00.0 -v
02:00.0 Serial controller: Oxford Semiconductor Ltd Device c138 (prog-if 02 [165
50])
Subsystem: Oxford Semiconductor Ltd Device c138
Flags: fast devsel, IRQ 255
Capabilities: [40] Power Management version 3
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [b0] MSI-X: Enable- Count=16 Masked-
C:\pciutils-3.5.5-win32>lspci
00:00.0 Host bridge: Intel Corporation Device 4660 (rev 02)
00:01.0 PCI bridge: Intel Corporation Device 460d (rev 02)
00:01.1 PCI bridge: Intel Corporation Device 462d (rev 02)
00:0a.0 Signal processing controller: Intel Corporation Device 467d (rev 01)
00:14.0 USB controller: Intel Corporation Device 7ae0 (rev 11)
00:14.2 RAM memory: Intel Corporation Device 7aa7 (rev 11)
00:15.0 Serial bus controller [0c80]: Intel Corporation Device 7acc (rev 11)
00:15.1 Serial bus controller [0c80]: Intel Corporation Device 7acd (rev 11)
00:16.0 Communication controller: Intel Corporation Device 7ae8 (rev 11)
00:17.0 SATA controller: Intel Corporation Device 7ae2 (rev 11)
00:1c.0 PCI bridge: Intel Corporation Device 7abc (rev 11)
00:1c.7 PCI bridge: Intel Corporation Device 7abf (rev 11)
00:1d.0 PCI bridge: Intel Corporation Device 7ab4 (rev 11)
00:1f.0 ISA bridge: Intel Corporation Device 7a84 (rev 11)
00:1f.3 Audio device: Intel Corporation Device 7ad0 (rev 11)
00:1f.4 SMBus: Intel Corporation Device 7aa3 (rev 11)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 7aa4 (rev 11)
01:00.0 VGA compatible controller: NVIDIA Corporation GK208 [GeForce GT 730] (re
v a1)
01:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1)02:00.0 Serial controller: Oxford Semiconductor Ltd Device c140
02:00.1 Serial controller: Oxford Semiconductor Ltd Device c141
03:00.0 SATA controller: ASMedia Technology Inc. Device 1064 (rev 02)
04:00.0 Ethernet controller: Intel Corporation Device 15f3 (rev 03)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 P
CI Express Gigabit Ethernet Controller (rev 06)C:\pciutils-3.5.5-win32>lspci -s 02:00.0 -v
02:00.0 Serial controller: Oxford Semiconductor Ltd Device c140 (prog-if 02 [165
50])
Subsystem: Oxford Semiconductor Ltd Device c140
Flags: fast devsel, IRQ 255
I/O ports at <unassigned> [disabled]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Legacy Endpoint, MSI 00
C:\pciutils-3.5.5-win32>lspci -s 02:00.1 -v
02:00.1 Serial controller: Oxford Semiconductor Ltd Device c141 (prog-if 02 [165
50])
Subsystem: Oxford Semiconductor Ltd Device c141
Flags: fast devsel, IRQ 255
I/O ports at <unassigned> [disabled]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Legacy Endpoint, MSI 00
C:\pciutils-3.5.5-win32>lspci
00:00.0 Host bridge: Intel Corporation Device 4660 (rev 02)
00:01.0 PCI bridge: Intel Corporation Device 460d (rev 02)
00:01.1 PCI bridge: Intel Corporation Device 462d (rev 02)
00:0a.0 Signal processing controller: Intel Corporation Device 467d (rev 01)
00:14.0 USB controller: Intel Corporation Device 7ae0 (rev 11)
00:14.2 RAM memory: Intel Corporation Device 7aa7 (rev 11)
00:15.0 Serial bus controller [0c80]: Intel Corporation Device 7acc (rev 11)
00:15.1 Serial bus controller [0c80]: Intel Corporation Device 7acd (rev 11)
00:16.0 Communication controller: Intel Corporation Device 7ae8 (rev 11)
00:17.0 SATA controller: Intel Corporation Device 7ae2 (rev 11)
00:1c.0 PCI bridge: Intel Corporation Device 7abc (rev 11)
00:1c.7 PCI bridge: Intel Corporation Device 7abf (rev 11)
00:1d.0 PCI bridge: Intel Corporation Device 7ab4 (rev 11)
00:1f.0 ISA bridge: Intel Corporation Device 7a84 (rev 11)
00:1f.3 Audio device: Intel Corporation Device 7ad0 (rev 11)
00:1f.4 SMBus: Intel Corporation Device 7aa3 (rev 11)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 7aa4 (rev 11)
01:00.0 VGA compatible controller: NVIDIA Corporation GK208 [GeForce GT 730] (re
v a1)
01:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1)02:00.0 Serial controller: MosChip Semiconductor Technology Ltd. PCIe 9912 Multi
-I/O Controller
02:00.1 Serial controller: MosChip Semiconductor Technology Ltd. Device 9900
03:00.0 SATA controller: ASMedia Technology Inc. Device 1064 (rev 02)
04:00.0 Ethernet controller: Intel Corporation Device 15f3 (rev 03)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 P
CI Express Gigabit Ethernet Controller (rev 06)C:\pciutils-3.5.5-win32>lspci -s 02:00.0 -v
02:00.0 Serial controller: MosChip Semiconductor Technology Ltd. PCIe 9912 Multi
-I/O Controller (prog-if 02 [16550])
Subsystem: Device a000:1000
Flags: fast devsel
I/O ports at <unassigned> [disabled]
Capabilities: [50] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [78] Power Management version 3
Capabilities: [80] Express Legacy Endpoint, MSI 00
C:\pciutils-3.5.5-win32> -
Here is the pic from the PEX2S553 PCIe slotcard,
just in Slot from the Biostar z690A board with 12900k cpu
Dietmar
-
-
Look at the date, when kdnet.dll was changed.
I did it on Dienstag, 8. Oktober 2019, 12:15:39
Dietmar
PS: The kdnet.dll in this post is from 2014, so it is original file from win8.1 .
-
Yes, until now it is only for 32 bit, XP SP3 and Win2003.
https://github.com/MovAX0xDEAD/KDNET
But maybe, that @Mov AX, 0xDEAD already has make the files for Windbg for 64 bit
Dietmar
-
-
Make a try with freeldr from Reactos.
You also can use Windbg via Lan from @Mov AX, 0xDEAD
it works in most cases and is ultrafast
Dietmar
Bootfiles
-
With the storport driver from Kai Schtrom I succeed to see the harddisks from nvme bootdevice. But when I make a one by one copy from the nvme boot device to the Sata disk,
compi tells at boot from the Sata disk:
"Missing MBR-helper."
This message I have never seen before. And it is so strange, because on this board
are 2 different Sata ports: One from Intel and one from Asmedia,
both give me this crazy message
Dietmar
EDIT: I solved this problem "Missing MBR-helper."
I forget, that I use freeldr via grub4dos on the Plextor nvme device. And the correction was easy: Just via RMPrepUSB I connect the harddisk via USB box and type there "install grub4dos". Now I can boot on the Biostar z690A board with the storport driver from Kai on any Sata connector.
EDIT: Crazy day, but now I have everything to run under XP.
All is on the Biostar z690A itself , only no network under XP.
For this I installed a small TP link card.
It is stable. Another advantage of this board is: You have 2 Bios chips, between you can switch. During SPI I was not able to read out the whole Bios chip, I think because of some crazy protection, as long as the Bios chip Winbond 25Q257JVEQ is soldered on the board.
It gives during read out via EEpromer Revelprog IS only 00000 everywhere. So I updated Bios chip 1 to newest Bios and the old Bios stays on Bios chip 2. The old Bios is more stable than the new one.
-
@Andalu
I use the acpi.sys from August 2021, with my last modd.
This is the standard acpi.sys now for Ramsey's XP SP3.
The USB8 files are here. They are different from yours
Dietmar
-
Full acpi XP SP3 on Biostar z690A board with 12900k cpu.
Still a lot of problems but it can be done^^
Dietmar
EDIT: Only install of XP SP3 to nvme and run from nvme works nice until now.
No USB, no Sata but works Serial Mouse(!), PS/2 keyboard, sound, 3D graphic, Internet via TPLink card, Moorhuhn;))..
Geekbench2 is 28446 for the 12900k
compared to 19000 for the 8700k, means 50% faster
under XP SP3, running on nvme, here Plextor with freeldr from Reactos.
EDIT2: ALL USB2, 3, 3.1, 3.2 work with the original win8 USB driver, transported from @Mov AX, 0xDEAD
from 5 May 2020, niccce:))).
This USB driver is without any Extender.
-
#6644 Gelip ⇗ @diderius6
I just tested debugging with WinXP SP2 32-bit on other laptop IdeaPad S10e and working
I edited the second location of F8 03 in the kdcom.dll file offset C50. kdcom.dll EN is exactly same on WinXP SP2 and SP3 regardless of the language version of the system. The card in this laptop has a different I/O address than in the X220, so you need to put the same in the kdcom.dll file.
It is enough to change the I/O address COM1 3F8 in the kdcom.dll 64-bit 5.2.3790.1830 file in offset 1024 by changing F8 03 to the address of our card (I have 00 40)
Dietmar
I just change at 3 places in your nice NTLDR_dbg
3F8h ---> D010h
And Waaaooh,
my Startech Serial PCI-e card works with Windbg,
COM in Bios disabled, oh so much fun )
Dietmar
EDIT: This at 3 places modded ntldr_dbg build from XP SP1 Sources works also on my Startech Serial PCI-e card
for large NTFS harddisks with 2048 Sectors preceding partition 1 .
-
May be, that the value for the mode APIC or PIC is not given to hal.dll,
because of the hack against Acpi Bsod A5, (0x00000003,xxx,yyy,zzz)
makes always true
_ACPIBuildCompleteMustSucceed
Because as @Mov AX, 0xDEAD mentioned,
not all code works then correct (because the Bsod A5, 0x3 shows exact this)
Dietmar
-
Yepp, first I cancel BSOD A5 (0x00000003,xxx,yyy,zzz)
and then I get the same output via Windbg as before,
now with ntoskrnl checked and hal.dll checked
Dietmar
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.Opened \\.\com1
Waiting to reconnect...
Connected to Windows XP 2600 x86 compatible target at (Sun Jan 23 17:16:44.203 2022 (UTC + 1:00)), ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: C:\symbols;C:\symbolss;C:\symbolsss
Executable search path is: C:\Symbols
Windows XP Kernel Version 2600 MP (1 procs) Checked x86 compatible
Built by: 2600.xpsp.080413-2133
Machine Name:
Kernel base = 0x80a02000 PsLoadedModuleList = 0x80b019e8
System Uptime: not available
WARNING: Inaccessible path: 'C:\symbolsssE:\binaries.x86fre\Symbols'
MM: Loader/HAL memory block indicates large pages cannot be used for 80100000->8012EFFF
MTRR feature disabled.
KiInitializeMTRR: OS support for MTRRs disabled
KiInitializeMTRR: OS support for MTRRs disabled
KiInitializeMTRR: OS support for MTRRs disabled
KiInitializeMTRR: OS support for MTRRs disabled
KiInitializeMTRR: OS support for MTRRs disabled
KiInitializeMTRR: OS support for MTRRs disabled
KiInitializeMTRR: OS support for MTRRs disabled
KiInitializeMTRR: OS support for MTRRs disabled
KiInitializeMTRR: OS support for MTRRs disabled
KiInitializeMTRR: OS support for MTRRs disabled
KiInitializeMTRR: OS support for MTRRs disabled
KiInitializeMTRR: OS support for MTRRs disabled
PS: Unhandled Kernel Mode Exception Pointers = 0xBACC2BF4
Code c0000005 Addr 801227C9 Info0 00000001 Info1 00000000 Info2 00000000 Info3 80ADEDD8*** Fatal System Error: 0x0000007e
(0xC0000005,0x801227C9,0xBACC30A8,0xBACC2DA4)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 XP 2600 x86 compatible target at (Sun Jan 23 17:16:51.750 2022 (UTC + 1:00)), ptr64 FALSE
Loading Kernel Symbols
.......................
Loading User Symbols*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************Use !analyze -v to get detailed debugging information.
BugCheck 7E, {c0000005, 801227c9, bacc30a8, bacc2da4}
*** No owner thread found for resource 80afd640
*** No owner thread found for resource 80afd640
*** No owner thread found for resource 80afd640
*** No owner thread found for resource 80afd640
Probably caused by : ACPI.sys ( ACPI!NotifyHalWithMachineStatesAndRetrieveInterruptModel+35b )Followup: MachineOwner
---------nt!RtlpBreakWithStatusInstruction:
80ac37ec cc int 3
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 801227c9, The address that the exception occurred at
Arg3: bacc30a8, Exception Record Address
Arg4: bacc2da4, Context Record AddressDebugging Details:
------------------*** No owner thread found for resource 80afd640
*** No owner thread found for resource 80afd640
*** No owner thread found for resource 80afd640
*** No owner thread found for resource 80afd640EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung "0x%08lx" verweist auf Speicher bei "0x%08lx". Die Daten wurden wegen eines E/A-Fehlers in "0x%081x" nicht in den Arbeitsspeicher bertragen.
FAULTING_IP:
hal!HaliAcpiMachineStateInit+51 [e:\xpsp1\nt\base\hals\halacpi\xxacpi.c @ 740]
801227c9 c70001000000 mov dword ptr [eax],1EXCEPTION_RECORD: bacc30a8 -- (.exr 0xffffffffbacc30a8)
ExceptionAddress: 801227c9 (hal!HaliAcpiMachineStateInit+0x00000051)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000000
Attempt to write to address 00000000CONTEXT: bacc2da4 -- (.cxr 0xffffffffbacc2da4)
eax=00000000 ebx=00000000 ecx=00b60002 edx=00b50001 esi=bacc31e8 edi=80aeb98a
eip=801227c9 esp=bacc3170 ebp=bacc3188 iopl=0 nv up ei ng nz ac pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297
hal!HaliAcpiMachineStateInit+0x51:
801227c9 c70001000000 mov dword ptr [eax],1 ds:0023:00000000=????????
Resetting default scopePROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung "0x%08lx" verweist auf Speicher bei "0x%08lx". Die Daten wurden wegen eines E/A-Fehlers in "0x%081x" nicht in den Arbeitsspeicher bertragen.
EXCEPTION_PARAMETER1: 00000001
EXCEPTION_PARAMETER2: 00000000
WRITE_ADDRESS: 00000000
FOLLOWUP_IP:
ACPI!NotifyHalWithMachineStatesAndRetrieveInterruptModel+35b
ba78444d 53 push ebxBUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_DEREFERENCE
LOCK_ADDRESS: 80afd6c0 -- (!locks 80afd6c0)
Resource @ nt!IopDeviceTreeLock (0x80afd6c0) Shared 1 owning threads
Threads: 8a6502c0-01<*>
1 total locks, 1 locks currently heldPNP_TRIAGE:
Lock address : 0x80afd6c0
Thread Count : 1
Thread address: 0x8a6502c0
Thread wait : 0xb4LAST_CONTROL_TRANSFER: from 80a30d7b to 80ac37ec
STACK_TEXT:
bacc3188 ba78444d 8a582fa0 bacc31e8 00000000 hal!HaliAcpiMachineStateInit+0x51 [e:\xpsp1\nt\base\hals\halacpi\xxacpi.c @ 740]
bacc3218 ba788b6f bacc3230 801035b0 ba782a60 ACPI!NotifyHalWithMachineStatesAndRetrieveInterruptModel+0x35b
bacc3234 ba745458 8a619f18 8a619d88 00000000 ACPI!ACPIInitialize+0x189
bacc3264 ba78d79a 8a619f18 8a61a2e0 ba78d68e ACPI!ACPIInitStartACPI+0x6a
bacc3290 ba73f9ed 8a619f18 8a61a200 8a619f18 ACPI!ACPIRootIrpStartDevice+0x10c
bacc32c0 80a21c8d 8a619f18 8a619d88 8a619f18 ACPI!ACPIDispatchIrp+0xfd
bacc32d8 80b5e526 bacc3348 8a61b1a0 8a61b038 nt!IopfCallDriver+0x51
bacc3304 80b5e66e 8a619f18 bacc3324 00000000 nt!IopSynchronousCall+0xf0
bacc334c 80a2c123 8a61b038 00000001 00000000 nt!IopStartDevice+0x82
bacc3368 80b5d2e8 8a61b038 00000000 00000000 nt!PipProcessStartPhase1+0x9f
bacc35c4 80a2cff0 8a61fc80 00000000 00000000 nt!PipProcessDevNodeTree+0x238
bacc3608 80a2d2fb 00000000 00000000 8008fa78 nt!PipDeviceActionWorker+0xc4
bacc3620 80d37f53 00000000 00000006 00000000 nt!PipRequestDeviceAction+0x13b
bacc3684 80d341f1 80084000 bacc36a0 00034000 nt!IopInitializeBootDrivers+0x39b
bacc3830 80d31940 80084000 00000000 8a6502c0 nt!IoInitSystem+0x82d
bacc3dac 80bd81ac 80084000 00000000 00000000 nt!Phase1Initialization+0xb12
bacc3ddc 80ae4212 80d30e2e 80084000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
SYMBOL_STACK_INDEX: 1SYMBOL_NAME: ACPI!NotifyHalWithMachineStatesAndRetrieveInterruptModel+35b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ACPI
IMAGE_NAME: ACPI.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 42df0d89
STACK_COMMAND: .cxr 0xffffffffbacc2da4 ; kb
FAILURE_BUCKET_ID: 0x7E_ACPI!NotifyHalWithMachineStatesAndRetrieveInterruptModel+35b
BUCKET_ID: 0x7E_ACPI!NotifyHalWithMachineStatesAndRetrieveInterruptModel+35b
Followup: MachineOwner
---------0: kd> lm
start end module name
80100000 8012f000 hal (private pdb symbols) c:\symbolsss\halmacpi.pdb
80a02000 80da3000 nt (pdb symbols) c:\symbols\ntkrpamp.pdb\5B9E8A586D3D49D98927B5D5117577231\ntkrpamp.pdb
ba2ea000 ba303b80 Mup (deferred)
ba304000 ba330980 NDIS (deferred)
ba331000 ba3bd600 Ntfs (deferred)
ba3be000 ba3d4880 KSecDD (deferred)
ba3d5000 ba3e6f00 sr (deferred)
ba3e7000 ba406b00 fltMgr (deferred)
ba407000 ba6bc000 iaStor (deferred)
ba6bc000 ba6e1a00 dmio (deferred)
ba6e2000 ba700d80 ftdisk (deferred)
ba701000 ba711a80 pci (deferred)
ba712000 ba735d80 ntoskrn8 (deferred)
ba736000 ba7a7000 ACPI (pdb symbols) c:\symbolsss\acpi.pdb
ba8a8000 ba8b1300 isapnp (deferred)
ba8b8000 ba8c2580 MountMgr (deferred)
ba8c8000 ba8d5200 VolSnap (deferred)
ba8d8000 ba8e0e00 disk (deferred)
ba8e8000 ba8f4180 CLASSPNP (deferred)
bab28000 bab2cd00 PartMgr (deferred)
bacb8000 bacbb000 BOOTVID (deferred)
bada8000 bada9b80 kdcom (deferred)
badaa000 badab100 WMILIB (deferred)
badac000 badad700 dmload (deferred) -
Or we can fake
HaliAcpiMachineStateInit
that it always gives out value 1,
because in Vista may be no PIC mode at all
Dietmar
-
-
And this error belongs to hal.dll
; __stdcall HaliAcpiMachineStateInit(x, x, x)
_HaliAcpiMachineStateInit@12 proc nearInputBuffer= dword ptr -10h
var_C= byte ptr -0Ch
var_8= dword ptr -8
var_4= dword ptr -4
arg_4= dword ptr 0Ch
arg_8= dword ptr 10hmov edi, edi
push ebp
mov ebp, esp
sub esp, 10h
mov eax, [ebp+arg_8]
push ebx
push esi
mov esi, [ebp+arg_4]
mov _HalpWakeupState, 1
mov byte_80022621, 0
mov dword ptr [eax], 1
cmp byte ptr [esi], 0
push edi
mov edi, ds:__imp__ZwPowerInformation@20 ; ZwPowerInformation(x,x,x,x,x)
mov ebx, offset _HaliAcpiSleep@20 ; HaliAcpiSleep(x,x,x,x,x)
jz short loc_800293C6 -
EAX is 00000000 at this place
Dietmar
-
I found the exact place of this Bsod
806fe35c cc int 3
806fe35d cc int 3
hal!HaliAcpiMachineStateInit:
806fe35e 8bff mov edi,edi
806fe360 55 push ebp
806fe361 8bec mov ebp,esp
806fe363 83ec10 sub esp,10h
806fe366 8b4510 mov eax,dword ptr [ebp+10h]
806fe369 53 push ebx
806fe36a 56 push esi
806fe36b 8b750c mov esi,dword ptr [ebp+0Ch]
806fe36e c60520766f8001 mov byte ptr [hal!HalpWakeupState (806f7620)],1
806fe375 c60521766f8000 mov byte ptr [hal!HalpWakeupState+0x1 (806f7621)],0
806fe37c c70001000000 mov dword ptr [eax],1 ds:0023:00000000=????????
806fe382 803e00 cmp byte ptr [esi],0
806fe385 57 push edi
806fe386 8b3dd4556e80 mov edi,dword ptr [hal!_imp__ZwPowerInformation (806e55d4)]
806fe38c bbd8886f80 mov ebx,offset hal!HaliAcpiSleep (806f88d8)
806fe391 7433 je hal!HaliAcpiMachineStateInit+0x68 (806fe3c6)
806fe393 33c9 xor ecx,ecx
806fe395 8a4e02 mov cl,byte ptr [esi+2]
806fe398 33c0 xor eax,eax
806fe39a 33d2 xor edx,edx
806fe39c 8a5601 mov dl,byte ptr [esi+1]
806fe39f 50 push eax
806fe3a0 50 push eax -
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.Opened \\.\com1
Waiting to reconnect...
Connected to Windows XP 2600 x86 compatible target at (Sun Jan 23 15:15:56.921 2022 (UTC + 1:00)), ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: C:\symbols;C:\symbolss;C:\symbolsss
Executable search path is: C:\Symbols
Windows XP Kernel Version 2600 (Service Pack 3) MP (12 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Jan 23 15:13:33.125 2022 (UTC + 1:00)
System Uptime: 0 days 0:00:02.109
WARNING: Inaccessible path: 'C:\symbolsssE:\binaries.x86fre\Symbols'
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 XP 2600 x86 compatible target at (Sun Jan 23 15:15:58.750 2022 (UTC + 1:00)), ptr64 FALSE
Loading Kernel Symbols
........................
Loading User Symbols*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************Use !analyze -v to get detailed debugging information.
BugCheck 7E, {c0000005, 806fe37c, bacc70c4, bacc6dc0}
*** No owner thread found for resource 8055b4e0
*** No owner thread found for resource 8055b4e0
*** No owner thread found for resource 8055b4e0
*** No owner thread found for resource 8055b4e0
Probably caused by : ACPI.sys ( ACPI!NotifyHalWithMachineStatesAndRetrieveInterruptModel+35b )Followup: MachineOwner
---------nt!RtlpBreakWithStatusInstruction:
8052b5dc cc int 3
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 806fe37c, The address that the exception occurred at
Arg3: bacc70c4, Exception Record Address
Arg4: bacc6dc0, Context Record AddressDebugging Details:
------------------*** No owner thread found for resource 8055b4e0
*** No owner thread found for resource 8055b4e0
*** No owner thread found for resource 8055b4e0
*** No owner thread found for resource 8055b4e0EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung "0x%08lx" verweist auf Speicher bei "0x%08lx". Die Daten wurden wegen eines E/A-Fehlers in "0x%081x" nicht in den Arbeitsspeicher bertragen.
FAULTING_IP:
hal!HaliAcpiMachineStateInit+1e
806fe37c c70001000000 mov dword ptr [eax],1EXCEPTION_RECORD: bacc70c4 -- (.exr 0xffffffffbacc70c4)
ExceptionAddress: 806fe37c (hal!HaliAcpiMachineStateInit+0x0000001e)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000000
Attempt to write to address 00000000CONTEXT: bacc6dc0 -- (.cxr 0xffffffffbacc6dc0)
eax=00000000 ebx=00000000 ecx=00740002 edx=00730001 esi=bacc7204 edi=8054b2e0
eip=806fe37c esp=bacc718c ebp=bacc71a4 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
hal!HaliAcpiMachineStateInit+0x1e:
806fe37c c70001000000 mov dword ptr [eax],1 ds:0023:00000000=????????
Resetting default scopePROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung "0x%08lx" verweist auf Speicher bei "0x%08lx". Die Daten wurden wegen eines E/A-Fehlers in "0x%081x" nicht in den Arbeitsspeicher bertragen.
EXCEPTION_PARAMETER1: 00000001
EXCEPTION_PARAMETER2: 00000000
WRITE_ADDRESS: 00000000
FOLLOWUP_IP:
ACPI!NotifyHalWithMachineStatesAndRetrieveInterruptModel+35b
ba78444d 53 push ebxBUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_DEREFERENCE
LOCK_ADDRESS: 8055b560 -- (!locks 8055b560)
Resource @ nt!IopDeviceTreeLock (0x8055b560) Shared 1 owning threads
Threads: 89faf680-01<*>
1 total locks, 1 locks currently heldPNP_TRIAGE:
Lock address : 0x8055b560
Thread Count : 1
Thread address: 0x89faf680
Thread wait : 0x85LAST_CONTROL_TRANSFER: from 804f8df9 to 8052b5dc
STACK_TEXT:
bacc71a4 ba78444d 89f12718 bacc7204 00000000 hal!HaliAcpiMachineStateInit+0x1e
bacc7234 ba788b6f bacc724c 806e7900 ba782a60 ACPI!NotifyHalWithMachineStatesAndRetrieveInterruptModel+0x35b
bacc7250 ba745458 89fca918 89fca788 00000000 ACPI!ACPIInitialize+0x189
bacc7280 ba78d79a 89fca918 89fcc150 ba78d68e ACPI!ACPIInitStartACPI+0x6a
bacc72ac ba73f9ed 89fca918 89fcc100 89fcc208 ACPI!ACPIRootIrpStartDevice+0x10c
bacc72dc 804ef18f 89fca918 89fca788 bacc7358 ACPI!ACPIDispatchIrp+0xfd
bacc72ec 80592b63 bacc7358 89fcccc0 00000000 nt!IopfCallDriver+0x31
bacc7318 80592be1 89fca918 bacc7334 00000000 nt!IopSynchronousCall+0xb7
bacc735c 804f61ea 89fcccc0 00000000 00000001 nt!IopStartDevice+0x4d
bacc7378 8059229b 89fcccc0 00000000 00000000 nt!PipProcessStartPhase1+0x4e
bacc75d0 804f68d3 89fd0840 00000000 00000000 nt!PipProcessDevNodeTree+0x1db
bacc7614 804f6b78 00000000 00000000 8008fa78 nt!PipDeviceActionWorker+0xad
bacc762c 8069d0ee 00000000 00000006 00000000 nt!PipRequestDeviceAction+0x118
bacc7690 80699f70 80084000 bacc76ac 00034000 nt!IopInitializeBootDrivers+0x376
bacc7838 806983d3 80084000 00000000 89faf680 nt!IoInitSystem+0x712
bacc7dac 805cff64 80084000 00000000 00000000 nt!Phase1Initialization+0xac7
bacc7ddc 805460de 8069790c 80084000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
SYMBOL_STACK_INDEX: 1SYMBOL_NAME: ACPI!NotifyHalWithMachineStatesAndRetrieveInterruptModel+35b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ACPI
IMAGE_NAME: ACPI.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 42df0d89
STACK_COMMAND: .cxr 0xffffffffbacc6dc0 ; kb
FAILURE_BUCKET_ID: 0x7E_ACPI!NotifyHalWithMachineStatesAndRetrieveInterruptModel+35b
BUCKET_ID: 0x7E_ACPI!NotifyHalWithMachineStatesAndRetrieveInterruptModel+35b
Followup: MachineOwner
---------0: kd> lm
start end module name
804d7000 806e5000 nt (pdb symbols) c:\symbols\ntkrpamp.pdb\7D6290E03E32455BB0E035E38816124F1\ntkrpamp.pdb
806e5000 80705d00 hal (pdb symbols) c:\symbols\halmacpi.pdb\9875FD697ECA4BBB8A475825F6BF885E1\halmacpi.pdb
ba2ea000 ba303b80 Mup (deferred)
ba304000 ba330980 NDIS (deferred)
ba331000 ba3bd600 Ntfs (deferred)
ba3be000 ba3d4880 KSecDD (deferred)
ba3d5000 ba3e6f00 sr (deferred)
ba3e7000 ba406b00 fltMgr (deferred)
ba407000 ba6bc000 iaStor (deferred)
ba6bc000 ba6e1a00 dmio (deferred)
ba6e2000 ba700d80 ftdisk (deferred)
ba701000 ba711a80 pci (deferred)
ba712000 ba735d80 ntoskrn8 (deferred)
ba736000 ba7a7000 ACPI (pdb symbols) c:\symbolsss\acpi.pdb
ba8a8000 ba8b1300 isapnp (deferred)
ba8b8000 ba8c2580 MountMgr (deferred)
ba8c8000 ba8d5200 VolSnap (deferred)
ba8d8000 ba8e0e00 disk (deferred)
ba8e8000 ba8f4180 CLASSPNP (deferred)
bab28000 bab2cd00 PartMgr (deferred)
bacb8000 bacbb000 BOOTVID (deferred)
bacbc000 bacbf580 HAL8 (deferred)
bada8000 bada9b80 kdcom (deferred)
badaa000 badab100 WMILIB (deferred)
badac000 badad700 dmload (deferred) -
Hi,
I try your Vista-Longhorn acpi.sys.
First I get Bsod A5 (0x00000003,xxx,yyy,zzz).
This Bsod I know and I do for it the same hack as for the very last acpi.sys for Ramsey.
After this hack now
I get Bsod 0x7E (0xC0000005,xxx,yyy,zzz),
which means, that compi writes in not allowed memory.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s"
For to take a closer look at this 7E Bsod I just now start a Windbg session
Dietmar
-
Thanks a lot!
This weekend I have crazy work with examen from pupils.
But on next weekend (or even 2 days earlier) I will try this new acpi.sys .
Have a nice day
Dietmar
-
With bootvid.dll from XP SP3 and XP SP1 same Bsod
Dietmar
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.Opened \\.\com1
Waiting to reconnect...
Connected to Windows XP 2600 x86 compatible target at (Sat Dec 18 15:28:32.140 2021 (UTC + 1:00)), ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: C:\symbols;C:\symbolss
Executable search path is: C:\Symbols
Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
Built by: 2600.xpsp_sp3_qfe.180912-0606
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
System Uptime: not available
Break instruction exception - code 80000003 (first chance)
*******************************************************************************
* *
* You are seeing this message because you pressed either *
* CTRL+C (if you run kd.exe) or, *
* CTRL+BREAK (if you run WinDBG), *
* on your debugger machine's keyboard. *
* *
* THIS IS NOT A BUG OR A SYSTEM CRASH *
* *
* If you did not intend to break into the debugger, press the "g" key, then *
* press the "Enter" key now. This message might immediately reappear. If it *
* does, press "g" and "Enter" again. *
* *
*******************************************************************************
nt!RtlpBreakWithStatusInstruction:
8052b724 cc int 3
kd> bp 805452e5
kd> g*** Fatal System Error: 0x0000000a
(0x55FAF8EC,0x0000001C,0x00000001,0x805452E0)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 XP 2600 x86 compatible target at (Sat Dec 18 15:28:46.968 2021 (UTC + 1:00)), ptr64 FALSE
Loading Kernel Symbols
.......................
Loading User Symbols*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************Use !analyze -v to get detailed debugging information.
BugCheck A, {55faf8ec, 1c, 1, 805452e0}
*** ERROR: Symbol file could not be found. Defaulted to export symbols for halmacpi.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for BOOTVID.dll -
Probably caused by : BOOTVID.dll ( BOOTVID!VidInitialize+106 )Followup: MachineOwner
---------nt!RtlpBreakWithStatusInstruction:
8052b724 cc int 3
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 55faf8ec, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 805452e0, address which referenced memoryDebugging Details:
------------------
WRITE_ADDRESS: 55faf8ecCURRENT_IRQL: 1c
FAULTING_IP:
nt!KeUpdateRunTime+54
805452e0 ff8344010000 inc dword ptr [ebx+144h]DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: bacc369c -- (.trap 0xffffffffbacc369c)
ErrCode = 00000002
eax=ffdff000 ebx=89faf7a8 ecx=89fafb98 edx=00000000 esi=00000000 edi=0002625a
eip=805452e0 esp=bacc3710 ebp=bacc3724 iopl=0 nv up ei ng nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010293
nt!KeUpdateRunTime+0x54:
805452e0 ff8344010000 inc dword ptr [ebx+144h] ds:0023:89faf8ec=00000000
Resetting default scopeLAST_CONTROL_TRANSFER: from 804f8e95 to 8052b724
STACK_TEXT:
bacc3250 804f8e95 00000003 bacc35ac 00000000 nt!RtlpBreakWithStatusInstruction
bacc329c 804f9a80 00000003 55faf8ec 805452e0 nt!KiBugCheckDebugBreak+0x19
bacc367c 8054483c 0000000a 55faf8ec 0000001c nt!KeBugCheck2+0x574
bacc367c 805452e0 0000000a 55faf8ec 0000001c nt!KiTrap0E+0x180
bacc3710 80545246 ba2fd000 ba2fd000 000000d1 nt!KeUpdateRunTime+0x54
bacc3710 806e79a3 ba2fd000 ba2fd000 000000d1 nt!KeUpdateSystemTime+0x146
WARNING: Stack unwind information not available. Following frames may be wrong.
bacc37fc bacb893a 800860b8 00000001 80084000 hal!KfLowerIrql+0x17
bacc3820 80697a7a 80698701 00000000 80698701 BOOTVID!VidInitialize+0x106
bacc3834 806989d7 80084000 00000013 00000000 nt!InbvDriverInitialize+0x6c
bacc3dac 805cffee 80084000 00000000 00000000 nt!Phase1Initialization+0xcb
bacc3ddc 8054623e 8069890c 80084000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kbFOLLOWUP_IP:
BOOTVID!VidInitialize+106
bacb893a 680099cbba push offset BOOTVID!VidBitBlt+0x12a (bacb9900)SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: BOOTVID!VidInitialize+106
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: BOOTVID
IMAGE_NAME: BOOTVID.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 3b7d8345
FAILURE_BUCKET_ID: 0xA_BOOTVID!VidInitialize+106
BUCKET_ID: 0xA_BOOTVID!VidInitialize+106
Followup: MachineOwner
---------kd> lm
start end module name
804d7000 806e5000 nt (pdb symbols) c:\symbols\ntkrpamp.pdb\270E083F57714738A1895FE542CFB8DE1\ntkrpamp.pdb
806e5000 80709f80 hal (export symbols) halmacpi.dll
ba319000 ba332b80 Mup (deferred)
ba333000 ba35f980 NDIS (deferred)
ba360000 ba3ec600 Ntfs (deferred)
ba3ed000 ba403880 KSecDD (deferred)
ba404000 ba415f00 sr (deferred)
ba416000 ba435b00 fltMgr (deferred)
ba436000 ba6eb000 iaStor (deferred)
ba6eb000 ba710a00 dmio (deferred)
ba711000 ba72fd80 ftdisk (deferred)
ba730000 ba740a80 pci (deferred)
ba741000 ba763f00 ntoskrn8 (deferred)
ba764000 ba7a7000 ACPI (deferred)
ba8a8000 ba8b1300 isapnp (deferred)
ba8b8000 ba8c2580 MountMgr (deferred)
ba8c8000 ba8d5200 VolSnap (deferred)
ba8d8000 ba8e0e00 disk (deferred)
ba8e8000 ba8f4180 CLASSPNP (deferred)
bab28000 bab2cd00 PartMgr (deferred)
bacb8000 bacbb000 BOOTVID (export symbols) BOOTVID.dll
bada8000 bada9b80 kdcom (deferred)
badaa000 badab100 WMILIB (deferred)
badac000 badad700 dmload (deferred)
I am looking for a PCIe card for WinXP debugging
in Microsoft Windows XP
Posted
@Gelip
The COM2 port is crazy setting on this board from Biostar z690A for the onboard COM port.
ALL devices have the same notation, connected through PCI bridge,
which I think simple means, that they sit in an Pcie-slot.
I think, that the real problem is in ntldr.
Did you make a try with freeldr from Reactos? In some kind it is the better choice,
have a nice day
Dietmar