Is it the fault of the owners PC or Boinc-server? Happend for the 4th time now. Any suggestions?

---

To boldly go where no human has gone before!

It's a problem on the person's computer.
See this FAQ.

---

It's a problem on the person's computer.
See this FAQ.

1. Your system is over-clocked to the max. Clock back to a more normal level for troubleshooting.

Nope, this PC is brand new, fresh out of the box, all updates are there.

2. You use corrupt system drivers. Update your motherboard chipset drivers.

I've the latest driver installed.

3. You use outdated/corrupt graphics drivers. Update the drivers for your graphics card or do not use the screen saver/graphics in BOINC.

I don't use the screensaver from BOINC. Graphics Card driver is up to date, have a Asus Nvidia 8600 GT. Going to check with Nvidia again for a driver.

4. Your DirectX version is outdated. Update DirectX. See Self Help: Links to Drivers for the link.

I use Directx 10, Vista Ultimate OS standard issue.

5. The image link(s) in BOINC are broken. Uninstall BOINC and reinstall it/upgrade it to the latest available version.

BOINC has been freshly installed.

6. The image link(s) in the project's application are broken. Reset the project from within BOINC.

That I'm going to try, right now.

7. Since the error is based on the Windows 0xc0000005 error (Access Violation), it could also be:
- faulty RAM
- an incorrect/corrupt device driver
- poorly written/updated software
- malware/adware installations.

This computer had a update installed because the store where I bought it, installed me the wrong version of the OS, the installed the correct version for me Vista Ultimate 32-bit. Had a flawless record when I used Vista Home premium 32-bit.

---

To boldly go where no human has gone before!

Where did you install BOINC to?
The default directory c:\\program files\\BOINC ?
Or did you install it to C:\\BOINC ?

If to the default directory, could you at least try to uninstall BOINC from there, then install to c:\\boinc and try again?
(You can uninstall BOINC, move the remaining BOINC directory with all sub-directories to C:\\BOINC, then reinstall BOINC to that new directory. This way you won't lose any new work you downloaded or the projects you're attached to).

By default Vista doesn't allow programs to write to directories in c:\\program files\\ .. since BOINC is writing to disk a lot of the time, this could give trouble.

---

Where did you install BOINC to?
The default directory c:\\program files\\BOINC ?
Or did you install it to C:\\BOINC ?

If to the default directory, could you at least try to uninstall BOINC from there, then install to c:\\boinc and try again?
(You can uninstall BOINC, move the remaining BOINC directory with all sub-directories to C:\\BOINC, then reinstall BOINC to that new directory. This way you won't lose any new work you downloaded or the projects you're attached to).

By default Vista doesn't allow programs to write to directories in c:\\program files\\ .. since BOINC is writing to disk a lot of the time, this could give trouble.

This is correct! I installed it on: C:\\Program Files\\BOINC. Strange thing is for now only big WU are send in correctly e.t.a 3 hour of work at 72 creditpoints, the small ones, I saw one time a WU request for only 968 sec. of work, it crashed directly after 1.14%!

---

To boldly go where no human has gone before!

Where did you install BOINC to?
The default directory c:\\program files\\BOINC ?
Or did you install it to C:\\BOINC ?

If to the default directory, could you at least try to uninstall BOINC from there, then install to c:\\boinc and try again?
(You can uninstall BOINC, move the remaining BOINC directory with all sub-directories to C:\\BOINC, then reinstall BOINC to that new directory. This way you won't lose any new work you downloaded or the projects you're attached to).

By default Vista doesn't allow programs to write to directories in c:\\program files\\ .. since BOINC is writing to disk a lot of the time, this could give trouble.

This is correct! I installed it on: C:\\Program Files\\BOINC. Strange thing is for now only big WU are send in correctly e.t.a 3 hour of work at 72 creditpoints, the small ones, I saw one time a WU request for only 968 sec. of work, it crashed directly after 1.14%!

You are probably hitting the conflict between Boinc and VISTA UAC. Vista does not allow writes to the C:\\Program files\\ directory tree unless elevated priveleges are granted first. This does not happen with BOINC V5, so, BOINC fails every write to its data. The applications fail every write to their data...

