Vista RTM acpi.sys on XP.

**Damnation** · February 12, 2024

I've made a my own custom HAL adding in ACPI table finding code into HalAcpiDispatchTable inside the HAL -

I'm wondering if this might get us any closer to being able to boot XP with Vista RTM acpi.sys

Still get a 7E BSOD with this but I'm wondering if it happens because of PmHalDispatchTable in acpi.sys or not, try it out when you have time.

Edited February 12, 2024 by Damnation

**Damnation** · February 17, 2024

@Dietmar

If we can get this working it might help with that HP laptop thats been giving you trouble.

Have you got a spare PC that you can use to debug this?

**Damnation** · February 28, 2024

@Dietmar

Have you finished with ACPI testing on the HP laptop as of yet?

If you have, would you mind trying to trace this 7E BSOD?

**Dietmar** · February 28, 2024

@Damnation

Yes, I fixed everything that is possible on the HP 255 g6 board. Now, there is ACPI-Multprocessor with mostly all drivers.

A lot of other notebooks boot with the same idea XP SP3 now, which show before Bsod, not direct related to acpi.sys.

All those Bsods happen because of their VGA settings in DSDT and their internal VGA cant be disabled via Bios.

Now I am just setting up a new XP SP3 on my Asrock z370 k6 board.

Without any extra driver, just naked and ready for debug.

This is possible, because it can use PS/2 for mouse and keyboard. Then I add your acpi.sys, hal.dll and ntoskrn8.sys.

Soon I report

Dietmar

**Dietmar** · February 28, 2024

@Damnation

First I make small joke, just replace acpi.sys, halmacpi.dll and ntoskrn8.sys with your version on the XP SP3

Setup xp.iso.

But during the "Setup is inspecting your hardware configuration" comes message, that "acpi.sys is damaged".

Now I setup with the original files and debug

Dietmar

**Dietmar** · February 28, 2024

@Damnation

A first run shows only the same error as you have, that someone tries to write in forbidden memory

Dietmar

*** Fatal System Error: 0x0000007e
                       (0xC0000005,0x00000000,0xF789E168,0xF789DE64)

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 (Wed Feb 28 18:25:27.820 2024 (UTC + 1:00)), ptr64 FALSE
Loading Kernel Symbols
..............................
Loading User Symbols

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {c0000005, 0, f789e168, f789de64}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

nt!RtlpBreakWithStatusInstruction:
804e2a42 cc              int     3
11: 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: 00000000, The address that the exception occurred at
Arg3: f789e168, Exception Record Address
Arg4: f789de64, Context Record Address

Debugging Details:
------------------


EXCEPTION_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: 
+150b5800150b78
00000000 ??              ???

EXCEPTION_RECORD:  f789e168 -- (.exr 0xfffffffff789e168)
ExceptionAddress: 00000000
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000000
Attempt to read from address 00000000

CONTEXT:  f789de64 -- (.cxr 0xfffffffff789de64;r)
eax=00000000 ebx=80702790 ecx=54445358 edx=00000001 esi=f7472b20 edi=807026c0
eip=00000000 esp=f789e230 ebp=f789e250 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
00000000 ??              ???
Last set context:
eax=00000000 ebx=80702790 ecx=54445358 edx=00000001 esi=f7472b20 edi=807026c0
eip=00000000 esp=f789e230 ebp=f789e250 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
00000000 ??              ???
Resetting default scope

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_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:  00000000

EXCEPTION_PARAMETER2:  00000000

READ_ADDRESS:  00000000 

FOLLOWUP_IP: 
+150b5800150b78
00000000 ??              ???

FAILED_INSTRUCTION_ADDRESS: 
+150b5800150b78
00000000 ??              ???

BUGCHECK_STR:  0x7E

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

LAST_CONTROL_TRANSFER:  from 00000000 to 00000000

STACK_TEXT:  
f789e22c 00000000 00000000 00000000 f74774fc 0x0


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  0x7E_NULL_IP_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  0x7E_NULL_IP_ANALYSIS_INCONCLUSIVE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x7e_null_ip_analysis_inconclusive

