Let me address your questions here
1. x64 has the benefit of using more than 4GB of ram. x86 binaries can only use a maximum of 4GB.
2. The facepalm is because you gave a silly idea to people, of using a 32bit binary in place of the 64bit binary.
3. You don't understand what bottlenecks are, its when hardware is stunting the faster performance of other hardware. It's like mixing RAM, mixing 1600 with 1800 ram will force the 1800 down to 1600 speeds. Same can happen with CPU > GPU and vice versa.
4. I never said defrag SSDs, I was generally speaking that people should do everything possible to keep their systems in top performance. Don't jump in and assume I meant something else.
As said I have no problems as do others in this thread with using the 64bit binary, the fact you are can be hardware conflict with the software or poor upkeep of your PC.
1) I know that, addressing length etc etc. Yet the game doesn't need over 4GB of RAM, which makes the whole idea of using a malfunctioning x64 bit .exe pointless in the first place.
2) It is not a silly idea if it works, go check out the steam community forums (and the rest of the internet) before dismissing stuff that works and calling such things "facepalms". Sure, its not an official fix, but hey, whatever works works.
3) I know what bottlenecks are. Experiencing stuttering does not directly indicate a bottleneck as a culprit. And FYI, that's why clock rate and direct memory access exist in the first place.
Now, if exchanging x64 with x32 fixes the problem, then one can assume that the problem is with the x64 execs and dlls (software) and not hardware as you are stating, until proven wrong; which as of yet hasn't been done.
The usual culprit of such issues is Vsync, yet doesn't seem to be the case here.
4) I was not referring to your post, which is why it wasn't quoting your post like this one is. Some people may not know about the defrag nono's, which is why I pre-empted and wrote that in the first place.
All of the above apart, using an x64 executable on a x64 system, which is beyond the recommended requirements should make the game faster and not worse, which explains the inference of a buggy x64 executable. Since x64 can handle a larger address than x86, it should be faster, in this case its the opposite.
Even if you do not have any problems with the x64 binary, that doesn't mean that others cannot experience them. And it also doesn't mean that it has to be a hardware issue.
Now, we can either keep this on, or we can agree to disagree.
Ah ok. I usually just call 1600mhz.
1. Nope, not if the game doesn't use it. I have never played a game that required more than 4GB of ram (for the actual game).
2. Not a silly idea as there is no difference in performance except for people who experience the buggy 64bit problem. The game doesn't use that much ram and there is no extra "addressing" or cross-talk or voodoo involved. Encoders, decoders, and some encryption software can benefit from 64bit but 3d graphics oriented software (like games) usually does not unless it needs more than 4GB of ram. No performance gain when using the 64bit over the 32bit.
3. Why would anyone mix different types of ram??? As long as your specs are within the recommended or better range and your hd is not an old fragmented piece of crap you should be fine.
The stuttering, rapid changes in FPS, SLIDESHOW behavior is indicative of some issues the games 64bit binary has with some hardware configurations - possibly some incompatibility with some older 64bit processors.
When everything else runs fine, other games including other 64bit games RUN FINE, then that is what is called a BUG!