Please:
Uninstall BOINC.
Move the ENTIRE BOINC directory tree from c:\\Program Files\\BOINC\\ to c:\\BOINC\\
Install the same or newer version of BOINC to c:\\BOINC\\

This is required to get BOINC V5 5o work on Vista. V6 splits the BOINC core executables and dlls from the project executables and all of the data. However, V6 is not even in Alpha testing yet.

---

BOINC WIKI

Where did you install BOINC to?
The default directory c:\\program files\\BOINC ?
Or did you install it to C:\\BOINC ?

If to the default directory, could you at least try to uninstall BOINC from there, then install to c:\\boinc and try again?
(You can uninstall BOINC, move the remaining BOINC directory with all sub-directories to C:\\BOINC, then reinstall BOINC to that new directory. This way you won't lose any new work you downloaded or the projects you're attached to).

By default Vista doesn't allow programs to write to directories in c:\\program files\\ .. since BOINC is writing to disk a lot of the time, this could give trouble.

This is correct! I installed it on: C:\\Program Files\\BOINC. Strange thing is for now only big WU are send in correctly e.t.a 3 hour of work at 72 creditpoints, the small ones, I saw one time a WU request for only 968 sec. of work, it crashed directly after 1.14%!

You are probably hitting the conflict between Boinc and VISTA UAC. Vista does not allow writes to the C:\\Program files\\ directory tree unless elevated priveleges are granted first. This does not happen with BOINC V5, so, BOINC fails every write to its data. The applications fail every write to their data...

Please:
Uninstall BOINC.
Move the ENTIRE BOINC directory tree from c:\\Program Files\\BOINC\\ to c:\\BOINC\\
Install the same or newer version of BOINC to c:\\BOINC\\

This is required to get BOINC V5 5o work on Vista. V6 splits the BOINC core executables and dlls from the project executables and all of the data. However, V6 is not even in Alpha testing yet.

Thx for the tip. I have 2 more WU to crunch e.t.a. today, so I'll try to move them to a higher Subdir. Does this count for my XP pc too? At work we use XP prof. SP2. I think we have a simular problem there. 3 out of 4 WU was a fail from station at work. Going to try 5.10.45.

---

To boldly go where no human has gone before!

Where did you install BOINC to?
The default directory c:\\program files\\BOINC ?
Or did you install it to C:\\BOINC ?

If to the default directory, could you at least try to uninstall BOINC from there, then install to c:\\boinc and try again?
(You can uninstall BOINC, move the remaining BOINC directory with all sub-directories to C:\\BOINC, then reinstall BOINC to that new directory. This way you won't lose any new work you downloaded or the projects you're attached to).

By default Vista doesn't allow programs to write to directories in c:\\program files\\ .. since BOINC is writing to disk a lot of the time, this could give trouble.

This is correct! I installed it on: C:\\Program Files\\BOINC. Strange thing is for now only big WU are send in correctly e.t.a 3 hour of work at 72 creditpoints, the small ones, I saw one time a WU request for only 968 sec. of work, it crashed directly after 1.14%!

You are probably hitting the conflict between Boinc and VISTA UAC. Vista does not allow writes to the C:\\Program files\\ directory tree unless elevated priveleges are granted first. This does not happen with BOINC V5, so, BOINC fails every write to its data. The applications fail every write to their data...

Please:
Uninstall BOINC.
Move the ENTIRE BOINC directory tree from c:\\Program Files\\BOINC\\ to c:\\BOINC\\
Install the same or newer version of BOINC to c:\\BOINC\\

This is required to get BOINC V5 5o work on Vista. V6 splits the BOINC core executables and dlls from the project executables and all of the data. However, V6 is not even in Alpha testing yet.

Thx for the tip. I have 2 more WU to crunch e.t.a. today, so I'll try to move them to a higher Subdir. Does this count for my XP pc too? At work we use XP prof. SP2. I think we have a simular problem there. 3 out of 4 WU was a fail from station at work. Going to try 5.10.45.

No. XP has to have a different problem. Look for overheating (when was the last time the dust bunnies were cleaned out), conflicts with the Anti Virus scanner, overclocking (not likely in a work environment), bad RAM, and a failing Hard Disk.

