See also RAH's forum post "Foldit keeps failing under Windows 10".
YGK posted an update to an old feedback with a similar issue. In YGK's case, as here, the traceback lists alListeneriv +2897 as the first entry. Reinstalling may have resolved that issue.
I haven't had any issues specific to Windows 10 after nearly a year, but plenty of regular crashes.
Some other random thoughts follow.
On current main, 20160502-30496ba116-win_x86, check that you have these directories:
cmp-binary-2d9e86ef893a241e1537090b282c38cd
cmp-database-4aa3799f5de6b1475e948fb77682d90f
cmp-resources-f3f5689675a05a73fb3d5d1f6e8950e6
These directories are pointed to by version-binary.txt, version-database.txt, and version-resources.txt.
I normally run multiple clients on a single machine, but each client runs in its own directory, so I have c:\foldit\foldit1 for one client, c:\foldit\foldit2 for the second, c:\foldit\foldit3 for the third, and so on. On Windows, you can simply copy and rename an existing Foldit installation folder to create a new one. (Don't expect the uninstaller to work if you do this, however.)
The only time a start a second client from a given folder is share a solution without interrupting a long-running recipe. This works because things like the current creditbest solution are saved as files with the extension .ir_solution.
I had bad experiences running multiple clients from a single directory back when I started, which is why I went with the multiple directory solution.
Foldit leaves a lot of .ir_solution and other files lying around. This one reason why periodically starting with a fresh install may be a good idea. I install to a new directory, then use to replace my existing directories. Be sure to save your options.txt and all.macro from the old setup, then copy them into the new clean install. (I also back up the old setup before cleaning house, just in case.) This type of cleaning means your old solutions (autosaves, quicksaves, creditbest, etc.) will no longer be available, so don't do it in the middle of playing a puzzle unless you've shared your work.
Some crashes may generate a debug.txt, and debug.txt may get uploaded automatically to Foldit central. Not all crashes generate a debug.txt, and I've never had any definite confirmation that debug.txt gets uploaded, but we can still hope.
Sometimes crashes may depend on settings. If you're using the selection interface, see if you still crash in the original interface. If you're using the advanced GUI, try turning it off for a bit. Switch to a basic coloring like "hydro" and a basic view like "cartoon" or "cartoon thin".
I'd also be suspicious of video drivers. Some manufacturers offer tools to check and update driver versions. I know there were some video driver issues when I upgraded to Win 10 last year, but they seemed to mostly sort themselves out.
One thing that's still an issue seems to be video mode. It seems like anything that changes the screen resolution may cause clients to crash or hang. On my Win 10 Pro, logging in as another user with clients running seems to cause this type of crash. I haven't got around to opening a feedback on it, however. Obviously most run-of-the-mill applications just keep going, although Windows does like to rearrange your desktop icons as part of the package.
