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

I decided to check your memory and compare compatibility with your CPU
This is what I found, your CPU doesn't support your memory frequency at 2400MHz.
Code: [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 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 [/quote]

 

strange, how is this possible that Intel Skylake 6600K doesn't support 2400MHz DDR4 memory?

I know Intel considers everything beyond 2133MHz as OC but there are so many people using even >3000MHz ram on Skylake.
I just can't believe my cpu shouldn't be able to handle anything over 2133MHz.

Corsair claims the memory is "Designed for high-performance overclocking on Intel X99 and 100 Series motherboards".
http://www.corsair.com/en/vengeance...00mhz-c14-memory-kit-black-cmk16gx4m2a2400c14

is it the only clue you can get from all the trobleshooting we did until now?
is there any sort of test I can perform to find out if it is really the issue?

 

It is just that you want to go beyond compatibility possibilities what causes crashes.

I did tell you a few times to not overclock anything, it is a big clue *Wink

A stability test: change the memory frequency and test your system.

 

so my system is not able to handle the XMP overclock from 2133MHz to 2400MHz? *sarc

 

Your CPU doesn't support it and since your CPU does quite a lot you'll have to use 2133MHz, unless you change the CPU for one that does support 2400MHz *Smile

 

but there is no Skylake officially supporting more than that?
are all customers buying Skylake just throwing their money in the trashcan regarding ram?

I mean what's the meaning of buying an Intel 'K' cpu and highend overclock Z170 motherboard if they can't even handle 2400MHz.
I just generally don't get the point in this, although I get your point...

 

It is better to start a thread at PC Custom Builds and Overclocking - Windows 10 Forums for it, I'm not a person to ask such questions to.

 

anyway axe0, thank you very much for your help. *Wink


just as a side note axe0:
many people are reporting issues with Skylake C-States leading to random freezes/crashes at idle.
the problems reported describe the issue I face and after all the troubleshooting I tent to believe I have the same C-State issue.

it seems to be related to nothing else but the cpu itself and how Skylake handles the C-States.
lots of people having the issue spent a lot of time troubleshooting like me and nothing really helped.
issue persist all across the motherboard and ram manufacturers, the common point being the Skylake cpu and chipset.

the issue has been forwarded to Intel but there seems to be no official statement or solution yet.

this information could help people like me having BSOD or freezes with Skylake.

thread at Intel Community:
Skylake hard locks seeminly when IDLE / CStates ON | Intel Communities

thread at Tomshardware:
New Skylake Build Randomly Freezing/Crashing - Page 7 - Intel i7 - Windows 10

 

hi axe0, I'm afraid I need your help again.

I just got a "MEMORY_MANAGEMENT" BSOD, leterally while doing nothing.
I played Fallout 4 for about half an hour, closed the game and opened the Chrome browser.

after some reading for 10 minutes I opened a new browser tab and within 2-3 seconds the system rebooted.
there was no blue screen but just a very short freeze prior the reboot.

everything in the rig is on stock speed and voltage, NO XMP, the rams run at 2133MHz.
there was a new bios for my motherboard and new driver for the gpu, which I clean installed yesterday.

I'm attaching the collected logs, I'm really going crazy with this issue...*sarc

 

What is the voltage of the memory? You could also check the latency while checking the voltage *Smile

 

a solid standard DRAM voltage of 1.2V, as it should be according to SPD.

I just don't get the ponit why all this happen at idle, no issue under load. *sarc

anything unusual in the logs?

 

There was some NTFS and FLTMGR in the stack which may be indicative to the hard drive.
NTFS = Windows NT File system driver
FLTMGR = Windows File System Filter driver





Diagnostics Test

HDD TEST


Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run following tests

• Short Drive Self Test
• Short generic
• Long generic

If the short generic fails, no need for the long generic.


Note Do not run SeaTools on an SSD as the results will be invalid.



Run chkdsk
Disk Check - Windows 7 Help Forums



Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• benchmark.

It may take some time, but please take the time you need to perform it properly.
Let me know what the results are

• of the error scan,
• make a screenshot of the health of every hard drive and post the screenshots,
• post screenshots with the benchmark of the
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

Code: 3: kd> k # Child-SP RetAddr Call Site 00 ffffd000`206ecfe8 fffff800`137f1b0a nt!KeBugCheckEx 01 ffffd000`206ecff0 fffff800`136e926b nt! ?? ::FNODOBFM::`string'+0x1ea0a 02 ffffd000`206ed0b0 fffff800`136b2522 nt!MiUnlinkStandbyBatch+0x14b 03 ffffd000`206ed100 fffff800`136b124e nt!MmCheckCachedPageStates+0x822 04 ffffd000`206ed2a0 fffff800`13a596bf nt!CcFetchDataForRead+0x8e 05 ffffd000`206ed300 fffff800`136b101e nt!CcMapAndCopyFromCache+0xcf 06 ffffd000`206ed3a0 fffff801`93414faf nt!CcCopyReadEx+0xfe 07 ffffd000`206ed410 fffff801`934136ca NTFS!NtfsCachedRead+0x173 08 ffffd000`206ed480 fffff801`934128b2 NTFS!NtfsCommonRead+0xc5a 09 ffffd000`206ed630 fffff801`92b07895 NTFS!NtfsFsdRead+0x1f2 0a ffffd000`206ed6e0 fffff801`92b05816 FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x1a5 0b ffffd000`206ed770 fffff800`13a6a506 FLTMGR!FltpDispatch+0xb6 0c ffffd000`206ed7d0 fffff800`13a6a052 nt!IopSynchronousServiceTail+0x176 0d ffffd000`206ed8a0 fffff800`137cefa3 nt!NtReadFile+0x672 0e ffffd000`206ed990 00000000`73df21bc nt!KiSystemServiceCopyEnd+0x13 0f 00000000`0008eba8 00000000`00000000 0x73df21bc[/quote]