Jump to content

Compiling ACPI v2.0 driver for Windows XP SP3 and Windows 2003 SP2 (x32/x64)


Mov AX, 0xDEAD

Recommended Posts


The videodriver seems to make this problems

Dietmar

Use !analyze -v to get detailed debugging information.

BugCheck B4, {89ebb8b8, 89eb6000, 89eb5000, 50000}

Probably caused by : win32k.sys ( win32k!DrvDriverFailure+1af )

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

nt!RtlpBreakWithStatusInstruction:
8052b724 cc              int     3
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_DRIVER_INIT_FAILURE (b4)
The system was not able to go into graphics mode because no display drivers
were able to start.  This usually occurs if no video miniport drivers load
successfully.
Arguments:
Arg1: 89ebb8b8, Driver failure data.
Arg2: 89eb6000, Graphics device list.
Arg3: 89eb5000, Graphics device list data.
Arg4: 00050000, Possible cause of the bugcheck.

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


DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xB4

PROCESS_NAME:  csrss.exe

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

LAST_CONTROL_TRANSFER:  from 804f8e95 to 8052b724

STACK_TEXT:  
ba2777dc 804f8e95 00000003 ba277b38 00000000 nt!RtlpBreakWithStatusInstruction
ba277828 804f9a80 00000003 ba277d24 bbdd15dc nt!KiBugCheckDebugBreak+0x19
ba277c08 804f9fcf 000000b4 89ebb8b8 89eb6000 nt!KeBugCheck2+0x574
ba277c28 bf91cfa7 000000b4 89ebb8b8 89eb6000 nt!KeBugCheckEx+0x1b
ba277d30 ba277d64 0015fd98 bf8ab5af 00000001 win32k!DrvDriverFailure+0x1af
WARNING: Frame IP not in any known module. Following frames may be wrong.
ba277d48 bf8ab620 ba277d64 80541818 00050000 0xba277d64
ba277d50 80541818 00050000 0000005c 00000060 win32k!NtUserInitialize+0x87
ba277d50 7eb3e514 00050000 0000005c 00000060 nt!KiSystemServicePostCall
0015fd80 75b686df 75b68669 00050000 0000005c ntdll!KiFastSystemCallRet
0015fdb0 75b43472 00000000 00000000 0016274d winsrv!NtUserInitialize+0xc
0015fe20 75b4301b 0016272a 00162731 00000003 CSRSRV!CsrLoadServerDll+0x1a0
0015ff74 75b430f3 0000000a 001624f0 7eb3dc9e CSRSRV!CsrParseServerCommandLine+0x2d6
0015ff88 4a68115d 0000000a 001624f0 00000005 CSRSRV!CsrServerInitialization+0x95
0015ffa8 4a6818d7 0000000a 001624f0 0016251c csrss!main+0x4f
0015fff4 00000000 7ffde000 000000c8 00000146 csrss!NtProcessStartup+0x1d2


STACK_COMMAND:  kb

FOLLOWUP_IP:
win32k!DrvDriverFailure+1af
bf91cfa7 90              nop

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  win32k!DrvDriverFailure+1af

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5c93004e

IMAGE_VERSION:  5.1.2600.7684

FAILURE_BUCKET_ID:  0xB4_win32k!DrvDriverFailure+1af

BUCKET_ID:  0xB4_win32k!DrvDriverFailure+1af

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xb4_win32k!drvdriverfailure+1af

FAILURE_ID_HASH:  {28d7d534-884c-fc26-c175-02817df2d217}

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

 

Link to comment
Share on other sites

4 hours ago, Damnation said:

 

@SEDANEH

If you're running setup from USB then use WinsetupfromUSB to make your installation media. works much better for XP.

im running from usb  by winsetupfromusb to install windows xp but i see A5  and i reset and befor  load the windows setup  i press F7 and i see B7

Because I am using CORE I9 13900K, it might not be installed. Can it be from CORE I9 13900K?

Link to comment
Share on other sites

@SEDANEH

No, the CPU doesn't cause this.

Andalu posted that pic showing that it's possible to install XP on your motherboard, so your making a mistake somewhere in the process of making your XP installation media.

Can you go through, step by step, how you're making your XP install media?

Link to comment
Share on other sites

51 minutes ago, Damnation said:

@SEDANEH

No, the CPU doesn't cause this.

Andalu posted that pic showing that it's possible to install XP on your motherboard, so your making a mistake somewhere in the process of making your XP installation media.

Can you go through, step by step, how you're making your XP install media?

https://zone94.com/downloads/software/operating-systems/123-windows-xp-professional-sp3-x86-integral-edition?comment_id=10538

that is the windows xp

i copy this windows xp to usb flash by winsetupfromusb

i boot from usb

i see A5

i bootint from usb and before the windows install are loding i press F7 and see B7

Link to comment
Share on other sites

@Mov AX, 0xDEAD

It is an acpi related error.

Do you have an idea, for what I can look in its DSDT and maybe repair?

Windbg tells, that an _HID or _ADR is somewhere misses in DSDT

Dietmar


