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

here you go, all done. *Smile

 

Please double check the settings and set the frequency of the memory manual, the auto setting may sometimes change it a little bit what may cause trouble.

 

done, I set the DRAM speed manually to 2133MHz and the timings to 15-15-15-36-50.

is there no clear sign on the BSOD cause in the dump file?

 

There isn't always a clear sign in the dumps, the dumps we analyse are minidump. Minidumps contain a very minimum of data that was present in the memory at time of the crash, but minidumps are usually enough.

However, this driver is a little outdated. I'm not sure what it is but I think you know more *Smile
Code: svthlsns SvThLSNS \??\c:\program files (x86)\savitech\svloadsense\x64\svthlsns.sys[/quote]

 

I understand, so there is no need to switch to bigger minidump settings - right?

regarding the driver I already wondered myself what this driver is about.
I thought it could have been installed together with my Asus motherboard drivers.

but to be honest right now I have no idea what it really is and will investigate it.

note: it seems that it's used to start the Sonic Studio 2 at startup.
I found a short topic on the ROG forums, attached the comments as a jpg.
I've just uninstalled it as I don't like it and don't need it anyway. *Smile

 

Not really no, you could but I am no BSOD Kernel Dump Analyst as some call it, I am a BSOD crash analyst what is in my opinion different from a kernel dump analyst. It would require knowledge to proper analyse a kernel dump or complete dump what I do not have.

Keep me posted *Smile

 

so there is nothing else I can do right now except using the system the usual way?
and waiting for something unusual to happen?

 

You can check if your memory modules are proper seated and if necessary reseat them proper *Smile

 

I'll do that of course. would not properly seated modules cause much more issues than just random bsods?

 

Yes it could, like that a memory module isn't detected what causes that the system doesn't have enough memory what forces the system to close some programs to regain memory (assuming everything is proper*) and use the memory for something else.

*It happens that when a program is closed the used memory isn't deallocated (memory made free for other programs) what may cause the same problem as in the example above, other programs need to be closed to regain the memory that something else requires.

 

yes, you are right - I'll make sure everything sits right and tight.
it's really frustrating to know there is an issue inside but not to be able to really sort it out.
I spent quite some time to choose the right components for this rig and I thought I've done a good job.
the ram is in the motherboards support list and so is the motheboards in the rams support list.
I check almost daily for new driver and bios but all this doesn't seem enough.

note: I double and even triple checked that everything sits rock solid on it's place.

 

a aside note, I regularly get this warning in the event log after startup:

I have generally no problems while using the mentioned flash drive.
but could this somehow sometimes lead to the BSOD?

also today morning after cold start the sfc found again some corrupt files and repaired them.
it always manages to repair in the first run so in the second run there are no more corruptions detected.
but what's corrupting those file so often and could it be also BSOD related?

I'm including the latest CBS.log file.

 

If SFC fixes the corruption, then I can't find it as fast as I can when there is unrepaired corruption.

Please try following command in admin command prompt
Code: DISM /Online /Cleanup-Image /RestoreHealth[/quote] If there are problems with RestoreHealth, please follow step 6 or 7 (depending on the file you have from the download) from the tutorial DISM - Repair Windows 10 Image - Tutorial

 

done, no issues or errors found.

 

Try running SFC again to see what it produces now.