STOP: 0x0000000A

**miccha** · 2002-07-05, 09:26 AM

我的解決方式是:不讓電腦穿衣服....
我發生的狀況就是這樣解決的...

**Ryu** · 2002-07-05, 10:25 AM

我的直覺
ram有問題

無名 · 2002-07-05, 02:13 PM

最初由沉默ソ狼發表
已經自動重新開機數十次了,我快瘋掉了

最多的就是用光碟機的時候,不管灌遊戲還是怎樣,十次有五次是在用光碟機的時候自動
重開

我看過之前別人的文章,我自己測試了很多但還是一樣

我檢查過 CPU 溫度沒超瀕 42度而以
我也重灌過 2K
POWER 不穩定我也拆了二個系統風扇,但也沒有好改
記憶體我就沒辦法試了,已經沒錢買也沒人可以借
我曾經把自動重開機取消,但是我放edonkey什麼都沒有動,第二天起床
開螢幕後就是已經當機了.....
但我這台自己組的才不到半年,不知道各位能幫我看看

P4S333
P4 1.6 + 王者之風
創見DDR266 256RAM
S60G + S20G
ACER 50X
TRAXDATA2410
RTL8139C

硬碟下裝一顆雙風扇
前置一顆系統風扇
後置三個系統風扇,目前後置風扇拆了二顆,所以剩一顆
POWER 350 連機箱的

Windows98se+Windows2k

這台我組了大約才4個半月
除了光碟機跟S20G是舊的,其它都是新的

強烈建議極有可能是記憶體問題,我發生過這個問題狂當機,結果是記憶體掛了一條

**KingHsuan** · 2002-07-05, 02:31 PM

經過我更新ram之後的結果
的確是ram有問題....
正確的說...
創見的茂矽顆粒和微星的版子會相衝
我換成SAMSUNG的就可以了...

**flyup** · 2002-07-09, 12:56 AM

我敢保證：
電腦主機板的CPU附近的"電容器已經燒毀"，才會發生這樣。

一般電腦維修常識以外的問題：主機板電子零件燒毀。

常易做出錯誤的判斷，因為軟體安裝會有時可以，有時中斷。

或是在windows98開機後出現...........VxD VMM(01)的藍色畫面！

我個人已經碰過兩片主機板都是如上述，一樣的狀況。

解決方式：更換主機板即可！！

**Schnaufer** · 2002-07-09, 01:36 PM

STOP: 0x0000000A (parameter, parameter, parameter, parameter)
IRQL_NOT_LESS_OR_EQUAL

Explanation:

　　This is a Windows 2000 Executive character-mode STOP message. It indicates an attempt was made to touch pageable memory at a process IRQL (interrupt request level) that is too high. This is usually caused by drivers using incorrect addresses. The fourth parameter in the message parameter list is the memory address at which the fault happened. The second parameter shows the IRQL. If the IRQL was not equal to 2, then the interrupt most likely came from a driver. Compare the memory address in the fourth parameter with the base addresses of the drivers in the driver table on the STOP screen to find the driver that is the problem. Note that the third parameter encodes read/write access (0 = read, 1= write).

User Action:

　　If this is the first time you have booted after installing new hardware, remove the hardware and boot again. Check the Microsoft Hardware Compatibility List to verify that the hardware and its drivers are compatible with Windows 2000. For information about the hardware, contact the supplier. If you are installing Windows 2000 for the first time, check the Windows 2000 system requirements, including the amount of RAM and disk space required to load the operating system. Also, check the Hardware Compatibility List to verify that the system can run Windows 2000. If Windows 2000 is loaded and no new hardware has been installed, reboot with recovery options set to create a dump file. If the message continues to appear, select the Last Known Good option when you reboot. If there is no Last Known Good configuration, try using the Emergency Repair Disk. If you do not have an Emergency Repair Disk, contact your technical support group.

　　根據你的訊息，應該是 driver 的問題，在執行 read 動作發生的，因為有 memory dump 的動作，可以找該檔案來找出問題所在。很有可能 DRAM 有問題，找個記憶體測試軟體測測看。

　　0x0000000A indicates a kernel-mode process attempted to access a portion of memory at an Interrupt Request Level (IRQL) that was too high. A kernel-mode process can only access other processes that have an IRQL lesser than or equal to its own.

Interpreting the Message

　　The four parameters listed in the Stop 0xA message are defined in order of appearance as follows:

1. Memory address referenced
2. IRQL
3. Type of access (0 = read operation, 1 = write operation)
4. Address that referenced memory in parameter 1

Resolving the Problem

