Windows 10: Error ATTEMPTED_WRITE_TO_READONLY_MEMORY and crashs

Hello I have many problems with the error code Error ATTEMPTED_WRITE_TO_READONLY_MEMORY. For example, none of my games that require power can run. Also, I can't reset windows or try to boot into safe mode: my pc crashes and displays the error code.I have already done the updates, checked my drivers and all the basic advice on the internet, but still no solution. Can you help me?

:)

 

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.

 

all games crash!

I suggest you run rthdribl > http://www.daionet.gr.jp/~masa/archives/rthdribl_1_2.zip
Increase the window size step by step and watch your vga temps permanently.
What happens?
If it crashes, run at stock speeds as suggested before and retry.

P.S.: When your system locks, does the display signal turn off after a time?
Stuttering sound or no sound at all when freezing?
What X1800XT model do you own exactly?

 

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 )