The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Memory can't be written error

    Discussion in 'HP' started by thinkwierd, Apr 26, 2007.

  1. thinkwierd

    thinkwierd Notebook Evangelist

    Reputations:
    5
    Messages:
    418
    Likes Received:
    0
    Trophy Points:
    30
    I am running some programs on my dv2000t with windows XP sp2 installed. But I often gets "memory can't be written" error when I tried to run the program.

    Does it mean that my memory is bad? (I add an extra 1G)
    Or do I need to reinstall Nvidia go 7200 driver?

    How to fix this probleM
     
    thinkwierd, Apr 26, 2007
    #1
  2. ruibing

    ruibing Notebook Consultant

    Reputations:
    1
    Messages:
    117
    Likes Received:
    0
    Trophy Points:
    30
    Run memtest86 by burning it onto a cd and booting up with it. It will test your memory for errors. Let it repeat the test two times and then we can safely say it's not the physical memory.

    If that doesn't solve the problem, it may be the virtual page table or swap file. But try the first method before making guesses.
     
    ruibing, Apr 26, 2007
    #2
  3. thinkwierd

    thinkwierd Notebook Evangelist

    Reputations:
    5
    Messages:
    418
    Likes Received:
    0
    Trophy Points:
    30
    I tried memtest+86 and found no errors after running once. What are the other causes of Memory can't be written error?
     
    thinkwierd, Apr 27, 2007
    #3
  4. brianstretch

    brianstretch Notebook Virtuoso

    Reputations:
    441
    Messages:
    3,667
    Likes Received:
    0
    Trophy Points:
    105
    It's probably caused by buggy software. Is there any particular program you're running when this error happens?
     
    brianstretch, Apr 27, 2007
    #4