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

after working great the last few days I got a total system freeze today.
the only solution to recover was a system reset.
rebooting worked fine and now system is running as if nothing happened.

I was doing nothing special while it happened, just 2 browser were running.

I attached the log files, hope it helps. *sarc

note: I realize that no dump file was written although it's switched on.

 

A dump is only created with a bluescreen as that is actually a system crash that can be caught. The other crashes can't be caught by the system, with a freeze the system can't response and with a shutdown/restart the system doesn't get the opportunity to generate a dump because the data in the memory will be gone already as it is volatile memory (memory that is present as long as there is power).

 

got a BSOD right now, 5 min. after the reboot. *sarc

as if something made the system unstable, while doing actually nothing I suddenly got the "IRQL_NOT_LESS_OR_EQUAL" BSOD caused by ntoskrnl.exe.

 

Are you OC'ing?
Code: CPUID: "Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz" MaxSpeed: 3500 CurrentSpeed: 3504[/quote] What are the memory timings according to the BIOS?
They should be
Code: 15-15-15-36[/quote]

 

no, I'm not - everything on stock and auto in the bios.
for the ram I use the XMP-2400 profile (last attached picture).

my ram is 1,5 months old, exact specs:
Corsair Vengeance LPX 16GB (4 x 4GB) DDR4 DRAM 2400MHz C14 memory kit for DDR4 Systems (CMK16GX4M4A2400C14) at Amazon.com

 

after the BSOD I rebooted and run a "sfc /scannow" which found and corrected some errors.
those were not there prior the BSOD but still I don't know if they are a cause or a result of the BSOD.
but strangely mostly after a BSOD there are some errors, luckily all repairable by "sfc /scannow".

 

Please remove all OC'ing on your system, OC'ing may make the system stability worse when there are problems present.
Even if the OC'ing is not the cause just remove it with the reason that it may cause more instability.

 

but I don't have any OC at all axe0, you can see it on the pics above that I run everything on stock speed. *sarc

what you got about the cpu can only be a sudden spike and I have no idea why it may have occured.

 

XMP with the memory is overclocking.

I mean everything, CPU, memory, GPU.

 

ok, I can disable the XMP profile and let the ram run at lowest possible 2133MHz.

why do you suspect the XMP as being the cause?

the ram is rated exactly for that speed and is additionally listed in the "DRAM QVL" list for my motherboard.

that's why I bought this specific model. *sarc

 

I don't suspect it as a cause, it is a standard thing to remove overclocking when troubleshooting and I want to rule out as much as possible to improve stability

 

got it, I didn't consider XMP as overclocking in my previous posts.
I'll reboot, switch XMP off and then go on using the system as usually.

 

Most don't consider XMP as OC'ing, but on the site of the motherboard is clearly stated (O.C.) *Wink

 

yes, that's right - easy to overlook for a normal daily user.

XMP is switched off, ram is set to "auto" in bios and running JEDEC at 2133MHz.

so now there is really no OC in the system.

 

Please provide all CPU-Z screenshots according to below instructions *Smile
Please run CPU-Z | Softwares | CPUID, open it and make screenshots of the following tabs

• CPU
• Mainboard
• Memory
• SPD*
• Graphics

*SPD shows the details of each module, you can show the details by choosing different slots in the left upper corner.
Please make screenshots of each module.

Please post each screenshot in your next reply/replies.