Your one minidump file just indicated generic errors, nothing specific as the cause of that crash.
Did your system only crash once, or if this is an on-going problem, do you have any more minidump files available that you can upload for analysis.
ATTEMPTED_WRITE_TO_READONLY_MEMORY BSOD, looking for troubleshooting
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 96%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMZ%3C/text%3E%3C/svg%3E)
Mike Zacowski
0
Reputation points
Hi, yesterday after closing Lost Ark i've got aforementioned BSOD and I'm worried, because every time I've got any of those, something was about to break in my PC. Also, that's the first time I'm seeing this bugcheck.
CPU: Ryzen 5 5600
GPU: Sapphire RX 6600, ADRN 25.8.1 (it's not the latest, i know, but on the latest version there's a problem with driver/system crashes while using HDMI)
PSU: SilentiumPC Vero L3 500W 80+ Bronze
MOBO: Gigabyte AB350M-DS3H V2
RAM: Lexar 32GB (2x16GB) 3200MHz CL16 Thor (XMP disabled)
I know, not the newest parts, but RAM was bought 6 months ago, same as GPU and CPU, I have latest BIOS.
https://www.mediafire.com/file/u3i07ysu991mai3/121925-8656-01.dmp/file
| Dump File | Crash Time | Bug Check String | Bug Check Code | Parameter 1 | Parameter 2 | Parameter 3 | Parameter 4 | Caused By Driver | Caused By Address | File Description | Product Name | Company | File Version | Processor | Crash Address | Stack Address 1 | Stack Address 2 | Stack Address 3 | Computer Name | Full Path | Processors Count | Major Version | Minor Version | Dump File Size | Dump File Time |
| 121925-8656-01.dmp | 19.12.2025 22:28:59 | ATTEMPTED_WRITE_TO_READONLY_MEMORY | 0x000000be | ffffa7fb3bc0d00|8a00000000200121 |
fffff38817857140|000000000000000b |
ntoskrnl.exe | ntoskrnl.exe+3fd5c0 | x64 | ntoskrnl.exe+3fd5c0 | C:\WINDOWS\Minidumps\121925-8656-01.dmp | 12 | 15 | 19041 | 1 406 561 | 19.12.2025 22:29:32 |
Windows for home | Windows 10 | Performance and system failures
2 answers
Sort by: Most helpful
-
DaveM121 884.2K Reputation points Independent Advisor2025-12-20T11:37:57.6966667+00:00 -
Mike Zacowski 0 Reputation points
2025-12-20T13:19:52.0933333+00:00 unfortunately, that was one time only and I have only this one minidump, but I decided to reach here due to my history with my PC (BSODs always were just a beginning).
so, was it just random crash due to system having a stroke or it indicates something else?
-
DaveM121 884.2K Reputation points Independent Advisor
2025-12-20T13:27:25.5066667+00:00 There is no indication in the minidump file data of any problems with Windows or with your hardware, Windows may have been updating drivers in the background and that caused a temporary conflict, and there is nothing further you need to do, if your system does crash again, please upload any new minidump file you may get for analysis.
Sign in to comment -
-
AI answer
2025-12-20T11:03:26.9766667+00:00 The bug check code 0x000000BE (ATTEMPTED_WRITE_TO_READONLY_MEMORY) indicates that a driver or application attempted to write to a memory segment that is marked as read-only. This can occur due to various reasons, including driver issues, hardware malfunctions, or system file corruption.
Here are some troubleshooting steps you can follow to address this issue:
- Update Drivers: Ensure that all your drivers, especially the graphics driver, are up to date. Since you mentioned issues with the latest version, consider reverting to a stable version that does not cause crashes.
- Check for Hardware Issues: Run hardware diagnostics to check for any faulty components. This includes checking RAM and other hardware connections.
- System File Checker: Use the System File Checker tool to repair any missing or corrupted system files. You can do this by running the command
SFC /scannowin an elevated Command Prompt. - Check for Windows Updates: Ensure that your Windows operating system is fully updated, as updates can fix bugs and improve stability.
- Safe Mode: Boot into Safe Mode to see if the issue persists. This can help determine if the problem is caused by third-party software or drivers.
- Event Viewer: Check the Event Viewer for any critical errors or warnings that occurred around the time of the crash. This can provide more insight into what might be causing the issue.
- Memory Diagnostics: Use the Windows Memory Diagnostics tool to check for memory issues. You can find this in the Control Panel under Memory.
- Revert Recent Changes: If you have made any recent changes to your system, such as installing new hardware or software, consider reverting those changes to see if it resolves the issue.
If the problem persists after trying these steps, you may want to consider seeking professional assistance or further analyzing the crash dump file for more specific insights.
References:
AI-generated content may be incorrect. Read our transparency notes for more information.