Going by what Rom said perhaps you need to run "ipconfig /flushdns" from a windows command box. Just a guess though........more memory couldn't hurt either. With Windows more memory is better.

---

Boinc....Boinc....Boinc....Boinc....

If I understand you correctly, the BIOS needs to detect that I have my DIMMs as dual channel, vs. single channel as is current? I'll try that before I take the RAM back for exchange. Thanks Hans.... (-:<

It depends. If you manually changed your RAM settings then resetting the CMOS might help.

Regards Hans

Well, I tried it for about an hour and a half, about 10 times clearing the CMOS and it would not allow me into setup. I put the old RAM back in, cleared the CMOS and I was allowed into setup. The PC is running fine again, with the old RAM.

The new RAM is detected just fine, says it's in dual channel, gives the correct amount of RAM. It detects my devices and sets them up. Then says the settings are wrong because of date/time. Hit F1 to enter setup. I hit F1, nothing, won't bring up setup. Go figure.... )-:<

The crash you are experiencing happens when something goes wrong with looking up a DNS entry.

Curl spawns another thread to do a gethostbyname lookup and for some reason curl is confused about how to handle the response.

Ok.... So, I know what DNS is, I know what gethostbyname is, but I have no idea what Curl is, except that which the ladies do to their hair now and then.

So, how do I fix this? Or is this something that needs fixin' on your end....? \\-:<

---

CAPT Siran d'Vel'nahr XO - L L & P _\\//
USS Vre'kasht NCC-33187
Winders 10 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

If I understand you correctly, the BIOS needs to detect that I have my DIMMs as dual channel, vs. single channel as is current? I'll try that before I take the RAM back for exchange. Thanks Hans.... (-:<

It depends. If you manually changed your RAM settings then resetting the CMOS might help.

Regards Hans

Well, I tried it for about an hour and a half, about 10 times clearing the CMOS and it would not allow me into setup. I put the old RAM back in, cleared the CMOS and I was allowed into setup. The PC is running fine again, with the old RAM.

The new RAM is detected just fine, says it's in dual channel, gives the correct amount of RAM. It detects my devices and sets them up. Then says the settings are wrong because of date/time. Hit F1 to enter setup. I hit F1, nothing, won't bring up setup. Go figure.... )-:<

The crash you are experiencing happens when something goes wrong with looking up a DNS entry.

Curl spawns another thread to do a gethostbyname lookup and for some reason curl is confused about how to handle the response.

---

----- Rom
BOINC Development Team, U.C. Berkeley
My Blog

If I understand you correctly, the BIOS needs to detect that I have my DIMMs as dual channel, vs. single channel as is current? I'll try that before I take the RAM back for exchange. Thanks Hans.... (-:<

It depends. If you manually changed your RAM settings then resetting the CMOS might help.

Regards Hans

Well, I tried it for about an hour and a half, about 10 times clearing the CMOS and it would not allow me into setup. I put the old RAM back in, cleared the CMOS and I was allowed into setup. The PC is running fine again, with the old RAM.

The new RAM is detected just fine, says it's in dual channel, gives the correct amount of RAM. It detects my devices and sets them up. Then says the settings are wrong because of date/time. Hit F1 to enter setup. I hit F1, nothing, won't bring up setup. Go figure.... )-:<

---

CAPT Siran d'Vel'nahr XO - L L & P _\\//
USS Vre'kasht NCC-33187
Winders 10 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

If I understand you correctly, the BIOS needs to detect that I have my DIMMs as dual channel, vs. single channel as is current? I'll try that before I take the RAM back for exchange. Thanks Hans.... (-:<

It depends. If you manually changed your RAM settings then resetting the CMOS might help.

Regards Hans

---

I stopped off, after work, and got a matched set of 512MB DDR400 Kingston RAM, 1GB. I pulled the box out, installed it, put the box back, hit the power switch, lights flashed on for a second than all went dead. I reseated the DIMMs, tried it again, with the same results. I repeated this 2 more times, same results. I pulled the new RAM, replaced it with my old RAM, and guess what? All's well.

