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

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

sahafiec said:

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.

Code:

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 ......

Code:

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.

Well, we can test a CPU ....

Stress test the CPU.

Prime95 - Stress Test Your 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.

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.

No, overload is not causing your issue for sure.