Windows 10: Attempted to write to read only memory - BEdaisy.sys BSOD crash

Discus and support Attempted to write to read only memory - BEdaisy.sys BSOD crash in Windows 10 Software and Apps to solve the problem; Received this messaged while playing Warthunder on windows 11.Since there is no way to reinstall battle eye which i read causes this error i'm not sure... Discussion in 'Windows 10 Software and Apps' started by Winters Sin, Apr 1, 2025.

  1. WINTERS SIN
    Winters Sin Win User

    Attempted to write to read only memory - BEdaisy.sys BSOD crash


    Received this messaged while playing Warthunder on windows 11.Since there is no way to reinstall battle eye which i read causes this error i'm not sure how to go about fixing this.

    :)
     
    Winters Sin, Apr 1, 2025
    #1
  2. ALUMEL01
    ALUMEL01 Win User

    BSOD - Attemped Write Readonly Memory xusb22.sys

    Recently got a BSOD with the error "Attempted Write Readonly Memory" and it mentioned xusb22.sys as a problem.

    Here is the DMP file from the BSOD:

    Microsoft OneDrive
     
    ALUMEL01, Apr 1, 2025
    #2
  3. STAVROS ANDST
    Stavros Andst Win User
    BSOD : Attempted write to readonly memory

    Unfortunatelly, even if i deleted the problematic drivers (i can not find them anymore at verifier), i got a bsod again with attempted write to readonly memory.

    Any more suggestion?
     
    Stavros Andst, Apr 1, 2025
    #3
  4. KINGDANGO
    kingdango Win User

    Attempted to write to read only memory - BEdaisy.sys BSOD crash

    BSoD During Windows 10 Factory USB install, attempted write to read only memory (WimFsf.sys)

    I purchased a Windows 10 Home Edition OEM USB Installation kit (factory USB-based install). During the "Enter your license key" step of the install a blue screen of death (BSoD) is displayed and a page access fault is described as the culprit.

    Attempted write to read only memory (WimFsf.sys)

    This is a brand new build with top-end hardware (ASUS board, i7 GPU, ASUS GPU, Crucial memory, Samsung SSD). I have tried numerous bios tweaks, swapped the SSD, removed one of the sticks of RAM (thinking it might be RAM related) all to no avail.
     
    kingdango, Apr 1, 2025
    #4
Thema:

Attempted to write to read only memory - BEdaisy.sys BSOD crash

Loading...

  1. Attempted to write to read only memory - BEdaisy.sys BSOD crash - Similar Threads - Attempted write read

  2. Attempted to write to read only memory - BEdaisy.sys BSOD crash

    in Windows 10 Gaming
    Attempted to write to read only memory - BEdaisy.sys BSOD crash: Received this messaged while playing Warthunder on windows 11.Since there is no way to reinstall battle eye which i read causes this error i'm not sure how to go about fixing this....

  3. BSOD Attempted to Write to Read-Only Memory bugcheck 0x0000000be

    in Windows 10 Gaming
    BSOD Attempted to Write to Read-Only Memory bugcheck 0x0000000be: I got BSOD after playing Space Marines 2, I hope someone will help me to identify the problem or the faulty.I got this message in Event Viewer:The computer has rebooted from a bugcheck. The bugcheck was: 0x000000be 0xffff91fec5c15000, 0x8a00000000100121, 0xffffa0096377a140,...

  4. BSOD Attempted to Write to Read-Only Memory bugcheck 0x0000000be

    in Windows 10 Software and Apps
    BSOD Attempted to Write to Read-Only Memory bugcheck 0x0000000be: I got BSOD after playing Space Marines 2, I hope someone will help me to identify the problem or the faulty.I got this message in Event Viewer:The computer has rebooted from a bugcheck. The bugcheck was: 0x000000be 0xffff91fec5c15000, 0x8a00000000100121, 0xffffa0096377a140,...

  5. BSOD Attempted to Write to Read-Only Memory bugcheck 0x0000000be

    in Windows 10 BSOD Crashes and Debugging
    BSOD Attempted to Write to Read-Only Memory bugcheck 0x0000000be: I got BSOD after playing Space Marines 2, I hope someone will help me to identify the problem or the faulty.I got this message in Event Viewer:The computer has rebooted from a bugcheck. The bugcheck was: 0x000000be 0xffff91fec5c15000, 0x8a00000000100121, 0xffffa0096377a140,...

  6. BSOD error 0x000000BE attempted to write to read only memory

    in Windows 10 Gaming
    BSOD error 0x000000BE attempted to write to read only memory: From event viewer:The computer has rebooted from a bugcheck. The bugcheck was: 0x000000be 0xffff9c0303eb69c8, 0x8a00000004500121, 0xffffa485c657f9d0, 0x000000000000000a. A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 759f6185-c59a-4fd1-ab37-1d404705582c.Edition:...

  7. BSOD error 0x000000BE attempted to write to read only memory

    in Windows 10 Software and Apps
    BSOD error 0x000000BE attempted to write to read only memory: From event viewer:The computer has rebooted from a bugcheck. The bugcheck was: 0x000000be 0xffff9c0303eb69c8, 0x8a00000004500121, 0xffffa485c657f9d0, 0x000000000000000a. A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 759f6185-c59a-4fd1-ab37-1d404705582c.Edition:...

  8. BSOD error 0x000000BE attempted to write to read only memory

    in Windows 10 BSOD Crashes and Debugging
    BSOD error 0x000000BE attempted to write to read only memory: From event viewer:The computer has rebooted from a bugcheck. The bugcheck was: 0x000000be 0xffff9c0303eb69c8, 0x8a00000004500121, 0xffffa485c657f9d0, 0x000000000000000a. A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 759f6185-c59a-4fd1-ab37-1d404705582c.Edition:...

  9. "Attempted to write to read only memory" BSOD

    in Windows 10 BSOD Crashes and Debugging
    "Attempted to write to read only memory" BSOD: I have been getting this bsod once or twice per month for the past 5 months and I don't know what's the problem. Here is the dump file: https://1drv.ms/u/s!AplVCE-1Tov_3ymzsBUX3sFROVPm?e=vRjUBV...

  10. BSOD - Attempted write to read-only memory.

    in Windows 10 BSOD Crashes and Debugging
    BSOD - Attempted write to read-only memory.: Hello, I am troubleshooting a BSOD that has happened twice now, randomly, in the past week or so. Apparently it is a faulty driver, from what I've researched. The minidump files are located here. Please advise on what driver is causing this issue or next steps....