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

Page 4 of 17 FirstFirst ... 2345614 ... LastLast
  1.    19 Feb 2016 #31

    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?
      My ComputerSystem Spec

  2. axe0's Avatar
    Posts : 13,707
    Windows 10 Pro
       19 Feb 2016 #32

    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 :)
    svthlsns	SvThLSNS	\??\c:\program files (x86)\savitech\svloadsense\x64\svthlsns.sys
      My ComputersSystem Spec

  3.    19 Feb 2016 #33

    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. :)
    Last edited by sahafiec; 19 Feb 2016 at 14:19.
      My ComputerSystem Spec

  4. axe0's Avatar
    Posts : 13,707
    Windows 10 Pro
       19 Feb 2016 #34

    so there is no need to switch to bigger minidump settings - right?
    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 :)
      My ComputersSystem Spec

  5.    19 Feb 2016 #35

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

  6. axe0's Avatar
    Posts : 13,707
    Windows 10 Pro
       19 Feb 2016 #36

    You can check if your memory modules are proper seated and if necessary reseat them proper :)
      My ComputersSystem Spec

  7.    19 Feb 2016 #37

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

  8. axe0's Avatar
    Posts : 13,707
    Windows 10 Pro
       19 Feb 2016 #38

    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.
      My ComputersSystem Spec

  9.    19 Feb 2016 #39

    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.
    Last edited by sahafiec; 20 Feb 2016 at 02:05.
      My ComputerSystem Spec

  10.    20 Feb 2016 #40

    a aside note, I regularly get this warning in the event log after startup:
    The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_SanDisk&Prod_Extreme&Rev_0001#AA010508150033040106&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

    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.
      My ComputerSystem Spec

Page 4 of 17 FirstFirst ... 2345614 ... LastLast

Related Threads
Hopefully somebody here can help me. I've looked around everywhere to find a solution for this issue, but this problem differs from all the threads you can find in many forums around there: it already worked well for me :sleepy: My problem: I...
Hi, So I upgraded my system. Bought a new motherboard, CPU, CPU Cooler, RAM, PSU & SSD. Installed windows 10, worked fine for the first week. Now when I start my PC in the morning or from when I get in from work, I get a BSOD when the PC...
I originally upgraded to Win 10 over Win 8.1 when it first came out. Recently it started to slow up and I decided to reinstall from a DVD which I'd burnt as ISO disc from Win10 software from Microsoft download site. I had also saved the product...
Ever since I updated to Windows 10 from 8.1, I've been getting a BSOD (ATTEMPTED_WRITE_TO_READONLY_MEMORY) almost every time I wake my computer up from sleep. I tried to figure out how to fix this myself, but unfortunately am not the most computer...
I've been receiving both attempted_to_write_readonly_memory (netio.sys) and IRQL_not_less_or_equal (netio.sys) blue screens for some time. It tends to happen at random intervals when playing games or just browsing on the internet. At this point I'm...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 04:31.
Find Us