Skip to content
PCDecoder
0x000000BEATTEMPTED_WRITE_TO_READONLY_MEMORYStop codeWidely reported

ATTEMPTED_WRITE_TO_READONLY_MEMORY (0xBE): what it means and how to fix it

Updated Oct 10, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

Windows triggered stop code 0x000000BE because a driver tried to alter a protected section of memory designated as read-only. A buggy, outdated, or corrupted device driver is almost always responsible. Identifying the specific driver file shown on screen and updating or rolling it back is the primary fix.

What it means

Windows assigns specific access permissions to different regions of memory to keep the operating system stable and secure. Certain memory ranges containing critical operating system code, essential tables, and protected configurations are marked strictly as read-only. Stop code 0x000000BE, formally designated as ATTEMPTED_WRITE_TO_READONLY_MEMORY, occurs when a driver attempts to write data into one of these protected memory addresses.

Why Windows Halts

When a driver instructs the processor to write to a read-only memory address, the hardware triggers a fault. Windows halts the entire system immediately with a blue screen instead of letting the write operation execute. Allowing an unauthorized write to a read-only memory segment could corrupt essential kernel data, destabilize system security, or cause silent data loss.

Locating the Faulting Driver

When bug check 0x000000BE occurs, Windows collects crash parameters. Parameter 1 records the virtual memory address of the attempted write. Parameter 2 records the Page Table Entry (PTE) contents, while parameters 3 and 4 are reserved by the system.

If Windows can identify which driver initiated the illegal write, it prints the driver file name directly on the blue screen display and stores it in memory at the KiBugCheckDriver location. The driver typically ends with a .sys extension. When no driver name is visible on the crash screen, the crash dump file can be inspected using debugging tools with the !analyze command to pinpoint the exact module that caused the failure. Because the error is triggered by code attempting an illegal memory operation, the problem almost always points to software driver logic rather than damaged physical RAM.

Common causes

  • A hardware driver attempted to write data to a protected read-only memory segment.
  • A recently installed driver contains a programming bug.
  • Corrupted driver files related to storage controllers, chipset devices, or graphics adapters.

How to fix it

Safest and most likely fixes first. Readers' answers to "Did this fix it?" reorder this list over time.

  1. Identify and update the faulting driver

    Use this first if a specific driver file ending in .sys was named on the blue screen.

    1. Take note of the file name ending in .sys displayed on the blue screen.
    2. Right-click the Start button and select Device Manager.
    3. Locate the hardware device associated with that driver, such as your storage controller or network adapter.
    4. Right-click the device and select Update driver.
    5. Choose Search automatically for drivers, or download the latest package directly from the hardware manufacturer's support site and install it.
    6. Restart the computer to apply the changes.
    Did this fix it?

  2. Roll back a recently updated driver

    Use this if the crash started happening shortly after updating a driver or hardware component.

    1. Right-click the Start button and select Device Manager.
    2. Find the device you recently updated and double-click it to open its properties.
    3. Select the Driver tab.
    4. Click the Roll Back Driver button.
    5. Select a reason when prompted, confirm the rollback, and restart your computer.
    Did this fix it?

  3. Boot into Safe Mode to remove unstable drivers

    Use this if Windows crashes during boot and you cannot access the desktop normally.

    1. Hold the Shift key while clicking Restart on the Windows sign-in screen.
    2. Select Troubleshoot, then Advanced options, then Startup Settings.
    3. Click Restart, then press 4 or F4 to start Windows in Safe Mode.
    4. Open Device Manager and locate the device driver that triggered the crash.
    5. Right-click the device and select Uninstall device, then check the box to attempt driver removal if prompted.
    6. Restart the PC normally.
    Did this fix it?

Is it just you?

25+ Microsoft Q&A threads discuss this. Most recent activity:

Checked Oct 9, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

What does ATTEMPTED_WRITE_TO_READONLY_MEMORY mean?

It means a software driver tried to modify a memory segment that Windows marked as read-only. Windows forces a crash to stop unauthorized modifications and protect system integrity.

How do I find out which driver caused error 0xBE?

Windows often prints the driver name directly on the blue screen. If it does not appear, opening the minidump file with a debugger and running the !analyze command identifies the offending driver module.

Does stop code 0x000000BE mean my RAM is broken?

Usually no. This specific bug check indicates that driver software executed an invalid write command against protected memory, making a faulty driver far more likely than defective physical RAM.

More stop codes decoded