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

Discus and support BSOD - ATTEMPTED_WRITE_TO_READONLY_MEMORY - Windows 10 Pro 64bit... in Windows 10 BSOD Crashes and Debugging to solve the problem; SFC finds nothig to complain about. I already ran it today and it was able to repair the corruption. but why does this corruption happen so frequently... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by sahafiec, Feb 11, 2016.

Page 4 of 7
  1. SAHAFIEC
    sahafiec Win User

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


    SFC finds nothig to complain about. I already ran it today and it was able to repair the corruption.
    but why does this corruption happen so frequently and does it have something to do with the BSOD?!
     
    sahafiec, Feb 19, 2016
    #46
  2. AXE0
    axe0 New Member

    Do you upload the CBS.log when the 2nd SFC is finished?
    If you do, then I certainly can't find the fixed corruption because the results of the fixed corruption are overwritten with the new results.
     
    axe0, Feb 19, 2016
    #47
  3. SAHAFIEC
    sahafiec Win User
    no, after the first one which repaired the corruption.
    I thought the log doesn't overwrite but append new entries instead?! *sarc
    there are even entries from yesterday in the cbs.log and I see 2 "Initializing Trusted Installer" entries from today.
     
    sahafiec, Feb 19, 2016
    #48
  4. AXE0
    axe0 New Member

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

    That I understand are some of the SFC results volatile what means they are present for a short period, so basically it indeed doesn't overwrite them but the results are gone after some time and with a fresh SFC the new results are added instead.
    I'm not 100% certain if this is correct, although I have read this at several (trusted) sites.
     
    axe0, Feb 19, 2016
    #49
  5. SAHAFIEC
    sahafiec Win User
    I understand, so what would be the best way to get those corruptions included in the CBS.log?
     
    sahafiec, Feb 19, 2016
    #50
  6. AXE0
    axe0 New Member
    Try a few things first
    Code: DISM /Online /Cleanup-Image /AnalyzeComponentStore[/quote] If this commands says you can cleanup than copy/paste following command
    Code: DISM /Online /Cleanup-Image /StartComponentCleanup[/quote]
     
    axe0, Feb 19, 2016
    #51
  7. SAHAFIEC
    sahafiec Win User
    "Component Store Cleanup Recommended: No"
     
    sahafiec, Feb 19, 2016
    #52
  8. AXE0
    axe0 New Member

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

    Please try a cold boot again and run SFC, see if that gives repaired corruption.
     
    axe0, Feb 19, 2016
    #53
  9. SAHAFIEC
    sahafiec Win User
    Ran sfc and had no corruption. Then performed a cold boot and ran sfc again. Result was no corruption.
     
    sahafiec, Feb 20, 2016
    #54
  10. SAHAFIEC
    sahafiec Win User
    I found something worth mentioning regarding the file corruption. after the test in my previous post I did another one.
    this time I cleaned the system from temporary and unused files prior shutting down. I like to have a slim system without any mess in it and I use mostly CCleaner and Wise Care 365. I deleted all files both applications found and also cleaned the registry then shut the system down.

    this morning after cold boot I ran "sfc /scannow" and got a surprise: there was a file corruption again. it could be repaired as always it seems to be caused by the applications I use for cleaning and slimming the system. I have a screenshot from sfc as well as a CBS.log after the first sfc which found the corruption.

    what' your opinion?
    could this be related to the BSOD or maybe even cause it?
     
    sahafiec, Feb 20, 2016
    #55
  11. AXE0
    axe0 New Member
    I have been able to find the files, they are all in the C:\Windows\Help directory.

    Please do NOT 'clean' the registry with any program, if there is a bug somewhere you're the one that is having a problem.
    Please do NOT use Wise Care 365, the reason is that this program has caused quite some problems.
    Code: 2016-02-21 08:52:44, Info CSI 000013ea [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:13]"artnoloc.mshi" from store 2016-02-21 08:52:44, Info CSI 000013eb [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:13]"artnoloc.mshc" from store 2016-02-21 08:52:44, Info CSI 0000141a [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:8]"art.mshc" from store 2016-02-21 08:52:44, Info CSI 0000141b [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:8]"art.mshi" from store 2016-02-21 08:52:45, Info CSI 00001460 [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:10]"noarm.mshc" from store 2016-02-21 08:52:45, Info CSI 00001461 [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:10]"noarm.mshi" from store 2016-02-21 08:52:45, Info CSI 00001469 [SR] Repairing corrupted file [l:25 ml:26]"\??\C:\WINDOWS\Help\tr-TR"\[l:11]"credits.rtf" from store 2016-02-21 08:52:45, Info CSI 00001472 [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:18]"windowsclient.mshc" from store 2016-02-21 08:52:45, Info CSI 00001473 [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:18]"windowsclient.mshi" from store 2016-02-21 08:52:45, Info CSI 00001475 [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:17]"clientserver.mshi" from store 2016-02-21 08:52:45, Info CSI 00001476 [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:17]"clientserver.mshc" from store 2016-02-21 08:52:46, Info CSI 00001494 [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:14]"resources.mshc" from store 2016-02-21 08:52:46, Info CSI 00001495 [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:14]"resources.mshi" from store 2016-02-21 08:53:06, Info CSI 00001955 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:11]"cliconf.chm" from store 2016-02-21 08:53:06, Info CSI 00001956 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:12]"odbcinst.chm" from store 2016-02-21 08:53:06, Info CSI 00001957 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:12]"sqlsodbc.chm" from store 2016-02-21 08:53:06, Info CSI 00001958 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:12]"sqlsoldb.chm" from store 2016-02-21 08:53:06, Info CSI 00001959 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:10]"msdasc.chm" from store 2016-02-21 08:54:40, Info CSI 000032cc [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:7]"mmc.CHM" from store 2016-02-21 08:55:15, Info CSI 00003c9b [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:11]"odbcjet.chm" from store 2016-02-21 08:55:15, Info CSI 00003c9c [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:12]"msorcl32.chm" from store 2016-02-21 08:56:30, Info CSI 000050a7 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:11]"odbcjet.chm" from store 2016-02-21 08:56:30, Info CSI 000050a8 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:12]"msorcl32.chm" from store 2016-02-21 08:56:30, Info CSI 000050aa [SR] Repairing corrupted file [l:25 ml:26]"\??\C:\WINDOWS\Help\tr-TR"\[l:11]"credits.rtf" from store 2016-02-21 08:56:30, Info CSI 000050ac [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:18]"windowsclient.mshc" from store 2016-02-21 08:56:30, Info CSI 000050ad [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:18]"windowsclient.mshi" from store 2016-02-21 08:56:30, Info CSI 000050af [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:17]"clientserver.mshi" from store 2016-02-21 08:56:30, Info CSI 000050b0 [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:17]"clientserver.mshc" from store 2016-02-21 08:56:30, Info CSI 000050b2 [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:14]"resources.mshc" from store 2016-02-21 08:56:30, Info CSI 000050b3 [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:14]"resources.mshi" from store 2016-02-21 08:56:30, Info CSI 000050b5 [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:13]"artnoloc.mshi" from store 2016-02-21 08:56:30, Info CSI 000050b6 [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:13]"artnoloc.mshc" from store 2016-02-21 08:56:30, Info CSI 000050b8 [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:10]"noarm.mshc" from store 2016-02-21 08:56:30, Info CSI 000050b9 [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:10]"noarm.mshi" from store 2016-02-21 08:56:30, Info CSI 000050bb [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:8]"art.mshc" from store 2016-02-21 08:56:30, Info CSI 000050bc [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:8]"art.mshi" from store 2016-02-21 08:56:30, Info CSI 000050be [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:7]"mmc.CHM" from store 2016-02-21 08:56:30, Info CSI 000050c0 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:11]"cliconf.chm" from store 2016-02-21 08:56:30, Info CSI 000050c1 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:12]"odbcinst.chm" from store 2016-02-21 08:56:30, Info CSI 000050c2 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:12]"sqlsodbc.chm" from store 2016-02-21 08:56:30, Info CSI 000050c3 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:12]"sqlsoldb.chm" from store 2016-02-21 08:56:30, Info CSI 000050c4 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:10]"msdasc.chm" from store[/quote]
     
    axe0, Feb 20, 2016
    #56
  12. SAHAFIEC
    sahafiec Win User
    thanks for the warning, I've been using CCleaner for years now whitout any issues.
    I started using Wise Care 365 a couple of months a go but I'm deleting it right now.
    I'II stop cleaning the registry even with CCleaner immediately.

    could there be any relation to the BSOD issue?
     
    sahafiec, Feb 20, 2016
    #57
  13. AXE0
    axe0 New Member

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

    Depending on what has actually been removed there could.
     
    axe0, Feb 20, 2016
    #58
  14. SAHAFIEC
    sahafiec Win User
    ok, I'll keep an eye on what happens from now on without touching the registry.

    any other suggestion what to try except waiting for a casual BSOD with the current settings?
     
    sahafiec, Feb 20, 2016
    #59
  15. SAHAFIEC
    sahafiec Win User
    after so many days without BSOD or other issues I decided to make a clean Windows 10 install.
    after doing so, everything went smooth, suddenly I got a BSOD while updating my Origin games.
    the BSOD is of the kind "Memory_Management" with "ntoskrnl.exe" as a cause.

    I don't understand that, the only difference was my ram was on XPM.
    could this be the simple cause for all that axe0? *sarc
     
    sahafiec, Feb 24, 2016
    #60
