Windows 10: Attempted_write_to_readonly_memory

Hi,since today morning I'm having problem with my PC and since I'm not a computer expert, I don't know what to do with this.Yesterday my PC was working without the smallest problems, but today it is totaly useless as it keeps crashing programs/games and other times giving me the infamous blue screen with text ''Attempted_write_to_readonly_memory'' instead. As I said, it started happening on todays morning without any possible reason that is known to me. Thank you for your help in advance. Procesor IntelR CoreTM i5-3570 CPU @ 3.40GHz 3.40 GHz RAM 16,0 GB ID 50D29B3B-D9E7-4F01-94A5-140C7BB

:)

 

ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen

Hi Eve,

For us to further isolate your concern with the error message appearing on your screen and blue screen errors, kindly ensure to follow the helpful articles below and perform the methods:

• Troubleshooting the Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
• Hotfix
• Troubleshoot Blue Screen

If you need further assistance, please let us know.

 

BSOD - ATTEMPTED_WRITE_TO_READONLY_MEMORY - Windows 10 Pro 64bit...


hi axe0 & Arc,

I have a small request, I attached the log files from a BugCheck I got today while browsing on the internet.
I was testing a new bios setting as suggested by Asus, regarding my poroblem with using XMP.

can you have a short look at it and confirm it is the same "ATTEMPTED_WRITE_TO_READONLY_MEMORY" I originally started this thread with?
or is it something kompletely different?

that would really helpful for me.

 

AMD driver Attempted_Write_to_ReadOnly_Memory

I've been getting this error whenever I wake the computer from sleep mode. When I had hybrid sleep on it would automatically restart the computer when waking from sleep. When I disabled hybrid sleep it just displays the error on waking up and I have to manually
restart. I've run driver verifier and it has flagged the AMD drivers. I've updated to the latest beta driver and the problem persists. I've run clean boot but this hasn't fixed the issue either.

Here are the details:

• ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
  
  An attempt was made to write to readonly memory. The guilty driver is on the
  
  stack trace (and is typically the current instruction pointer).
  
  When possible, the guilty driver's name (Unicode string) is printed on
  
  the bugcheck screen and saved in KiBugCheckDriver.
  
  Arguments:
  
  Arg1: ffffd00000002178, Virtual address for the attempted write.
  
  Arg2: 8000000000800121, PTE contents.
  
  Arg3: ffffd00021206500, (reserved)
  
  Arg4: 000000000000000b, (reserved)

• BugCheck BE, {ffffd00000002178, 8000000000800121, ffffd00021206500, b}
  
  Probably caused by : netbt.sys ( netbt!NbtQueryWinsSettings+4e )