The Label on the RAM package says PC3200 and DDR400 are one and the same. My MB takes PC3200 and below. The RAM is exactly the same as that installed in my newest box I built a couple months ago. I'm thinking, bad RAM.... )-:<

Try resetting your CMOS. There should be a jumper on your mainboard.
Make sure that you follow the instructions: DONT power the board up when the reset jumper is in place.

You could also load the BIOS defaults while the old RAMs are installed.

Regards Hans

If I understand you correctly, the BIOS needs to detect that I have my DIMMs as dual channel, vs. single channel as is current? I'll try that before I take the RAM back for exchange. Thanks Hans.... (-:<

---

CAPT Siran d'Vel'nahr XO - L L & P _\\//
USS Vre'kasht NCC-33187
Winders 10 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

I stopped off, after work, and got a matched set of 512MB DDR400 Kingston RAM, 1GB. I pulled the box out, installed it, put the box back, hit the power switch, lights flashed on for a second than all went dead. I reseated the DIMMs, tried it again, with the same results. I repeated this 2 more times, same results. I pulled the new RAM, replaced it with my old RAM, and guess what? All's well.

The Label on the RAM package says PC3200 and DDR400 are one and the same. My MB takes PC3200 and below. The RAM is exactly the same as that installed in my newest box I built a couple months ago. I'm thinking, bad RAM.... )-:<

Try resetting your CMOS. There should be a jumper on your mainboard.
Make sure that you follow the instructions: DONT power the board up when the reset jumper is in place.

You could also load the BIOS defaults while the old RAMs are installed.

Regards Hans

---

....

....

So, the bottom line is this:

BOINC will remain on hiatus until there is a new version of it and/or SETI "enhanced" released. I am NOT going to continually upload errored results. That is counter productive. Hopefully, since I haven't seen Rom back here yet, he is hard at work trying to figure out what is going on.... )-:<

One thing to check, if you haven't (I've not gone thru the details of all the posts), is that you might be short on real/virtual memory.

Once ANY app encounters an error, it, if's it's a good program, should report it, but many do not handle it well. That can result is junk being scattered in memory, impacting losts of stuff on the machine.

I'd suggest using task manager in windows to keep an eye on things, or perfmon to watch things over time.

Much of what you describe could be explained with a "low memory" condition in windows. It might not show up in RAM tests, but only when the computer is busy with your normal mix of applications.

Hmmmm.... Now that makes sense, judging from what I've been seeing these past few days. Maybe it's time I up'ed it to 1 GB ram. Thanks AZ.... (-:<

I went from 384k to 1Gb a few weeks back (It's on Win2k on that machine), and it cleared up a bunch of "weird problems" (Weird and Windows both start with W, but 'nuff said).

Got a 1GB stick for ~ $100 US locally. Windoze is kind of poor when another app does weird things, and no Memtest app in the world will really find it.

Dang.. I had a machine that had a 640k limit on memory, and never thought I'd use it all!

Well, the best laid plans....

I stopped off, after work, and got a matched set of 512MB DDR400 Kingston RAM, 1GB. I pulled the box out, installed it, put the box back, hit the power switch, lights flashed on for a second than all went dead. I reseated the DIMMs, tried it again, with the same results. I repeated this 2 more times, same results. I pulled the new RAM, replaced it with my old RAM, and guess what? All's well.

The Label on the RAM package says PC3200 and DDR400 are one and the same. My MB takes PC3200 and below. The RAM is exactly the same as that installed in my newest box I built a couple months ago. I'm thinking, bad RAM.... )-:<

---

CAPT Siran d'Vel'nahr XO - L L & P _\\//
USS Vre'kasht NCC-33187
Winders 10 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Rick, the 0xc0000005 errors under BOINC are essentially Windows errors, not BOINC specific. Most of the time they are about memory errors, or at trying to occupy memory that the science application doesn't own. In Windows this would be an "memory access violation".

This can be caused by anything from faulty RAM, an incorrect/corrupt device driver, poorly written/updated software and more commonly under Windows XP Service pack 2, malware/adware installations.

OK! Here's the situation, again:

