Folding crashes, but prime95 stable?

[VeoDigital]

As the title states, I have been folding and crashing, folding and crashing......yet I am dual prime95 stable. I pretty much fold all day, everyday, for the last 2 weeks or so, Im hooked, but more so because Alzheimers and MS seem to run in my family. Sometimes the system crashes after 10 hrs, sometimes after 48 hrs. I even went to stock speeds, and still crashing....Im beginning to think somethin is up. When I ran the F@H GUI, it never crashed. Is there any possible settings I may have wrong with the text version??? Im running two instances, both installed into two seperate directories and both active leading up to the crash or system reboot.

Target & Flags: C:\FAH\FAH502-Console.exe -local -advmethods -verbosity 9 -forceasm

Client.cfg

[settings]
username=VeoDigital
team=11314
asknet=no
bigpackets=yes
machineid=1
local=4

[http]
active=no
host=localhost
port=8080
usereg=no

[core]
priority=96
cpuusage=98
disableassembly=no
checkpoint=10
ignoredeadlines=no

[power]
battery=no

[clienttype]
type=1

FAHlog (last few lines):

03:38:37] Timered checkpoint triggered.
[03:40:57] Writing local files
[03:40:57] Completed 4550000 out of 5000000 steps  (91)
[03:46:40] ***** Got a SIGTERM signal (2)

Folding@Home Client Shutdown.

[DemonicInflu]

That just means u closed it lol.

[VeoDigital]

Just trying to post any info that might help solve my issues.

Warning:
 By using the -forceasm flag, you are overriding
 safeguards in the program. If you did not intend to
 do this, please restart the program without -forceasm.
 If work units are not completing fully (and particularly
 if your machine is overclocked), then please discontinue
 use of the flag.

[DSwarP]

lol

Yeah, that just means you either closed the client/gui or whatever, OR you shut down the PC...

ALSO, do you have the machine ID different on each instance? And do you have dual core? If not, then only run one instance...

[KillerBeagle]

So the entire system is crashing (as in rebooting)? Since it happens with no overclocking as well, maybe the system is overheating.

When you ran the GUI and it never crashed, were you running 2 instances (1 gui and 1 console) or just the GUI?

[Rhiyddun]

Har! I didn't think Windows even knew what SIGTERM was. About the original question, I have indeed had it not fold on a p95 stable system. But what you tend to get for OC-related issues is EARLY WORK UNIT END and this insulting message about instability. It typically says something about a constraint being violated, like some molecules/atoms being closer or further apart than is possible, cause your FPU started returning garbage. If you ever see one of those, STOP immediately and get your system stable, because I noticed it feeds that system real trashy WU's for a while after such a failure, presumably to check your system out.