- The computer automatically restarts.
- After you log on, you receive the following error message: Microsoft WindowsIf the error message still appears and if you want to see the data that the error report contains, click the Click here link at the bottom of the message box. You then see error-signature information that is similar to the following:
The system has recovered from a serious error.
A log of this error has been created.
Please tell Microsoft about this problem.
We have created an error report that you can send to help us improve Microsoft Windows. We will treat this report as confidential and anonymous.
To see what data this error report contains, click here.BCCode : 0000000A BCP1 : 0f6ff8c0 BCP2 : 000000ff BCP3 : 00000000 BCP4 : 8074867e OSVer : 5_2_3718 SP : 0_0 Product : 272_3
- You receive the following "Stop" error message on a blue screen: A problem has been detected and Windows has been shut down to prevent damage to your computer.
*** STOP: 0x0000000A (0x0f6ff8c0, 0x000000ff, 0x00000000, 0x8074867e)
- An error message that is similar to the following is logged in the System event log: Date: date
Event ID: 1003
Description: Error code 0000000A, parameter1 0f6ff8c0, parameter2 000000ff, parameter3 00000000, parameter4 8074867e.For more information, see Help and Support Center at http://support.microsoft.com.Data:0000: 53 79 73 74 65 6d 20 45 System E0008: 72 72 6f 72 20 20 45 72 rror Er0010: 72 6f 72 20 63 6f 64 65 ror code0018: 20 30 30 30 30 30 30 35 00000 0A0020: 30 20 20 50 61 72 61 6d 0 Param0028: 65 74 65 72 73 20 66 66 eters ff0030: 66 66 66 66 64 31 2c
- The symptoms of a "Stop" error vary according to the computer's system failure options. For more information, click the following article number to view the article in the Microsoft Knowledge Base:307973 How to configure system failure and recovery options in Windows
- The four parameters that are included in the error signature information vary according to the computer's configuration.
- Not all "Stop 0x0000000A" errors are caused by the problem that this article describes.
Instruction bytes are read into the instruction cache in fixed-size blocks (cache lines). When the bytes that make up an instruction cross a cache line boundary, the instruction bytes occupy multiple adjacent cache lines. If a certain specific processor error occurs, the processor may read in the second part of the instruction from the wrong cache line for execution. This behavior causes an incorrect instruction.
The Ntkrnlmp.exe file that is included in hotfix 840987 includes a sequence of instructions that reveal this bug.
Note This problem occurs only when the processor is handling an interprocessor interrupt (IPI) that causes the processor to resume from the C1 idle state.
To work around this problem, prevent the processor from entering the C1 idle state. To do this, follow these steps:
- Start Registry Editor. To do this, click Start, click Run, type regedt32, and then click
- Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\System\CurrentControlset\Control\Session Manager\Power
- Click Edit, point to New, click DWORD Value, and then type
- Right-click IdleFrom0IdlePercent, and then click
Modify. In the Edit DWORD Value dialog box, type a number that is more than 100 in the Value data box, click Decimal under Base, and then click
- HKEY_LOCAL_MACHINE\System\CurrentControlset\Control\Session Manager\Power\IdleFrom0Delay
- HKEY_LOCAL_MACHINE\System\CurrentControlset\Control\Session Manager\Power\IdleFrom0IdlePercent