I get home and my screen is full of error messages. Everytime Beta tried to start on a new WU, it would error. It finally settled down. I let it go for about 45 minutes. I clicked back to the XP box and the screesaver [blank] had kicked in. I entered my password and tried to disable the screensaver, with a right click on the desktop, and all I got were error messages that the program had to stop. I couldn't even run msconfig to disable BOINC. I rebooted and got an error message about auto updates running into an error. I quickly shut down BOINC and was able to get msconfig to run. I disabled BOINC, rebooted, and guess what? Everything is running just hunky dorey.

I ran my Combat Flight Simulator last night for about 2 hours without a single problem. As long as BOINC is NOT running, the machine runs just fine. No one is going to convince me that that is NOT a problem with BOINC/SETI "enhanced". If it were, I would continually have the problems whether BOINC/SETI "enhanced" was running or not. If I was having the problems when running my simulator, and then no problems when not running it, that would tell me that there was a problem with the simulator.

I ran a memory utility on my memory yesterday and the memory passed. If BOINC/SETI "enhanced" is trying to access memory that it doesn't "own", then that is a problem with BOINC/SETI "enhanced". If, as has been said, the problem is Windows, then maybe it's time I send Windows to the trashcan and put FreeBSD on that machine too. Oh wait! I have it on my other 2 machines and they can't run SETI "enhanced", ohhhh myyyyy.

So, the bottom line is this:

BOINC will remain on hiatus until there is a new version of it and/or SETI "enhanced" released. I am NOT going to continually upload errored results. That is counter productive. Hopefully, since I haven't seen Rom back here yet, he is hard at work trying to figure out what is going on.... )-:<

One thing to check, if you haven't (I've not gone thru the details of all the posts), is that you might be short on real/virtual memory.

Once ANY app encounters an error, it, if's it's a good program, should report it, but many do not handle it well. That can result is junk being scattered in memory, impacting losts of stuff on the machine.

I'd suggest using task manager in windows to keep an eye on things, or perfmon to watch things over time.

Much of what you describe could be explained with a "low memory" condition in windows. It might not show up in RAM tests, but only when the computer is busy with your normal mix of applications.

Hmmmm.... Now that makes sense, judging from what I've been seeing these past few days. Maybe it's time I up'ed it to 1 GB ram. Thanks AZ.... (-:<

I went from 384k to 1Gb a few weeks back (It's on Win2k on that machine), and it cleared up a bunch of "weird problems" (Weird and Windows both start with W, but 'nuff said).

Got a 1GB stick for ~ $100 US locally. Windoze is kind of poor when another app does weird things, and no Memtest app in the world will really find it.

Dang.. I had a machine that had a 640k limit on memory, and never thought I'd use it all!

---

Rick, the 0xc0000005 errors under BOINC are essentially Windows errors, not BOINC specific. Most of the time they are about memory errors, or at trying to occupy memory that the science application doesn't own. In Windows this would be an "memory access violation".

This can be caused by anything from faulty RAM, an incorrect/corrupt device driver, poorly written/updated software and more commonly under Windows XP Service pack 2, malware/adware installations.

OK! Here's the situation, again:

I get home and my screen is full of error messages. Everytime Beta tried to start on a new WU, it would error. It finally settled down. I let it go for about 45 minutes. I clicked back to the XP box and the screesaver [blank] had kicked in. I entered my password and tried to disable the screensaver, with a right click on the desktop, and all I got were error messages that the program had to stop. I couldn't even run msconfig to disable BOINC. I rebooted and got an error message about auto updates running into an error. I quickly shut down BOINC and was able to get msconfig to run. I disabled BOINC, rebooted, and guess what? Everything is running just hunky dorey.

I ran my Combat Flight Simulator last night for about 2 hours without a single problem. As long as BOINC is NOT running, the machine runs just fine. No one is going to convince me that that is NOT a problem with BOINC/SETI "enhanced". If it were, I would continually have the problems whether BOINC/SETI "enhanced" was running or not. If I was having the problems when running my simulator, and then no problems when not running it, that would tell me that there was a problem with the simulator.

