After booting Windows I see a message:

The instruction at 0x01005140 referenced a memory at 0x0000000. The memory could not be read.

Click OK to terminate program
Click Cancel to debug program

------
But neglecting on what is clicked, Boinc starts to work without any noticeable problem. I am using a release 5.10.30. It does not occur after all boots, but time to time.

Is it possible to fix this issue?

---

It could be a dodgy driver, but it could also be a memory problem.
If you have more than one memory module, i'd remove one & run the system for a while- if that fixes the problem, there's the cause. If not, swap modules over & see how it goes for a while.

---

Grant
Darwin NT

It could be a dodgy driver, but it could also be a memory problem.

I have 1Gb memory that consists from two 512MB modules.
I have checked a memory a lot without any problem. I am normally compiling
more than 100MB source codes. If any memory problem occur compiler would fail.

Is Boinc sensitive to memory modules, when no other app has any problem?
How is it possible?

If you have more than one memory module, i'd remove one & run the system for a while- if that fixes the problem, there's the cause. If not, swap modules over & see how it goes for a while.

This problem does not occur on every boot but say every 4th boot. It occurs after boot only.
But after clicking the Boinc normally continues. It runs for more than day without any noticeable problem.


I have also upgraded Boinc to the current release 5.10.45. The only change is:
The instruction at 0x77F8f281 referenced a memory at 0x0000000. The memory could not be read.

---

Since it seems to work properly when started after boot up, the only idea I have is the chance that there is a conflicts with some other program at boot up. I'm not knowledgeable enough to help you with this, so I leave it to someone else to address this possibility.

A couple of questions that might point to the problem.
Is Boinc being run as a service or from the startup menu?
What other programs or services start at boot up?

It could be a dodgy driver, but it could also be a memory problem.

I have 1Gb memory that consists from two 512MB modules.
I have checked a memory a lot without any problem. I am normally compiling
more than 100MB source codes. If any memory problem occur compiler would fail.

Is Boinc sensitive to memory modules, when no other app has any problem?
How is it possible?

If you have more than one memory module, i'd remove one & run the system for a while- if that fixes the problem, there's the cause. If not, swap modules over & see how it goes for a while.

This problem does not occur on every boot but say every 4th boot. It occurs after boot only.
But after clicking the Boinc normally continues. It runs for more than day without any noticeable problem.


I have also upgraded Boinc to the current release 5.10.45. The only change is:
The instruction at 0x77F8f281 referenced a memory at 0x0000000. The memory could not be read.

Try to run a memory checkprogram or check your memory RAM within your BIOS. If this is ok, try to use msconfig (using your startmenu and then go to run and type the word) to check what programs are running during startup, could be a driver issue or a program conflict. Check your pc for spyware or virusses. When you have the option to plug other or more RAM memory in, please do. My personal guess is, one of your memory modules is defective.

Hope this helps in some way for you.

---

To boldly go where no human has gone before!

This problem does not occur on every boot but say every 4th boot. It occurs after boot only.

From the Microsoft Knowledge Base:
This error message occurs because the operating system does not allocate a large enough buffer for the maximum string length that is permitted. When the data is larger than the buffer size, the Winlogon service stops unexpectedly and your computer generates the error message.

Now they say to update to the latest service pack, but you already have SP4 on Windows 2000, which is the last full service pack available (if you don't count the SP4 Rollup package).

It is possible though that your automatic Windows updates have been failing. Check in Event Viewer (Start->Settings->Control Panel->Administrative Tools->Event Viewer) what is causing these errors. It'll be flagged either in the System or Application logs.

---

Is Boinc being run as a service or from the startup menu?

Yes

What other programs or services start at boot up?

PGP, Sygate Personal firewall, Varftp
and a lot of Windows internal stuff.


The frustrating think is that I cannot debug a process, because pressing Cancel to debug does not work.

But after that BOINC does not crash it survives this and normally continues.

---

It is possible though that your automatic Windows updates have been failing.

Excuse me stisvc.exe has nothing to do with SETI. Sorry. This message started to appear after installing BOINC so I falsely guess it is service of seti.

---

stisvc.exe is an executable which is installed by Windows together with digital cameras, scanners or another graphical input devices.

---