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

Page 11 of 17 FirstFirst ... 910111213 ... LastLast

  1. Posts : 90
    Windows 10 Pro 64bit
    Thread Starter
       #101

    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.

    anything unusual in the logs?
      My Computer


  2. Posts : 14,903
    Windows 10 Pro
       #102

    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
    1. Short Drive Self Test
    2. Short generic
    3. Long generic

    If the short generic fails, no need for the long generic.
    Note   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
      My Computers


  3. Posts : 90
    Windows 10 Pro 64bit
    Thread Starter
       #103

    I will be just adding the tests results and editing the same poost:

    1. I can't use the SeaTools as my both hard drives are WD. I have to use Western Digital Data LifeGuard instead.
    - both hard drives passed the Quick test, no issues.
    - both hard drives passed the Extended test, no issues.

    2. Running Chkdsk on both HDD's - D: and E:
    - hard drive D: passed chkdsk with no errors.
    - hard drive E: passed chkdsk with no errors.

    3. Running HDTune on both HDD's - D: and E:
    - hard drive D: health status is ok, hard drive E: health status is ok.
    - benchmarks for D: and E: seem also to be ok
    - long error scan for D: and E: seem to be ok
    Last edited by sahafiec; 03 Apr 2016 at 13:29.
      My Computer


  4. Posts : 14,903
    Windows 10 Pro
       #104

    sahafiec said:
    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.

    anything unusual in the logs?
    Could you check in the BIOS for the 3.3v, 5v and 12v please, just to ensure those are proper because software isn't as proper as the BIOS with these values :)

    2 other things I will ask for now,
    1. I don't believe we have checked the SSD firmware for updates?
    2. Could you change your system language to english please, I can't read most of the logs because of the language.
      My Computers


  5. Posts : 90
    Windows 10 Pro 64bit
    Thread Starter
       #105

    I'll check the voltages in my bios as soon as the hdd long error test ist over.

    1. I regularly check for new firmware on the ssd, the current one is the latest (screenshot included). some more info on that, the OS resides on my m.2 SSD but system temp directory resides on my 1st HDD drive, which also carries all my games, Steam, Origin etc. I didn't want too much write cycles on my SSD.

    2. not really sure how to do that, I have a genuine turkish version of Windows 10 Pro. I'll gladly assist in that matter, I also see that a lot on OS internal messages are still in english.

    3. I've checked the voltages in the bios this morning while booting the system. seems pretty good so far, not much difference to the readings in Windows.
    Last edited by sahafiec; 04 Apr 2016 at 00:46.
      My Computer


  6. Posts : 14,903
    Windows 10 Pro
       #106

    I have an upgraded version of Windows 10 Home which originally is Dutch, I changed it almost completely to english for Cortana.
    In control panel go to 'Region', click 'Administrative' tab and click 'Copy settings'.
    My settings that 'Copy settings' shows
    Attachment 72903

    In control panel go to 'Language' and add the language english or change the language to english, I'm not exactly sure how it works with Pro because there are a few differences with Pro and Home, I had to remove the dutch language to get the english language.
      My Computers


  7. Posts : 90
    Windows 10 Pro 64bit
    Thread Starter
       #107

    yes I found the location you meen, I have everything in turkish of course. :)
    I'll have a look at it and add english as well.
      My Computer


  8. Posts : 90
    Windows 10 Pro 64bit
    Thread Starter
       #108

    and yet another crash with "DRIVER_IRQ_NOT_LESS_OR_EQUAL" while just browsing the net.

    axe0, where is this going to end?!
      My Computer


  9. Posts : 14,903
    Windows 10 Pro
       #109

    Don't cleanup your pc, this deletes the dumps and so I cannot find any patterns.

    There is a known problem with the Nvidia drivers you're using, it is recommended to try WHQL 361.75
      My Computers


  10. Posts : 90
    Windows 10 Pro 64bit
    Thread Starter
       #110

    so this crash was caused by the nVidia driver?

    I included all the logs using the log collector tool. do you need any other logs?

    I was using 361.82 as I started troubleshooting this issue and I had crashes with all versions.
    there was no sign nVidia could be the cause until now.
      My Computer


 

  Related Discussions
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 08:40.
Find Us




Windows 10 Forums