I ran a memory utility on my memory yesterday and the memory passed. If BOINC/SETI "enhanced" is trying to access memory that it doesn't "own", then that is a problem with BOINC/SETI "enhanced". If, as has been said, the problem is Windows, then maybe it's time I send Windows to the trashcan and put FreeBSD on that machine too. Oh wait! I have it on my other 2 machines and they can't run SETI "enhanced", ohhhh myyyyy.

So, the bottom line is this:

BOINC will remain on hiatus until there is a new version of it and/or SETI "enhanced" released. I am NOT going to continually upload errored results. That is counter productive. Hopefully, since I haven't seen Rom back here yet, he is hard at work trying to figure out what is going on.... )-:<

One thing to check, if you haven't (I've not gone thru the details of all the posts), is that you might be short on real/virtual memory.

Once ANY app encounters an error, it, if's it's a good program, should report it, but many do not handle it well. That can result is junk being scattered in memory, impacting losts of stuff on the machine.

I'd suggest using task manager in windows to keep an eye on things, or perfmon to watch things over time.

Much of what you describe could be explained with a "low memory" condition in windows. It might not show up in RAM tests, but only when the computer is busy with your normal mix of applications.

Hmmmm.... Now that makes sense, judging from what I've been seeing these past few days. Maybe it's time I up'ed it to 1 GB ram. Thanks AZ.... (-:<

---

CAPT Siran d'Vel'nahr XO - L L & P _\\//
USS Vre'kasht NCC-33187
Winders 10 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Rick, the 0xc0000005 errors under BOINC are essentially Windows errors, not BOINC specific. Most of the time they are about memory errors, or at trying to occupy memory that the science application doesn't own. In Windows this would be an "memory access violation".

This can be caused by anything from faulty RAM, an incorrect/corrupt device driver, poorly written/updated software and more commonly under Windows XP Service pack 2, malware/adware installations.

OK! Here's the situation, again:

I get home and my screen is full of error messages. Everytime Beta tried to start on a new WU, it would error. It finally settled down. I let it go for about 45 minutes. I clicked back to the XP box and the screesaver [blank] had kicked in. I entered my password and tried to disable the screensaver, with a right click on the desktop, and all I got were error messages that the program had to stop. I couldn't even run msconfig to disable BOINC. I rebooted and got an error message about auto updates running into an error. I quickly shut down BOINC and was able to get msconfig to run. I disabled BOINC, rebooted, and guess what? Everything is running just hunky dorey.

I ran my Combat Flight Simulator last night for about 2 hours without a single problem. As long as BOINC is NOT running, the machine runs just fine. No one is going to convince me that that is NOT a problem with BOINC/SETI "enhanced". If it were, I would continually have the problems whether BOINC/SETI "enhanced" was running or not. If I was having the problems when running my simulator, and then no problems when not running it, that would tell me that there was a problem with the simulator.

I ran a memory utility on my memory yesterday and the memory passed. If BOINC/SETI "enhanced" is trying to access memory that it doesn't "own", then that is a problem with BOINC/SETI "enhanced". If, as has been said, the problem is Windows, then maybe it's time I send Windows to the trashcan and put FreeBSD on that machine too. Oh wait! I have it on my other 2 machines and they can't run SETI "enhanced", ohhhh myyyyy.

So, the bottom line is this:

BOINC will remain on hiatus until there is a new version of it and/or SETI "enhanced" released. I am NOT going to continually upload errored results. That is counter productive. Hopefully, since I haven't seen Rom back here yet, he is hard at work trying to figure out what is going on.... )-:<

One thing to check, if you haven't (I've not gone thru the details of all the posts), is that you might be short on real/virtual memory.

Once ANY app encounters an error, it, if's it's a good program, should report it, but many do not handle it well. That can result is junk being scattered in memory, impacting losts of stuff on the machine.

I'd suggest using task manager in windows to keep an eye on things, or perfmon to watch things over time.

Much of what you describe could be explained with a "low memory" condition in windows. It might not show up in RAM tests, but only when the computer is busy with your normal mix of applications.

---

Rick, the 0xc0000005 errors under BOINC are essentially Windows errors, not BOINC specific. Most of the time they are about memory errors, or at trying to occupy memory that the science application doesn't own. In Windows this would be an "memory access violation".

