I have had several crashes in early hand folding (I'm trying to extend the sheet, still haven't gotten that far). Nothing mutated, Less precise wiggle is checked, I haven't changed the filter/constraint settings, I have banded atoms, I'm doing a local wiggle on my extended strand. RMS = 0.0

CB: 0 1
dof_atom1 atomno= 3 rsd= 1
atom1 atomno= 1 rsd= 1
atom2 atomno= 2 rsd= 1
atom3 atomno= 5 rsd= 1
atom4 atomno= 6 rsd= 1
THETA1 1.#QNAN
THETA3 1.#QNAN
PHI2 1.#QNAN

ERROR: AtomTree::torsion_angle_dof_id: angle range error
ERROR:: Exit from: ..\..\..\source\src\core\kinematics\AtomTree.cc line: 783

Okay now I've reloaded my puzzle, and did a local wiggle...AND IT WON'T STOP. Actually, it looks like it did stop, then kept going. Half the UI thinks it stopped, half thinks a function in running. I was able to click save and exit.

I suppose that there will come a time when the powers that be
will notice that 814 is, as currently configured, unplayable for
a great many people. I suppose further that they would care to inform
the humble players on the ground, what exactly they are doing about it!
But I for one am not holding my breath.

Problem signature:
Problem Event Name: APPCRASH
Application Name: Foldit.exe
Application Version: 0.0.0.0
Application Timestamp: 4e761405
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.18229
Fault Module Timestamp: 51fb1116
Exception Code: e06d7363
Exception Offset: 0000c41f
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1043
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

LOG.TXT:
blahblah
Autosaved puzzles/0000996338/0000108474/evo/autosave.ir_solution.
Autosaved puzzles/0000996338/0000108474/evo/autosave-best-improver.ir_solution.
Autosaved puzzles/0000996338/0000108474/evo/autosave-recentbest-improver.ir_solution.
Autosaved puzzles/0000996338/0000108474/evo/autosave-creditbest-improver.ir_solution.
protocols.indexed_structure_store.filters.FragmentLookupFilter: apply(pose=<460 residues>)
protocols.indexed_structure_store.filters.FragmentLookupFilter: lookup returned results: 86 seconds: 0
protocols.indexed_structure_store.filters.FragmentLookupFilter: apply(pose=<460 residues>)
protocols.indexed_structure_store.filters.FragmentLookupFilter: lookup returned results: 86 seconds: 0
protocols.indexed_structure_store.filters.FragmentLookupFilter: apply(pose=<460 residues>)
protocols.indexed_structure_store.filters.FragmentLookupFilter: lookup returned results: 86 seconds: 0
protocols.indexed_structure_store.filters.FragmentLookupFilter: apply(pose=<460 residues>)
protocols.indexed_structure_store.filters.FragmentLookupFilter: lookup returned results: 86 seconds: 0
protocols.indexed_structure_store.filters.FragmentLookupFilter: apply(pose=<460 residues>)
protocols.indexed_structure_store.filters.FragmentLookupFilter: lookup returned results: 86 seconds: 0
protocols.indexed_structure_store.filters.FragmentLookupFilter: apply(pose=<460 residues>)
protocols.indexed_structure_store.filters.FragmentLookupFilter: lookup returned results: 86 seconds: 0
protocols.indexed_structure_store.filters.FragmentLookupFilter: apply(pose=<460 residues>)
protocols.indexed_structure_store.filters.FragmentLookupFilter: lookup returned results: 86 seconds: 0
protocols.indexed_structure_store.filters.FragmentLookupFilter: apply(pose=<460 residues>)
protocols.indexed_structure_store.filters.FragmentLookupFilter: lookup returned results: 86 seconds: 0
protocols.indexed_structure_store.filters.FragmentLookupFilter: apply(pose=<460 residues>)
protocols.indexed_structure_store.filters.FragmentLookupFilter: lookup returned results: 86 seconds: 0
protocols.indexed_structure_store.filters.FragmentLookupFilter: apply(pose=<460 residues>)
protocols.indexed_structure_store.filters.FragmentLookupFilter: lookup returned results: 86 seconds: 0
protocols.indexed_structure_store.filters.FragmentLookupFilter: apply(pose=<460 residues>)
protocols.indexed_structure_store.filters.FragmentLookupFilter: lookup returned results: 86 seconds: 0

