When I open BOINC, it will reset my computer to BIOS. My computer has a lengthy start-up process, so I'm not happy about it.
I don't know when, exactly, but it's either resetting when the localclient connects or when the manager attempts to start work on one of the modules.
7.0.25 and I run all available resources.

I am running WinXP-32 and started having problems on 22 April. It was very sudden; I don't think I had downloaded new BOINC software, which leads me to believe that it is a work module that's failed.

Initial thoughts are its a hardware issue - prime suspects would be dust bunnies, failing power supply (possibly even a dodgy fan on ps) or suboptimal thermal paste between cpu & heatshink

---

CIC1=CC=C(C2=N[C@@H](CC(OC(C)(C)C)=O)C3=NN=C(C)N3C4=C2C(C)=C(C)S4)C=C1

Even Windows XP registers why it restarts. Check Start->(Control Panel->)Administrative Tools->Event Viewer. Check for red and yellow warnings around the time of your reboot.

---

It's not a CPU issue in the sense that I can run intensive games and the CPU / GPU are clocking 100% for hours on end. I think it's either compatibility between software or an issue with a work unit. The problem is, I can't even get close to having enough reaction time to Snooze before it resets the whole system.

Interesting alternate theory: Could it have something to do with Windows Time Service being unable to synchronize? If BOINC and my computer are at odds, could it be causing trouble?
Looking in the Event Viewer, I see only a few warnings, but a HUGE number of "Information" bubbles that mostly talk about warnings coming from ATI's Catalyst Control Center (CCC.exe).

It's not a CPU issue in the sense that I can run intensive games and the CPU / GPU are clocking 100% for hours on end.

The flaw here is that most games don't use the CPU extensions (MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX), while the projects science applications do. So if any project's application optimized towards any of the before extensions starts up and your CPU does not like that, it'll blue screen and reboot.

Check that Automatic restart is off:
Start->Run->type Sysdm.cpl and hit Enter, Advanced Tab, Start Up and Recovery->Settings->System Failure->Unmark "Automatically Restart"->OK->OK.

Then you have a good chance at seeing the BSOD if there is one.

Now, if there isn't a BSOD, but the system just reboots when it starts a certain project's science application, first try to figure out on which one it does this. It may well be that your power supply isn't feeding enough juice out and that it needs to be replaced.

---

Out of curiosity, is there a way to set the default project status to "Suspended"? Otherwise, I can't react quickly enough to do it inside the application.

Try the <start_delay> option in cc_config.xml. This file isn't installed by default; you'll have to create one in your BOINC data directory if you haven't done so already.

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

Sounds good, what's the syntax?
<start_delay>500.000000</start_delay> ?

If so, are there other lines that I should also put in? <project>, <user_name>, etc?

Sorry, OTHER than <cc_config> and <log_flags>.

New development: Turned off Auto-Restart and changed cc_config.xml to read:

"<cc_config>
<log_flags>
<start_delay>500.000000</start_delay>
<log_flags>
</cc_config>"

as requested. If the above code is correct, no changes in behavior, so it would be a hardware issue.

BSoD:

Bad_Pool_Header
[...]
Stop: 0x00000019 (0x00000020, 0xE49FD348, 0xE49FD418, 0x0C1A0801)

...If the above code is correct...

No, it's not. Did you read the linked document? ;-)

It should be

<cc_config>
    <options>
        <start_delay>500.000000</start_delay>
    </options>
</cc_config>

Your cc_config.xml should have caused several error messages. Did you place it in the BOINC data directory?

Gruß,
Gundolf

Bad_Pool_Header
[...]
Stop: 0x00000019 (0x00000020, 0xE49FD348, 0xE49FD418, 0x0C1A0801)

http://www.faultwire.com/solutions-fatal_error/BAD-POOL-HEADER-0x00000019-*1040.html?order=date

---

I stopped reading after the technical bit - didn't get down to the examples... Had somewhere to be Saturday.
I'll check it later today.

Another failure.
Is there any other way to tell whether it's a driver issue, other than updating drivers or rolling back to before the trouble happened?

Joined on 24 April, ATI released a new driver on 25 April, after I had been to the site several times and found my "newest" driver update was 28 March.

So that's how I'm going to tell when ATI releases new drivers... X-D

Thanks, everyone.