按分类浏览
& & & & & & & & & & & & & & & & & & & & & & & & & & & & & & & & & & & & & & & & & & & & & & & & & & & & &Bug Check 0xA5: ACPI_BIOS_ERROR (Windows Debuggers)
Bug Check 0xA5: ACPI_BIOS_ERROR
The ACPI_BIOS_ERROR bug check has a value of 0x. This bug check indicates that the Advanced Configuration and Power Interface (ACPI) BIOS of the computer is not fully compliant with the ACPI specification.
Important Info If You Have Received a STOP Code
If you received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss.
For information about how to recover from this error, see .
ACPI_BIOS_ERROR Parameters
Four bug check parameters appear on the blue screen. Parameter 1 indicates the kind of the incompatibility. The meaning of the other parameters depends on the value of Parameter 1.
If the BIOS incompatibility is related to Plug and Play (PnP) or power management, the following parameters are used.
Parameter 1Parameter 2Parameter 3Parameter 4Cause
ACPI's deviceExtension
ACPI's ResourceList
0: No resource list is found
1: No IRQ resource is found in list
ACPI cannot find the System Control Interrupt (SCI) vector in the resources that are handed to it when ACPI is started.
(See the table later on this page)
The ACPI object that was being run
The return value from the interpreter
The name of the control method (in ULONG format)
ACPI tried to run a control method while creating device extensions to represent the ACPI namespace, but this control method failed.
The ACPI extension that _PRW belongs to
A pointer to the method
The DataType returned (see Amli.h)
ACPI evaluated a _PRW and expected to find an integer as a package element.
The ACPI extension that _PRW belongs to
Aointer to the _PRW
The number of elements in the _PRW
ACPI evaluated a _PRW, and the package that came back failed to contain at least two elements. The ACPI specification requires that two elements always be present in a _PRW.
The ACPI extension that _PRx belongs to
A pointer to the _PRx
A pointer to the name of the object to look for
ACPI tried to find a named object, but it could not find the object.
The ACPI extension that the method belongs to
A pointer to the method
The DataType returned (see Amli.h)
ACPI evaluated a method and expected to receive a buffer in return. However, the method returned some other data type.
The ACPI extension that the method belongs to
A pointer to the method
The DataType returned (see Amli.h)
ACPI evaluated a method and expected to receive an integer in return. However, the method returned some other data type.
The ACPI extension that the method belongs to
A pointer to the method
The DataType returned (see Amli.h)
ACPI evaluated a method and expected to receive a package in return. However, the method returned some other data type.
The ACPI extension that the method belongs to
A pointer to the method
The DataType returned (see Amli.h)
ACPI evaluated a method and expected to receive a string in return. However, the method returned some other data type.
The ACPI extension that _EJD belongs to
The status that the interpreter returns
The name of the object that ACPI is trying to find
ACPI cannot find the object that an _EJD string references.
The ACPI extension that ACPI found a dock device for
A pointer to the _EJD method
0: BIOS does not claim system is dockage
1: Duplicate device extensions for dock device
ACPI provides faulty or insufficient information for dock support.
The ACPI extension that ACPI needs the object for
The (ULONG) name of the method that ACPI looked for
0: Base case
1: Conflict
ACPI could not find a required method or object in the namespace This bug check code is used if there is no _HID or _ADR present.
The NS PowerResource that ACPI needs the object for
The (ULONG) name of the method that ACPI looked for
0: Base case
ACPI could not find a required method or object in the namespace for a power resource (or entity other than a "device"). This bug check code is used if there is no _ON, _OFF, or _STA present for a power resource.
The current buffer that ACPI was parsing
The buffer's tag
The specified length of the buffer
ACPI could not parse the resource descriptor.
(See the table later on this page)
(See the table later on this page)
The current buffer that ACPI was parsing
The buffer's tag
A pointer to a variable that contains the ULONGLONG length of the buffer
ACPI could not parse the resource descriptor. The length exceeds MAXULONG.
The ACPI Machine Language (AML) context
Failed to load table
The Parameter Path String Object was not found
Failed to insert Parameter Data into the ParameterPath String Object
Out of system memory
The NT status code
ACPI had a fatal error when attempting to load a table.
A pointer to the parent NSOBJ
A pointer to the illegal child ACPI namespace object
ACPI had a fatal error when processing an xSDT.
An object was declared as a child of a parent that cannot have children.
If an interrupt routing failure or incompatibility has occurred, the following parameters are used.
Parameter 1Parameter 2Parameter 3Parameter 4Cause
InterruptModel (integer)
The return value from the interpreter
A pointer to the PIC control method
ACPI tried to evaluate the PIC control method but failed.
A pointer to the device object
A pointer to the parent of the device object
A pointer to the _PRT object
(See the following Comments section)
ACPI tried to do interrupt routing, but failed.
A pointer to the device object
A pointer to the string name that ACPI was looking for but could not find
A pointer to the _PRT object
(See the following Comments section)
ACPI could not find the link node referenced in a _PRT.
A pointer to the device object
The device ID or function number.
This DWORD is encoded as follows: bits 5:0 are the PCI device number, and bits 8:6 are the PCI function number
A pointer to the _PRT object
(See the following Comments section)
ACPI could not find a mapping in the _PRT package for a device.
A pointer to the _PRT object
(See the following Comments section)
A pointer to the current _PRT element.
(This pointer is an index into the _PRT.)
The device ID or function number.
This DWORD is encoded as follows: bits 15:0 are the PCI function number, and bits 31:16 are the PCI device number
ACPI found an entry in the _PRT that the function ID is not all F's for.
(The generic format for a _PRT entry is that the device number is specified, but the function number is not.)
A pointer to the link node.
(This device is missing the _DIS method.)
ACPI found a link node, but it cannot disable the node.
(Link nodes must be disabled to allow for reprogramming.)
The vector that could not be found
The _PRT contained a reference to a vector that is not described in the I/O APIC entry's MAPIC table.
The invalid interrupt level.
The ACPI SCI interrupt level is invalid.
The Fixed ACPI Description Table (FADT) could not be located.
The Root System Description Pointer (RSDP) or Extended System Description Table (XSDT) could not be located
The ACPI table signature
A pointer to the ACPI table
The length of the ACPI table is not consistent with the table revision.
The I/O port in the Fixed Table
The PM_TMR_BLK entry in the Fixed ACPI Description Table doesn't point to a working ACPI timer block.
If a miscellaneous failure or incompatibility has occurred, the following parameters are used.
Parameter 1Parameter 2Parameter 3Parameter 4Cause
The I/O port in the Fixed Table
The PM_TMR_BLK entry in the Fixed ACPI Description Table does not point to a working ACPI timer block.
If Parameter 1 equals 0x02, the ACPI BIOS could not process the resource list for the PCI root buses. In this case, Parameter 3 specifies the exact problem, and the remaining parameters have the following definitions.
Parameter 2Parameter 3Parameter 4Cause
The ACPI extension for the PCI bus
A pointer to the QUERY_RESOURCES IRP
ACPI cannot convert the BIOS' resource list into the proper format. This probably represents an error in the BIOS' list encoding procedure.
The ACPI extension for the PCI bus
A pointer to the QUERY_RESOURCE_REQUIREMENTS IRP
ACPI cannot convert the BIOS' resource list into the proper format. This probably represents an error in the BIOS' list encoding procedure.
The ACPI extension for the PCI bus
ACPI found an empty resource list.
The ACPI extension for the PCI bus
A pointer to the PNP CRS descriptor
ACPI could not find the current bus number in the CRS.
The ACPI extension for the PCI bus
A pointer to the resource list for PCI
A pointer to the E820 memory table
The list of resources that PCI claims to decode overlaps with the list of memory regions that the E820 BIOS interface reports. (This kind of conflict is never permitted.)
If Parameter 1 equals 0x10, the ACPI BIOS could not determine the system-to-device-state mapping correctly. In this situation, Parameter 3 specifies the exact problem, and the remaining parameters have the following definitions.
Parameter 2Parameter 3Parameter 4Cause
The ACPI extension whose mapping is needed
The DEVICE_POWER_STATE (this is "x+1")
_PRx was mapped back to a non-supported S-state.
The ACPI extension whose mapping is needed
The SYSTEM_POWER_STATE that cannot be mapped
ACPI cannot find a D-state to associate with the S-state.
The ACPI extension whose mapping is needed
The SYSTEM_POWER_STATE that cannot be mapped
The device claims to be able to wake the system when the system is in this S-state, but the system does not actually support this S-state.
If Parameter 1 equals 0x11, the system could not enter ACPI mode. In this situation, Parameter 2 specifies the exact problem, and the remaining parameters have the following definitions.
Parameter 2Parameter 3Parameter 4Cause
The system could not initialize the AML interpreter.
The system could not find RSDT.
The system could not allocate critical driver structures.
The system could not load RSDT.
The system could not load DDBs.
The system cannot connect the Interrupt vector.
SCI_EN never becomes set in PM1 Control Register.
A pointer to the table that had a bad checksum
Creator revision
The table checksum is incorrect.
A pointer to the table that ACPI failed to load
Creator revision
ACPI failed to load DDB.
FADT version
Unsupported firmware version.
The system could not find MADT.
The system could not find any valid Local SAPIC structures in the MADT.
The value of Parameter 1 indicates the error.
Resolution
If you are debugging this error, use the
extension. This extension displays all the relevant data (device extensions, nsobjects, or whatever is appropriate to the specific error).
If you are not performing debugging, this error indicates that you have to obtain a new BIOS. Contact your vendor or visit the internet to get a new BIOS.
If you cannot obtain an updated BIOS, or the latest BIOS is still not ACPI compliant, you can turn off ACPI mode during text-mode setup. To turn off ACPI mode, press the F7 key when you are prompted to install storage drivers. The system does not notify you that the F7 key was pressed, but it silently disables ACPI and enables you to continue your installation.
A PCI routing table (_PRT) is the ACPI BIOS object that specifies how all the PCI devices are connected to the interrupt controllers. A computer with multiple PCI buses might have multiple _PRTs.
You can display a _PRT in the debugger by using the !acpikd.nsobj extension together with the address of the _PRT object as its argument.
Was this page helpful?
Your feedback about this content is important.Let us know what you think.
Additional feedback?
1500 characters remaining
Thank you!
We appreciate your feedback.
Related developer sites
Other Windows sites
Essentials
Stay connected
Hello from Seattle.软件日志-第1页-Storm_Center
病毒安全知识,电脑网络技术,手工杀毒方法,答疑解决笔记
　　小米的MIUI有个单手模式，用于在大屏上缩小到利于单手操作的状态，开启此功能后，可在手机底部，不是屏幕底部，是安卓手机下边三个按键的地方，从中间按键向左或右边按键滑动，从而缩小屏幕。向左边滑动，屏幕就向左缩小，向右就向右缩小。 &
　　想在Windows命令提示符窗口CMD中复制粘贴不能直接Ctrl+C、Ctrl+V，如果直接在CMD窗口中Ctrl+V，就会出现^V。正确的复制粘贴方法是，点击CMD窗口左上角，出现菜单，转到编辑，然后就出现标记、复制、粘贴等命令。
　　办公室一台电脑开机时蓝屏，错误代码为0x，查了下，通常0x错误表示硬件设备的驱动程序遇到了问题，可能因为硬件设备驱动程序引起。但是在屏幕上显示的蓝屏信息中没有找到文件名，就无法根据文件确定可能的问题驱动。
　　一个decode的SQL语句老是筛不出想要的数据，应该是判断的字段包括了NULL，instr无法对其行使正常的查找。Oracle中的instr，在被查找的字符串中找得到要查找的字符串，就返回其所在的位置数值，找不到就返回0，而如果被查找的字符串是NULL，就返回不了任何东西。
　　在一台电脑上用ghost恢复win7系统之后，就进不了系统，满屏的英文，什么slic loader、RSDT、XSDT、DSDT、FACP、slic entry found 0x7af8fea0 index 0xb、recalculating checksums rsdt len 0x54，等等一大堆，滚两屏才看完，似乎要用windows安装光盘来修复。&
　　原本各部门PPT汇总需要使用统一格式，不过那次会议第一不作要求，第二时间紧，第三各部门制作的PPT竟然不同母版，如果强行使用同一母版格式，很多地方都要重新调整适应，需要是时间与精力，第四有些得瑟的做的还挺好看（同样这种导入统一母版肯定是一塌胡涂），还是保留的好，所以就保留原来格式进行拼接合并。
　　Oracle中的trunc函数用于不四舍五入地截取数字或日期，不过它不仅仅是取整那么简单。比如要做个累计报表，需要从数据库中定期取出某月固定一天或某周固定周几开始的数据累计，可用trunc(sysdate,'mm')取当月第一天的日期，或trunc(sysdate,'d')取当周第一天的日期（以周日为一周第一天）。
　　在XP的文件夹选项里有一个选项&使用简单文件共享（推荐）&，默认勾选。&利用简单文件共享，您可以与工作组或网络上的任何人共享文件夹，以及将您的用户配置文件中的文件夹设为专用。但是，如果启用了简单文件共享，则无法阻止特定用户和组访问您的共享文件夹。如果关闭简单文件共享，则可以允许特定用户和组访问共享文件夹。那些用户必须使用您授权访问您的共享文件夹的用户配置文件的凭据登录。&简单模式其实就是用guest登录。
　　我遇到的此故障出现在开机启动时，在显示帐户登录窗口之前跳出来：Parser Message: Value creation failed ' ' at line 422。从网上搜索的情况看，line后的数字会有变化，所报的行数各有不同。查找中看到一篇微软的文章，称此问题原因是C:\WINDOWS\System32\Shellstyle.dll文件丢失或损坏。
　　其实从Windows 7到Win8、Win10都会自动更新硬件驱动程序，只是有时你可能并不喜欢由Windows来提示你更新驱动以及它找到的驱动，何况有的驱动并不是越新越好，所以需要关闭windows的驱动更新。
　　在Oracle的SQL语句中要用到条件判断，除了decode外，还有case when。decode只能进行等式比较判断，如decode(字段,值1,结果1,值2,结果2,...,值n,结果n,默认值)，当所选字段等于值1时，取结果1，等于值2时，取结果2，&&，最后都不等时取默认值，而case when除了等于，可以使用大于、小于的比较，可以替代decode，更象&if ...else...&。
　　带个地图APP去外地是个很好的方法，虽然一些目的地或目标仍需要用嘴来问，但地图能把我们指引到最近的位置，有时已经就到了。比如百度地图APP，出发前，先下个目的地的离线地图，如果有的话，回来就删掉，否则一有更新就会自动下载，如果不常去就不用长期保存，只是百度地图的离线地图并不支持线下搜索，必须联网才行，所以要保证手机流量足够并支持外地漫游，否则找不到WIFI又不能在当地用流量，再好的工具也用不上&&
　　iPad也会死机，如果真的是死机而不是其它什么致命的故障，那么重启一下就可以解决。重启iPad的方法一般是：1、长按电源键，直到重启，2，如果长按的方法失败，就同时按HOME与电源键，让它重启，3、如果还不行，等它消耗光电量自己关机，再充电尝试开机，当然这时也可能再也开不了机，希望有好运吧。
　　Oracle的左连接类似于a.id=b.id(+)的条件在where子句中，实现a表全部数据与b表中id与a表中id相等数据的合集，这时a表中那些在b表中无对应id的数据所取得的b表所独有字段数据为空，但是如果这时在where子句中再加上一个b表的限制条件，比如减少搜索范围，如where a.id=b.id(+) and b.created_time&=sysdate-365，则在b表中无对应id的a表数据将消失，就和a.id=b.id一样。
　　我不知道是否此问题仅出现在安卓手机上，对于压缩包内含有中文文件名的文件，如果在手机上打开压缩包或解压这些中文文件名都显示乱码，但文档内容正常，不得不先打开看看是什么文件，再重命名文件名。出现这种问题的原因据说是因为在WINDOWS下打包与在安卓或linux下解压时的汉字编码不同&&
　　一、Excel的四舍五入计算，Excel单元格格式可以设置显示小数的位数，但是如果在设置过显示小数位数的单元格上再进行计算，Excel则还是按原来未截取位数的原始数据进行运算，而不是用从表面上看来已经截取小数位数的结果进行的计算，两者结果间会有细小的偏差，有时这种偏差是不允许的，所以要想保证最后的运算结果是由前面各个单元格显示之数得出来的，必须先对各个单元格的数据进行实际的处理，而不能仅仅是显示
　　没想到好压里的压缩包看图是要下载安装2345看图王，但是想卸载时却卸载不掉，老是提示2345picviewer.exe无法删除，要求先关闭程序，然后重试。可是无论是进程还是桌面都没有看到这个程序被打开，即使重启也仍然是这个无法删除2345picviewer.exe的提示，卸载不得不放弃。
　　第一台打印机打印时出现错误，右下角打印图标上出现红色问题，另一台打印机在打印邮件出现缺少对象preview.js的提示，打印测试页失败，但任意打开一个excel文档打印又正常。这两台出现问题的打印机后来都通过重装打印机驱动程序解决。
　　U盘接电脑无反应可能有不同的原因，本文遇到的是在同事的一台电脑上，她说自己不知道动了什么还是说删了什么，没太听明白，反正是插上U盘，右下角没有出接上USB设备的提示，也没出现移动设备的盘符和图标，而该U盘在其它电脑上是正常的，而且该同事强调原先能用的数码相机的存储卡最近接这台电脑也是同样没有反应，这就排除了这只U盘损坏的理由，也迫使我必须看看，毕竟已经不是一只U盘的问题了。
　　本例来源电脑报论坛系统版一个求助。原问题是出现.NET Framework初始化错误后重新下载安装NET.Framework 4，但出现尚未安装.NET Framework 4的提示，原因是HRESULT 0xc8000222。解决方案是：控制面板－程序与功能－启用或关闭Windows功能，勾选.net framework，然后确定开始安装，之后重启。
文章归档-鼠标滑过查看}