I'm starting to think it's an overheating issue; I got MemTest from here: http://hcidesign.com/ and ran it for an hour checking all RAM that isn't in use by Windows and my machine suddenly rebooted after reaching 15% coverage. I didn't see any errors in the error log though, and Windows was unable to point any fingers after automatically rebooting. What's weirder is that I purposely disabled automatic restart on STOP errors, so maybe the restarting hardware is a failsafe in case of overheating?

Also, according to Green Power Center diagnostics, my CPU temp is 65C and my RAM's IOH temp is 80C. That does seem to be a bit hot.

To stop BOINC running, either suspend BOINC using BOINC Manager, or set the BOINC service to "disabled".

STOP: 0x0000001E (parameter, parameter, parameter, parameter) KMODE_EXCEPTION_NOT_HANDLED

This means that a kernel-mode exception was not handled. This totally exonerates BOINC (but we ruled that out already). I strongly suspect a memory issue - however, this precise error is completely generic and rather unhelpful.

aeridus, if you get a different STOP message (which is quite likely) please post that, too. It may be more specific.

Hardware people: this one's all yours, now. There is nothing further I can do to help.

Thanks, I've completely disabled BOINC for the time being to narrow down the problem. I agree that most of the errors I've seen are extremely generic so my only guess is overheating, which is mainly being triggered by BOINC's calculations. Under normal load, my computer runs at 36C for the CPU and 66C for the RAM, and jumps to 65C for the CPU and 80C for the RAM when running BOINC. I'll try running MemTest again now that I'm sure BOINC isn't running at the same time.

Here's the event log information about the sudden crash, which is almost identical to all of the other crashes:

Log Name: System
Source: EventLog
Date: 5/20/2009 7:09:27 PM
Event ID: 6008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Bigfoot-Ninja
Description:
The previous system shutdown at 7:05:28 PM on 5/20/2009 was unexpected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6008</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-05-20T23:09:27.000Z" />
<EventRecordID>44859</EventRecordID>
<Channel>System</Channel>
<Computer>Bigfoot-Ninja</Computer>
<Security />
</System>
<EventData>
<Data>7:05:28 PM</Data>
<Data>5/20/2009</Data>
<Data>
</Data>
<Data>
</Data>
<Data>150</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>D907050003001400130005001C006D00D907050003001400170005001C006D00600900003C00000001000000600900000
0000000B00400000100000000000000</Binary>
</EventData>
</Event>

Log Name: Security
Source: Microsoft-Windows-Eventlog
Date: 5/20/2009 7:09:29 PM
Event ID: 1101
Task Category: Event processing
Level: Error
Keywords: Audit Success
User: N/A
Computer: Bigfoot-Ninja
Description:
Audit events have been dropped by the transport. The real time backup file was corrupt due to improper shutdown.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Eventlog" Guid="{fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}" />
<EventID>1101</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>101</Task>
<Opcode>0</Opcode>
<Keywords>0x4020000000000000</Keywords>
<TimeCreated SystemTime="2009-05-20T23:09:29.359Z" />
<EventRecordID>44014</EventRecordID>
<Correlation />
<Execution ProcessID="232" ThreadID="528" />
<Channel>Security</Channel>
<Computer>Bigfoot-Ninja</Computer>
<Security />
</System>
<UserData>
<AuditEventsDropped xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2004/08/windows/eventlog">
<Reason>34</Reason>
</AuditEventsDropped>
</UserData>
</Event>

Ok ... with BOINC out of the way the next time you run Prime, select the first option ... small FFTs which will heat up your CPU faster and when it BSODs ... towards the bottom on the message there will be a long series of numbers ... at the beggining it will likely will say 0124 and while that is still very generic it will point away from issues with the CPU itself (which is a good thing). If you do want to run WCG while you are waiting for your HSF you can tell BOINC to "Use at most 60 percent of CPU time". While this won't fix anything it will cycle your CPU up for 6 seconds and then cycle down for 4, then back up for 6 ... rinse and repeat. This should keep you cool enough to stay up and running ... definately turn the fan on high (not sure where in your BIOS but it should be in there somewhere).

you can use SpeedFan to check the temps on the CPU (http://www.almico.com/speedfan.php)
or the hardware monitor from CPUID (http://www.cpuid.com/hwmonitor.php)