This can be caused by anything from faulty RAM, an incorrect/corrupt device driver, poorly written/updated software and more commonly under Windows XP Service pack 2, malware/adware installations.

OK! Here's the situation, again:

I get home and my screen is full of error messages. Everytime Beta tried to start on a new WU, it would error. It finally settled down. I let it go for about 45 minutes. I clicked back to the XP box and the screesaver [blank] had kicked in. I entered my password and tried to disable the screensaver, with a right click on the desktop, and all I got were error messages that the program had to stop. I couldn't even run msconfig to disable BOINC. I rebooted and got an error message about auto updates running into an error. I quickly shut down BOINC and was able to get msconfig to run. I disabled BOINC, rebooted, and guess what? Everything is running just hunky dorey.

I ran my Combat Flight Simulator last night for about 2 hours without a single problem. As long as BOINC is NOT running, the machine runs just fine. No one is going to convince me that that is NOT a problem with BOINC/SETI "enhanced". If it were, I would continually have the problems whether BOINC/SETI "enhanced" was running or not. If I was having the problems when running my simulator, and then no problems when not running it, that would tell me that there was a problem with the simulator.

I ran a memory utility on my memory yesterday and the memory passed. If BOINC/SETI "enhanced" is trying to access memory that it doesn't "own", then that is a problem with BOINC/SETI "enhanced". If, as has been said, the problem is Windows, then maybe it's time I send Windows to the trashcan and put FreeBSD on that machine too. Oh wait! I have it on my other 2 machines and they can't run SETI "enhanced", ohhhh myyyyy.

So, the bottom line is this:

BOINC will remain on hiatus until there is a new version of it and/or SETI "enhanced" released. I am NOT going to continually upload errored results. That is counter productive. Hopefully, since I haven't seen Rom back here yet, he is hard at work trying to figure out what is going on.... )-:<

---

CAPT Siran d'Vel'nahr XO - L L & P _\\//
USS Vre'kasht NCC-33187
Winders 10 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Turn OFF screensaver

I don't run the screen saver....

---

CAPT Siran d'Vel'nahr XO - L L & P _\\//
USS Vre'kasht NCC-33187
Winders 10 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Rick, the 0xc0000005 errors under BOINC are essentially Windows errors, not BOINC specific. Most of the time they are about memory errors, or at trying to occupy memory that the science application doesn't own. In Windows this would be an "memory access violation".

This can be caused by anything from faulty RAM, an incorrect/corrupt device driver, poorly written/updated software and more commonly under Windows XP Service pack 2, malware/adware installations.

---

