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

This says enough,
You can't overclock your memory.

Code:

IMAGE_NAME:  memory_corruption

CPUID:        "Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz"
Memory Specifications

Max Memory Size (dependent on memory type)
64 GB

Memory Types
DDR4-1866/2133, DDR3L-1333/1600 @ 1.35V

Max # of Memory Channels
2

Max Memory Bandwidth
34.1 GB/s

ECC Memory Supported ‡
No



[Memory Device (Type 17) - Length 40 - Handle 0045h]
  Physical Memory Array Handle  0041h
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          8192MB
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                ChannelB-DIMM2
  Bank Locator                  BANK 3
  Memory Type                   1ah - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         2400MHz
  Manufacturer                  Corsair
  Serial Number                         
  Asset Tag Number                        
  Part Number                   CMK16GX4M2A2400C14

With a quick view I have not + because I can't read your language I only had a look at the things I understand without reading.

Memory corruption can mean quite a few things:

• Drivers passing bad stuff to the memory,
• The memory is corrupting data,
• The vram is causing problems,
• Problems with the hard drive.

There are some more, but these are the most frequent occuring onces.
What it means here is that there is a compatibility issue with the CPU and memory causing either of them to not function proper.

I can better say that what it means here is unclear, there are quite a few things that could have happened but the cause we know. The only way to know what it means here is to debug the kernel dump that is in %systemroot%, but I'm not experienced with debugging kernel dumps.

I understand, is it possible to narrow it down from within the log files?

* Drivers passing bad stuff to the memory - that's what we ran Driver Verifier for with no errors
* The memory is corrupting data - I ran MemTest86+ for over 9 passes with no errors
* Problems with the hard drive - I checked all drives and posted the results here, no errors
* The vram is causing problems - I haven't tested that but never had th crash while gaming. could it be nvidia driver related?

what I can do right now is just to run the rams at SPD speed of 2133MHz, as always.

I would like to point to another thing, that is the memory controller. It frames the limiting factor of the usage of RAM. Your Motherboard warns you about in:

* Hyper DIMM support is subject to the physical characteristics of individual CPUs.

That is what you are pointed to, twice, in post #136 and in post #151.

There should be a way to enhance the capabilities of the CPU hardware to make it support the RAM with more speed. But IMHO that will fall within the scope of Overclocking. But that will be a different topic. In this section of the forum we concentrate on how to make the Programs free from BSODs.

Code:

BugCheck BE, {fffffc0007ac5ed8, 8000000000200121, ffffd0002153a3f0, a}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40ee3 )

Followup:     MachineOwner
---------

Bugcheck 0XBE is ATTEMPTED_WRITE_TO_READONLY_MEMORY .... a memory related BSOD. Either the RAM is behaving incorrectly or any driver is causing a memory malfunction.

We havnet got any failing driver in the deepest level of analysis.

The "probably caused by" line is saying ntkrnlmp.exe .... which is not a cause of any BSOD at all. It is a flaw of the dump recording mechanism. When it fails to identify the actual cause of the BSOD, it mistakenly blames the kenrel itself on which the BSOD took place.

So till now we will point to the same thing as previous: the RAM speed which is apparently mismatch to the specs.

Code:

  Speed                         2400MHz

I think it is the time to decide which is desired. Stability or XMP.