---

BOINC WIKI

Where did you install BOINC to?
The default directory c:\\program files\\BOINC ?
Or did you install it to C:\\BOINC ?

If to the default directory, could you at least try to uninstall BOINC from there, then install to c:\\boinc and try again?
(You can uninstall BOINC, move the remaining BOINC directory with all sub-directories to C:\\BOINC, then reinstall BOINC to that new directory. This way you won't lose any new work you downloaded or the projects you're attached to).

By default Vista doesn't allow programs to write to directories in c:\\program files\\ .. since BOINC is writing to disk a lot of the time, this could give trouble.

This is correct! I installed it on: C:\\Program Files\\BOINC. Strange thing is for now only big WU are send in correctly e.t.a 3 hour of work at 72 creditpoints, the small ones, I saw one time a WU request for only 968 sec. of work, it crashed directly after 1.14%!

You are probably hitting the conflict between Boinc and VISTA UAC. Vista does not allow writes to the C:\\Program files\\ directory tree unless elevated priveleges are granted first. This does not happen with BOINC V5, so, BOINC fails every write to its data. The applications fail every write to their data...

Please:
Uninstall BOINC.
Move the ENTIRE BOINC directory tree from c:\\Program Files\\BOINC\\ to c:\\BOINC\\
Install the same or newer version of BOINC to c:\\BOINC\\

This is required to get BOINC V5 5o work on Vista. V6 splits the BOINC core executables and dlls from the project executables and all of the data. However, V6 is not even in Alpha testing yet.

Thx for the tip. I have 2 more WU to crunch e.t.a. today, so I'll try to move them to a higher Subdir. Does this count for my XP pc too? At work we use XP prof. SP2. I think we have a simular problem there. 3 out of 4 WU was a fail from station at work. Going to try 5.10.45.

No. XP has to have a different problem. Look for overheating (when was the last time the dust bunnies were cleaned out), conflicts with the Anti Virus scanner, overclocking (not likely in a work environment), bad RAM, and a failing Hard Disk.

Hmmm...Intel(R) Pentium(R) 4 CPU 3.00GHz [x86 Family 15 Model 2 Stepping 9] This is the pc I use at work, strange, it's a single CPU but BOINC said 2 CPU onboard...could it be a "co-CPU" (I think it was a swapfile) on the mainboard that caused the problem? To be sure I adjusted the count of CPU in BOINC (was 16) to only 1. This should do the trick. This is rated as an error between keyboard and chair..:))...LOL..Even a professional, like me, makes mistakes..:p. Dumb, Dumber, ME. Thanks for your help.

---

To boldly go where no human has gone before!

Hmmm...Intel(R) Pentium(R) 4 CPU 3.00GHz [x86 Family 15 Model 2 Stepping 9] This is the pc I use at work, strange, it's a single CPU but BOINC said 2 CPU onboard...

A Pentium 4 3GHz CPU does Hyper-Threading, meaning that it has one physical CPU and a virtual one. You can read here in wikipedia more about what it does. BOINC will recognize the 'extra' CPU as long as it is enabled in the BIOS and supported by the operating system.

---

Hmmm...Intel(R) Pentium(R) 4 CPU 3.00GHz [x86 Family 15 Model 2 Stepping 9] This is the pc I use at work, strange, it's a single CPU but BOINC said 2 CPU onboard...

A Pentium 4 3GHz CPU does Hyper-Threading, meaning that it has one physical CPU and a virtual one. You can read here in wikipedia more about what it does. BOINC will recognize the 'extra' CPU as long as it is enabled in the BIOS and supported by the operating system.

Thanks!
Hyper-threading has to be the cause of it, because I reported 2 WU packages in to day, without problems now. Anybody using Hyper-threading, and have the same experience?

---

To boldly go where no human has gone before!

Hmmm...Intel(R) Pentium(R) 4 CPU 3.00GHz [x86 Family 15 Model 2 Stepping 9] This is the pc I use at work, strange, it's a single CPU but BOINC said 2 CPU onboard...

A Pentium 4 3GHz CPU does Hyper-Threading, meaning that it has one physical CPU and a virtual one. You can read here in wikipedia more about what it does. BOINC will recognize the 'extra' CPU as long as it is enabled in the BIOS and supported by the operating system.