1. Buggy device driver, system service, or BIOS. The error that generates Stop 0xA usually occurs after the installation of a buggy device driver, system service, or BIOS. To resolve it quickly, restart your computer, and press F8 at the character-mode screen that displays the prompt "For troubleshooting and advanced startup options for Windows 2000, press F8." On the resulting Windows 2000 Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time.

2. Incompatible device driver, system service, virus scanner, or backup tool. If you encounter Stop 0xA while upgrading to a newer version of Windows, it might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version. If possible, remove all third-party device drivers and system services and disable any virus scanners prior to upgrading. Contact the software manufacturers to obtain updates of these tools.

　　For additional error messages that might help pinpoint the device or driver that is causing the error, check the System Log in Event Viewer. Disabling memory caching of the BIOS might also resolve this error. You also need to run hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer.

　　If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows 2000 drivers. Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming proper termination. For enhanced integrated drive electronics (EIDE) devices, define the onboard EIDE port as Primary only. Also, check each EIDE device for the proper master/slave or stand-alone setting. Try removing all EIDE devices except for hard disks.

　　If the message appears during an installation of Windows 2000, make sure that the computer and all installed peripherals are listed on the Microsoft Windows 2000 Hardware Compatibility List (HCL). For more information about the HCL, see "Additional Resources" at the end of this chapter.

　　Microsoft periodically releases a package of product improvements and problem resolutions called a Service Pack. Because many problems are resolved by installing the latest Service Pack, it is recommended that all users install them as they become available. To check which Service Pack, if any, is installed on your system, click Start, click Run, type winver, and then press ENTER. The About Windows 2000 dialog box displays the Windows version number and the version number of the Service Pack, if one has been installed. For information about installing the latest Service Pack, see "Additional Resources" at the end of this chapter.

　　Occasionally, remedies to specific problems are developed after the release of a Service Pack. These remedies are called hotfixes. Microsoft does not recommend that you install a post–Service Pack hotfix unless the specific problem it addresses has been encountered. Service Packs include all of the hotfixes released since the release of the previous Service Pack. The status of hotfix installations is not indicated in the About Windows 2000 dialog box. For information about downloading hotfixes and Service Packs, see "Additional Resources" at the end of this chapter.

　　For more troubleshooting information about the 0xA Stop message, refer to the Microsoft Knowledge Base link, using the keywords winnt and 0x0000000A. For information about this resource, see "Additional Resources" at the end of this chapter.

**conankun** · 2002-07-09, 05:12 PM

字面上是irq有所重疊使用之意
看看將介面卡換個槽來插看看

**Schnaufer** · 2002-07-09, 05:52 PM

　　請 post 出錯誤代碼，就是 0x ...... 開頭的那一段，連後面四個參數也要。

IRQL_NOT_LESS_OR_EQUAL

Explanation:

　　This Stop message indicates that a kernel-mode process or driver attempted to access a memory address to which it did not have permission to access. The most common cause of this error is an incorrect or corrupted pointer that references an incorrect location in memory. A pointer is a variable used by a program to refer to a block of memory. If the variable has an incorrect value in it, the program tries to access memory that it should not. When this occurs in a user-mode application, it generates an access violation. When it occurs in kernel mode, it generates a STOP 0x0000000A message. If you encounter this error while upgrading to a newer version of Windows, it might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

User Action:

　　This error usually occurs after the installation of a buggy device driver, system service, or BIOS. To resolve it quickly, restart your computer, and press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows 2000 Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time. If you encounter this error while upgrading from Windows NT 4.0 or earlier, it might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version. If possible, remove all third-party device drivers and system services and disable any virus scanners prior to upgrading. Contact the software manufacturers to obtain updates of these tools. For additional error messages that might help pinpoint the device or driver that is causing the error, check the System Log in Event Viewer. Disabling memory caching of the BIOS might also resolve this error. You should also run hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owners manual for your computer. If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows 2000 drivers. Disable sync negotiation in the SCSI BIOS, check the cables and the SCSI IDs of each device, and confirm proper termination. For enhanced integrated device electronics (EIDE) devices, define the onboard EIDE port as Primary only. Also, check each EIDE device for the proper master/slave/stand-alone setting. Remove all EIDE devices except for hard disks. If the message appears during an installation of Windows 2000, make sure that the computer and all installed peripherals are listed on the Microsoft Windows 2000 Hardware Compatibility List (HCL) on http://www.microsoft.com. For more troubleshooting information about this Stop message, refer to the Microsoft Knowledge Base at http://support.microsoft.com/support.