I run Einstein@home and SETI@home. After running for awhile, and after moving the mouse to set aside the application, I get a BOINC Application error: [The instruction at "0x004060df" referenced memory at "0x0013024c." The memory could not be "written." Click on OK to terminate the program.] I click OK and proceed with my business. Both screen saver applications seem to work.

---

Go into your account and change the setting to leave the program in memory. Enable this feature and see if that fixes it.

---

Go into your account and change the setting to leave the program in memory. Enable this feature and see if that fixes it.

Two days ago, I took your advice and change the setting to leave the program in memory. I still get the 'memory could not be written.' I assume two days is enough time for the setting to take effect. It doesnt seem to stop the work. It's just a nuissance. If you can think of anything else, I'd appreciate your advice. Thanks.

---

Memory could not be written could be an issue with the memory. There is a good test out there called Memtest86+ which will help you determine if you have bad memory.

---

My movie https://vimeo.com/manage/videos/502242

Memory could not be written could be an issue with the memory. There is a good test out there called Memtest86+ which will help you determine if you have bad memory.

What I first did was run Defrag which in previous versions of Windows picks up any bad memory and does a low level format to fix it. I did the same in XP and assumed that when it was complete, there was no bad memory sectors. Can I still have bad memory sectors and should run the Memtest86+ you advised?

---

What I first did was run Defrag which in previous versions of Windows picks up any bad memory and does a low level format to fix it. I did the same in XP and assumed that when it was complete, there was no bad memory sectors. Can I still have bad memory sectors and should run the Memtest86+ you advised?

I am not sure what kind of Windows you previously had... but defrag only defragments a hard disk. Defragmenting means: "to free up spaces between files, add them back to the amount of free space on your hard disk"

It does not low level format, for if it did, all information, all partitions and all programs on your hard disk would be gone after you defragged your drive.

A low level format cannot be done by Windows.
It can be done with specialized software for your hard disk, supplied by your hard disk manufacturer. If Windows would do it through defrag, you'd be in serious trouble.

A low level format writes all sectors of the disk with zeros first, then it restarts and does them with ones. (bits) It'll probably repeat this a couple of times. Afterwards you have a drive that looks to the outside world as if it just came from the factory, no partition even on it. You'd have to make a new partition on it.

Then, defrag does not defragment memory. Memory means RAM. The sticks of memory you add into your computer in which programs from the hard drive are loaded when you run them.

Defrag also doesn't repair errors on the disk. That's scandisk and chkdsk which will do that. Look up in Windows Help.

The full and complete error message, including the numbers would help a great deal to get to the bottom of this, but yes, do run Memtest86+... it will test your RAM.

---

What I first did was run Defrag which in previous versions of Windows picks up any bad memory and does a low level format to fix it. I did the same in XP and assumed that when it was complete, there was no bad memory sectors. Can I still have bad memory sectors and should run the Memtest86+ you advised?

You've confused Hard Drive "memory" with system memory or RAM. Common mistake.

When you run Window's Defrag, it checks the Hard Drive for errors, and if it finds them it runs Window's ScandDisk and fixes all Hard Drive errors, marking bad spots as unusable.

The problem you're having is with system RAM. Defrag and Scandisk do not test RAM and therefore would not let you know if there's an error. They work with the Hard Disk alone. In order to test your system RAM, you'll have to use a third party tool, such as the one suggested (I use that one too). This tool will help you diagnose your computer to see if a RAM chip is going bad.

---

What I first did was run Defrag which in previous versions of Windows picks up any bad memory and does a low level format to fix it. I did the same in XP and assumed that when it was complete, there was no bad memory sectors. Can I still have bad memory sectors and should run the Memtest86+ you advised?

I am not sure what kind of Windows you previously had... but defrag only defragments a hard disk. Defragmenting means: "to free up spaces between files, add them back to the amount of free space on your hard disk"

It does not low level format, for if it did, all information, all partitions and all programs on your hard disk would be gone after you defragged your drive.

A low level format cannot be done by Windows.
It can be done with specialized software for your hard disk, supplied by your hard disk manufacturer. If Windows would do it through defrag, you'd be in serious trouble.

A low level format writes all sectors of the disk with zeros first, then it restarts and does them with ones. (bits) It'll probably repeat this a couple of times. Afterwards you have a drive that looks to the outside world as if it just came from the factory, no partition even on it. You'd have to make a new partition on it.

Then, defrag does not defragment memory. Memory means RAM. The sticks of memory you add into your computer in which programs from the hard drive are loaded when you run them.

Defrag also doesn't repair errors on the disk. That's scandisk and chkdsk which will do that. Look up in Windows Help.

The full and complete error message, including the numbers would help a great deal to get to the bottom of this, but yes, do run Memtest86+... it will test your RAM.

Thanks. Yes, I just assumed that Windows made corrected bad sectors like DOS did. I am going to try the Memtest86+.

---

Thanks. Yes, I just assumed that Windows made corrected bad sectors like DOS did. I am going to try the Memtest86+.

I ran DOS, and it did not automatically correct sectors. If you got a bad sector, you many times needed to start over with a low level format, then a format, then reinstall, until a couple of tools came out that you could run and lock out bad sectors.

---

My movie https://vimeo.com/manage/videos/502242

Memory could not be written could be an issue with the memory. There is a good test out there called Memtest86+ which will help you determine if you have bad memory.

I ran the Memtest86+ and the RAM tested out fine. Still a mystery.

---

Memory could not be written could be an issue with the memory. There is a good test out there called Memtest86+ which will help you determine if you have bad memory.

I ran the Memtest86+ and the RAM tested out fine. Still a mystery.

Since I posted this message, I have not had the problem. About 10 days now. It seems to have disappeared as mysteriously as it appeared. Thanks for the help. I got a RAM test diskette out of it.

---