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

Page 13 of 17 FirstFirst ... 31112131415 ... LastLast

  1. Posts : 14,901
    Windows 10 Pro
       #121

    Those reports could have to do with problems including BSOD's, but that can't be said with certainty because it could also have nothing to do with it. What I mean to say is it can't be said that the reports are crucial but it can't also be said that the reports are not crucial, it is better to include them with troubleshooting to not left anything out.

    So, yes try to update it and see how it goes :)
      My Computers


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

    ok, I understand. I've just updated the application to the latest 4.4.2.
    I have the same application as a PortableApp as well so I can use that one and uninstall the one from the system.
    would it make any difference regarding crash relevance?
      My Computer


  3. Posts : 14,901
    Windows 10 Pro
       #123

    would it make any difference regarding crash relevance?
    If the portable version does not have the same executable file the problem reports are talking about than it may.
      My Computers


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

    the portable version is the 32bit one, which can run on both 32bit and 64bit systems.
    the executable is "i_view32.exe" as shown on the picture.

    strange though as I have IrfanView only active as long as I use it. when done I always close the application and don't let it run in the background.
      My Computer


  5. Posts : 14,901
    Windows 10 Pro
       #125

    strange though as I have IrfanView only active as long as I use it. when done I always close the application and don't let it run in the background.
    Not exactly strange, a program doesn't have to crash for Windows to create a problem report, the problem report is being generated in the background. Some may say otherwise, but I had a few problem reports that were created because a program didn't respond for a short time but it didn't crash in the way that I had to open it again.
      My Computers


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

    I see, so maybe I should uninstall the 64bit IrfanView from my system and use the portable version instead.

    update 1: done, uninstaled the 64bit IrfanView and using the portable version.

    update 2: bad news, got a bugcheck again with "ATTEMPTED_WRITE_TO_READONLY_MEMORY" so we are back to page 1 of the topic. I never had this crash since and this is the second crash within 24hours after I went back to nVidia 371.75 WHQL driver.
    relevant or coincidence? no idea form my side.

    to sum up the situation generally there seem to be three types of bugchecks I'm getting with no obvious reason:
    "ATTEMPTED_WRITE_TO_READONLY_MEMORY"
    "IRQ_NOT_LESS_OR_EQUAL" and
    "MEMORY_MANMAGEMENT".

    I'm ataching the log files including the previous minidump as well as I didn't clean the logs.
    After the crash there was also file corruption found and fixed by "sfc /scannow".
    Last edited by sahafiec; 07 Apr 2016 at 09:33.
      My Computer


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

    and just got another one axe0, this time it is "MEMORY_MANAGEMENT".
    was just browsing the internet and listening to musik, no real load at all.
    it got worse after changing the nVidia driver, in my opinion.
      My Computer


  8. Posts : 14,901
    Windows 10 Pro
       #128

    You've cleaned your system again?

    Is hardware acceleration in Google Chrome enabled?

    In the right upper corner, click on and choose settings.
    Scroll below and click on 'advanced settings', scroll all the way to the end of the settings.
    In the part 'system' is the option to enable/disable hardware acceleration.
    If this option is enabled, disable it and let me know how it goes.
    Code:
    PROCESS_NAME:  chrome.exe
    

      My Computers


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

    yes, I cleaned the system after the last crash and prior to this one.
    should I never clean as long as we troubleshoot?

    no, hardware acceleration in Chrome in not enabled.

    do you think the whole issue can be related to the nVidia driver?
      My Computer


  10. Posts : 14,901
    Windows 10 Pro
       #130

    should I never clean as long as we troubleshoot?
    My answer from the previous page "Don't cleanup your pc, this deletes the dumps and so I cannot find any patterns." :)
    I cleanup my system once in a while because the size of all the zips I download to help slowly grows to a few gigs, if I don't my partition would have a folder containing about 50gig of zips which is more than the partition can handle (current stuff + 50gig of zips can't be handled by the partition) and I can't add enough space because of some private stuff, this causes that any deleted data from your side and my side can't be recovered which sometimes may be a pain because the deleted data may be extremely helpful.

    That is why it is for now important that you don't cleanup your system while troubleshooting.

    Though I can try to selectively delete the zips I download, but the last time I tried that I lost way too much time for a few downloads due to the amount of the total downloaded files.
      My Computers


 

  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:42.
Find Us




Windows 10 Forums