Page 4 of 7
Thema:

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

Loading...

  1. BSOD - ATTEMPTED_WRITE_TO_READONLY_MEMORY - Windows 10 Pro 64bit... - Similar Threads - BSOD ATTEMPTED_WRITE_TO_READONLY_MEMORY Pro

  2. BSOD - ATTEMPTED_WRITE_TO_READONLY_MEMORY

    in Windows 10 Software and Apps
    BSOD - ATTEMPTED_WRITE_TO_READONLY_MEMORY: Hi, I've had this reoccuring BSOD ATTEMPTED_WRITE_TO_READONLY_MEMORY for a while. It doesnt occur often, and seems to be random. I have attempted multiple fixes, all of which haven't worked. I have:Updated all my drivers. Ran Windows Memory Diagnosic Tool, which found...

  3. BSOD ATTEMPTED_WRITE_TO_READONLY_MEMORY

    in Windows 10 Software and Apps
    BSOD ATTEMPTED_WRITE_TO_READONLY_MEMORY: Hey, guys. Help me solve the problem. I am getting an error and blue screen. I have a memory dump. Here is the basic information from the dump:************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit...

  4. BSOD ATTEMPTED_WRITE_TO_READONLY_MEMORY

    in Windows 10 BSOD Crashes and Debugging
    BSOD ATTEMPTED_WRITE_TO_READONLY_MEMORY: Hey, guys. Help me solve the problem. I am getting an error and blue screen. I have a memory dump. Here is the basic information from the dump:************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit...

  5. ATTEMPTED_WRITE_TO_READONLY_MEMORY be BSOD

    in Windows 10 Gaming
    ATTEMPTED_WRITE_TO_READONLY_MEMORY be BSOD: Recently cloned my windows installation SSD to a new SSD using clonezilla.Seems to be working fine but under load I will get a BSOD: Unexpected_Store_Exception, Kernal_Data_Inpage_Error, Critical_Process_Died.Any help would be appreciated!Attached is the memorydump from...

  6. BSoD ATTEMPTED_WRITE_TO_READONLY_MEMORY

    in Windows 10 Gaming
    BSoD ATTEMPTED_WRITE_TO_READONLY_MEMORY: I get a BSoD many times! They are all happened while I was using Edge Browser. One time is while I was hovering the cursor over things on an AliExpress items, I spent time on that AliE page long before the problem occured.My system is Lenovo Legion 5 82B1CPU: Ryzen 7...

  7. BSOD: ATTEMPTED_WRITE_TO_READONLY_MEMORY be

    in Windows 10 BSOD Crashes and Debugging
    BSOD: ATTEMPTED_WRITE_TO_READONLY_MEMORY be: Hello. Been having a number of different types of BSODs on my computer. The recent one, and one that i've had before is: ATTEMPTED_WRITE_TO_READONLY_MEMORY According to WinDBG: ATTEMPTED_WRITE_TO_READONLY_MEMORY be An attempt was made to write to readonly memory. The...

  8. BSOD Windows 10 Pro 64bit

    in Windows 10 Drivers and Hardware
    BSOD Windows 10 Pro 64bit: Hello I have just built a new PC with the following specs and it gives me BSOD every 5 mins or so. How can I locate the minidump files to share them with you? I have the following specs CPU: Ryzen 7 2700 RAM: Corsair 3200Mhz XMP enabled MB: Gigabyte B450 Aorus Elite...

  9. Windows 10: ATTEMPTED_WRITE_TO_READONLY_MEMORY then INVALID_PROCESS_ATTEMPT_ATTACH BSOD...

    in Windows 10 Drivers and Hardware
    Windows 10: ATTEMPTED_WRITE_TO_READONLY_MEMORY then INVALID_PROCESS_ATTEMPT_ATTACH BSOD...: This is kind of a weird one, I never seen anything like this before. After attempting to format a USB drive, I get this stop error: ATTEMPT_WRITE_TO_READONLY_MEMORY, after a restart, attempting enter the 4 digit pin on the logon screen, I get this error:...

  10. Bsod attempted_write_to_readonly_memory

    in Windows 10 BSOD Crashes and Debugging
    Bsod attempted_write_to_readonly_memory: Yesterday my computer started randomly showing the BSOD 0x000000be ATTEMPTED_WRITE_TO_READONLY_MEMORY. At the time I wasn't doing anything on the PC, but I do have programs such as Plex media sever and steam running in the background always. The description of the error said...
  1. UWUSEKKI
    Thread

    Encountering frequent BSODs during use, error code: ATTEMPTED_WRITE_TO_READONLY_MEMORY,...

    Can anyone help me identify what the issue is? Thanks in advance. minidump: https://1drv.ms/u/s!AllzkVx-4QHOkkBq17sYo3u9nZcG?e=MtypBF...
    Thread by: uwuSekki, Jan 18, 2020, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
  2. SFLYER5
    Thread

    Windows 10: ATTEMPTED_WRITE_TO_READONLY_MEMORY then INVALID_PROCESS_ATTEMPT_ATTACH BSOD...

    This is kind of a weird one, I never seen anything like this before. After attempting to format a USB drive, I get this stop error:...
    Thread by: Sflyer5, Jun 6, 2019, 3 replies, in forum: Windows 10 Drivers and Hardware
  3. WINCLUB
    Thread

    Fix ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen on Windows

    [ATTACH] The ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen has an error code 0x000000BE. This error occurs when you try to boot into Windows....
    Thread by: WinClub, Dec 15, 2018, 3 replies, in forum: Windows 10 News
  4. WOLFLEADER116
    Thread

    ATTEMPTED_WRITE_TO_READONLY_MEMORY at Random

    Hello, I have gotten two ATTEMPTED_WRITE_TO_READONLY_MEMORY BSOD's in the past 2 days now. Both times I had Firefox and Discord open, but wasn't...
    Thread by: WolfLeader116, Sep 2, 2018, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
  5. NAYTHAN
    Thread

    2 BSOD's - latest ATTEMPTED_WRITE_TO_READONLY_MEMORY

    I had one BSOD yesterday and I thought it would be a one off - but today I've had another with ATTEMPTED_WRITE_TO_READONLY_MEMORY. I've...
    Thread by: Naythan, May 8, 2017, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
Tags: