Attempted_write_to_readonly_memory bsod


  1. Posts : 3
    64
       #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)
    Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY

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

    Thanks in advance
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    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.
    ___________________________________________
    Code:
    BugCheck BE, {80000, 9810000417680025, fffff8800944b330, a}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4333b )
    
    Followup: MachineOwner
    ---------
    Code:
    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
     atikmdag+0x8148d
    Code:
    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 Computer


  3. Posts : 3
    64
    Thread Starter
       #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

    Thanks
      My Computer


  4. Posts : 3
    64
    Thread Starter
       #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 Computer


  5. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #5

    Apparently it is a good news. Let us know for any further issue.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About 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 11:29.
Find Us