This has been posted on the BOINC (http://boinc.berkeley.edu/) home page:

June 7, 2006
Windows users: if BOINC applications are repeatedly crashing on your computer, it's possibly that you need to upgrade to the latest version of DirectX.

Any of you not using the latest version of DirectX?

Well, at this point in time, I'm willing to try most anything to get back to crunching. I did the DirectX upgrade. I have reactivated BOINC and set Beta to get new work. I will hold off on SETI and Einstein to see how things go with Beta first. If Beta shows no signs of erroring, then I will try SETI and Einstein. I hope this works. Thanks.... (-:<

---

CAPT Siran d'Vel'nahr XO - L L & P _\\//
USS Vre'kasht NCC-33187
Winders 10 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

This has been posted on the BOINC (http://boinc.berkeley.edu/) home page:

June 7, 2006
Windows users: if BOINC applications are repeatedly crashing on your computer, it's possibly that you need to upgrade to the latest version of DirectX.

Any of you not using the latest version of DirectX?

---

SL

snipped....
[/list]
I have "Keep in memory...." set to "no".
I do remember seeing that MemTest86 reported my Ram and FSB at only 199Mhz when I have an 800Mhz motherboard. Maybe the CMOS idea isn't so far fetched. I'll look at it when I'm finished with this reply.
That computer is only about a year and a half old, with all new components installed at build time.

bit more snip....

Going to check my CMOS now.... (-:<

The fsb at 200MHz is correct it is only marketing speak to say it runs at 800, it has to do with Double Data Rate (DDR) and number of bits.

Andy

....

....

Well, sorry it took so long to get back, had some errands to run and had to clean my floppy drive so I could make the disk for MemTest86.

Ok, here's the scoop:

• I have disabled all BOINC and BOINC related apps, BoincView etc.
  
• I ran Kaspersky, a suite of apps for virus, ad/spyware, the whole nine yards. It reported everything clean.
  
• I downloaded MemTest86, and made the floppy disk for it and ran it. Memory passes.
  
• Since disabling BOINC, I have seen no problems at all, it's even running better, faster, stronger....
  

I have "Keep in memory...." set to "no".
I do remember seeing that MemTest86 reported my Ram and FSB at only 199Mhz when I have an 800Mhz motherboard. Maybe the CMOS idea isn't so far fetched. I'll look at it when I'm finished with this reply.
That computer is only about a year and a half old, with all new components installed at build time.

@Tony:
I do not run a screensaver unless I'm away for an extended period, such as when I'm at work. I do set the blank one, no graphics. I also have the *nix box shut off the monitor.

This is just too weird. I didn't start having problems until the "enhanced" version was released. I have heard of others having to re-format their HD and re-install the OS and software because of "enhanced". Since my XP box is running just fine now, without any memory problems and without any BOINC running, I have to be suspicious of the "enhanced" app. I was running v5.4.9 of the manager long before the "enhanced" app came out.

Going to check my CMOS now.... (-:<

Try another project and see what happens.

The problem happens when running Einstein as well as Beta and SETI. I have returned a boat load of errored results for all three projects. Thanks for the assist, oh Gaseous One.... (-:<

---

CAPT Siran d'Vel'nahr XO - L L & P _\\//
USS Vre'kasht NCC-33187
Winders 10 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Hi Jim,

The only popups I'm seeing is "[insert client app here] has encounter a problem and needs to shut down. We regret the inconvenience". The other I see is something about writing or not writing to a memory address. I don't remember which it is now. I still have one Beta WU crunching, all others have gone to their respective projects as errored out. Let me see what I have in my error logs and get back to you.... )-:<

Hi Siran,
I've looked at your wu's and man are they a weird lot! Do you have "keep work units in memory when preempted" or whatever it says set to "yes"? Are you stopping and starting either Windows or boinc? the reason I'm asking is I see some wu's that crunched perfectly with only a single entry in the log, while others have several log entries but still crunched, then others bombed out with either no log entries or from one to several! So it's not consistent. I'm beginning to agree with Mookie that you might have a memory problem (which your above error message points to) or your computer is overheating, or possibly something has happened to reset your cmos settings and thrown off your memory timings?
Just throwing around some ideas! Good luck!

Well, sorry it took so long to get back, had some errands to run and had to clean my floppy drive so I could make the disk for MemTest86.

Ok, here's the scoop:

• I have disabled all BOINC and BOINC related apps, BoincView etc.
  
• I ran Kaspersky, a suite of apps for virus, ad/spyware, the whole nine yards. It reported everything clean.
  
• I downloaded MemTest86, and made the floppy disk for it and ran it. Memory passes.
  
• Since disabling BOINC, I have seen no problems at all, it's even running better, faster, stronger....
  

I have "Keep in memory...." set to "no".
I do remember seeing that MemTest86 reported my Ram and FSB at only 199Mhz when I have an 800Mhz motherboard. Maybe the CMOS idea isn't so far fetched. I'll look at it when I'm finished with this reply.
That computer is only about a year and a half old, with all new components installed at build time.

@Tony:
I do not run a screensaver unless I'm away for an extended period, such as when I'm at work. I do set the blank one, no graphics. I also have the *nix box shut off the monitor.

This is just too weird. I didn't start having problems until the "enhanced" version was released. I have heard of others having to re-format their HD and re-install the OS and software because of "enhanced". Since my XP box is running just fine now, without any memory problems and without any BOINC running, I have to be suspicious of the "enhanced" app. I was running v5.4.9 of the manager long before the "enhanced" app came out.

Going to check my CMOS now.... (-:<

Try another project and see what happens.