System Crash (STOP error) 0xBE, Attempted to Write to Read-only Memory (Identifying Registry Interceptor Crashes)

Follow

Summary

This Knowledgebase article provides information about System Crash (STOP error) 0xBE, Attempted to Write to Read-only Memory (Identifying Registry Interceptor Crashes).


More Information

See Knowledgebase article #147 - 'How to Retrieve the Neverfail Heartbeat Logs and Other Useful Information for Support Purposes' and Knowledgebase article #148 - 'System Crash (STOP error), General Advice for Support Partners, Including Steps Towards Initial Diagnosis' for general information relating to STOP errors.

Stop Code (or Bugcheck) 0xBE (ATTEMPTED_WRITE_TO_READONLY_MEMORY) is caused by a driver attempting to write to read-only memory. Usually, the driver in question will be named in the error message. This is a known issue if the crash has the following footprint:

  • the system is Windows 2003.
  • either the system has less than 256MB of memory or the /3GB boot time switch is enabled (see BOOT.INI).
  • the driver mentioned in the error message is HookRegistryDriver.sys.

Heartbeat can support the 3GB switch option in Boot.ini under certain circumstances. Please see Knowledgebase article #112 - 'Neverfail Heartbeat V4.3.3 onwards support /3GB switch with Windows 2003 SP1' for further information.
Heartbeat does not support memory configurations of less than 256MB.

In all other cases, please provide the full error information as described in Knowledgebase article #146 - ' How to Retrieve the Neverfail Heartbeat Logs and Other Useful Information for Support Purposes' and Knowledgebase article #148 - 'System Crash (STOP error), General Advice for Support Partners, Including Steps Towards Initial Diagnosis to Neverfail Support.


Applies To

All Versions


Related Information

None

KBID-150

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.