FAILURE_ID_HASH:  {dfedf0b5-2624-ece8-95fa-645295e3260a}

Followup: MachineOwner
---------

**Dietmar** · February 28, 2024

@Damnation

Next try gives this

Dietmar

https://ufile.io/tw0rd9vu

**Damnation** · February 28, 2024

@Dietmar

hmmm. so it's not even getting to the ACPI table finding code I added to my HAL.

IoReleaseVpbSpinLock wouldn't be the cause would it?

**Damnation** · February 28, 2024

@Dietmar

Maybe load the symbols for my HAL and see if that gives more information?

**Dietmar** · February 28, 2024

@Damnation

I have your hal.pdb integrated.

Now I get this,

looks like kind of loop, or if something cant be found

Dietmar

https://ufile.io/310s052p

**Damnation** · February 29, 2024

@Dietmar

There are some IoResource functions in my ntoskrn8.sys

Perhaps it's getting stuck there?

does loading my ntoskrn8.pdb show anything?

**Dietmar** · February 29, 2024

@Damnation

This is Bsod surrounding without any breakpoint, Windbg continous with "p", F10,

Dietmar

https://ufile.io/b5j6aq0z

**Damnation** · February 29, 2024

@Dietmar

OK, thanks for testing.

let me try a few things...

**Dietmar** · February 29, 2024

@Damnation

nt!KiDispatchInterrupt+0x393:
804dcbe5 3b6d00          cmp     ebp,dword ptr [ebp]
11: kd> p
nt!KiDispatchInterrupt+0x396:
804dcbe8 740d            je      nt!KiDispatchInterrupt+0x3a5 (804dcbf7)
11: kd> p
nt!KiDispatchInterrupt+0x3a5:
804dcbf7 83bb2801000000  cmp     dword ptr [ebx+128h],0
11: kd> p
nt!KiDispatchInterrupt+0x3ac:
804dcbfe 74d7            je      nt!KiDispatchInterrupt+0x385 (804dcbd7)
11: kd> p

Packet failed authentication.  Please make sure the host and target encryption
keys match exactly. Also make sure you don't have multiple target machines
pointed at the same network port on your host.
Bad packet sent from 192.168.2.102.
Run nslookup 192.168.2.102 from a command prompt to get the machine name.

Packet failed authentication.  Please make sure the host and target encryption
keys match exactly. Also make sure you don't have multiple target machines
pointed at the same network port on your host.
Bad packet sent from 192.168.2.102.
Run nslookup 192.168.2.102 from a command prompt to get the machine name.

Packet failed authentication.  Please make sure the host and target encryption
keys match exactly. Also make sure you don't have multiple target machines
pointed at the same network port on your host.
Bad packet sent from 192.168.2.102.
Run nslookup 192.168.2.102 from a command prompt to get the machine name.
nt!KiDispatchInterrupt+0x38d:
804dcbdf f390            pause
10: kd> p

**Dietmar** · February 29, 2024

@Damnation

Break instruction exception - code 80000003 (first chance)
nt!KiDispatchInterrupt+0x38d:
804dcbdf f390            pause
1: kd> g
Break instruction exception - code 80000003 (first chance)
*******************************************************************************
*                                                                             *
*   You are seeing this message because you pressed either                    *
*       CTRL+C (if you run console kernel debugger) or,                       *
*       CTRL+BREAK (if you run GUI kernel debugger),                          *
*   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!DbgBreakPointWithStatus+0x4:
804e2a42 cc              int     3
0: kd> g

*** Fatal System Error: 0x0000007e
                       (0xC0000005,0x00000000,0xF789E168,0xF789DE64)

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 (Thu Feb 29 19:05:36.031 2024 (UTC + 1:00)), ptr64 FALSE
Loading Kernel Symbols
..............................
Loading User Symbols

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {c0000005, 0, f789e168, f789de64}

Probably caused by : NDIS.sys ( NDIS!ndisMQueryNetworkAddress+23 )

