And now for something completely different

[tes1900]

This Problem may be out of place or not. Instead of a particular WU causing problems it is the amount of fold that causes the problems…let me explain:
I am using F@H6.3 -smp and I to date I have only received two sizes of project 500K projects and 2000K projects. The 500K projects are of no problem it is the 2000K project that are the problem. Even the 2000K projects run well except at the point where they send the completed project back to Stanford that is where I get a BSOD. I have never been sitting at the computer when this happens but I do see the results and I know the completed package is being sent because my work units continues to climb.
If someone can give me ea direction which I might follow? Maybe a different topic area? I have thought that it might be the configuration of the program, in actually I have been considering deleting the entire folder, making a new folder and downloading the whole program anew.
Thank you in advance,
Tom

[P5-133XL]

Blue screens are a symptom of something else than a folding configuration issue. If it is actually associated with folding normally the problem is CPU temps or bad RAM. It might help diagnose a folding issue if you actualy posted the fahlog.txt file.

[7im]

Yep. BSODs are a windows/hardware related problem. If this was fah related, it would BSOD the same place on all work units, not just the larger work units. For example, someone just fixed a BSOD by replacing memory: http://foldingforum.org/viewtopic.php?p=170540#p170540

Are you running out of hard drive space? Computer memory? Overclocked? What version of Windows? You'll need to post a lot more details, starting with your fahlog.txt showing where the computer BSODs. Posting Project:RCG numbers from each type of WU might also help.