Thanks!
Hyper-threading has to be the cause of it, because I reported 2 WU packages in to day, without problems now. Anybody using Hyper-threading, and have the same experience?

Don't go thinking that it has to be user error all the time here is a link for everyone to look at

http://setiathome.berkeley.edu/workunit.php?wuid=234798380

everyone that proccessed this WU got the same results in different times I fail to think that this many people could have Hyper-Threading on all of their machines, I know I don't! Just something to ponder. I was getting ready to send this link to you anyway Ageless to see what you thought when I ran across this post. Maybe someone needs to look into this, not really sure why one speific work unit is causing access failures, doesn't make a whole lot of sense to me.

Hmmm...Intel(R) Pentium(R) 4 CPU 3.00GHz [x86 Family 15 Model 2 Stepping 9] This is the pc I use at work, strange, it's a single CPU but BOINC said 2 CPU onboard...

A Pentium 4 3GHz CPU does Hyper-Threading, meaning that it has one physical CPU and a virtual one. You can read here in wikipedia more about what it does. BOINC will recognize the 'extra' CPU as long as it is enabled in the BIOS and supported by the operating system.

Thanks!
Hyper-threading has to be the cause of it, because I reported 2 WU packages in to day, without problems now. Anybody using Hyper-threading, and have the same experience?

Don't go thinking that it has to be user error all the time here is a link for everyone to look at

http://setiathome.berkeley.edu/workunit.php?wuid=234798380

everyone that proccessed this WU got the same results in different times I fail to think that this many people could have Hyper-Threading on all of their machines, I know I don't! Just something to ponder. I was getting ready to send this link to you anyway Ageless to see what you thought when I ran across this post. Maybe someone needs to look into this, not really sure why one speific work unit is causing access failures, doesn't make a whole lot of sense to me.

That one of the 13fe08ac WU's that were produced with a bad header by a rogue splitter. More discussion in Number Crunching here

F.

---

Hmmm...Intel(R) Pentium(R) 4 CPU 3.00GHz [x86 Family 15 Model 2 Stepping 9] This is the pc I use at work, strange, it's a single CPU but BOINC said 2 CPU onboard...

A Pentium 4 3GHz CPU does Hyper-Threading, meaning that it has one physical CPU and a virtual one. You can read here in wikipedia more about what it does. BOINC will recognize the 'extra' CPU as long as it is enabled in the BIOS and supported by the operating system.

Thanks!
Hyper-threading has to be the cause of it, because I reported 2 WU packages in to day, without problems now. Anybody using Hyper-threading, and have the same experience?

Don't go thinking that it has to be user error all the time here is a link for everyone to look at

http://setiathome.berkeley.edu/workunit.php?wuid=234798380

everyone that proccessed this WU got the same results in different times I fail to think that this many people could have Hyper-Threading on all of their machines, I know I don't! Just something to ponder. I was getting ready to send this link to you anyway Ageless to see what you thought when I ran across this post. Maybe someone needs to look into this, not really sure why one speific work unit is causing access failures, doesn't make a whole lot of sense to me.

That one of the 13fe08ac WU's that were produced with a bad header by a rogue splitter. More discussion in Number Crunching here

F.

Many thanx every one, most of all rq2000 and Fred, thought it was a problem of the work pc, but had the same problem with the WU at home. So I can use Hyper-threading at work without problems now. Maybe worth of making a ticket out of this.

---

To boldly go where no human has gone before!

Maybe worth of making a ticket out of this.

Trac tickets are only for the BOINC developers. The workunit issue is a SETI@Home problem and the SETI Admins have been made aware of the problem. Unfortunately there's not much that can be done once the workunits are sent out to hosts. They simply have to work their way through the system.

---

Maybe worth of making a ticket out of this.

Trac tickets are only for the BOINC developers. The workunit issue is a SETI@Home problem and the SETI Admins have been made aware of the problem. Unfortunately there's not much that can be done once the workunits are sent out to hosts. They simply have to work their way through the system.

Thanks anyway for your help! We will live with it..:))

---

To boldly go where no human has gone before!