Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: Attempted_write_to_readonly_memory bsod

22 Feb 2014   #1

Attempted_write_to_readonly_memory bsod

I had a game minimized idling (which ive done for a long time) and came back to this BSOD

This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xBE (0x80000, 0x9810000417680025, 0xFFFFF8800944B330, 0xA)

Attached is the required zip...I think I've followed protocol and hope some one can help..

Thanks in advance

My System SpecsSystem Spec
22 Feb 2014   #2

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit

Hi process.

Do two things.

Uninstall your installed latest version of the display driver.
Then clean up any possible leftover.
Then install version 13.9 WHQL only.
And, Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.
BugCheck BE, {80000, 9810000417680025, fffff8800944b330, a}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4333b )

Followup: MachineOwner
fffff880`0944b0e8  fffff880`112cc48dUnable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
fffff880`0448c000 fffff880`0452e000   atikmpag   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Sat Feb 01 00:58:51 2014 (52EBF973)
    CheckSum:         000A9D84
    ImageSize:        000A2000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
23 Feb 2014   #3


Thanks a lot for the reply Arc...

This is pretty much a fresh win ult x64 install. I have overclocked cpu/ram & cards, but with the current clock they have passed IBT and P95 stress tests. I've put the clocks back to default to see if this makes a difference, and so far so good.

I do want to run this comp clocked, so will put the overclock back on and first run the memtest86 you recommended.

I'm running a Corsair850TX power supply with: FX8350/ 2 X HD7970 / 16GB Kingston Beast @ 1.7v... could the issue be power related?

I'll also remove Daemon tools

Everytime I restart the comp I get the windows Duum-Dur...Dum-Dur sound like it's found a new USB device... maybe related

Will leave memmtest86 on tonight (with comp OCed) and get back to you tomorrow

My System SpecsSystem Spec

25 Feb 2014   #4


I changed ram timings to 11-12-11-32 from (30) for 2133mhz @ 1.7v and ran memtest86 for about 5/6 hours.... it made 7 passes with no faults and for the last day/2 I havent had any BSOD. Will consider this fixed and ram related for now.

Thanks for everything
My System SpecsSystem Spec
25 Feb 2014   #5

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit

Apparently it is a good news. Let us know for any further issue.
My System SpecsSystem Spec

 Attempted_write_to_readonly_memory bsod

Thread Tools

Similar help and support threads
Thread Forum
I had another seemingly random BSOD - ATTEMPTED_WRITE_TO_READONLY_MEMORY (be). The windbg output says that the offending driver name is saved in KiBugCheckDriver. I do not know enough about windbg to be able to find the driver name. I have made a summary of all of the 73 BSODs I have...
BSOD Help and Support
Hi i got 8 repeated BSOD and then suddenly after a restart today the computer stopped bsoding... for now. I was just wondering if anyone saw something out of the minidumps i attatched that i did not see.
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 10:09.
Twitter Facebook Google+