Followup: MachineOwner
---------

nt!RtlpBreakWithStatusInstruction:
804e2a42 cc              int     3
11: 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: 00000000, The address that the exception occurred at
Arg3: f789e168, Exception Record Address
Arg4: f789de64, Context Record Address

Debugging Details:
------------------


EXCEPTION_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: 
+1f451c801f451e8
00000000 ??              ???

EXCEPTION_RECORD:  f789e168 -- (.exr 0xfffffffff789e168)
ExceptionAddress: 00000000
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000000
Attempt to read from address 00000000

CONTEXT:  f789de64 -- (.cxr 0xfffffffff789de64;r)
eax=00000000 ebx=80702790 ecx=54445358 edx=00000001 esi=f7472b20 edi=807026c0
eip=00000000 esp=f789e230 ebp=f789e250 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
00000000 ??              ???
Last set context:
eax=00000000 ebx=80702790 ecx=54445358 edx=00000001 esi=f7472b20 edi=807026c0
eip=00000000 esp=f789e230 ebp=f789e250 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
00000000 ??              ???
Resetting default scope

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_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:  00000000

EXCEPTION_PARAMETER2:  00000000

READ_ADDRESS:  00000000 

FOLLOWUP_IP: 
NDIS!ndisMQueryNetworkAddress+23
bac63a56 e6ff            out     0FFh,al

FAILED_INSTRUCTION_ADDRESS: 
+23
00000000 ??              ???

BUGCHECK_STR:  0x7E

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

LAST_CONTROL_TRANSFER:  from 00000000 to 00000000

SYMBOL_ON_RAW_STACK:  1

STACK_ADDR_RAW_STACK_SYMBOL: fffffffff789d9e0

STACK_COMMAND:  dps fffffffff789d9e0-0x20 ; kb

STACK_TEXT:  
f789d9c0  6c674a6f
f789d9c4  6e666e67
f789d9c8  ee776a67
f789d9cc  6a676a67
f789d9d0  7e647a66
f789d9d4  7b667866
f789d9d8  38063a0e
f789d9dc  bac63a56 NDIS!ndisMQueryNetworkAddress+0x23
f789d9e0  3a063a06
f789d9e4  3a063206
f789d9e8  91ea67db
f789d9ec  c37cf2f2
f789d9f0  f1ea779b
f789d9f4  e3ff5070
f789d9f8  b1eb67d3
f789d9fc  e3fed2f2
f789da00  00008070
f789da04  00000000
f789da08  8071e0fe hal!HalpGetFeatureBits+0x52 [e:\xpsp1\nt\base\hals\halmps\i386\mphal.c @ 1097]
f789da0c  00000001
f789da10  f78feb3c
f789da14  f78feb38
f789da18  f78feb38
f789da1c  00008070
f789da20  00000000
f789da24  00000000
f789da28  756e6547
f789da2c  49656e69
f789da30  6c65746e
f789da34  00d1e300
f789da38  00000000
f789da3c  00000000


SYMBOL_NAME:  NDIS!ndisMQueryNetworkAddress+23

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NDIS

IMAGE_NAME:  NDIS.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  48025d03

IMAGE_VERSION:  5.1.2600.5512

FAILURE_BUCKET_ID:  0x7E_NULL_IP_NDIS!ndisMQueryNetworkAddress+23

BUCKET_ID:  0x7E_NULL_IP_NDIS!ndisMQueryNetworkAddress+23

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x7e_null_ip_ndis!ndismquerynetworkaddress+23

FAILURE_ID_HASH:  {6cac7e57-f19c-4081-7e29-9f6a6f30cf6b}

Followup: MachineOwner
---------

Sign In

Vista RTM acpi.sys on XP.

Recommended Posts

Damnation

Damnation

Damnation

Dietmar

Dietmar

Dietmar

Dietmar

Damnation

Damnation

Dietmar

Damnation

Dietmar

Damnation

Dietmar

Dietmar

Create an account or sign in to comment

Create an account

Sign in

Recently Browsing 0 members

Activity

Browse