UNHANDLED EXCEPTION
1: no symbol (no line)
2: no symbol (no line)
3: no symbol (no line)
4: no symbol (no line)
5: no symbol (no line)
6: no symbol (no line)
7: no symbol (no line)
8: no symbol (no line)
9: no symbol (no line)
10: no symbol (no line)
11: no symbol (no line)
12: no symbol (no line)
13: no symbol (no line)
14: no symbol (no line)

Latest error before total collapse of 814:

Popup shows:

Foldit.exe - No Disk
"There is no disk in the drive. Please insert a disk into drive D:."

Followed by:

Problem signature:
Problem Event Name: APPCRASH
Application Name: Foldit.exe
Application Version: 0.0.0.0
Application Timestamp: 4e761405
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.18229
Fault Module Timestamp: 51fb1116
Exception Code: e06d7363
Exception Offset: 0000c41f
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1043
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

And log.txt says:
protocols.indexed_structure_store.filters.FragmentLookupFilter: lookup returned results: 86 seconds: 0
protocols.indexed_structure_store.filters.FragmentLookupFilter: apply(pose=<460 residues>)
protocols.indexed_structure_store.filters.FragmentLookupFilter: lookup returned results: 86 seconds: 0
delta_score: 0
Playing sound: 4
Tool on_action_complete called
Tool on_action_complete called
core.pack.interaction_graph.interaction_graph_factory: Instantiating PDInteractionGraph
core.pack.pack_rotamers: built 2372 rotamers at 2 positions.
Sending SOPs:
Operation ID: SetGameLog Correlation ID: 64208
Operation ID: SetGameLog Correlation ID: 64209

Operation ID: ClientInformation Correlation ID: 64210
Autosaved puzzles/0000996338/0000108474/nomove/autosave.ir_solution.
Autosaved puzzles/0000996338/0000108474/nomove/autosave-best.ir_solution.
Autosaved puzzles/0000996338/0000108474/nomove/autosave-recentbest.ir_solution.
Autosaved puzzles/0000996338/0000108474/nomove/autosave-creditbest.ir_solution.
SOP Success Operation ID: SetGameLog Correlation ID: 64208
SOP Success Operation ID: SetGameLog Correlation ID: 64209

UNHANDLED EXCEPTION
1: RaiseException +88 bytes (no line)
2: library_main +30236773 bytes (no line)
3: library_main +30236700 bytes (no line)
4: library_main +10871339 bytes (no line)
5: library_main +18862367 bytes (no line)
6: library_main +23039198 bytes (no line)
7: library_main +20518841 bytes (no line)
8: library_main +19665196 bytes (no line)
9: library_main +19673222 bytes (no line)
10: library_main +18890574 bytes (no line)
11: library_main +18893357 bytes (no line)
12: library_main +18893857 bytes (no line)
13: library_main +6318745 bytes (no line)
14: library_main +4385438 bytes (no line)
15: library_main +4388582 bytes (no line)
16: BaseThreadInitThunk +18 bytes (no line)
17: RtlInitializeExceptionChain +99 bytes (no line)
18: RtlInitializeExceptionChain +54 bytes (no line)

This is a bug report.

a reinstall has fixed the problem, but models from puzzle 813 can't be opened with puzzle 816 even if they have been saved and shared with self

All scripts cause the client to crash, but only on puzzle 814. I can't play the puzzle.

It would be fair to cancel this puzzle, and to re-offer it once the bug(s) is/are cured.

Any update on this one? Puzzle is about to close and it's still unplayable for me outside of handfolding (Win 7 64 Main). I've seen the crash with any script I've run, also seen it while doing manual work and simply shaking or wiggling.

I did eventually get one design that doesn't crash the client, so perhaps it's related in some way to a specific sidechain combination. I'm letting it run without any mutating and it was able to stay up over night. Didn't have time for further comparison and don't have access to my logs at the moment.

Can you share solutions in a pre-crash state, with steps on what to run in order to make them crash?

We have been trying a number of scripts and other actions, and are having trouble reproducing the crashes.

Some other 814 log files error dumps and information on this now closed post: http://fold.it/portal/node/996325
Apparently it is not happening on Macs.

Posted this before, but wanted to make sure I posted here as well:

We unfortunately haven't had any luck reproducing the issue with 814 internally, but we are continuing to investigate nonetheless. You can help us out a lot by continuing to keep an eye out for anything similar going forward. You've done a bang up job so far, and we couldn't have gotten this far without your help!

The positive development to come out of this is that we do have a new crash reporting feature in development that should help us chug through bugs that are tricky to reproduce in-house.