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

Page 15 of 17 FirstFirst ... 51314151617 LastLast
  1.    09 Apr 2016 #141

    I've already done it, this is a fresh Windows 10 Pro install performed on this same rig. don't remember exactly but the installation shouldn't be older than 1-2months. the only additional drivers loaded are Intel network, Realtek sound and nVidia graphics drivers.
    what I just can't understand is that I never have a crash under high load, only at very low load mostly just a browser running.
    I've changed the ram, reseated, run MemTest86+, Driver Verifier and so on just to come back to the beginning.
      My ComputerSystem Spec

  2. Arc's Avatar
    Posts : 1,643
    Microsoft Windows 10 Home
       09 Apr 2016 #142

    In that case you have to search for the reasons in either the RAM incompatibility or the motherboard itself, unfortunately.
      My ComputerSystem Spec

  3.    09 Apr 2016 #143

    I thought that with exchanging the ram I could eliminate at least the ram as a cause.
    there has been meanwhile 2 bios updates I've updated to but the issue is not gone.
    what I generally read on the forums leads me to the assumption that an incompability should cause much more severe issues.
    this very high randomness of my issue make it very difficult for me to test and troubleshoot.

    I'm just out of ideas after so much testing, it still can be anything and I don't have the means to narrow it down.
      My ComputerSystem Spec

  4. Arc's Avatar
    Posts : 1,643
    Microsoft Windows 10 Home
       09 Apr 2016 #144

    sahafiec said: View Post
    it still can be anything and I don't have the means to narrow it down.
    Post #127, your last BSOD upload. Let us revisit.

    BugCheck 1A, {41284, 94a8000, 219a8, fffff58010804000}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+15f0f )
    Followup:     MachineOwner
    We have no more useful information in the dump other than the bugcheck code. It is the situation there, from the very beginning, post #1 ......
    BugCheck BE, {fffffa8804c16da0, 8000000000200121, ffffd00021e694e0, a}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4126b )
    Followup:     MachineOwner
    And no more information.

    All your crash dumps are the same.

    Stop 0x1A or stop 0xBE, all of them are memory related issue. It can be two types of things, viz ...
    • A driver is passing bad information to the memory
    • A memory hardware is failing. A memory hardware includes
      1. RAM,
      2. DIMM slots, and
      3. Memory Controller, a motherboard element.

    Now coming to narrowing the issue down. First of all, we need to discriminate it between software (driver) issue and hardware issue.

    There are various different ways to determine a driver issue.
    • Driver verifier ==> The thread say it was enabled but was not fruitful.
    • Reinstalling Windows as vanilla ==> You say you have done it, with no change.
    • Installing any other OS. Say Linux Mint ==> That is still a open option.

    If the crashes are just the same irrespective of the above three, then it is not a software/driver related issue but a hardware caused issue.

    Now to narrow down the possibilities in the hardware environment, Memtest86+ comes with no issue. So the RAMs are good themselves; as the DIMM slots are. But we see that those are technically incompatible with the hardware. So it adds to the list as number
    #4, possible RAM incompatibility.
    If it is not that issue too, then it is a memory controller related issue, that means the motherboard.

    Now you know all about how to narrow the possibilities down. Solution of the issue depends on what you can do to narrow it down.
    That's all.
      My ComputerSystem Spec

  5.    09 Apr 2016 #145

    thanks for the the short summary of the situation Arc, that's indeed very helpfull for me to keep the focus on.

    the idea of installing Linux is not bad at all as I'm familiar with Linux.
    the problem is I'd have to use it for at least until one crash which could take a week or even more.
    but I'm not able to do my work on that platform as I'm using the rig for my work as well.

    speaking of the memory controller, as far as I know the memory controller resides on the cpu in Skylake.
    or am I wrong?
    this would mean in case of memory controller issue it'd be the cpu not working as it should.

    assuming the ram is ok, which has the higher possibility in my situation: failing cpu or motherboard?
      My ComputerSystem Spec

  6. Arc's Avatar
    Posts : 1,643
    Microsoft Windows 10 Home
       09 Apr 2016 #146

    Well, we can test a CPU ....
    Stress test the CPU.It saves the result as a .txt file in the prime95's folder. Upload the file for us.
    But we cannot test a motherboard.
      My ComputerSystem Spec

  7.    09 Apr 2016 #147

    I can Prime95 test my cpu, no problem at all.
    the big questions mark is why generally stress tests don't lead to error reproduction.
    this makes me suspicious that the error is not load related at all. everything seems to work as it should under load. thus stress testing the memory or ram doesn't lead to a result.
    many user report about system freeze or hard locking at idle. they suspect some issues with skylake c-state transitions causing systems to lock down.
    Last edited by sahafiec; 09 Apr 2016 at 14:36.
      My ComputerSystem Spec

  8. Arc's Avatar
    Posts : 1,643
    Microsoft Windows 10 Home
       09 Apr 2016 #148

    No, overload is not causing your issue for sure.
      My ComputerSystem Spec

  9.    12 Apr 2016 #149

    thank you both axe0 and Arc for the great assistance and help.

    I'll try to further troubleshoot with some changes in the bios settings as suggested on other forums.

    if it doesn't bring any stability I'll have to RMA my cpu and motherboard until the issue gets solved.

    you are great so keep the good work going on.
      My ComputerSystem Spec

  10.    22 Apr 2016 #150

    a new BugCheck, same as old one?!

    hi guys,
    could you please have a short look at this BugCheck I got today?
    I wonder if it's the same as the crashes I got before.

    meanwhile I got a replacement cpu fron Intel , tested both cpus over the weekend with no issues.
    I thought everything was fixed now, there was also a very slightly bent pin on the motherboard which I fixed.
    I was running error free for over a week now until today at noon where at idle the system got a bugcheck.
      My ComputerSystem Spec

Page 15 of 17 FirstFirst ... 51314151617 LastLast

Related Threads
Hopefully somebody here can help me. I've looked around everywhere to find a solution for this issue, but this problem differs from all the threads you can find in many forums around there: it already worked well for me :sleepy: My problem: I...
Hi, So I upgraded my system. Bought a new motherboard, CPU, CPU Cooler, RAM, PSU & SSD. Installed windows 10, worked fine for the first week. Now when I start my PC in the morning or from when I get in from work, I get a BSOD when the PC...
I originally upgraded to Win 10 over Win 8.1 when it first came out. Recently it started to slow up and I decided to reinstall from a DVD which I'd burnt as ISO disc from Win10 software from Microsoft download site. I had also saved the product...
Ever since I updated to Windows 10 from 8.1, I've been getting a BSOD (ATTEMPTED_WRITE_TO_READONLY_MEMORY) almost every time I wake my computer up from sleep. I tried to figure out how to fix this myself, but unfortunately am not the most computer...
I've been receiving both attempted_to_write_readonly_memory (netio.sys) and IRQL_not_less_or_equal (netio.sys) blue screens for some time. It tends to happen at random intervals when playing games or just browsing on the internet. At this point I'm...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 04:25.
Find Us