Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Stop error message when a Windows Server 2008-based computer randomly restarts: "0x000000BE ATTEMPTED_WRITE_TO_READONLY_MEMORY"


View products that this article applies to.

Error description

A Windows Server 2008-based server may randomly restart. When this problem occurs, you receive a Stop error message that resembles the following message:
STOP 0x000000BE (
parameter1, parameter2,
parameter3, parameter4 )

ATTEMPTED_WRITE_TO_READONLY_MEMORY
Notes
  • The parameters in this Stop error message may vary, depending on the configuration of the computer.
  • Not all 0x000000BE Stop error messages are caused by this problem.
This article helps you fix the problem.

↑ Back to the top


Cause

This problem occurs because Windows Server 2008 does not correctly synchronize memory protection changes when the system writes registry hive files.

↑ Back to the top


Workaround

To have us work around this problem for you, go to the "Fix it for me" section. If you would rather work around this problem yourself, go to the "Let me fix it myself" section.

Fix it for me

To work around this problem automatically, click the Fix this problem link. Then, click Run in the File Download dialog box, and follow the steps in this wizard.





Note this wizard may be in English only; however, the automatic fix also works for other language versions of Windows.

Note If you are not on the computer that has the problem, you can save the automatic fix to a flash drive or to a CD, and then you can run it on the computer that has the problem.

Now go to the "Did this fix the problem?" section.

Let me fix it myself

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
To work around this problem, follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Configuration Manager\
  3. In the details pane, right-click
    ProtectedStorage, and then click Modify.

    NoteIf the ProtectedStorage registry entry does not exist, you must create it. To do this, follow these steps:
    1. On the Edit menu, point to
      New, and then click DWORD Value.
    2. Type ProtectedStorage, and then press ENTER.
  4. In the Base box, click
    Decimal, type 0 in the Value data box, and then click OK.
  5. Exit Registry Editor.
  6. Restart the computer.

Did this fix the problem?

If this problem does not occur again, you are finished with this article. If this problem occurs again, you can contact support.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


Keywords: kbmsifixme, kbfixme, kbexpertiseadvanced, kbtshoot, kbprb, kb

↑ Back to the top

Article Info
Article ID : 959056
Revision : 1
Created on : 1/7/2017
Published on : 10/9/2011
Exists online : False
Views : 195