Microsoft (R) Windows Debugger Version 6.3.9600.17200 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Using NET for debugging
Opened WinSock 2.0
Waiting to reconnect...
Connected to target 192.168.2.103 on port 50000 on local IP 192.168.2.101.
Connected to Windows XP 2600 x86 compatible target at (Sun Feb  4 20:07:03.609 2024 (UTC + 1:00)), ptr64 FALSE
Kernel Debugger connection established.

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
OK                                             C:\Symbols

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
OK                                             C:\symbolssss
Symbol search path is: C:\symbolssss
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

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
OK                                             E:\binaries.x86fre\Symbols

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
OK                                             C:\Symbols

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
OK                                             C:\symbolssss
OK                                             C:\symbols
OK                                             C:\symbolss
OK                                             C:\symbolsss
OK                                             E:\binaries.x86fre\Symbols
Deferred                                       https://msdl.microsoft.com/download/symbols
Deferred                                       srv*
Break instruction exception - code 80000003 (first chance)
nt!DbgBreakPoint:
80ac37e0 cc              int     3
kd> g
MM: Loader/HAL memory block indicates large pages cannot be used for 80100000->8012777F
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 
ACPI0007 def #1 

*** Fatal System Error: 0x000000a5
                       (0x0000000D,0x8A776980,0x5244415F,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 XP 2600 x86 compatible target at (Sun Feb  4 20:07:08.421 2024 (UTC + 1:00)), ptr64 FALSE
Loading Kernel Symbols
.............................
Loading User Symbols

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

Use !analyze -v to get detailed debugging information.

BugCheck A5, {d, 8a776980, 5244415f, 0}

Probably caused by : ACPI.sys ( ACPI!ACPIBuildProcessDevicePhaseAdrOrHid+4f )

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

nt!RtlpBreakWithStatusInstruction:
80ac37ec cc              int     3
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ACPI_BIOS_ERROR (a5)
The ACPI Bios in the system is not fully compliant with the ACPI specification.
The first value indicates where the incompatibility lies:
This bug check covers a great variety of ACPI problems.  If a kernel debugger
is attached, use "!analyze -v".  This command will analyze the precise problem,
and display whatever information is most useful for debugging the specific
error.
Arguments:
Arg1: 0000000d, ACPI_REQUIRED_METHOD_NOT_PRESENT
	ACPI could not find a required method/object in the namespace
	This is the bugcheck that is used if a vendor does not have an
	_HID or _ADR present
Arg2: 8a776980, The ACPI Extension that ACPI needs the object for
Arg3: 5244415f, The (ULONG) name of the method ACPI looked for
Arg4: 00000000, Base Case

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


ACPI_EXTENSION:  8a776980 -- (!acpikd.acpiext 8a776980)

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xA5

PROCESS_NAME:  System

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

DPC_STACK_BASE:  FFFFFFFFBACC8000

LAST_CONTROL_TRANSFER:  from 80a30d7b to 80ac37ec

STACK_TEXT:  
bacc7b18 80a30d7b 00000003 bacc7e74 00000000 nt!RtlpBreakWithStatusInstruction
bacc7b64 80a319e6 00000003 8a776980 8a776930 nt!KiBugCheckDebugBreak+0x19
bacc7f44 80a31f77 000000a5 0000000d 8a776980 nt!KeBugCheck2+0x574
bacc7f64 ba739821 000000a5 0000000d 8a776980 nt!KeBugCheckEx+0x1b
bacc7f8c ba73a4b2 00000000 00000000 80addf90 ACPI!ACPIBuildProcessDevicePhaseAdrOrHid+0x4f [c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\buildsrc.c @ 2901]
bacc7fb0 ba73b29e ba781768 ba77c288 bacc7fe0 ACPI!ACPIBuildProcessGenericList+0x52 [c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\buildsrc.c @ 4851]
bacc7fc8 80ae3f59 ba781720 00000000 00000000 ACPI!ACPIBuildDeviceDpc+0xe2 [c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\buildsrc.c @ 661]
bacc7ff4 80ae3a3b bacc3108 00000000 00000000 nt!KiRetireDpcList+0x7e
bacc7ff8 bacc3108 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b
WARNING: Frame IP not in any known module. Following frames may be wrong.
80ae3a3b 00000000 00000009 0081850f bb830000 0xbacc3108


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ACPI!ACPIBuildProcessDevicePhaseAdrOrHid+4f [c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\buildsrc.c @ 2901]
ba739821 894624          mov     dword ptr [esi+24h],eax

FAULTING_SOURCE_LINE:  c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\buildsrc.c

FAULTING_SOURCE_FILE:  c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\buildsrc.c

FAULTING_SOURCE_LINE_NUMBER:  2901

FAULTING_SOURCE_CODE:  
No source found for 'c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\buildsrc.c'


SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  ACPI!ACPIBuildProcessDevicePhaseAdrOrHid+4f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ACPI

IMAGE_NAME:  ACPI.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  639267ed

IMAGE_VERSION:  5.1.2600.7777

FAILURE_BUCKET_ID:  0xA5_ACPI!ACPIBuildProcessDevicePhaseAdrOrHid+4f

BUCKET_ID:  0xA5_ACPI!ACPIBuildProcessDevicePhaseAdrOrHid+4f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xa5_acpi!acpibuildprocessdevicephaseadrorhid+4f

FAILURE_ID_HASH:  {58890b9a-d3fd-b56d-86d9-787ef65b881a}

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

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...